Get Device ID: support new version format

We plan to change our version string to the format
"<platform>-YEAR.WEEK.BUILD-g<hash>-<hash>".

This supports the new format by allowing for a dot instead of a dash
before the BUILD number and by using only the last two characters of the
major version string.

Tested:
Confirmed that "ipmitool mc info" and "ipmitool raw 6 1" both return the
correct version information from the old and new version strings.

Change-Id: I7e9cdffd37c0033062377a0b575d8d4635fb5625
Signed-off-by: Jason M. Bills <jason.m.bills@intel.com>
1 file changed
tree: c6afa94e98e063472f5bf5c5d713bc92fe5eb36b
  1. cmake/
  2. docs/
  3. include/
  4. non-yocto/
  5. src/
  6. subprojects/
  7. tests/
  8. .clang-format
  9. .gitignore
  10. cmake-format.json
  11. CMakeLists.txt
  12. CMakeLists.txt.in
  13. generate-allowlist.py
  14. ipmi-allowlist.conf
  15. LICENSE
  16. meson.build
  17. meson.options
  18. OWNERS
  19. README.md
README.md

Intel IPMI OEM support library

This component is intended to provide Intel-specific IPMI[3] command handlers for OpenBMC. These handlers are intended to integrate BMC with servers based on Intel architecture.

Overview

intel-ipmi-oem serves as an extension[1] to OpenBMC IPMI daemon[2]. It is compiled as a shared library and intended to both:

  • override existing implementation of standard IPMI commands to comply with Intel-specific solutions,
  • provide implementation for non-standard OEM extensions.

Capabilities

Related features provided by the library are grouped in separate source files. Main extensions to vanilla OpenBMC IPMI stack are the following:

  • Acquiring SMBIOS data over IPMI
  • Commands for better integration with Intel hardware
  • Firmware update extensions
  • Extended parsing of IPMI Platform Events[4]

References

  1. OpenBMC IPMI Architecture
  2. Phosphor IPMI Host
  3. IPMI Specification v2.0
  4. Intel Platform Events parsing