Make the name of the signature verify feature unique

The verify_signature feature name is the same as the one used
in the phosphor-software-manager repo which manages the BMC
firmware updates. Change the name to make it different to
be able to control enabling the feature individually via recipes,
since enabling it on the phosphor recipe enables it for the
pnor code as well (due to the recipe dependency on
virtual-obmc-image-manager).

Change-Id: I73e446dd6d5f0995132bc60403e08d16d07703bd
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
1 file changed
tree: bf388d8e1708788df9c579b8ba942fd7444a2cba
  1. m4/
  2. org/
  3. test/
  4. .clang-format
  5. .gitignore
  6. activation.cpp
  7. activation.hpp
  8. bootstrap.sh
  9. configure.ac
  10. generate-squashfs
  11. generate-ubi
  12. image_verify.cpp
  13. image_verify.hpp
  14. item_updater.cpp
  15. item_updater.hpp
  16. item_updater_main.cpp
  17. LICENSE
  18. Makefile.am
  19. README.md
  20. serialize.cpp
  21. serialize.hpp
  22. version.cpp
  23. version.hpp
  24. watch.cpp
  25. watch.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`.