OpenBMC - FRU inventory with Entity Manager

[Ed Tanous]

On Wed, Aug 26, 2020 at 11:11 PM Andrei Kartashev <a.kartashev at yadro.com>
wrote:

> Since there is a plan to move to EM for inventory, I believe it is
> really good idea to also have support for FruDevice in phosphor-host-
> ipmid. Then we can have a common way on how to handle it.
> Same for SDR BTW.
>

+1.  This was attempted a long time ago, but nobody was able to come up
with a design that kept the "old" way working for those that needed it, and
at the time there were some missing features.  Given where entity manager
has gotten, it's probably time to start that discussion up again.  Do you
think you could put together a patch that does what you describe?


>
> But there is other thing: there is catastrophically not enough
> documentation for EntityManager/dbus-sensors. Looks like common way
> just to adjust existing config and hope that it still will work.
> <sorry, was all the day trying to get adcsensors work yesterday>
>

That being the case, would you mind taking a look at the docs changes I
just put up.  It's trying to improve the EM documentation a bit, although I
realize it doesn't get all the way to where it needs to be.
https://gerrit.openbmc-project.xyz/c/openbmc/entity-manager/+/36110

Also, it'd be great if you can come up with some concrete examples of what
else we can improve in this regard.  Unfortunately the "copy an existing
config and modify" approach was the best way we found to make platform
ports easy.  A lot of systems tend to look pretty similar, based on similar
reference platforms, so usually there's something to use as a starting
point.  Building a config from scratch using first principals and
documentation is kind of daunting, and became a non-starter for most
people, given that the config files tend to be large.

What were the biggest roadblocks you hit trying to get ADCSensor working?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200831/03f58b95/attachment.htm>