From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Does CFG_CMD_SDRAM only use for SDRAM DIMMs?
Date: Mon, 4 Apr 2005 08:38:10 -0400 [thread overview]
Message-ID: <42513532.7020407@smiths-aerospace.com> (raw)
In-Reply-To: <20050402085527.0A157C108D@atlas.denx.de>
Wolfgang Denk wrote:
> In message <20050402075050.98724.qmail@web15908.mail.cnb.yahoo.com> you wrote:
>
>>>>> CFG_CMD_SDRAM * print SDRAM configuration information
>>
>>Well, should we add a note beside it like
>>"Must be used with CFG_CMD_I2C" to show their
>>relationship?
>
>
> Good idea. Submit a patch?
>
> Best regards,
>
> Wolfgang Denk
When you are submitting this patch ;-), you might want to add a note
that this is reading from the standard configuration information from
the I2C EEPROM on a DIMM memory module. This command is not useful for
built-in SDRAM memories (i.e. soldered to the motherboard).
I suspect that applies to Frank and the SDRAM configuration read command
is not useful for him. In general, if you have DIMM memory modules, you
probably have I2C enabled in order to configure them. Conversely, if
you don't have I2C, you probably don't have DIMM memory modules and the
command is useless. The third case is that you have DIMM memory modules
but are not using the I2C configuration information out of them... in
that case you should be adding I2C and the automatic configuration.
gvb
next prev parent reply other threads:[~2005-04-04 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 7:50 [U-Boot-Users] Does CFG_CMD_SDRAM only use for SDRAM DIMMs? Sam Song
2005-04-02 8:55 ` Wolfgang Denk
2005-04-04 12:38 ` Jerry Van Baren [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-01 1:06 Frank
2005-04-01 0:39 Sam Song
2005-03-31 14:46 Sam Song
2005-03-31 16:02 ` Wolfgang Denk
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=42513532.7020407@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.com \
--cc=u-boot@lists.denx.de \
/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