| To: | Jean Delvare <khali@linux-fr.org> |
|---|---|
| Subject: | Re: [PATCH V2] MIPS: Octeon: Register EEPROM device on the I2C bus |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Thu, 18 Mar 2010 18:00:30 +0100 |
| Cc: | Yang Shi <yang.shi@windriver.com>, ddaney@caviumnetworks.com, ben-linux@fluff.org, linux-mips@linux-mips.org, linux-i2c@vger.kernel.org |
| In-reply-to: | <20100316200647.3803edf1@hyperion.delvare> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <1268026190-18300-1-git-send-email-yang.shi@windriver.com> <20100316180946.GC20160@linux-mips.org> <20100316200647.3803edf1@hyperion.delvare> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.20 (2009-08-17) |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 3/4] bcm63xx: add DWVS0 board, Ralf Baechle |
|---|---|
| Next by Date: | Re: [PATCH V2] MIPS: Octeon: Register EEPROM device on the I2C bus, Jean Delvare |
| Previous by Thread: | Re: [PATCH V2] MIPS: Octeon: Register EEPROM device on the I2C bus, Jean Delvare |
| Next by Thread: | Re: [PATCH V2] MIPS: Octeon: Register EEPROM device on the I2C bus, Jean Delvare |
| Indexes: | [Date] [Thread] [Top] [All Lists] |