Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Create /boot/uImage symlink to the currentkernel image
Date: Fri, 4 Jan 2008 14:45:54 +0100	[thread overview]
Message-ID: <028e01c85141$ba1d0fd0$030514ac@atmel.com> (raw)
In-Reply-To: d6cda7730801031650i439f5821h566eeef460615172@mail.gmail.com



| 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

  parent reply	other threads:[~2008-01-04 13:45 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 [this message]
2008-01-07 16:41   ` Thiago A. Corrêa

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='028e01c85141$ba1d0fd0$030514ac@atmel.com' \
    --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