From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/5] port wandboards to use the generic distro configs
Date: Fri, 06 Dec 2013 21:37:59 +0100 [thread overview]
Message-ID: <20131206203759.47710380BFA@gemini.denx.de> (raw)
In-Reply-To: <20131206162854.GX420@bill-the-cat>
Dear Tom,
In message <20131206162854.GX420@bill-the-cat> you wrote:
>
> > But this is crap. The meaning of these variables has been wel-defined
> > for a long, long time. "fdt_addr" is the FDT address in NOR flash (or
> > similar memory except system RAM); "fdt_addr_r" is the FDT address
> > when loaded to system RAM (hence the "_r" in the variable name).
>
> It's a well defined and widely ignored in ARM convention then. We've
> got lots of 'fdt_addr' meaning RAM and no 'fdt_addr_r' and then in both
> ARM and PowerPC 'fdtaddr' being presumably RAM.
I think it's actually OK to omit the "_r" in NOR-less systems. The
number of devices with actual NOT flash is decreasing, and if you can
be sure that there is no such memory device available, then it is
just overhead to always carry the "_r" suffice around, knowing all
the time that there will never be any other option than RAM to store
that data.
I do not complain if such systems use a simplified setup without the
"_r".
What I don't like to see is to have "fdt_addr_r" and "fdt_addr" used
with a new, totally different meaning.
I don't know where the spelling "fdtaddr" is coming from; I would
consider it one of the many "non-standard" variants (assuming we agree
that there is actually something like a "standard"). Note that there
is no "fdtaddr_r" anywhere.
> I would say that 'fdt_addr' being the system provided DT, even when not
> found on memory-mapped flash and 'fdt_addr_r' being the user provided
> one is a logical extension.
Um... you enter completely new terms here - "system provided" and
"user provided". I cannot see how a "user provided" DTB in NOR flash
would fit in such a concept, nor how this would work on systems with
NOR if a "system provided" DTB gets loaded into RAM from a DHCP
server.
I understand that you are trying to give the old names a new
definition that would magically cover the suggested use, but this is
extremely thin ice. I recommend not to try that.
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 at denx.de
The important thing about being a leader is not being right or wrong,
but being *certain*. - Terry Pratchett, _Truckers_
next prev parent reply other threads:[~2013-12-06 20:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 2:18 [U-Boot] [RFC] implementation of generic distro configs Dennis Gilmore
2013-12-06 2:18 ` [U-Boot] [PATCH 1/5] add a generic set of configs to enable Distros to more easier support u-boot based systems Dennis Gilmore
2013-12-06 10:53 ` Wolfgang Denk
2013-12-06 2:18 ` [U-Boot] [PATCH 2/5] port wandboards to use the generic distro configs Dennis Gilmore
2013-12-06 3:47 ` Robert Nelson
2013-12-06 5:01 ` Dennis Gilmore
2013-12-06 5:06 ` Dennis Gilmore
2013-12-06 5:13 ` Robert Nelson
2013-12-06 5:07 ` Robert Nelson
2013-12-06 10:59 ` Wolfgang Denk
2013-12-06 14:48 ` Dennis Gilmore
2013-12-06 15:26 ` Wolfgang Denk
2013-12-06 16:28 ` Tom Rini
2013-12-06 20:37 ` Wolfgang Denk [this message]
2013-12-06 22:13 ` Tom Rini
2013-12-06 22:59 ` Wolfgang Denk
2013-12-06 22:44 ` Dennis Gilmore
2013-12-06 23:16 ` Wolfgang Denk
2013-12-07 0:09 ` Dennis Gilmore
2013-12-07 12:20 ` Wolfgang Denk
2013-12-06 2:18 ` [U-Boot] [PATCH 3/5] port omap4 based devices to use " Dennis Gilmore
2013-12-06 2:18 ` [U-Boot] [PATCH 4/5] port beagleboard " Dennis Gilmore
2013-12-06 2:18 ` [U-Boot] [PATCH 5/5] port beaglebones " Dennis Gilmore
2013-12-06 3:31 ` Dennis Gilmore
2013-12-06 17:14 ` [U-Boot] [RFC] implementation of " Tom Rini
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=20131206203759.47710380BFA@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