From: damon3000 <damon3000@163.com>
To: openbmc@lists.ozlabs.org
Subject: FRU access configuration
Date: Tue, 15 Feb 2022 11:13:22 +0800 (CST) [thread overview]
Message-ID: <ad1d881.3105.17efb5ed0dc.Coremail.damon3000@163.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 284 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 481 bytes --]
next reply other threads:[~2022-02-15 4:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 3:13 damon3000 [this message]
2022-02-15 19:34 ` FRU access configuration Patrick Williams
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=ad1d881.3105.17efb5ed0dc.Coremail.damon3000@163.com \
--to=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).