Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] What's up with the kernel names? (Again)
Date: Thu, 05 Feb 2009 21:23:52 +0100	[thread overview]
Message-ID: <1233865432.4148.6.camel@elrond.atmel.com> (raw)
In-Reply-To: <873aeue676.fsf@macbook.be.48ers.dk>

ons 2009-02-04 klockan 13:29 +0100 skrev Peter Korsgaard:
> >>>>> "Thiago" == Thiago A Corr?a <thiago.correa@gmail.com> writes:
> 
>  Thiago> Hi,
>  Thiago>     I thought it was seattled sometime last year that kernel names
>  Thiago> would not include timestamps or any think that breaks u-boot from
>  Thiago> loading the kernel.
> 
>  Thiago>     I just had atngw100-linux-2.6.27.13-20090203.gz for a kernel name.
>  Thiago> It's already bad enough that rootfs has stupid timestamps, we don't
>  Thiago> really need kernel binaries too. If I wanted to preserve binaries, I
>  Thiago> would copy them over before building again. Whenever I type make, I
>  Thiago> expect things to be overwritten.
> 
> The rootfs timestamp is because your defconfig sets the
> BR2_ROOTFS_SUFFIX to a nonstandard value.
> 
> I had a look at target/linux/Makefile.in.advanced and see that it
> uses:
> 
> LINUX26_KERNEL:=$(BINARIES_DIR)/$(BOARD_NAME)-linux-$(LINUX26_VERSION)-$(DATE)$(KERNEL_EXT)
> 
> whereas the normal (!advanced) Linux config uses:
> 
> LINUX26_KERNEL:=$(BINARIES_DIR)/linux-kernel-$(LINUX26_VERSION)-$(KERNEL_ARCH)
> 
> To me the sane thing would just be for the files to be named whatever
> the kernel names them (uImage/zImage/bzImage/..), but even if we don't
> do that we should atleast make the 2 Linux types use the same style.

> 
> We can add BR2_KERNEL_PREFIX/SUFFIX (defaulting to "") if people
> really to do something special.
> 
> Ulf, what do you say?
> 

I think that we should have a symbolic link to xImage as we do for
u-boot.bin for those that do not like the more complex filenames.
Then there is no need for a 

The purpose of having a more complex file name is to
be able to see which kernel you have and it configuration.
Also to be able to copy multiple kernels for multiple chips to a single
directory - Typically /tftpboot.

uImage really does not give you *any* information on the contents.

When testing several configurations for the same kernel,
adding some kind of revision information is important.
THat is why the date is there, a little simplistic, but
it works for me.


> -- 
> Bye, Peter Korsgaard
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  parent reply	other threads:[~2009-02-05 20:23 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04  1:49 [Buildroot] What's up with the kernel names? (Again) Thiago A. Corrêa
2009-02-04  7:39 ` Peter Korsgaard
2009-02-04 12:29 ` Peter Korsgaard
2009-02-05  2:33   ` Thiago A. Corrêa
2009-02-05 13:23     ` Peter Korsgaard
2009-02-05 20:37       ` Ulf Samuelsson
2009-02-06  2:28         ` Thiago A. Corrêa
2009-02-06  6:16           ` Ulf Samuelsson
2009-02-06  8:49             ` Peter Korsgaard
2009-02-06  9:06               ` Ulf Samuelsson
2009-02-06 12:30                 ` Peter Korsgaard
2009-02-06  8:45           ` Peter Korsgaard
2009-02-06  8:58             ` Ulf Samuelsson
2009-02-06  8:44         ` Peter Korsgaard
2009-02-05 20:23   ` Ulf Samuelsson [this message]
2009-02-06  8:41     ` Peter Korsgaard
2009-02-06  8:56       ` Ulf Samuelsson
2009-02-06 12:27         ` Peter Korsgaard
2009-02-06 14:31         ` Thiago A. Corrêa
2009-02-06 15:18           ` Thiago A. Corrêa
2009-02-09 17:24           ` Ulf Samuelsson
2009-02-09 19:34             ` Peter Korsgaard
2009-02-09 22:52               ` Ulf Samuelsson
2009-02-10  1:25                 ` Thiago A. Corrêa
2009-02-10  8:02                   ` Ulf Samuelsson
2009-02-10  9:28                     ` Peter Korsgaard
2009-02-10 10:32                       ` Ulf Samuelsson
2009-02-10  9:17                 ` Peter Korsgaard
2009-02-10 10:16                   ` Ulf Samuelsson
2009-02-10 12:51                     ` Peter Korsgaard
2009-02-10 13:50                       ` Ulf Samuelsson
2009-02-10 16:34                         ` Thiago A. Corrêa
2009-02-10 17:17                           ` Thiago A. Corrêa
2009-02-10 17:42                             ` Ulf Samuelsson
2009-02-10 18:48                               ` Thiago A. Corrêa
2009-02-11 20:03                                 ` Ulf Samuelsson
2009-02-11 20:15                                   ` Peter Korsgaard
2009-02-12 18:16                                     ` Ulf Samuelsson
2009-02-16 22:21                                       ` Thiago A. Corrêa
2009-02-17 11:26                                         ` Peter Korsgaard
2009-02-10 18:26                           ` Ulf Samuelsson
2009-02-10 18:50                           ` Ulf Samuelsson
2009-02-10 20:06                             ` Thiago A. Corrêa
2009-02-10 18:59                           ` Ulf Samuelsson
2009-02-10 19:49                           ` Ulf Samuelsson
2009-02-10 20:06                             ` Peter Korsgaard

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=1233865432.4148.6.camel@elrond.atmel.com \
    --to=ulf.samuelsson@atmel.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