Move to new association interface

A new association interface is defined in phosphor-dbus-interfaces
It would be nice to move the local version of the interface
to the new one.

The behavior of how association work is described here:
https://github.com/openbmc/docs/blob/master/object-mapper.md#associations

Partially resolves openbmc/openbmc#3584

Tested: See the org.openbmc.Associations interface has been replaced by the xyz
one in /xyz/openbmc_project/software/version_id object and only when the
version number is less than PNOR_MSL, "PNOR Minimum Ship Level NOT met"
is reported.

Signed-off-by: John Wang <wangzqbj@inspur.com>
Change-Id: If4afeb69a9bd8bc494b77826f2ec2854a71f56f5
7 files changed
tree: 6c271d05d5f9226346f65cdb40580bb55139d394
  1. m4/
  2. static/
  3. test/
  4. ubi/
  5. .clang-format
  6. .gitignore
  7. activation.cpp
  8. activation.hpp
  9. bootstrap.sh
  10. configure.ac
  11. generate-tar
  12. generate-ubi
  13. image_verify.cpp
  14. image_verify.hpp
  15. item_updater.cpp
  16. item_updater.hpp
  17. item_updater_main.cpp
  18. LICENSE
  19. MAINTAINERS
  20. Makefile.am
  21. msl_verify.cpp
  22. msl_verify.hpp
  23. msl_verify_main.cpp
  24. op-pnor-msl.service
  25. openpower-pnor-update@.service
  26. org.open_power.Software.Host.Updater.service
  27. README.md
  28. utils.cpp
  29. utils.hpp
  30. version.cpp
  31. version.hpp
README.md

openpower-pnor-code-mgmt

OpenPower PNOR (Processor NOR) Code Management provides a set of host software management applications for OpenPower systems. The host firmware is stored on the PNOR chip. More information can be found at Software Architecture or Host Code Update

To Build

To build this package, do the following steps:

    1. ./bootstrap.sh
    2. ./configure ${CONFIGURE_FLAGS}
    3. make

To clean the repository run `./bootstrap.sh clean`.