From: w@1wt.eu (Willy Tarreau)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Build a uImage with dtb already appended
Date: Thu, 15 Jan 2015 08:33:23 +0100 [thread overview]
Message-ID: <20150115073323.GB32460@1wt.eu> (raw)
In-Reply-To: <CAOesGMh8ZXt4fbw-AKOVWTQ8X5bVC8gEOhDFLroOYt+S43xBrA@mail.gmail.com>
Hi Olof,
On Wed, Jan 14, 2015 at 06:31:48PM -0800, Olof Johansson wrote:
> On Wed, Jan 14, 2015 at 6:08 PM, Christoph Junghans <ottxor@gentoo.org> wrote:
> > Add new targets to build zImage and uImage with DTB appended (i.e. make
> > 'uImage-dtb.am335x-bone' or 'make zImage-dtb.omap3-evm').
> >
> > Signed-off-by: Jeremy Kerr <jeremy.kerr@canonical.com>
> > Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> > Signed-off-by: Domenico Andreoli <domenico.andreoli@linux.com>
> > Signed-off-by: Christoph Junghans <ottxor@gentoo.org>
> > ---
> >
> > I don't know why this never got merged, but I think it is still useful.
>
> Maybe the patch description on the first version of the patch is a hint?
>
> https://lkml.org/lkml/2011/8/2/200
>
> In general, we're moving away from generating custom images straight
> out of the kernel build system. You should make that part of your
> installation scripts or similar instead.
FWIW, I *do* find this useful. My build scripts have to differ between
x86 and ARM only because of dtb. I would love to see this patch merged,
and anyway I'll add it to my own tree because it will simplify my build
process.
Thanks,
Willy
next prev parent reply other threads:[~2015-01-15 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 14:31 [PATCH] Build a uImage with dtb already appended Grant Likely
2011-08-02 15:33 ` [PATCH] fix for: " Nicolas Ferre
2012-06-29 20:39 ` [PATCH v2] Build a zImage or " Domenico Andreoli
2015-01-15 2:08 ` [PATCH] Build a " Christoph Junghans
2015-01-15 2:31 ` Olof Johansson
2015-01-15 7:33 ` Willy Tarreau [this message]
2015-01-15 10:45 ` Russell King - ARM Linux
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=20150115073323.GB32460@1wt.eu \
--to=w@1wt.eu \
--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).