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 23:37:16 +0200 [thread overview]
Message-ID: <49D28D0C.2040402@valueteam.com> (raw)
In-Reply-To: <20090331210538.77DC283797DC@gemini.denx.de>
Wolfgang Denk wrote:
> Dear "Michele De Candia (VT)",
>
> In message <49D23E30.4060205@valueteam.com> you wrote:
>
>> 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?
>>
>
> Yes, of course it is possible to solve this problem otherwise.
>
> In a sane hardware design you can read this information from some
> board configuration register or so; for example, on the ADS5121 there
> could be such a register implemented in the CPLD. But alas, there
> ain't none.
>
> Martha Marx posted pretty good patches (identifyung board revisions
> based on the MAC address) more than a month ago, but then failed to
> address the last review comments.
>
> If you want to get that fixed, please pick up her patches (or nudge
> her to do it for you).
>
Hi Mr. Denk,
thanks for the suggestions, we've already picked up Martha Marx patches
and they work fine on ADS5121.
We want to avoid DDR identification by board revisions because we don't
know which DDR will be used in the future and it isn't a flexible way to
do that.
After all, if it is the only way, we'll use this one.
Thanks,
Michele De Candia
> 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 21:37 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
2009-03-31 21:05 ` Wolfgang Denk
2009-03-31 21:37 ` Michele De Candia [this message]
-- 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=49D28D0C.2040402@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