From: Michele De Candia (VT) <michele.decandia@valueteam.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] RAM Probing for ads5121rev4
Date: Tue, 31 Mar 2009 18:00:48 +0200 [thread overview]
Message-ID: <49D23E30.4060205@valueteam.com> (raw)
In-Reply-To: <20090218090133.A3FC2832E43F@gemini.denx.de>
Wolfgang Denk wrote:
> Dear Emanuele Placidi,
>
> In message <7c4b93310902180021o56da8320w2084e6a8c09c9509@mail.gmail.com> you wrote:
>
>> In your opinion it is possible to probe the ram before initialize it?
>> Unfortunately there are some rev4 which are equipped with different ram
>> model.
>> Examples are welcomed.
>>
>
> It is a standard feature in U-Boot (and has always been right from
> the start with PPCBoot nearly 10 years ago) that we auto-detected the
> memory configuration on the boards, both for RAM and flash. Some
> boards / architectures did not bother to implement this, but the
> feature itself is present.
>
> The details depend on processor, memory controller properties,
> specific RAM types used, etc.
>
> In case of the Micron/Elpida issue on the ADS5121, that should be not
> too difficult to solve.
>
The issue concerns the possibility to identify DDR chips type (e.g. by
VendorId) before initialize them.
It doesn't concern configuration parameters (size, bus frequency, ecc..).
There isn't a DDR command to read this information, do you think it is
possible to solve this problem in other ways?
> Best regards,
>
> Wolfgang Denk
>
>
--
*Michele Jr **De Candia*
------------------------------------------------------------------------
Value Team
Via Vespri Siciliani, 9
20146 Milano
Tel. +39 0248985722
michele.decandia at valueteam.com <mailto:michele.decandia@valueteam.com>
http://www.valueteam.com
CONFIDENTIALITY NOTICE -This message and its attachments (if any) may
contain confidential, proprietary or legally privileged information and
is intended only for the use of the addressee named above. No
confidentiality or privilege is waived or lost by any mistransmission.
If you are not the intended recipient of this message you are hereby
notified that you must not use, disseminate, copy it in any form or take
any action in reliance on it. If you have received this message in error
please delete it and any copies of it and kindly inform the sender of
this e-mail by replying or go to www.valueteam.com
<http://www.valueteam.com> on 'contacts'.
next prev parent reply other threads:[~2009-03-31 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 8:21 [U-Boot] RAM Probing for ads5121rev4 Emanuele Placidi
2009-02-18 9:01 ` Wolfgang Denk
2009-03-31 16:00 ` Michele De Candia [this message]
2009-03-31 21:05 ` Wolfgang Denk
2009-03-31 21:37 ` Michele De Candia
-- strict thread matches above, loose matches on Subject: below --
2009-04-01 10:15 m marx
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=49D23E30.4060205@valueteam.com \
--to=michele.decandia@valueteam.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