mboxd: mbox device is optional

The poorly-named mboxd daemon can now operate regardless of the
presence of /dev/aspeed-mbox. Particularly, OpenPOWER OpenBMC
configurations no-longer use this interface for the HIOMAP protocol
(it is now run over IPMI instead).

Remove hard dependencies on the presence of /dev/aspeed-mbox.

Change-Id: Ic3b73964d834472ebe6883aae8661de15dea7970
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
3 files changed
tree: 5b37196e71a738dcc0efa37614d425c0296131a5
  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.