mboxd: Depend on xyz.openbmc_project.Control.Host

This is one of the bus names claimed by ipmid, and according to
bea22141ca95 ("Ensure ipmid doesn't start until on dbus") it's the last
to be claimed. Depend on this to ensure our required IPMI services are
available. I've observed a reasonably reliable difference in behaviour
between depending on the canonical service (phosphor-ipmi-host.service)
vs the alias (xyz.openbmc_project.Control.Host.service) in that
setAttention()s from mboxd state changes were propagated as expected in
the latter case but not in the former.

Change-Id: I77ac1dfb2ef05a12db91af295b32c06b1628bc3d
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
1 file changed
tree: 242a0ff1303dda0f90336c353cf7d7fc98201a02
  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.