From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, paulus@samba.org
Subject: Re: [RFC] [PATCH 1/3] Merge mkimage tool for building uImages
Date: Thu, 20 Dec 2007 13:41:01 -0600 [thread overview]
Message-ID: <20071220134101.679d90cd@zod.rchland.ibm.com> (raw)
In-Reply-To: <476AB640.4040005@zytor.com>
On Thu, 20 Dec 2007 10:36:48 -0800
"H. Peter Anvin" <hpa@zytor.com> wrote:
> Josh Boyer wrote:
> > Several platforms require the mkimage tool to generate a uImage file
> > that is used with U-Boot. This brings the mkimage tool in-kernel to
> > enable building those platforms without having mkimage internally
> > provided.
> >
> > This is currently based off of the version found in U-Boot 1.3.1.
> >
>
> Can we rename it either "ubootimage" or "mkuboot" or something else that
> tells the user what kind of image it is? (It is, in particular, not
> bzImage, which is probably the first thing that someone who sees "image"
> in a arch-generic part of the Linux kernel tree will think.)
We can, yes. I have no particular objection to that and I've often
found mkimage to be too generic of a name myself. For the initial
round of patches, I just wanted to keep things as similar to what is
in U-Boot as possible.
josh
next prev parent reply other threads:[~2007-12-20 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 16:16 [RFC] Merge mkimage tool Josh Boyer
2007-12-20 16:17 ` [RFC] [PATCH 1/3] Merge mkimage tool for building uImages Josh Boyer
2007-12-20 18:36 ` H. Peter Anvin
2007-12-20 19:41 ` Josh Boyer [this message]
2007-12-20 16:18 ` [RFC] [PATCH 2/3] Rework arch specific Makefiles to use mkimage Josh Boyer
2007-12-21 1:02 ` Mike Frysinger
2007-12-21 1:20 ` Josh Boyer
2008-01-05 20:17 ` Sam Ravnborg
2007-12-20 16:19 ` [RFC] [PATCH 3/3] Remove mkuboot.sh script Josh Boyer
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=20071220134101.679d90cd@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®