From: Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>
To: Chris Packham
<Chris.Packham-6g8wRflRTwXFdCa3tKVlE6U/zSkkHjvu@public.gmane.org>
Cc: "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Using CONFIG_ARM_APPENDED_DTB with multiple device trees
Date: Tue, 20 Oct 2015 06:04:45 +0200 [thread overview]
Message-ID: <20151020040445.GA4478@lunn.ch> (raw)
In-Reply-To: <fce90e91fe3c452b80bcd2113f267003-5g7mGxlPNYb6GjIOKuZY+ItlCAj8ZROq@public.gmane.org>
On Tue, Oct 20, 2015 at 03:27:15AM +0000, Chris Packham wrote:
> Hi,
>
> We currently have several boards based around the 88f6281 (kirkwood) ARM
> CPU.
>
> The boards all share a kernel image (currently 3.16 based but we're in
> the process of moving to 4.3). We use the machine id (and some other
> eeprom type information) to distinguish the boards.
>
> We'd like to move to a device tree based model but we're restricted in
> that updating the bootloaders to a DT-aware u-boot is impractical.
> CONFIG_ARM_APPENDED_DTB allows us to append a device tree but we still
> need to account for the differences between the boards.
Hi Chris
You might want to look at what Debian does. When installing the
kernel, it appends the correct DT blob depending on what the current
running kernel is, to the new kernel image before writing it to the
boot medium.
Another option is the pxa-impedance-matcher.
Andrew
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-10-20 4:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 3:27 Using CONFIG_ARM_APPENDED_DTB with multiple device trees Chris Packham
[not found] ` <fce90e91fe3c452b80bcd2113f267003-5g7mGxlPNYb6GjIOKuZY+ItlCAj8ZROq@public.gmane.org>
2015-10-20 4:04 ` Andrew Lunn [this message]
[not found] ` <20151020040445.GA4478-g2DYL2Zd6BY@public.gmane.org>
2015-10-20 8:11 ` Arnd Bergmann
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=20151020040445.GA4478@lunn.ch \
--to=andrew-g2dyl2zd6by@public.gmane.org \
--cc=Chris.Packham-6g8wRflRTwXFdCa3tKVlE6U/zSkkHjvu@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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).