Document host/chassis/bmc mapping (current and future)

I believe this is the only possible way we can realistically
provide forwards and backwards API compatibility.

We have existing API users, and we can't go and rewrite the world,
so we need to extend the API in a way that enables them to continue
working.

Change-Id: I741485adf98126919b2a521d8bfbd235b13750ae
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
1 file changed
tree: b4557441ffe0e8e4da19adb04ca5b52e86abb448
  1. xyz/
  2. .gitignore
  3. bootstrap.sh
  4. configure.ac
  5. generate_makefile.sh
  6. generate_yaml_makefile.sh
  7. LICENSE
  8. Makefile.am
  9. Makefile.interfaces.in
  10. Makefile.yaml.in
  11. phosphor-dbus-interfaces.pc.in
  12. README.md
README.md

phosphor-dbus-interfaces

YAML descriptors of standard dbus interfaces