From: James Feist <james.feist@linux.intel.com>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>,
Deepak Kodihalli <dkodihal@linux.vnet.ibm.com>,
"Thomaiyar,
Richard Marian" <richard.marian.thomaiyar@linux.intel.com>,
"Bhat, Sumanth" <sumanth.bhat@intel.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Processing PLDM FRU information with entity manager
Date: Wed, 20 May 2020 10:46:28 -0700 [thread overview]
Message-ID: <064203ec-1917-b916-d2aa-4763ee8a6a89@linux.intel.com> (raw)
In-Reply-To: <d3bcea4e6ba97439a3c529cc8607186f10b00ebd.camel@fuzziesquirrel.com>
On 5/20/2020 10:35 AM, Brad Bishop wrote:
> On Wed, 2020-05-20 at 09:56 -0700, James Feist wrote:
>
>> I need a better example. FRUs are independent things, so there is no
>> hierarchy.
>
> A drive plugs into a riser which plugs into the motherboard. Isn't
> that a hierarchy?
>
For a FRU, no. FRUs are independent items. For inventory, yes. Assuming
you mean inventory then? If so, then the paths do not have any hierarchy
today. I assume it might be possible by creating an i2c device tree of
sorts and mapping back what bus is which item.
next prev parent reply other threads:[~2020-05-20 17:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 3:40 Processing PLDM FRU information with entity manager Deepak Kodihalli
2020-05-20 16:28 ` Brad Bishop
2020-05-20 16:56 ` James Feist
2020-05-20 17:35 ` Brad Bishop
2020-05-20 17:46 ` James Feist [this message]
2020-05-26 12:56 ` D-Bus interface to provide data to entity manager (was: Processing PLDM FRU information with entity manager) Deepak Kodihalli
2020-05-27 13:50 ` D-Bus interface to provide data to entity manager Thomaiyar, Richard Marian
2020-05-27 13:58 ` Deepak Kodihalli
2020-05-27 15:25 ` Thomaiyar, Richard Marian
2020-05-27 15:46 ` Deepak Kodihalli
2020-05-27 17:19 ` Thomaiyar, Richard Marian
2020-05-28 12:09 ` Patrick Williams
2020-05-28 12:03 ` D-Bus interface to provide data to entity manager (was: Processing PLDM FRU information with entity manager) Patrick Williams
2020-05-28 12:24 ` D-Bus interface to provide data to entity manager Deepak Kodihalli
2020-05-28 16:42 ` Thomaiyar, Richard Marian
2020-05-28 18:05 ` Patrick Williams
2020-05-28 18:31 ` James Feist
2020-05-29 5:11 ` Deepak Kodihalli
2020-05-29 5:09 ` Deepak Kodihalli
2020-05-29 7:17 ` Thomaiyar, Richard Marian
2020-05-29 7:31 ` Deepak Kodihalli
2020-05-29 9:03 ` Thomaiyar, Richard Marian
2020-05-29 10:19 ` Deepak Kodihalli
2020-05-29 10:30 ` Deepak Kodihalli
2020-05-29 10:33 ` Thomaiyar, Richard Marian
2020-05-28 15:43 ` D-Bus interface to provide data to entity manager (was: Processing PLDM FRU information with entity manager) Brad Bishop
2020-05-28 18:21 ` D-Bus interface to provide data to entity manager James Feist
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=064203ec-1917-b916-d2aa-4763ee8a6a89@linux.intel.com \
--to=james.feist@linux.intel.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=dkodihal@linux.vnet.ibm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=richard.marian.thomaiyar@linux.intel.com \
--cc=sumanth.bhat@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.