mmc: Move process host firmware to own service

The process-host-firmware subcommand waits for the Entity Manager
interface to appear in D-Bus. It's currently run from the mmc-init
script. But if a system does not support Entity Manager, then the init
service never exits, blocking its dependencies like PLDM from starting.

Move the process-host-firmware to its own service file so that if needs
to wait forever, it doesn't interfere with other processes. Need to
start it after the mmc-init so that all the directories are setup before
the symlinks are created.

Tested: Verified on tacoma that the service remains running and PLDM
starts successfully. Verified on rainier that the symlinks are created.

Change-Id: Ia746362e5ff688b972e9b92e9d78f3f5b3623a99
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
3 files changed
tree: a334ba5962ddfe5d1b2c20f8669235f22b0aeecd
  1. dbus/
  2. mmc/
  3. static/
  4. test/
  5. ubi/
  6. vpnor/
  7. .clang-format
  8. .gitignore
  9. .shellcheck
  10. activation.cpp
  11. activation.hpp
  12. functions.cpp
  13. functions.hpp
  14. generate-tar
  15. generate-ubi
  16. image_verify.cpp
  17. image_verify.hpp
  18. item_updater.cpp
  19. item_updater.hpp
  20. item_updater_main.cpp
  21. LICENSE
  22. MAINTAINERS
  23. meson.build
  24. meson_options.txt
  25. msl_verify.cpp
  26. msl_verify.hpp
  27. msl_verify_main.cpp
  28. op-pnor-msl.service
  29. openpower-pnor-update@.service
  30. org.open_power.Software.Host.Updater.service
  31. README.md
  32. utils.cpp
  33. utils.hpp
  34. version.cpp
  35. 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. meson build
  2. ninja -C build

To clean the repository run rm -r build.