From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target:device/Atmellinux
Date: Thu, 8 May 2008 21:58:34 +0200 [thread overview]
Message-ID: <006501c8b146$5e66c680$dfc4af0a@Glamdring> (raw)
In-Reply-To: d6cda7730805081116s4c3424e0yf1e468a72888bdde@mail.gmail.com
> It would still be possible to do that by choosing the custom config.
>
> You might have your reasons to want names with timestaps, but for most
> of us, it's nor required or desired. Forcing your way on everyone
> isn't quite the best approach.
>
I do not force this on anyone.
The linux kernel can be built in two ways.
The traditional way, which will build uImage etc.
and the "advanced" way, which I generated to allow me to build it the way I
see fit.
Select the traditional way, and you will get the traditional name.
I do not mind that there is an option to build it the traditional way,
but I do mind that it is implemented in such a way
that my way of doing things is no longer possible.
> As I've said before, changing the kernel name every time I build
> requires me to change u-boot, others will have to change their grub
> config, or what ever bootloader they use.
>
My U-Boot build generates an autoscript which is downloaded to the target
This allows AT91 users to configure the U-Boot environment from buildroot,
and allows them to initialize the environment with minimal typing.
- AND allows the user to figure out what is what.
You can easily change the name in the binaries dir before download
or propose a patch which will allow you to choose a simple name,
without changing the default behaviour.
config BR2_KERNEL_NAME_SIMPLE
bool "use simple kernel name"
default n
ifeq ($(BR2_KERNEL_NAME_SIMPLE),y)
LINUX26_KERNEL_NAME:=$(LINUX26_FORMAT)
else
LINUX26_KERNEL_NAME:=$(BOARD_NAME)-linux-$(LINUX26_VERSION)-$(DATE)$(KERNEL_EXT)
endif
(a little cleaned-up) would work for me, but Johns patch doesn't
because you will ALWAYS get a simple name if you choose
to build an uImage/vmlinux/zImage/bzImage.
It changes the default behaviour, and removes the possibility
to configure to default behaviour using easy options.
It is making one feature depend on another, and this restricts choice.
Best Regards
Ulf Samuelsson
prev parent reply other threads:[~2008-05-08 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 22:45 [Buildroot] svn commit: trunk/buildroot/target: device/Atmel linux ulf at uclibc.org
2008-05-08 14:43 ` Thiago A. Corrêa
2008-05-08 17:22 ` [Buildroot] svn commit: trunk/buildroot/target: device/Atmellinux Ulf Samuelsson
2008-05-08 18:16 ` Thiago A. Corrêa
2008-05-08 19:58 ` Ulf Samuelsson [this message]
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='006501c8b146$5e66c680$dfc4af0a@Glamdring' \
--to=ulf@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