From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2 V3] at91sam9261ek: make operational again
Date: Sat, 19 Feb 2011 20:22:59 +0100 [thread overview]
Message-ID: <20110219192259.C056715365A@gemini.denx.de> (raw)
In-Reply-To: <AANLkTinwsi4nNxkHfcNs19E7YBj78kqjYLGqG9LBaS+b@mail.gmail.com>
Dear Remy Bohmer,
In message <AANLkTinwsi4nNxkHfcNs19E7YBj78kqjYLGqG9LBaS+b@mail.gmail.com> you wrote:
>
> > I'd recommend setting this to the very beginning of SDRAM(0x20000000),
> > note that initial SP and GD would be put into SRAM further down.
>
> The SRAM is used by the LCD controller. So, we cannot use it for the SP and GD.
Why not?
LCD is most probably only initialized and used after relocation, while
stack and GD are needed and used only before that...
> >>> +#define CONFIG_SYS_SDRAM_SIZE 0x04000000 /* 64 megs> */
> >
> > It is up to you, but (64 << 20) might look "nicer".
>
> This is more a matter of taste I think. I will see what I do with it.
It's not only a matter of taste, but also a matter of readability. If
I see 0x04000000 I cannot really tell immediately if this is a bit
mask or anything else, and even if I know from the context that it's a
size, I cannot immediately say how much it is. On the other hand, a
notation like "64 * 1024 * 1024" or (shorter) "64 << 20" makes it
immediately clear that 1) it's some number, probably a size, and 2)
that it's 64 MiB.
In the interest of maitainability please chose a more readable way to
specify such numbers.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Es ist nicht genug zu wissen, man mu? auch anwenden; es ist nicht ge-
nug zu wollen, man mu? auch tun. -- Goethe, Maximen und Reflexionen
next prev parent reply other threads:[~2011-02-19 19:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 12:43 [U-Boot] [PATCH 1/2 V3] at91sam9261ek: make operational again Remy Bohmer
2011-02-05 12:43 ` [U-Boot] [PATCH 2/2 V1] Make at91sam9261ek and at91sam9g10ek work again Remy Bohmer
2011-02-17 19:21 ` Remy Bohmer
2011-02-17 23:45 ` Andreas Bießmann
2011-02-18 7:32 ` Reinhard Meyer
2011-02-17 19:19 ` [U-Boot] [PATCH 1/2 V3] at91sam9261ek: make operational again Remy Bohmer
2011-02-17 23:42 ` Andreas Bießmann
2011-02-18 6:51 ` Reinhard Meyer
2011-02-19 8:46 ` Remy Bohmer
2011-02-19 19:22 ` Wolfgang Denk [this message]
2011-02-19 19:59 ` Remy Bohmer
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=20110219192259.C056715365A@gemini.denx.de \
--to=wd@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