linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ian.molton@codethink.co.uk (Ian Molton)
To: linux-arm-kernel@lists.infradead.org
Subject: Device tree.
Date: Tue, 17 Jul 2012 14:07:29 +0100	[thread overview]
Message-ID: <50056391.3060208@codethink.co.uk> (raw)
In-Reply-To: <CAMW5UfZR5qrY4K=ty9HDcd9UqYGtfZitH0CBgDbZWvpAoTve2Q@mail.gmail.com>

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...

 >My understanding is you can
 > only append one DTB, there is no restriction on how many systems a
 > given kernel could support, so at the moment there isn't a clean way
 > of defining which DTB to append during make uImage? Josh C

Yes, hence why it'd be useful to have a way of specifying a .dtb file as 
a config option...

There isnt really a good way to solve this, AFAICT.

-Ian

  reply	other threads:[~2012-07-17 13:07 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 [this message]
2012-07-17 13:25         ` Ben Dooks
2012-07-17 13:52           ` Rob Herring
2012-07-17 13:56             ` Ben Dooks
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=50056391.3060208@codethink.co.uk \
    --to=ian.molton@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).