From: Ralf Baechle <ralf@linux-mips.org>
To: Jean Delvare <khali@linux-fr.org>
Cc: Yang Shi <yang.shi@windriver.com>,
ddaney@caviumnetworks.com, ben-linux@fluff.org,
linux-mips@linux-mips.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH V2] MIPS: Octeon: Register EEPROM device on the I2C bus
Date: Thu, 18 Mar 2010 18:00:30 +0100 [thread overview]
Message-ID: <20100318170030.GJ4554@linux-mips.org> (raw)
In-Reply-To: <20100316200647.3803edf1@hyperion.delvare>
On Tue, Mar 16, 2010 at 08:06:47PM +0100, Jean Delvare wrote:
> The Linux kernel doesn't care, but user-space may. As a matter of fact,
> there is a script out there (decode-dimms, in the i2c-tools package)
> decoding the SPD data and presenting it to the user. Some people want
> to know the details about their memory modules.
>
> > I also wonder how this will work for configurations with multiple memory
> > modules thus multiple SPD EEPROMS.
>
> The kernel code should instantiate one spd device per memory module
> (assuming they are all reachable.) Obviously this can't be done in a
> static way.
SPD is virtually omnipresent these days so I wonder if maybe there already
is some probing functionality already available?
Ralf
next prev parent reply other threads:[~2010-03-18 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 5:29 [PATCH V2] MIPS: Octeon: Register EEPROM device on the I2C bus Yang Shi
[not found] ` <1268026190-18300-1-git-send-email-yang.shi-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org>
2010-03-08 6:01 ` Wolfram Sang
2010-03-16 18:09 ` Ralf Baechle
2010-03-16 19:06 ` Jean Delvare
2010-03-18 17:00 ` Ralf Baechle [this message]
[not found] ` <20100318170030.GJ4554-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org>
2010-03-18 17:48 ` Jean Delvare
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=20100318170030.GJ4554@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ben-linux@fluff.org \
--cc=ddaney@caviumnetworks.com \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=yang.shi@windriver.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).