From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: Device tree.
Date: Tue, 17 Jul 2012 14:01:00 +0200 [thread overview]
Message-ID: <20120717140100.7c0ae90c@skate> (raw)
In-Reply-To: <500552C9.4090107@codethink.co.uk>
Le Tue, 17 Jul 2012 12:55:53 +0100,
Ian Molton <ian.molton@codethink.co.uk> a ?crit :
> I've found some references to this in the mailinglist archives but
> nothing conclusive.
>
> Whats the recommended way of dealing with devicetree when one is
> stuck with an unco-operative bootloader?
>
> I've made a small hack (below) to allow me to append a .dtb to the
> end of the kernel image. I note that other similar hacks have not
> been picked up, but I can't see why. Or I've missed the one that did
> get chosen.
You surely want to have a look at CONFIG_ARM_APPENDED_DTB, which does
what you want and is already part of the ARM kernel.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-17 12:01 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 [this message]
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
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=20120717140100.7c0ae90c@skate \
--to=thomas.petazzoni@free-electrons.com \
--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).