meta-phosphor: ipmi: improve entity YAML selection

The existing scheme for selecting an entity configuration YAML for
building ipmid consists of a virtual (phosphor-ipmi-entity-config) with
the preferred provider  set to a default recipe
(phosphor-ipmi-entity-inventory-native) in the Phosphor distro
configuration.

Instead, provide a reasonable default directly in the ipmid metadata.
This is a small step towards enabling ipmid to build without any distro
configuration and should lower the effort required (slightly) to
comprehend where the the entity YAML file is coming from.

There aren't any known clients overriding the entity YAML in the first
place, but a client could still override with an ipmid bbappend and
setting EXTRA_OECONF appropriately.

Change-Id: I652c1da26473822630440303786dc17b38ea73e7
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
4 files changed
tree: fc605234b901c146f88a01fa95cfbd5ca50f6fe5
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-graphics/
  10. recipes-phosphor/
  11. recipes-protocols/
  12. recipes-support/
  13. recipes-textproc/
  14. COPYING.apache-2.0
  15. COPYING.MIT
  16. LICENSE
  17. MAINTAINERS
  18. README.md
  19. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.