| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
This was a P9 DD1 workaround. These systems are no longer supported and
are not found in the wild, so the workaround has been retired.
All of the p9 systems in the tree exclude the package so this change
should be a noop.
(From meta-ibm rev: 38c5c9539fb3f01fc2b96d483701938bffdf48a0)
Change-Id: I1c7786526dee4d9bb0d5db916890c1cbe3d51577
Signed-off-by: Joel Stanley <joel@jms.id.au>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
A prior patch added a new recipe romulus-yaml-config to provide all the
YAML configuration for Romulus systems. This patch switches the layer
to that recipe by setting EXTRA_OECONF and DEPENDS as appropriate in the
required bbappends.
With this switch, a number of recipes and their provided YAML are now
dead metadata, so remove those.
(From meta-ibm rev: 66ca8269544784908b0abf78715620adf04d69cc)
Change-Id: I02305ec4c431122ae6ab440c5dcb3def509b7ff9
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The ipmi configs were using .bbappends to override the default ones.
There was a change in OpenBMC about overriding variable assignments,
that causes the .bbappends not working anymore due to they are native.
This commit fixes the issue, by adding romulus specific configs to
replace the default ones.
Tested: Verify the ipmi sensor, fru are correct on Romulus.
(From meta-ibm rev: e020d0d8973cb4fa36d382bc9af5c056e8d8e913)
Change-Id: If804ced6d53c8c4433351b982ebcf079cd014f56
Signed-off-by: Lei YU <mine260309@gmail.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
meta-phosphor dropped support for native class config recipes and uses
target class config recipes by default. Drop the reference to
PHOSPHOR_FAN_CONFIG_USE_NATIVE_SYSROOT as it is no longer used in
meta-phosphor.
(From meta-ibm rev: 0bc0301510b3371510a86fa684b72ea4d4100cf1)
Change-Id: I6b59b1429ead70c1e4ac85a1c9d66b3e04197dd5
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
meta-phosphor recently enabled target class config recipes. Those are
preferable to native class config recipes because native recipes cannot
be overridden based on MACHINE, so switch to target class config
recipes.
Switching to target class recipes consists of temporarily setting
PHOSPHOR_FAN_CONFIG_USE_NATIVE_SYSROOT to 0, overriding the phosphor
distro default of 1. After all OpenBMC BSP layers have moved to target
class config recipes PHOSPHOR_FAN_CONFIG_USE_NATIVE_SYSROOT can be
removed from meta-phosphor and any BSP layers.
Any references to -native recipes are replaced with their target class
counterparts.
Any -native bbappends are re-worked to apply to their target class
counterparts.
Finally, use BPN instead of PN when setting FILESEXTRAPATHS, to avoid
unfortunate directory hierarchies if these bbappends are copy/pasted and
then used to bbappend a native recipe. Since this patch moves to target
class recipes, this is a noop; however, this avoids unfortunate
directory hierarchies with native bbappends such as:
meta-base/recipes-foo/bar/baz-native.bb
meta-base/recipes-foo/bar/baz/a-file
meta-append/recipes-foo/bar/baz-native.bbappend
meta-append/recipes-foo/bar/baz-native/b-file
Using "${THISDIR}/${BPN}:" enables a more sensible hierarchy:
meta-base/recipes-foo/bar/baz-native.bb
meta-base/recipes-foo/bar/baz/a-file
meta-append/recipes-foo/bar/baz-native.bbappend
meta-append/recipes-foo/bar/baz/b-file
This behavior occurs because By default FILESPATH is set in base.bbclass
(in OE-Core) to look for files in ${BP}, ${BPN} and files (and a number
of subdirectories of those based on ${FILESOVERRIDES}).
(From meta-ibm rev: 589ee00a5ec7bc97c7d5c079cf66b3dbd3ac2b4f)
Change-Id: I1a593373f1b4bc82c554a9330cdd75f04f21d1d8
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
openpower-occ-control requires a sensor header file generated from
occ_sensor.yaml. By default it uses an example yaml, which does not fit
for Romulus.
Add romulus-occ-control-config-native.bb to use its own
occ_sensor.yaml, so that the package uses the correct config.
Tested: Verify the build uses the correct config generated from
Romulus's occ_sensor.yaml.
(From meta-ibm rev: 54abf3c0be5618333cb37faebc55af48aa2a872b)
Change-Id: Iaa3adf0d20e5b6d080866dd1b19fa3ee7f4d7369
Signed-off-by: Lei YU <mine260309@gmail.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
ibm.inc simply includes openpower.inc. That, and meta-ibm is a distro
policy layer and doesn't enable any specific hardware.
Update machine configurations to include openpower.inc directly. Add a
conf/distro/include/ibm.inc to meta-ibm at a later time when meta-ibm
has distro policy to apply.
(From meta-ibm rev: 3d1be91f99c646b350c02bfe1004a019cd436c13)
Change-Id: I4bf1e9badba105f4ed10c478f7d5473e3f169791
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Set the license fields for the machine-readable-workbook.
(From meta-ibm rev: 7fc06531434db3ff03b148f7a8bd1925a094ec94)
Change-Id: I0d494889f62de9804f61b8a97b118482bbe2868b
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The new subtree model brings the subtrees up from the openbmc-machines
layer.
Change-Id: I58a03ae1be374bc79ae1438e65e888375d12d0c0
Signed-off-by: Dave Cobbley <david.j.cobbley@linux.intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
