public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CPU (405ep) clock upgrade..
Date: Mon, 30 Jun 2008 14:27:43 +0200	[thread overview]
Message-ID: <200806301427.43270.sr@denx.de> (raw)
In-Reply-To: <4868CB14.4050807@fiberlogic.com>

On Monday 30 June 2008, Yi-Neng Lin (???) wrote:
>  Thanks a lot for your reply, Stefan. However, in my understanding, only
> memory-related info is stored in the EEPROM in the memory module, isn't it?

Yes, the I2C EEPROM on the DIMM has of course only memory module related 
stuff. But I was referring to the 405EX bootstrap EEPROM (see chapter 9.2 IIC 
serial EPROM controller (IEC) Operation in the 405EP users manual).

> The CPU and bus related info is hard-coded in the code. This is what I saw
> from my code. Not very sure of it, though.

Yes, could be that you are using the fixed, compiled-in speed configuration.

>  ? I think it's the spd_sdram() [cpu/ppc4xx] who does the job, which could
> have been an outdated method.

It was renamed and is now called 40x_spd_sdram.c. For board with DIMM modules 
on 405EP this is the way to go.

> The timing info is read from the SPD (Serial 
> Presence Detect) EEPROM on the SDRAM module. My question is, with the
> upgraded CPU clock (333MHz), ordinary SDRAMs (PC100 and PC133) may not be
> able to support it, which means I may have to use PC2700 (333MHz; too
> fast?) or PC66(66MHz; too slow?). Am I correct? Any other comment or
> solution for this?

I'm pretty sure that you still can use the "ordinary" DIMMs. The driver should 
configure the needed parameters like CAS latency accordingly.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2008-06-30 12:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-30  5:33 [U-Boot-Users] CPU (405ep) clock upgrade "Yi-Neng Lin (林義能)"
2008-06-30  6:03 ` Stefan Roese
2008-06-30 12:01   ` "Yi-Neng Lin (林義能)"
2008-06-30 12:27     ` Stefan Roese [this message]
2008-07-02  9:23       ` Yi-Neng Lin
2008-07-02  9:38         ` Stefan Roese

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=200806301427.43270.sr@denx.de \
    --to=sr@denx.de \
    --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