From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: Device tree.
Date: Tue, 17 Jul 2012 14:56:33 +0100 [thread overview]
Message-ID: <5b5e32ecde7b96d3af217054150eb43c@codethink.co.uk> (raw)
In-Reply-To: <50056E22.5040308@gmail.com>
On 17/07/2012 14:52, Rob Herring wrote:
> On 07/17/2012 08:25 AM, Ben Dooks wrote:
>> On 17/07/2012 14:07, Ian Molton wrote:
>>> On 17/07/12 13:32, Josh Coombs wrote:
>>>> make make target.dtb
>>>> cat arch/arm/boot/target.dtb >> arch/arm/boot/zImage
>>>> make uImage
>>>
>>> Yick...
>>
>> How about adding a dts=<address> argument to the current
>> command line handling. If this is found, then the system
>> ignores the rest of the atags passed and uses the passed
>> address for the device-tree settings.
>>
>> This means in u-boot, you just need to load the .dts file
>> into place before booting the kernel.
>>
> You mean dtb...
>
> But no, we don't need a 3rd boot interface in the kernel. I don't see
> why cat + mkimage is too hard to run.
I suppose we can produce our own build-script
> Now that u-boot has direct support for zImage booting, I doubt
> anything
> uImage building related will ever be accepted into the kernel.
Depends on u-boot, the one we have been supplied doesn't seem to
have any interest in booting zImages.
--
Ben
next prev parent reply other threads:[~2012-07-17 13:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 11:55 Device tree Ian Molton
2012-07-17 12:01 ` Thomas Petazzoni
2012-07-17 12:13 ` Ian Molton
2012-07-17 12:29 ` Thomas Petazzoni
2012-07-17 12:41 ` Florian Fainelli
2012-07-17 13:32 ` Thomas Petazzoni
2012-07-17 12:32 ` Josh Coombs
2012-07-17 13:07 ` Ian Molton
2012-07-17 13:25 ` Ben Dooks
2012-07-17 13:52 ` Rob Herring
2012-07-17 13:56 ` Ben Dooks [this message]
2012-07-17 14:02 ` Florian Fainelli
2012-07-17 14:55 ` Ian Molton
2012-07-17 21:18 ` Nicolas Pitre
2012-07-18 7:51 ` Ian Molton
2012-07-18 13:42 ` Nicolas Pitre
2012-07-19 9:07 ` Ian Molton
2012-07-19 21:32 ` Nicolas Pitre
2012-07-23 13:10 ` Mark Brown
2012-07-17 14:05 ` Mark Brown
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=5b5e32ecde7b96d3af217054150eb43c@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).