From: Kim Phillips <kim.phillips@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Fixup of fdt with detected memory size instead of fixed values
Date: Wed, 24 Oct 2007 17:54:42 -0500 [thread overview]
Message-ID: <20071024175442.2e426dd0.kim.phillips@freescale.com> (raw)
In-Reply-To: <47F3F98010FF784EBEE6526EAAB078D1024F8796@tq-mailsrv.tq-net.de>
On Wed, 24 Oct 2007 18:41:51 +0200
"Martin Krause" <Martin.Krause@tqs.de> wrote:
> feature for all boards? AFAIK bd->bi_mestart and bd->bi_memsize
> should contain valid values on all boards. So why not fixup the "memory"
> node for all boards in ft_setup()? Does this make sense?
I think you're looking at the old CONFIG_OF_FLAT_TREE code, which has
since been superseded by CONFIG_OF_LIBFDT code.
In 83xx, all boards' /memory fixup occurs in ft_cpu_setup in
cpu/mpc83xx/cpu.c, but, yes, I agree, it should be put somewhere even
more common.
Kim
next prev parent reply other threads:[~2007-10-24 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 16:41 [U-Boot-Users] Fixup of fdt with detected memory size instead of fixed values Martin Krause
2007-10-24 22:54 ` Kim Phillips [this message]
2007-10-25 7:11 ` Martin Krause
2007-10-25 11:14 ` Jerry Van Baren
2007-10-25 12:28 ` Martin Krause
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=20071024175442.2e426dd0.kim.phillips@freescale.com \
--to=kim.phillips@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 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.