From: "Thomaiyar, Richard Marian" <richard.marian.thomaiyar@linux.intel.com>
To: Kumar Thangavel <thangavel.k@hcl.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>,
Vernon Mauery <vernon.mauery@linux.intel.com>,
"vijaykhemka@fb.com" <vijaykhemka@fb.com>,
James Feist <james.feist@linux.intel.com>,
"Velumani T-ERS, HCLTech" <velumanit@hcl.com>,
Patrick Williams <patrickw3@fb.com>
Subject: Re: Read FRU of host through ipmi in Entity manager.
Date: Mon, 14 Sep 2020 22:55:24 +0530 [thread overview]
Message-ID: <f31aa36a-4519-7e68-7ff4-fab62b6bb42e@linux.intel.com> (raw)
In-Reply-To: <HK0PR04MB2964FFC6D5EF008F106FFC13FD230@HK0PR04MB2964.apcprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2834 bytes --]
Hi Kumar,
Better to expose IPMI FRU of the host read via IPMB through FRU
Interface (i.e. say xyz.openbmc_project.IPMB.FruDevice daemon, which can
expose all the FRU's read through the same). In this way, current
EntityManager probe will still work. (Note: We can add the support in
FRUDevice if it is IPMB read of raw FRU data, so that conversion code in
FRUDevice can still be used).
Current plan (under discussion - Needs to finalize) to expose the PLDM
FRU in separate daemon under interface
(https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/xyz/openbmc_project/Inventory/Source/PLDM)
James, Do you see any issue with this approach / comments ?
Regards,
Richard
On 9/14/2020 10:25 PM, Kumar Thangavel wrote:
>
> Classification: *HCL Internal*
>
> Hi All,
>
> We are working on the Platform which has multi host and the
> host are FRUs. The host and BMC communication is based on IPMB. We
> have each host is connected in separate ipmb bus.
>
> Existing Entity manager has the FRU read info from EEPROM
> (I2C)in the form of bin file.
> We understand that entity manager does not support ipmb based
> host fru.
>
> So, we are proposing the design to support ipmb based FRU in
> entity manager.
> From Entity manager, we will send the generic "read host fru"
> command request to ipmbbrige to read the host FRU.
>
> Then, store the host fru info in the bin file to process and
> creating dbus objects in the entity manager.
>
> Please let us know your comments on this.
>
> Thanks,
>
> Kumar.
>
> ::DISCLAIMER::
> ------------------------------------------------------------------------
> The contents of this e-mail and any attachment(s) are confidential and
> intended for the named recipient(s) only. E-mail transmission is not
> guaranteed to be secure or error-free as information could be
> intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
> may contain viruses in transmission. The e mail and its contents (with
> or without referred errors) shall therefore not attach any liability
> on the originator or HCL or its affiliates. Views or opinions, if any,
> presented in this email are solely those of the author and may not
> necessarily reflect the views or opinions of HCL or its affiliates.
> Any form of reproduction, dissemination, copying, disclosure,
> modification, distribution and / or publication of this message
> without the prior written consent of authorized representative of HCL
> is strictly prohibited. If you have received this email in error
> please delete it and notify the sender immediately. Before opening any
> email and/or attachments, please check them for viruses and other defects.
> ------------------------------------------------------------------------
[-- Attachment #2: Type: text/html, Size: 7243 bytes --]
next prev parent reply other threads:[~2020-09-14 17:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 16:55 Read FRU of host through ipmi in Entity manager Kumar Thangavel
2020-09-14 17:25 ` Thomaiyar, Richard Marian [this message]
2020-09-14 17:28 ` James Feist
2020-09-14 17:28 ` Ed Tanous
2020-09-15 19:20 ` Vijay Khemka
2020-09-21 16:44 ` Kumar Thangavel
2020-09-21 16:44 ` Kumar Thangavel
2020-09-22 19:57 ` Vijay Khemka
2020-09-22 20:20 ` Ed Tanous
2020-09-22 20:26 ` Vijay Khemka
2020-09-22 20:56 ` Ed Tanous
2020-09-23 5:42 ` Vijay Khemka
2020-09-24 15:12 ` Kumar Thangavel
2020-09-22 20:04 ` Ed Tanous
2020-09-24 15:12 ` Kumar Thangavel
2020-09-22 7:51 ` Andrei Kartashev
2020-09-22 20:13 ` Ed Tanous
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=f31aa36a-4519-7e68-7ff4-fab62b6bb42e@linux.intel.com \
--to=richard.marian.thomaiyar@linux.intel.com \
--cc=jae.hyun.yoo@linux.intel.com \
--cc=james.feist@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrickw3@fb.com \
--cc=thangavel.k@hcl.com \
--cc=velumanit@hcl.com \
--cc=vernon.mauery@linux.intel.com \
--cc=vijaykhemka@fb.com \
/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).