From: Alban <albeu@free.fr>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
Alban Bedel <albeu@free.fr>
Subject: Re: [PATCH] OF: Add support for built in FDT blob
Date: Fri, 7 Nov 2014 13:59:31 +0100 [thread overview]
Message-ID: <20141107135931.376caf98@tock> (raw)
In-Reply-To: <20141107120933.GA5487@leverpostej>
On Fri, 7 Nov 2014 12:09:33 +0000
Mark Rutland <mark.rutland@arm.com> wrote:
> Hi,
>
> On Fri, Nov 07, 2014 at 11:14:09AM +0000, Alban Bedel wrote:
> > Allow embedding an FDT blob in the kernel image, this is mostly
> > useful to run new kernels on boards with old bootloaders.
>
> I am very much not keen on embedding a DTB within a kernel. It's far
> nicer for the two to remain separate blobs, with a small shim to set
> up the DTB address.
>
> On ARM we have appended DTB for this purpose, which is at least better
> than embedding the DT inside of the kernel.
I looked at that but that seemed quiet complicated to implement, not to
mention that it needed quiet a lot of arch specific code. On the other
hand having the DTB built in like this was trivial and would be portable
to every architecture, so that seemed like the best way to me.
> What architecture and bootloader are you using that necessitate this?
MIPS with an antic u-boot version patched by the board vendor to use
some non standard image format. Updating the boot loader is currently
not an option because of the lack of documentation for the board/SoC.
Alban
next prev parent reply other threads:[~2014-11-07 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 11:14 [PATCH] OF: Add support for built in FDT blob Alban Bedel
[not found] ` <1415358849-25879-1-git-send-email-albeu-GANU6spQydw@public.gmane.org>
2014-11-07 12:09 ` Mark Rutland
2014-11-07 12:59 ` Alban [this message]
2014-11-07 14:56 ` Rob Herring
[not found] ` <CAL_Jsq+n8owZz6yas=surm4fTaGWgUuCLLEKXYKm8_02S8DdYA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-07 16:47 ` Mark Rutland
2014-11-18 22:16 ` Grant Likely
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=20141107135931.376caf98@tock \
--to=albeu@free.fr \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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).