From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [u-boot-release] [PATCH] powerpc/85xx: verify the localbus device tree address before booting the OS
Date: Wed, 16 Nov 2011 14:00:23 -0600 [thread overview]
Message-ID: <4EC41657.4080206@freescale.com> (raw)
In-Reply-To: <DED7810745269A4D8EFEA0EE7F81C73B1164F0F7@039-SN1MPN1-005.039d.mgd.msft.net>
Swarthout Edward L-SWARTHOU wrote:
>> ... it's possible for the 'reg' property to be wrong.
>
> Instead of all this, why doesn't u-boot just fix it?
>
> I have the same annoyance with ccsrbar.
>
> U-boot controls the ccsrbar address via a user configured #define.
> So instead of having different dts's based on the u-boot ccsrbar,
> why can't u-boot update the device tree?
Because we can't just relocate the devices that we know about and ignore the rest. If CCSR is at the wrong address, then maybe the PCI memory ranges are wrong, too? Who's to say what else is wrong?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-11-16 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 19:28 [U-Boot] [PATCH] powerpc/85xx: verify the localbus device tree address before booting the OS Timur Tabi
2011-11-16 19:58 ` [U-Boot] [u-boot-release] " Swarthout Edward L-SWARTHOU
2011-11-16 20:00 ` Timur Tabi [this message]
2011-11-16 20:02 ` Scott Wood
2011-11-29 15:07 ` [U-Boot] " Kumar Gala
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=4EC41657.4080206@freescale.com \
--to=timur@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