Add OPENBMC_TARGET_MACHINE to /etc/os-release

This adds a new OS identification parameter (OPENBMC_TARGET_MACHINE) to
the /etc/os-release file in the generated OpenBMC image to indicate the
kind of device the OpenBMC image is targeted to control.
This is needed to be able to track the image back to its source code: the
distro and version indicate the exact source code that was used, and the
target machine says which Bitbake layer configuration within that source
was used.

Note the target machine name is typically set in the
openbmc/meta-*/meta-MACHINE/conf/local.conf.sample file.
(This is where TEMPLATECONF points to.)

The "uname" command options -m (machine) and -i (hardware platform) will
continue to refer to the BMC and not its target machine.

Tested: On the build system, `cat $IMAGE_ROOTFS/etc/os-release` shows
        the correct value.

Change-Id: I4b38ee882c8a7b04ade5b96d3e3a91d63309fcff
Signed-off-by: Joseph Reynolds <jrey@us.ibm.com>
1 file changed
tree: 3a83822ac6749f1e4598c3b203dd20a714be7ec6
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-phosphor/
  10. recipes-protocols/
  11. recipes-support/
  12. recipes-textproc/
  13. COPYING.apache-2.0
  14. COPYING.MIT
  15. LICENSE
  16. MAINTAINERS
  17. README.md
  18. 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.