Re: [PATCH 2/3] Kbuild: Implement CONFIG_UIMAGE_KERNEL_NOLOAD |
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH 2/3] Kbuild: Implement CONFIG_UIMAGE_KERNEL_NOLOAD
- From: Stephen Warren <swarren@xxxxxxxxxxxxx>
- Date: Wed, 07 Mar 2012 11:40:18 -0700
- Cc: Michal Marek <mmarek@xxxxxxx>, linux-arch@xxxxxxxxxxxxxxx, Michal Simek <monstr@xxxxxxxxx>, Guan Xuetao <gxt@xxxxxxxxxxxxxxx>, Mike Frysinger <vapier@xxxxxxxxxx>, nico@xxxxxxxxxxx, linux-sh@xxxxxxxxxxxxxxx, microblaze-uclinux@xxxxxxxxxxxxxx, linux-kbuild@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Paul Mundt <lethal@xxxxxxxxxxxx>, uclinux-dist-devel@xxxxxxxxxxxxxxxxxxxx, sparclinux@xxxxxxxxxxxxxxx, Russell King <linux@xxxxxxxxxxxxxxxx>, Haavard Skinnemoen <hskinnemoen@xxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxxxxx>, linux-arm-kernel@xxxxxxxxxxxxxxxxxxx, Hans-Christian Egtvedt <egtvedt@xxxxxxxxxxxx>
- In-reply-to: <20120307180815.GA27213@game.jcrosoft.org>
- References: <1331080238-1524-1-git-send-email-swarren@wwwdotorg.org> <1331080238-1524-2-git-send-email-swarren@wwwdotorg.org> <20120307180815.GA27213@game.jcrosoft.org>
- User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
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@xxxxxxxxxxxxx>
>> ---
>> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Linux USB Devel]
[Linux Media]
[Video for Linux]
[Linux Audio Users]
[Photo]
[Yosemite News]
[Yosemite Photos]
[Free Online Dating]
[Linux Kernel]
[Linux SCSI]
[XFree86]