From: "Thiago A. Corrêa" <thiago.correa@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] What's up with the kernel names? (Again)
Date: Fri, 6 Feb 2009 00:28:01 -0200 [thread overview]
Message-ID: <d6cda7730902051828if9915d3u31cf79bf5a68fcac@mail.gmail.com> (raw)
In-Reply-To: <1233866252.4148.12.camel@elrond.atmel.com>
On Thu, Feb 5, 2009 at 6:37 PM, Ulf Samuelsson <ulf.samuelsson@atmel.com> wrote:
>> Thiago> It will use the rootfs suffix if one is specified for the kernel, but
>> Thiago> if none is supplied, we get default kernel names. Then you can get
>> Thiago> both rootfs and kernel with your board names, dates, etc. And both
>> Thiago> rootfs and kernel names will always match.
>>
>
>
> And you have no clue about the kernel version.
> And you have to modify the suffix for every project.
> Much better to just create the link to uImage etc.
>
> Then you have both.
But if you use the rootfs suffix, not only you have both, but you also
can disable it.
Following your argument, I might just as well want to have rootfs in
/tftpboot, and if the names match (same suffix) then I know which
kernel is inside each rootfs image.
The $(DATE) seams to be default to rootfs suffix already, all you have
to do is change it per project to include the project or board name.
You have to touch your projects at some point to change things anyway,
otherwise they would always build the same thing, so that's not a very
good argument against.
You can have the same functionality as before, but with added flexibility.
I'm just trying to test it out before commiting. Since I can't build
my usual platform, avr32, I'm giving arm a try.
Kind Regards,
Thiago A. Correa
next prev parent reply other threads:[~2009-02-06 2:28 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 [this message]
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
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=d6cda7730902051828if9915d3u31cf79bf5a68fcac@mail.gmail.com \
--to=thiago.correa@gmail.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