From: Andrei Kartashev <a.kartashev@yadro.com>
To: Alexander Raih <61a91bc@gmail.com>, <openbmc@lists.ozlabs.org>
Subject: Re: How I can read fru information about cpu and dimm ?
Date: Fri, 10 Sep 2021 15:09:42 +0300 [thread overview]
Message-ID: <435cf6e388bf47385ba0c35c48a225beb3450262.camel@yadro.com> (raw)
In-Reply-To: <CAMqwjCDjaGDyRutmoqBM1zDK10VOWzkY82vQ6atUhqv1AsWa9g@mail.gmail.com>
Hello Alexander,
We can't tell you how to work with your hardware without any knowledge
about it's design.
Typically, CPU have no any EEPROM to read information from it. DIMMs
have special I2C channel, called SPD, but generally it is not connected
to BMC. I guess, you need to use some communication with the host to
request this information. But all this is common suggestion, you need
to know your hardware.
On Fri, 2021-09-10 at 13:10 +0300, Alexander Raih wrote:
> Hi guys, I am beginner in openbmc, cat you tell me a question.
> In device tree I describe eeprom on i2c bus. I read this eeprom file
> in fs and this file contained information only about
> mainboard(vendor,model,s/n,p/n). Please tell me how can I get fru
> information about cpu, dimms ??
>
> p.s. On another i2c bus I have 2 devices with addresses 0x70 0x71. I
> think that it is mux pca9545 and on the one on channel of this mux
> locate eeprom.
>
--
Best regards,
Andrei Kartashev
prev parent reply other threads:[~2021-09-10 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 10:10 How I can read fru information about cpu and dimm ? Alexander Raih
2021-09-10 12:09 ` Andrei Kartashev [this message]
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=435cf6e388bf47385ba0c35c48a225beb3450262.camel@yadro.com \
--to=a.kartashev@yadro.com \
--cc=61a91bc@gmail.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).