| /openbmc/phosphor-logging/extensions/openpower-pels/registry/schema/ |
| H A D | registry_example.json | diff 2edce4e2b9059d37f50f28c91d4bc5a4cd760e21 Wed Jan 17 11:13:51 CST 2024 Matt Spinler <spinler@us.ibm.com> PEL: Use raw procedure names in PEL msg reg
Start using the raw maintenance procedure names in the PEL message
registry, such as BMC0001, instead of the enum values, such as
'bmc_firmware'. This way, the script that generates documentation can
list the procedure in the section for that PEL. This was requested by
the support team.
Note that there is still one user of the enums - the checkstop analysis
code uses them when it creates callouts by passing in them via JSON user
data files.
There are pointers added to the README and schema to find the available
procedures and their descriptions.
Tested:
- The unit tests still work which verify the callout contents when PEL
callouts are created via the message registry.
- Also manually verified PEL procedure callouts look correct when
created from the message registry.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I3e8416956120d4dae1ff40592fd0df4f0285d072
|
| H A D | schema.json | diff 2edce4e2b9059d37f50f28c91d4bc5a4cd760e21 Wed Jan 17 11:13:51 CST 2024 Matt Spinler <spinler@us.ibm.com> PEL: Use raw procedure names in PEL msg reg
Start using the raw maintenance procedure names in the PEL message
registry, such as BMC0001, instead of the enum values, such as
'bmc_firmware'. This way, the script that generates documentation can
list the procedure in the section for that PEL. This was requested by
the support team.
Note that there is still one user of the enums - the checkstop analysis
code uses them when it creates callouts by passing in them via JSON user
data files.
There are pointers added to the README and schema to find the available
procedures and their descriptions.
Tested:
- The unit tests still work which verify the callout contents when PEL
callouts are created via the message registry.
- Also manually verified PEL procedure callouts look correct when
created from the message registry.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I3e8416956120d4dae1ff40592fd0df4f0285d072
|
| /openbmc/phosphor-logging/extensions/openpower-pels/registry/ |
| H A D | README.md | diff 2edce4e2b9059d37f50f28c91d4bc5a4cd760e21 Wed Jan 17 11:13:51 CST 2024 Matt Spinler <spinler@us.ibm.com> PEL: Use raw procedure names in PEL msg reg
Start using the raw maintenance procedure names in the PEL message
registry, such as BMC0001, instead of the enum values, such as
'bmc_firmware'. This way, the script that generates documentation can
list the procedure in the section for that PEL. This was requested by
the support team.
Note that there is still one user of the enums - the checkstop analysis
code uses them when it creates callouts by passing in them via JSON user
data files.
There are pointers added to the README and schema to find the available
procedures and their descriptions.
Tested:
- The unit tests still work which verify the callout contents when PEL
callouts are created via the message registry.
- Also manually verified PEL procedure callouts look correct when
created from the message registry.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I3e8416956120d4dae1ff40592fd0df4f0285d072
|
| H A D | message_registry.json | diff 2edce4e2b9059d37f50f28c91d4bc5a4cd760e21 Wed Jan 17 11:13:51 CST 2024 Matt Spinler <spinler@us.ibm.com> PEL: Use raw procedure names in PEL msg reg
Start using the raw maintenance procedure names in the PEL message
registry, such as BMC0001, instead of the enum values, such as
'bmc_firmware'. This way, the script that generates documentation can
list the procedure in the section for that PEL. This was requested by
the support team.
Note that there is still one user of the enums - the checkstop analysis
code uses them when it creates callouts by passing in them via JSON user
data files.
There are pointers added to the README and schema to find the available
procedures and their descriptions.
Tested:
- The unit tests still work which verify the callout contents when PEL
callouts are created via the message registry.
- Also manually verified PEL procedure callouts look correct when
created from the message registry.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I3e8416956120d4dae1ff40592fd0df4f0285d072
|
| /openbmc/phosphor-logging/test/openpower-pels/ |
| H A D | registry_test.cpp | diff 2edce4e2b9059d37f50f28c91d4bc5a4cd760e21 Wed Jan 17 11:13:51 CST 2024 Matt Spinler <spinler@us.ibm.com> PEL: Use raw procedure names in PEL msg reg
Start using the raw maintenance procedure names in the PEL message
registry, such as BMC0001, instead of the enum values, such as
'bmc_firmware'. This way, the script that generates documentation can
list the procedure in the section for that PEL. This was requested by
the support team.
Note that there is still one user of the enums - the checkstop analysis
code uses them when it creates callouts by passing in them via JSON user
data files.
There are pointers added to the README and schema to find the available
procedures and their descriptions.
Tested:
- The unit tests still work which verify the callout contents when PEL
callouts are created via the message registry.
- Also manually verified PEL procedure callouts look correct when
created from the message registry.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I3e8416956120d4dae1ff40592fd0df4f0285d072
|
| H A D | src_test.cpp | diff 2edce4e2b9059d37f50f28c91d4bc5a4cd760e21 Wed Jan 17 11:13:51 CST 2024 Matt Spinler <spinler@us.ibm.com> PEL: Use raw procedure names in PEL msg reg
Start using the raw maintenance procedure names in the PEL message
registry, such as BMC0001, instead of the enum values, such as
'bmc_firmware'. This way, the script that generates documentation can
list the procedure in the section for that PEL. This was requested by
the support team.
Note that there is still one user of the enums - the checkstop analysis
code uses them when it creates callouts by passing in them via JSON user
data files.
There are pointers added to the README and schema to find the available
procedures and their descriptions.
Tested:
- The unit tests still work which verify the callout contents when PEL
callouts are created via the message registry.
- Also manually verified PEL procedure callouts look correct when
created from the message registry.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I3e8416956120d4dae1ff40592fd0df4f0285d072
|
| H A D | pel_manager_test.cpp | diff 2edce4e2b9059d37f50f28c91d4bc5a4cd760e21 Wed Jan 17 11:13:51 CST 2024 Matt Spinler <spinler@us.ibm.com> PEL: Use raw procedure names in PEL msg reg
Start using the raw maintenance procedure names in the PEL message
registry, such as BMC0001, instead of the enum values, such as
'bmc_firmware'. This way, the script that generates documentation can
list the procedure in the section for that PEL. This was requested by
the support team.
Note that there is still one user of the enums - the checkstop analysis
code uses them when it creates callouts by passing in them via JSON user
data files.
There are pointers added to the README and schema to find the available
procedures and their descriptions.
Tested:
- The unit tests still work which verify the callout contents when PEL
callouts are created via the message registry.
- Also manually verified PEL procedure callouts look correct when
created from the message registry.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I3e8416956120d4dae1ff40592fd0df4f0285d072
|
| /openbmc/phosphor-logging/extensions/openpower-pels/ |
| H A D | src.cpp | diff 2edce4e2b9059d37f50f28c91d4bc5a4cd760e21 Wed Jan 17 11:13:51 CST 2024 Matt Spinler <spinler@us.ibm.com> PEL: Use raw procedure names in PEL msg reg
Start using the raw maintenance procedure names in the PEL message
registry, such as BMC0001, instead of the enum values, such as
'bmc_firmware'. This way, the script that generates documentation can
list the procedure in the section for that PEL. This was requested by
the support team.
Note that there is still one user of the enums - the checkstop analysis
code uses them when it creates callouts by passing in them via JSON user
data files.
There are pointers added to the README and schema to find the available
procedures and their descriptions.
Tested:
- The unit tests still work which verify the callout contents when PEL
callouts are created via the message registry.
- Also manually verified PEL procedure callouts look correct when
created from the message registry.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I3e8416956120d4dae1ff40592fd0df4f0285d072
|