From: Stephen Warren <swarren@wwwdotorg.org>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: Michal Marek <mmarek@suse.cz>,
linux-arch@vger.kernel.org, Michal Simek <monstr@monstr.eu>,
Guan Xuetao <gxt@mprc.pku.edu.cn>,
Mike Frysinger <vapier@gentoo.org>,
nico@fluxnic.net, linux-sh@vger.kernel.org,
microblaze-uclinux@itee.uq.edu.au, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, Paul Mundt <lethal@linux-sh.org>,
uclinux-dist-devel@blackfin.uclinux.org,
sparclinux@vger.kernel.org, Russell King <linux@arm.linux.org.uk>,
Haavard Skinnemoen <hskinnemoen@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org,
Hans-Christian Egtvedt <egtvedt@samfundet.no>
Subject: Re: [PATCH 2/3] Kbuild: Implement CONFIG_UIMAGE_KERNEL_NOLOAD
Date: Wed, 07 Mar 2012 11:40:18 -0700 [thread overview]
Message-ID: <4F57AB92.6060907@wwwdotorg.org> (raw)
In-Reply-To: <20120307180815.GA27213@game.jcrosoft.org>
On 03/07/2012 11:08 AM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> 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/
No, the whole point of this type of kernel image is that it doesn't need
a specific load address; the kernel zImage can run from anywhere in RAM
(provided AUTO_ZRELADDR is enabled, subject to some slight
restrictions), and hence the uImage doesn't need to be loaded to or
moved to any particular location.
The scripts that U-Boot runs determine where the image gets loaded into
memory.
> And this no the job of the kernel to build a boot loader specific boot image
> format.
Not everyone agrees with this.
> 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. The last time I heard anyone talk about that, it sounded like the
adoption was basically zero, so it seems pointless. Personally, I find
creating that kind of image more complex, and don't see any benefits in
that format either.
> 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.
U-Boot does not currently have the ability to boot zImage on ARM.
> Further more on server the vendor will use grub mostly (even on ARM) and will
> expect to boot a zImage.
But that is irrelevant for the people who are using U-Boot not grub.
next prev parent reply other threads:[~2012-03-07 18:40 UTC|newest]
Thread overview: 38+ 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 ` Stephen Warren
2012-03-07 0:30 ` [PATCH 2/3] Kbuild: Implement CONFIG_UIMAGE_KERNEL_NOLOAD Stephen Warren
2012-03-07 0:30 ` Stephen Warren
2012-03-07 0:52 ` Julian Calaby
2012-03-07 0:52 ` Julian Calaby
[not found] ` <1331080238-1524-2-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-03-07 6:52 ` [microblaze-linux] " Guan Xuetao
2012-03-07 6:52 ` Guan Xuetao
2012-03-07 18:10 ` Stephen Warren
2012-03-07 18:08 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-07 18:08 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-07 18:40 ` Stephen Warren [this message]
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: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:40 ` Stephen Warren
2012-03-07 18:50 ` Nicolas Pitre
2012-03-07 19:08 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-07 19:08 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-07 19:31 ` Nicolas Pitre
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 0:30 ` Stephen Warren
2012-03-07 3:56 ` [PATCH 1/3] Kbuild: centralize MKIMAGE and cmd_uimage definitions Mike Frysinger
2012-03-07 3:56 ` Mike Frysinger
2012-03-07 17:41 ` Stephen Warren
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 9:00 ` Hans-Christian Egtvedt
2012-03-07 14:15 ` Josh Boyer
2012-03-07 18:29 ` Stephen Warren
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=4F57AB92.6060907@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=davem@davemloft.net \
--cc=egtvedt@samfundet.no \
--cc=gxt@mprc.pku.edu.cn \
--cc=hskinnemoen@gmail.com \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=mmarek@suse.cz \
--cc=monstr@monstr.eu \
--cc=nico@fluxnic.net \
--cc=plagnioj@jcrosoft.com \
--cc=sparclinux@vger.kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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).