| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
There are new Yocto warnings when 'native' is not inherited last.
For example:
WARNING:
.../meta-intel-openbmc/meta-common/recipes-phosphor/leds/intel-led-manager-config-native.bb:
QA Issue: intel-led-manager-config-native: native/nativesdk class is not
inherited last, this can result in unexpected behaviour. Classes
inherited after native/nativesdk: obmc-phosphor-utils.bbclass
[native-last]
This moves 'native' to be inherited last to resolve the warnings.
Change-Id: Ia408acc8ee9cda5130d6b189074b0bfc97ecd7bd
Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com>
|
|
The raw PECI option is removed from bmcweb, so remove it from
here.
Change-Id: I8ab02cff96469a156e4ec6aa2ba6943b0fb9216f
Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com>
|
|
meta-intel conflicts with the upstream yocto meta layer of the same
name. This commit renames meta-intel to meta-intel-openbmc and updates
all the relevant bblayers files with the new name.
This is to pave the way for allowing the yocto meta-intel in the tree,
which would allow the use of generic-x86 machine type, which would allow
building and running tests natively.
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: Ia19a7a4a10245c1c2f85f6da216997cb6a836daa
|
