| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Change-Id: I9116ed7260e369136acb39eec15075db2d4dbeba
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
IBMBASE is only used for pointing at licenses...point at the
licenses in oe-core in meta/files/common-licenses instead. to match the
defacto convention used in other oe layers like meta-openembedded.
(From meta-ibm rev: cbbb0e5b4e44d831fce5daafd13272d401440f40)
Change-Id: Ib214f92b2c384e3eb2a1f53ecf4b21034438d001
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
YAML configuration files exist scattered throughout the OpenBMC tree and
how they are used is controlled with layers dependencies of virtuals and
preferred providers.
Most of the time the above scheme is very difficult to comprehend. This
patch continues a re-thinking of that approach towards a more
centralized scheme.
Specifically this patch implements a single YAML config recipe for the
Palmetto systems. The logic contained in the recipe was pulled from all
over the OpenBMC tree - the ability to comprehend how the different YAML
files are generated and consumed should be greatly eased.
One notable detail - unlike the upstream recipes, palmetto-yaml-config
is a target recipe and as such enables MACHINE based overrides.
YAML files were copied from different locations in the tree, and run
through a styling application (pyyaml dump(load(yaml))):
phosphor-ipmi-fru-properties-native:extra-properties.yaml ->
palmetto-yaml-config:palmetto-ipmi-fru-properties.yaml
phosphor-ipmi-sensor-inventory-native:config.yaml ->
palmetto-yaml-config:palmetto-ipmi-sensors.yaml
phosphor-ipmi-inventory-map-native:config.yaml ->
palmetto-yaml-config:palmetto-ipmi-fru.yaml
(From meta-ibm rev: 70eb689af4a1b27d5cdcca1acdff8d27329c6808)
Change-Id: I0f26e60db3caf66cbb2ec6d2ad0a053617eee50e
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
