From: Patrick Williams <patrick@stwcx.xyz>
To: damon3000 <damon3000@163.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: FRU access configuration
Date: Tue, 15 Feb 2022 13:34:38 -0600 [thread overview]
Message-ID: <YgwATu32A9FJUHxk@heinlein> (raw)
In-Reply-To: <ad1d881.3105.17efb5ed0dc.Coremail.damon3000@163.com>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
On Tue, Feb 15, 2022 at 11:13:22AM +0800, damon3000 wrote:
> Hi All,
>
> I am new to openbmc. I am started porting openbmc features to new hardware.
> So, I want to add support for FRUID EEPROM. FRUID contents should be available as dbus objects. What changes needs to done in the application side.
>
> Please provide the steps or suggestions to follow.
You should probably look at https://github.com/openbmc/entity-manager and
existing systems that leverage it. There is already support for specifying the
location of your EEPROM and interpreting it / exposing as dbus objects.
'FruDevice' is typically involved in the EEPROM parsing and then there is
entity-manager JSON that exposes specific EEPROM fields as the Inventory
object(s).
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-02-15 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 3:13 FRU access configuration damon3000
2022-02-15 19:34 ` Patrick Williams [this message]
2022-02-17 11:10 ` damon3000
2022-02-18 3:48 ` Zev Weiss
2022-02-18 6:08 ` damon3000
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YgwATu32A9FJUHxk@heinlein \
--to=patrick@stwcx.xyz \
--cc=damon3000@163.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).