exposing device-tree populated eeproms in FruDevice
venture at google.com
Tue Jul 30 03:59:41 AEST 2019
Per the previous email, some eeproms aren't supported by FruDevice. I
was curious if it made sense to have it not only search for responding
i2c devices on a bus, but also look at ones that have the "eeprom"
sysfs file, and talk to those as well? So that we can put things in
the device tree where the kernel will expose it with the known
driver/configuration, and then it can be read by FruDevice -- although
at that point, it may make sense to have a hybrid approach if possible
that uses ipmi-fru-parser (which uses the eeprom sysfs entry).
More information about the openbmc