exposing device-tree populated eeproms in FruDevice

[Patrick Venture]

On Mon, Jul 29, 2019 at 10:59 AM Patrick Venture <venture at google.com> wrote:
>
> 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).

Just wanted to promote this to the top of inboxes.  It isn't clear
from reading the code that this is doing anything beyond "installing"
the device via Exposes.  If it's a temperature sensor, it sets up the
dbus configuration, but otherwise not.

>
> Patrick