From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Breakage on arm/next
Date: Wed, 02 Dec 2009 11:07:44 -0600 [thread overview]
Message-ID: <4B169EE0.9060400@freescale.com> (raw)
In-Reply-To: <DDCDEEBE8F324D348DAA4E7A380D6A76@sisodomain.com>
apgmoorthy wrote:
> I felt moving these macros "include/linux/mtd/onenand.h" will be ideal in this
> scenario.
Are they going to be the same on all boards? We let the board determine
the environment location for other types of storage.
How about just using CONFIG_ENV_ADDR/CONFIG_ENV_SIZE? On boards that
must dynamically support multiple possibilities, define it as an
expression that returns the right thing.
-Scot
next prev parent reply other threads:[~2009-12-02 17:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 14:22 [U-Boot] Breakage on arm/next apgmoorthy
2009-12-01 14:39 ` Tom
2009-12-01 16:05 ` Alessandro Rubini
2009-12-02 12:13 ` apgmoorthy
2009-12-02 17:07 ` Scott Wood [this message]
2009-12-07 12:13 ` apgmoorthy
2009-12-07 17:26 ` Scott Wood
2009-12-10 4:15 ` apgmoorthy
2009-12-10 17:17 ` Scott Wood
2009-12-21 11:00 ` apgmoorthy
2010-01-06 22:47 ` Scott Wood
2009-12-17 15:53 ` Premi, Sanjeev
2009-12-18 11:01 ` apgmoorthy
-- strict thread matches above, loose matches on Subject: below --
2009-11-28 3:48 Tom
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=4B169EE0.9060400@freescale.com \
--to=scottwood@freescale.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