All of lore.kernel.org
 help / color / mirror / Atom feed
From: Behan Webster <behanw@websterwood.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] In kernel mkimage
Date: Tue, 17 Jul 2007 11:29:40 -0400	[thread overview]
Message-ID: <469CE064.3010401@websterwood.com> (raw)
In-Reply-To: <200707171712.55768.sr@denx.de>

Stefan Roese wrote:
> Hi Behan,
>   
Hey Stefan.

> On Tuesday 17 July 2007, Behan Webster wrote:
>   
>> mkimage is used for building kernel images (and other related things
>> like ramdisk images).
>>     
>
> And it is being used for building other images too. Not only Linux kernel 
> images but other OS images (VxWorks, QNX, etc.), FPGA images, bitmaps and so 
> on. Everything related to U-Boot in a way. So the mkimage tool should at 
> least be available in the U-Boot source tree.
>   
I was unaware.

It was merely an idea to remove the "duplication of code" concern.


>> Lowering the barrier to entry to the use of u-boot (i.e. by allowing
>> kernels to be more easily built for it) will encourage more to use it.
>> More people using it will eventually lead to more people interested in
>> learning about the code.  It also cuts down on people asking a FAQ.
>>
>> It also puts a tool in the kernel tree which encourages others to use
>> u-boot as their boot loader. :)
>>
>> It's a win-win solution.
>>     
>
> I have to support you here, that it should be easier to "use" mkimage in the 
> Linux kernel generation. But completely removing it from the U-Boot source 
> doesn't make sense to me because of the reasons mentioned above.
>   
Indeed.

> The easiest change would be to add a make target to the U-Boot top-level 
> Makefile, for mkimage generation. This way the Linux "user" would at least 
> not have to worry about compiling U-Boot for a not needed platform.
>   
This is the easiest and a good first step.

However, I agree with Josh that it's still strange that this is
necessary step to build a kernel.

Of course, if mkimage is a seperable tool, then at the very least linux
distributions can start to package it as a seperate tool. This is
something that a lot of users have asked for from what I've seen.

If it is both easy to build mkimage by itself, and can be distributed as
a package for the various distros, then most of this issue goes away.

-- 
Behan Webster
behanw at websterwood.com

  reply	other threads:[~2007-07-17 15:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17  2:04 [U-Boot-Users] In kernel mkimage Josh Boyer
2007-07-17  9:19 ` Clemens Koller
2007-07-17 11:15   ` Josh Boyer
2007-07-17 14:27   ` Behan Webster
2007-07-17 15:12     ` Stefan Roese
2007-07-17 15:29       ` Behan Webster [this message]
2007-07-17 21:18         ` Josh Boyer
2007-07-17 21:37           ` Behan Webster
2007-07-18  2:24             ` 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=469CE064.3010401@websterwood.com \
    --to=behanw@websterwood.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.