From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3 1/2] linux: add option to explicitly specify the kernel image name
Date: Tue, 15 Jul 2014 22:20:29 +0200 [thread overview]
Message-ID: <20140715222029.32f336dd@free-electrons.com> (raw)
In-Reply-To: <20140711124922.GA25220@waldemar-brodkorb.de>
Dear Waldemar Brodkorb,
On Fri, 11 Jul 2014 14:49:22 +0200, Waldemar Brodkorb wrote:
> For example the upcoming qemu-xtensa patch is using this feature,
> where the target is called "zImage", but the resulting kernel name
> is "Image.elf".
>
> ---
> Changes v2 -> v3:
> - improve subject (suggested by Thomas P.)
> - LINUX_IMAGE_NAME defaults to LINUX_TARGET_NAME (suggested by Yann)
> - improve help text (suggested by Yann)
> Changes v1 -> v2:
> - add comment about default value (suggested by Arnout)
> - reorder default value for LINUX_TARGET_NAME (suggested by Arnout)
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> linux/Config.in | 10 ++++++++++
> linux/linux.mk | 10 +++++++---
> 2 files changed, 17 insertions(+), 3 deletions(-)
Thanks, I've applied this patch and the one adding the qemu
xtensa defconfig. However, regarding this second one, I'd really like
to see a followup patch adding a way of downloading the toolchain
overlay file, instead of having it inside Buildroot.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-15 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 12:49 [Buildroot] [PATCHv3 1/2] linux: add option to explicitly specify the kernel image name Waldemar Brodkorb
2014-07-15 19:34 ` Yann E. MORIN
2014-07-15 20:20 ` Thomas Petazzoni [this message]
2014-07-16 23:01 ` Sagaert Johan
2014-07-17 15:29 ` [Buildroot] [PATCHv3 1/2] linux: add option to explicitlyspecify the kernel image name : breaks kernel build ! Sagaert Johan
2014-07-17 20:58 ` Thomas Petazzoni
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=20140715222029.32f336dd@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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