From: David Daney <ddaney@caviumnetworks.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: David VomLehn <dvomlehn@cisco.com>,
Grant Likely <grant.likely@secretlab.ca>,
linux-mips@linux-mips.org, Imre Kaloz <kaloz@openwrt.org>,
Gabor Juhos <juhosg@openwrt.org>,
John Crispin <blogic@openwrt.org>,
"Dezhong Diao (dediao)" <dediao@cisco.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Converting MIPS to Device Tree
Date: Fri, 10 Jun 2011 12:00:01 -0700 [thread overview]
Message-ID: <4DF269B1.2020407@caviumnetworks.com> (raw)
In-Reply-To: <20110610185745.GA3536@linux-mips.org>
On 06/10/2011 11:57 AM, Ralf Baechle wrote:
> On Tue, Jun 07, 2011 at 04:22:16PM -0700, David Daney wrote:
>
>>> use a parameter like "devtree=<virtual-address>" on the command line, passed
>>> in any way the bootloader likes.
>>
>> Some u-boots for non-mips platforms pass it in the environment of
>> the bootm protocol.
>>
>> I would say to pass the pointer to the DTB in the environment, but
>> not all platforms (like powertv) have an environment. So I guess
>> the command line has to do.
>
> 3 steps:
>
> 1) Use command line argument for DT
> 2) Iff 1) fails, use DT specified by environment
I'm OK with this as long as we can define 'the environment' to include
what I am currently doing on Octeon.
> 3) Iff 1) and 2) fail, use builtin DTB.
>
>> Also I think we should pass the physical address of the DTB, not the
>> virtual address. It would be the kernel's responsibility to figure
>> out what the virtual address is.
>
> I like the basic idea - but ... Most firmware will only use KSEG0 / XKPHYS
> mappings so there should be no aliasing issue but still there could be
> conflicting cache modes. So we should also specify that firmware should
> writeback and invalidate the DTB from caches.
>
> Ralf
>
next prev parent reply other threads:[~2011-06-10 19:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 1:07 Converting MIPS to Device Tree Ralf Baechle
2011-06-06 4:41 ` Grant Likely
2011-06-07 23:02 ` David VomLehn
2011-06-07 23:22 ` David Daney
2011-06-08 1:09 ` David VomLehn
2011-06-10 18:57 ` Ralf Baechle
2011-06-10 19:00 ` David Daney [this message]
2011-06-08 7:15 ` Geert Uytterhoeven
2011-06-08 10:10 ` Florian Fainelli
2011-06-12 18:20 ` Florian Fainelli
2011-06-13 5:10 ` Grant Likely
2011-06-09 2:19 ` Tonyliu
2011-06-09 2:19 ` Tonyliu
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=4DF269B1.2020407@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=blogic@openwrt.org \
--cc=dediao@cisco.com \
--cc=dvomlehn@cisco.com \
--cc=grant.likely@secretlab.ca \
--cc=juhosg@openwrt.org \
--cc=kaloz@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.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