summaryrefslogtreecommitdiff
path: root/meta-phosphor/nuvoton-layer
AgeCommit message (Collapse)AuthorFilesLines
2021-08-17meta-phosphor: Add option to disable u-boot shellVivekanand Veeracholan1-0/+1
For security, u-boot shell needs to be disabled. Setting the CONFIG_BOOTDELAY to -2 will disable the prompt for entering into shell. -1 will skip executing the commands. >=0 will prompt to enter shell. -2 will skip the prompt. https://github.com/u-boot/u-boot/blob/51aef405550e603ff702c034f0e2cd0f15bdf2bb/common/autoboot.c#L479 Making it configurable through DISTRO_FEATURES. Add "disable-u-boot-shell" to DISTRO_FEATURES for this feature. Signed-off-by: Vivekanand Veeracholan <vveerach@google.com> Change-Id: I1b1e1a6c2552335b13fb3f1a9561d08f3a0e8f94
2021-08-11meta-phosphor: prep for new override syntaxPatrick Williams3-5/+5
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I588025b614416c43aa2d053765ab53bacf890cb5
2021-03-01Remove phsophor-gpio-keys as a standalone featureJoel Stanley3-12/+0
The feature was implemented as an append to the kernel (BSP) layers in meta-phsophor. This created a three way dance between machine layers, BSP and meta-phosphor, when it should have been the kernel layer providing this feature and machines could then opt in. Fixing this means we could remove the KERNEL_DANGLING_FEATURES_WARN_ONLY workaround. As the feature is simply turning on a pair of kernel options without any other impact, we can implement it by adding the options to our defconfigs. In fact, aspeed and hpe kernel configurations enable the two kernel options: $ git grep CONFIG_KEYBOARD_GPIO=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_KEYBOARD_GPIO=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_KEYBOARD_GPIO=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_KEYBOARD_GPIO=y meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_KEYBOARD_GPIO=y $ git grep CONFIG_INPUT_EVDEV meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_INPUT_EVDEV=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_INPUT_EVDEV=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_INPUT_EVDEV=y meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_INPUT_EVDEV=y Other machines that wish to enable this feature should ensure it is added to their BSP's defconfig, or add it to their machine specific defconfig. Change-Id: I0726836319022f96c1d13d4a0cbd73708047302c Signed-off-by: Joel Stanley <joel@jms.id.au>
2020-09-09simplify setting of KERNEL_DANGLING_FEATURES_WARN_ONLYAndrew Geissler1-7/+3
Setting this within python is not required (From meta-phosphor rev: b737ffb23aff232b2ce212ad54171afe7b216a71) Change-Id: I3d799b5cd9e66c9bc1a4d145274bfa3c06bdf575 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-09-01nuvoton: enable KERNEL_DANGLING_FEATURES_WARN_ONLYAndrew Geissler1-0/+8
Uptream yocto recently added some new code which enforces kernel feature validation. The commit which did this is: https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=095175595d9f28d5a0eb7ea520c9af0100bb8dfd This caused OpenBMC builds to start failing with the following: | ERROR: Feature 'phosphor-gpio-keys' not found, this will cause configuration failures. | ERROR: Check the SRC_URI for meta-data repositories or directories that may be missing | ERROR: Set KERNEL_DANGLING_FEATURES_WARN_ONLY to ignore this issue OpenBMC does not utilize this aspect of the kernel-yocto.bbclass so make it a warning only. Tested: Verified that the resultant build still had the expected CONFIG options set in the linux-nuvoton .config file See openbmc/openbmc#3690 (From meta-phosphor rev: 75a6424eec93729fd40154413b1a350b9f10fe8b) Change-Id: I12bf3857601f186300d3b1c56c490be6e6582dda Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-07-09meta-phosphor: nuvoton-layer: postd: only set SNOOP_DEVICE for npcm7xxBenjamin Fair1-3/+1
This allows non-Nuvoton devices to build successfully, even if the Nuvoton layer is enabled. (From meta-phosphor rev: fa488de8cffc79be45cc069ca0b483abf9dfb04f) Change-Id: I1dd1833d4f6ea56c38ce021160cd6cc86f690b5f Signed-off-by: Benjamin Fair <benjaminfair@google.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-06-24nuvoton-layer: recipes-connectivity: jsnbd: Support jsnbd for virtual mediaMedad CChien2-0/+77
(From meta-phosphor rev: 204c9307ff7ec907aeee05d34f46e0f6b5d84bf9) Signed-off-by: Medad CChien <ctcchien@nuvoton.com> Change-Id: Ie397415954d965a9457ccecb0dc8c8d164c7991d Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2019-10-03meta-phosphor: nuvoton-layer: postd: add support for NPCM7xx BMCTim Lee1-0/+3
Enable BIOS POST CODE functionality for NPCM7xx BMC in phosphor-host-postd. We need to modify SNOOP_DEVICE = "npcm7xx-lpc-bpc0", due to default SNOOP_DEVICE is using aspeed BMC. (From meta-phosphor rev: ae30116e34c5ee4a1a10ff877192a0a633d84e9f) Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: I06e05d62a9c1b810620d3292b13e5a244851b061 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-09-25nuvoton: Apply image overrides to all image typesWilliam A. Kennington III1-70/+0
Right now, nuvoton overrides needed for generating and applying the bootblock are not applied to images other than obmc-phosphor-image. This means that core-image-minimal is unbootable on nuvoton platforms. This change makes the nuvoton overrides apply globally to all images. (From meta-phosphor rev: 9819cb9533f430797d47dadff558cf4462670976) Change-Id: If4bef5f8106278fa6ebeb2198bc43fdd2b70a641 Signed-off-by: William A. Kennington III <wak@google.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-11meta-phosphor: nuvoton-layer: generate full flash image.Oshri Alkoby (NTIL)1-0/+70
Nuvoton's full flash image includes also a bootloader called Bootblock, and headers for it and for the u-boot. Generating headers and merging the Bootblock and the u-boot are being done by Nuvoton's binary generator tool (Bingo), which uses external paramteres from XML files for that. (From meta-phosphor rev: 13cc41f61207bcf06a9daab552c66b05120aa379) Signed-off-by: Oshri Alkoby (NTIL) <oshri.alkoby@nuvoton.com> Change-Id: Ic95719e83d5a4c998b20d3ece70893ea34106a06 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-07-19meta-phosphor: nuvoton-layer: add gpio-keys kernel featureBenjamin Fair3-0/+13
The phosphor-base.inc distro file enables the phosphor-gpio-keys KERNEL_FEATURE. Add support for this feature to the linux-nuvoton recipe via a bbappend in meta-phosphor's nuvoton layer. Tested: Built and ran on NPCM750 EVB Change-Id: Id957c6209ebb841fce2cdad1cc0790e0d58da60c Signed-off-by: Benjamin Fair <benjaminfair@google.com>
generated by cgit v1.2.3 (git 2.39.0) at 2024-06-03 14:00:00 +0300