From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 3/3] Add support for the LaCie ED Mini V2 board
Date: Sat, 05 Dec 2009 08:03:05 +0100 [thread overview]
Message-ID: <4B1A05A9.4040104@free.fr> (raw)
In-Reply-To: <20091205003507.573673F6E3@gemini.denx.de>
Wolfgang Denk a ?crit :
> Dear Albert ARIBAUD,
>
> In message <4B126F68.9020005@free.fr> you wrote:
>>> Cannot you use get_ram_size() for auto-sizing and checking?
>> The SoC allows for up to 4 banks of DRAM, not necessarily contiguous.
>> Granted, this is not a frequent configuration, however I'd like to
>> support it correctly, and the heuristics of get_ram_size() are based on
>> the assumption that all DRAM is contiguous.
>
> No, this is not correct. get_ram_size() is used always on a single
> bank of memory only.
Do you mean calling get_ram_size() four up to times based on the
configured number of banks and configured sizes? I then fail to see the
added value of get_ram_size() wrt using the configured sizes directly.
>> However I realize that this code is actually SoC-specific, not
>> board-specific. It could be moved in cpu/arm926ejs/orion5x/dram.c, and
>> then orion5x_sdram_{bar,bs} could be made static (or inlined).
>>
>> What do you think?
>
> Seems to make sense.
All right. Does doing that lift the requirement to use get_ram_size()?
> Best regards,
>
> Wolfgang Denk
Amicalement,
--
Albert.
next prev parent reply other threads:[~2009-12-05 7:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 23:03 [U-Boot] [PATCH V2 0/3] Support for Marvell Orion5x SoC and LaCie ED Mini V2 board Albert Aribaud
2009-11-14 23:03 ` [U-Boot] [PATCH V2 1/3] Initial support for Marvell Orion5x SoC Albert Aribaud
2009-11-14 23:03 ` [U-Boot] [PATCH V2 2/3] Add Orion5x support to 16550 serial device driver Albert Aribaud
2009-11-14 23:03 ` [U-Boot] [PATCH V2 3/3] Add support for the LaCie ED Mini V2 board Albert Aribaud
2009-11-16 9:05 ` Prafulla Wadaskar
2009-11-29 11:22 ` Albert ARIBAUD
2009-11-18 22:21 ` Wolfgang Denk
2009-11-19 7:51 ` Stefan Roese
2009-11-19 12:48 ` Albert ARIBAUD
2009-11-19 13:10 ` Stefan Roese
2009-11-28 22:21 ` Albert ARIBAUD
2009-11-29 12:56 ` Albert ARIBAUD
2009-12-05 0:35 ` Wolfgang Denk
2009-12-05 7:03 ` Albert ARIBAUD [this message]
2009-12-07 21:56 ` Wolfgang Denk
2009-12-11 15:51 ` Albert ARIBAUD
2009-12-02 8:31 ` [U-Boot] Mixed 8/16 bits NOR FLASH support (was: [PATCH V2 3/3] Add support for the LaCie ED Mini V2 board) Albert ARIBAUD
2009-12-02 9:15 ` Stefan Roese
2009-12-02 9:38 ` Wolfgang Denk
2009-12-02 11:07 ` [U-Boot] Mixed 8/16 bits NOR FLASH support Albert ARIBAUD
2009-12-02 10:57 ` Albert ARIBAUD
2009-11-18 22:17 ` [U-Boot] [PATCH V2 1/3] Initial support for Marvell Orion5x SoC Wolfgang Denk
2009-11-18 22:51 ` Albert ARIBAUD
2009-11-29 8:55 ` Albert ARIBAUD
2009-12-05 0:37 ` Wolfgang Denk
2009-12-23 6:07 ` Prafulla Wadaskar
2009-11-29 10:34 ` Albert ARIBAUD
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=4B1A05A9.4040104@free.fr \
--to=albert.aribaud@free.fr \
--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.