All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: James Feeney <james@nurealm.net>
Cc: linux-i2c@vger.kernel.org
Subject: Re: i2c-tools - at24 vs eeprom - decode-dimms fails with the at24 module
Date: Sat, 14 Mar 2020 21:41:13 +0100	[thread overview]
Message-ID: <20200314214113.54e48d00@endymion> (raw)
In-Reply-To: <dc5201ea-de3f-f26c-c95e-fca392b521aa@nurealm.net>

Hi James,

On Sat, 14 Mar 2020 09:22:57 -0600, James Feeney wrote:
> The log says "kernel: eeprom 3-0050: eeprom driver is deprecated, please use at24 instead", but decode-dimms will only work with the deprecated eeprom driver.  With the at24 module, "Number of SDRAM DIMMs detected and decoded: 0".  With the eeprom module, "Number of SDRAM DIMMs detected and decoded: 6". This is on Arch Linux, with linux 5.5.9.arch1-2, on an old Asus P6T DELUXE V2 with a Core i7.

While the legacy eeprom driver (poorly) auto-detected SPD EEPROMs, the
at24 driver requires SPD EEPOMs to be explicitly enumerated. There is
work in progress [1] to automate this in some cases (namely x86 systems
using the i2c-i801 SMBus controller driver) but for now you'll have to
do it yourself from user-space. How to do that is explained in section 4
of:

https://www.kernel.org/doc/Documentation/i2c/instantiating-devices

TL;DR: Something like:

# echo spd 0x50 > /sys/bus/i2c/devices/i2c-3/new_device

should do the trick, if i2c-3 is your SMBus and you have 1 memory
module in the first slot. If you have more memory modules, use
"modprobe i2c-dev ; i2cdetect 0" to find out the proper addresses in
the 0x50-0x57 range and repeat the command.

I guess I should resubmit this patch set to make it transparent to the
users.

[1] https://lore.kernel.org/lkml/20191014113950.1f989ba6@endymion/

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2020-03-15  1:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-14 15:22 i2c-tools - at24 vs eeprom - decode-dimms fails with the at24 module James Feeney
2020-03-14 20:41 ` Jean Delvare [this message]
2020-03-15 22:49   ` James Feeney
2020-03-16 12: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=20200314214113.54e48d00@endymion \
    --to=jdelvare@suse.de \
    --cc=james@nurealm.net \
    --cc=linux-i2c@vger.kernel.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 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.