All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: "Jean-François Roy" <jf@devklog.net>
Cc: Wolfram Sang <wsa@kernel.org>, linux-i2c@vger.kernel.org
Subject: Re: [ee1004] Failed to select page 0 - G.Skill Trident Z5 NEO DDR5, ASUS X670E board - 6.2.11-arch1-1
Date: Sat, 29 Apr 2023 18:06:34 +0200	[thread overview]
Message-ID: <20230429180634.7f94b29e@endymion.delvare> (raw)
In-Reply-To: <20230429171522.05c671f8@endymion.delvare>

On Sat, 29 Apr 2023 17:15:22 +0200, Jean Delvare wrote:
> I took a quick look on jedec.org in search for information and found
> JESD400-5A which covers SPD contents for DDR5 and it enumerates 1024
> bytes. This is twice as much as what EE1004 EEPROMs can hold, so DDR5
> modules are definitely not using EE1004 EEPROMs. So far I couldn't find
> the "equivalent" of EE1004 for DDR5 modules so far.

Found it, it is named "SPD5118 Hub and Serial Presence Detect Device
Standard" and is published by Jedec under reference JESD300-5B. That's
a 126-page document. In comparison, the EE1004 specification was
35-page long.

So I expect there will be a lot of work to get it to work. And I don't
own a DDR5-based system yet, so I can't even test.

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2023-04-29 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20 22:51 [ee1004] Failed to select page 0 - G.Skill Trident Z5 NEO DDR5, ASUS X670E board - 6.2.11-arch1-1 Jean-François Roy
2023-04-21  4:35 ` Wolfram Sang
2023-04-29 15:15   ` Jean Delvare
2023-04-29 16:06     ` Jean Delvare [this message]
2023-05-01 16:42       ` Jean-François Roy

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=20230429180634.7f94b29e@endymion.delvare \
    --to=jdelvare@suse.de \
    --cc=jf@devklog.net \
    --cc=linux-i2c@vger.kernel.org \
    --cc=wsa@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.