| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Setting this within python is not required
(From meta-phosphor rev: b737ffb23aff232b2ce212ad54171afe7b216a71)
Change-Id: I3d799b5cd9e66c9bc1a4d145274bfa3c06bdf575
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
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>
|
|
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>
|
