generate-tar: Add machine name

The openbmc image manager expects "MachineName" in MANIFEST that matches
the BMC's OPENBMC_TARGET_MACHINE in /etc/os-release.
* If there is no MachineName in MANIFEST, it logs a warning for now;
* If they do not match, an error is reported and the version is deleted.

Add -m, --machine argument for generate-tar to make it support the
"MachineName".

Tested: Verify that when a correct machine name is given, the tarball is
        processed by image manager correctly;
        And if an invalid machine name is given, the tarball uploaded
        will get "Machine name doesn't match" error and is deleted.

Signed-off-by: Lei YU <mine260309@gmail.com>
Change-Id: I8fbb5060cb1be348c39e0688fe7306426cc4ed77
1 file changed
tree: 635ec199bcdcdbe3111ec69683d28d83c958e1e3
  1. m4/
  2. static/
  3. test/
  4. ubi/
  5. vpnor/
  6. .clang-format
  7. .gitignore
  8. activation.cpp
  9. activation.hpp
  10. bootstrap.sh
  11. configure.ac
  12. generate-tar
  13. generate-ubi
  14. image_verify.cpp
  15. image_verify.hpp
  16. item_updater.cpp
  17. item_updater.hpp
  18. item_updater_main.cpp
  19. LICENSE
  20. MAINTAINERS
  21. Makefile.am
  22. msl_verify.cpp
  23. msl_verify.hpp
  24. msl_verify_main.cpp
  25. op-pnor-msl.service
  26. openpower-pnor-update@.service
  27. org.open_power.Software.Host.Updater.service
  28. README.md
  29. utils.cpp
  30. utils.hpp
  31. version.cpp
  32. 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`.