From: "Thiago A. Corrêa" <thiago.correa@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Create /boot/uImage symlink to the currentkernel image
Date: Mon, 7 Jan 2008 14:41:42 -0200 [thread overview]
Message-ID: <d6cda7730801070841l4a5b1f6ahcbdbcb0bbbef2b87@mail.gmail.com> (raw)
In-Reply-To: <028e01c85141$ba1d0fd0$030514ac@atmel.com>
On Jan 4, 2008 11:45 AM, Ulf Samuelsson <ulf@atmel.com> wrote:
>
>
>
> | Hi,
> |
> | A while ago, the kernel naming have been changed to include $(DATE)
> | which makes it annoying to keep track. This patch adds an option to
> | the Advanced Kernel option to create an /boot/uImage symbolic link to
> | the built kernel. Please consider applying, this really improves
> | usability, if this naming scheme is to be kept.
> |
> | Kind Regards,
> | Thiago A. Correa
> |
>
> Looking at your patch, I see that we are talking about two different things.
> There is a feature to copy the linux kernel to /tftpboot directory,
> which I thought you were referring to, but If you want the kernel inside
> the root file system, then would it not make more sense to do:
>
> - cp -dpf $(LINUX26_KERNEL) $(TARGET_DIR)/boot/$(LINUX26_KERNEL_NAME)
> + cp -dpf $(LINUX26_KERNEL) $(TARGET_DIR)/boot/$(BR2_PACKAGE_LINUX_FORMAT)
>
> where BR2_PACKAGE_LINUX_FORMAT could be
> uImage, bzImage, vmlinux etc.
>
> Best Regards
> Ulf Samuelsson
>
Yes, that was the previous behavior, although perhaps not exactly the
same code, I haven't checked the svn logs to see how it was before.
Anyway, since I'm not sure why it changed in the first place, I
suggested the symlinking as an option.
Regards,
Thiago A. Correa
prev parent reply other threads:[~2008-01-07 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 0:50 [Buildroot] [PATCH] Create /boot/uImage symlink to the current kernel image Thiago A. Corrêa
[not found] ` <00fc01c84eb0$07a3e010$0a0514ac@atmel.com>
2008-01-04 12:59 ` [Buildroot] [PATCH] Create /boot/uImage symlink to the currentkernel image Thiago A. Corrêa
2008-01-04 13:45 ` Ulf Samuelsson
2008-01-07 16:41 ` Thiago A. Corrêa [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=d6cda7730801070841l4a5b1f6ahcbdbcb0bbbef2b87@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