tree 79e0931fc4640a38c7fc43528ab4443cbf215f88
parent 4de58763759a84f257b342ad3fd780790da83fad
author cchoux <cosmo.chou@quantatw.com> 1694536536 +0800
committer cchoux <cosmo.chou@quantatw.com> 1695798392 +0800

support specifying MB FRU eeprom path

The MB FRUID should be exposed with ID 0 for BIOS to get the data to
fill out SMBIOS table during POST. However, current IDs depend on the
ordering of the FruDevice object paths.

(1) Using the object with "Type: EEPROM" and "Name: MB FRU" in the
EntityManager to figure out the MB FRU eeprom path. Other FRUIDs still
depend on the ordering of the FruDevice object paths.

example of the entity-manager config:
```
    {
        "Address": "$address",
        "Bus": "$bus",
        "Name": "MB FRU",
        "Type": "EEPROM"
    },
```

(2) For System GUID that BIOS populates into SMBIOS table during POST,
also use the MB FRU eeprom path instead of the hardcoding eeprom path.

Change-Id: If950c471f92b99180bab1a629d56d3a912d3b5f4
Signed-off-by: Cosmo Chou <cosmo.chou@quantatw.com>