All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: SunNeo <sunwx2001@hotmail.com>
Cc: linuxppc-dev@ozlabs.org, U-Boot-Users <u-boot@lists.denx.de>
Subject: Re: Help!Some memory doesn't work on PPC405Ex based board!
Date: Tue, 14 Apr 2009 14:20:04 +0200	[thread overview]
Message-ID: <200904141420.04478.sr@denx.de> (raw)
In-Reply-To: <BAY114-W4176A96E45AE37FB5FBE02AB7C0@phx.gbl>

Hi Sun,

On Tuesday 14 April 2009, SunNeo wrote:
> My platform uses the MICRON MT47H256M8THN DDRII SDRAM and the DDRII SDRAM
> is soldered on the board.
>
> As I said, my board was similar with "Kilauea" evb, so I created my
> configuration header file from Kilauea's at U-Boot. In the configuration
> file, register value for the DDR SDRAM controller is defined. But I have
> removed DDR autocalibraton related configuration from the configuration
> file, do you think this will cause any issues?

Yes, this could definitely cause some SDRAM related problems. But this is 
off-topic here. We should continue this discussion on the U-Boot mailing list 
instead (on CC). So please when you reply to this mail, remove the 
linuxppc-dev list from the recipients list.

Best regards,
Stefan

WARNING: multiple messages have this Message-ID (diff)
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Help!Some memory doesn't work on PPC405Ex based board!
Date: Tue, 14 Apr 2009 14:20:04 +0200	[thread overview]
Message-ID: <200904141420.04478.sr@denx.de> (raw)
In-Reply-To: <BAY114-W4176A96E45AE37FB5FBE02AB7C0@phx.gbl>

Hi Sun,

On Tuesday 14 April 2009, SunNeo wrote:
> My platform uses the MICRON MT47H256M8THN DDRII SDRAM and the DDRII SDRAM
> is soldered on the board.
>
> As I said, my board was similar with "Kilauea" evb, so I created my
> configuration header file from Kilauea's at U-Boot. In the configuration
> file, register value for the DDR SDRAM controller is defined. But I have
> removed DDR autocalibraton related configuration from the configuration
> file, do you think this will cause any issues?

Yes, this could definitely cause some SDRAM related problems. But this is 
off-topic here. We should continue this discussion on the U-Boot mailing list 
instead (on CC). So please when you reply to this mail, remove the 
linuxppc-dev list from the recipients list.

Best regards,
Stefan

  reply	other threads:[~2009-04-14 12:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 12:05 Help!Some memory doesn't work on PPC405Ex based board! SunNeo
2009-04-14  9:23 ` Stefan Roese
2009-04-14 11:08   ` SunNeo
2009-04-14 12:20     ` Stefan Roese [this message]
2009-04-14 12:20       ` [U-Boot] " Stefan Roese
2009-04-14 14:04     ` Grant Erickson
2009-04-14 16:30     ` Feng Kan
2009-04-15  7:56       ` [U-Boot] " SunNeo
2009-04-15  8:08         ` Stefan Roese
2009-04-23  5:00           ` SunNeo
2009-04-23  6:01             ` Grant Erickson
2009-04-23  8:07               ` Stefan Roese
2009-04-23  9:13                 ` SunNeo
2009-04-23  9:55                   ` Stefan Roese
2009-05-04  4:56                     ` SunNeo

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=200904141420.04478.sr@denx.de \
    --to=sr@denx.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sunwx2001@hotmail.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 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.