Make phosphor-ipmi-kcs parameterized by device

The end goal is to run one ipmi bridge per interface, so that stopping
that bridge will effectively shut down ipmi on that interface.

By default, this enables KCS on /dev/ipmi-kcs3. If more than one KCS
interface is desired, they can be added in a bbbappend as follows:

phosphor-ipmi-kcs_%.bbappend:

ALT_KCS_DEV = "ipmi-kcs4"
SYSTEMD_SERVICE_${PN} += " \
    ${PN}@${ALT_KCS_DEV}.service \
    "

Change-Id: I547fb2d7d572a03c0fb3a73375085ba927157317
Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com>
2 files changed
tree: 114cb20b3549b319745f3c634d6419108644d630
  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.