prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

Change-Id: I0d25f27a5e449578967915d9f570cc29246927d7
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...

Change the entity type for system

In the current pldm code, we are using a number 11521 for
representing a system and this value is not in the Spec
and is vendor defined(OEM).

Changing it to Logica

Change the entity type for system

In the current pldm code, we are using a number 11521 for
representing a system and this value is not in the Spec
and is vendor defined(OEM).

Changing it to Logical Chassis (32813), so the BMC tree
would start with logical chassis as a parent , and under
that we would have physical chassis.

Tested By :
1. Entity Association PDR
{
"nextRecordHandle": 73,
"responseCount": 26,
"recordHandle": 72,
"PDRHeaderVersion": 1,
"PDRType": "Entity Association PDR",
"recordChangeNumber": 0,
"dataLength": 16,
"containerID": 1,
"associationType": "Physical",
"containerEntityType": "[Logical] System chassis (main enclosure)",
"containerEntityInstanceNumber": 1,
"containerEntityContainerID": 0,
"containedEntityCount": 1,
"containedEntityType[1]": "[Physical] System chassis (main enclosure)",
"containedEntityInstanceNumber[1]": 1,
"containedEntityContainerID[1]": 1
}

2. FRU Record PDR
{
"nextRecordHandle": 2,
"responseCount": 20,
"recordHandle": 1,
"PDRHeaderVersion": 1,
"PDRType": "FRU Record Set PDR",
"recordChangeNumber": 0,
"dataLength": 10,
"PLDMTerminusHandle": 0,
"FRURecordSetIdentifier": 1,
"entityType": "[Logical] System chassis (main enclosure)",
"entityInstanceNumber": 1,
"containerID": 0
}

Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I0a2aa5a9e3da4ea860bb3fa43322e8889e666d2f

show more ...

pldmtool: Fix tool to show the oem entities

START & END are meant to be used as range to figure out if an
entity/state_set is OEM or not.They are not entity & state set
names.

This commit fixes abo

pldmtool: Fix tool to show the oem entities

START & END are meant to be used as range to figure out if an
entity/state_set is OEM or not.They are not entity & state set
names.

This commit fixes above mentioned issue & also removes TPM entity
from the common fru_master configuration as the entity type is in
OEM range as per DSP0249_1.1.0 specification.

Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: Iba4fadabf1ae4f94cee8f2f47632731de0bfd85f

show more ...

Add support for vendor specific FruDbusLookup

In the current state, a vendor could not define the FRU's
that he wants to send to the host.

This commit adds a fru_master.json tha

Add support for vendor specific FruDbusLookup

In the current state, a vendor could not define the FRU's
that he wants to send to the host.

This commit adds a fru_master.json that can be used while
building the master , and the json would be replaced with
fru_master.json from the oem/<vendor>/configurations
directory when compiling for oem's.

Tested By:

IBM machine test :
1. meson build -Doem-ibm=enabled -Dprefix=<>
2. ninja -C build && ninja install
3. in the prefix directory we should see the json file
from the oem/ibm/configurations folder

Non IBM machine test :
1. meson build -Doem-ibm=disabled -Dprefix=<>
2. ninja -C build && ninja install
3. in the prefix directory we should see the json file
from the pldm/configurations folder.

Runtime test:
1. on an IBM machine make sure the pldm builds the fru record
table.

Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: Id3c2746c51a1f99f2038b2af48137133e9d0b405

show more ...