From: plagnioj@jcrosoft.com (Jean-Christophe PLAGNIOL-VILLARD)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] Kbuild: Implement CONFIG_UIMAGE_KERNEL_NOLOAD
Date: Wed, 7 Mar 2012 19:08:15 +0100 [thread overview]
Message-ID: <20120307180815.GA27213@game.jcrosoft.org> (raw)
In-Reply-To: <1331080238-1524-2-git-send-email-swarren@wwwdotorg.org>
On 17:30 Tue 06 Mar , Stephen Warren wrote:
> This allows the user to use U-Boot's mkimage's -T kernel_noload option
> if their arch Kconfig allows it, and they desire.
>
> Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
> ---
> The next patch enables this new CONFIG_ALLOW_ option for ARM. I assume
> that some other architectures will also be able to enable it, but I'm
> not familiar enough with any to know which.
I'm going to repeat. I don't think any impromevent here.
with no specific kernel load address the uImage for is useless/
And this no the job of the kernel to build a boot loader specific boot image
format.
And the uImage format here is called the legacy format where now U-Boot
support a new format based on DT format.
Will you plan to add it too?
no sorry I don't think it's the right way to go.
On X86 we boot zImage simply. The new uImage option to do not specify the load
address add nothing more than just boot a zImage for kernel point of view.
Further more on server the vendor will use grub mostly (even on ARM) and will
expect to boot a zImage.
Best Regards,,
J.
next prev parent reply other threads:[~2012-03-07 18:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 0:30 [PATCH 1/3] Kbuild: centralize MKIMAGE and cmd_uimage definitions Stephen Warren
2012-03-07 0:30 ` [PATCH 2/3] Kbuild: Implement CONFIG_UIMAGE_KERNEL_NOLOAD Stephen Warren
2012-03-07 0:52 ` Julian Calaby
2012-03-07 6:52 ` Guan Xuetao
2012-03-07 18:10 ` Stephen Warren
2012-03-07 18:08 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2012-03-07 18:40 ` Stephen Warren
2012-03-07 18:36 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-07 19:02 ` Nicolas Pitre
2012-03-07 20:27 ` Stephen Warren
2012-03-07 21:03 ` Nicolas Pitre
2012-03-07 21:30 ` Russell King - ARM Linux
2012-03-07 22:43 ` Nicolas Pitre
2012-03-07 21:28 ` Russell King - ARM Linux
2012-03-07 18:50 ` Nicolas Pitre
2012-03-07 19:08 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-07 19:31 ` Nicolas Pitre
2012-03-07 0:30 ` [PATCH 3/3] ARM: Allow the user to enable UIMAGE_KERNEL_NOLOAD Stephen Warren
2012-03-07 3:56 ` [PATCH 1/3] Kbuild: centralize MKIMAGE and cmd_uimage definitions Mike Frysinger
2012-03-07 17:41 ` Stephen Warren
2012-03-07 18:25 ` Mike Frysinger
2012-03-07 9:00 ` Hans-Christian Egtvedt
2012-03-07 14:15 ` Josh Boyer
2012-03-07 18:29 ` Stephen Warren
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=20120307180815.GA27213@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).