From: Stephen Warren <swarren@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 3/3] image: Allow images to indicate they're loadable at any address
Date: Tue, 08 Nov 2011 11:17:24 -0700 [thread overview]
Message-ID: <4EB97234.4000800@nvidia.com> (raw)
In-Reply-To: <20111108115053.3ED0413BE0C1@gemini.denx.de>
(resending due to MIME encoding last time; sorry)
On 11/08/2011 04:50 AM, Wolfgang Denk wrote:
> Dear Marek Vasut,
>
> In message <201111081235.05464.marek.vasut@gmail.com> you wrote:
>>
>> Ok, so guys ... let me ask a stupid question:
>
> Not a stupid question at all.
>
>> Will it be a problem to extend bootm (if not already done) to load zImages
>> directly, with -z option for example ? Won't that satisty both parties --
I originally thought about a bootz command or extending bootm to support
zImages. It looked like coding that up would be significantly more
complex and invasive than extending uImages to support relative or
unspecified load addresses, and hence I naively imagined that such
patches were far more likely to be accepted. It's evident that I was
very wrong in that assessment.
> bootm is for uImage format. I see no sense in "extending" it.
bootm already supports two completely different formats; legacy uImage
and FIT images. To me, it seems logical to simply add support for a
third image format for the kernel at least. Do you completely disagree
with this? Well, bootm would need to recognize raw (non-uImage-wrapped)
initrd and FDT blobs too, since currently bootm expects everything to be
uImage-wrapped.
> I already suggested to add a new command ("bootz" ?) that could be
> used to boot zImage files.
One potential advantage of extending bootz to recognize zImage directly
would be the re-use of the overall bootm flow and arch functions such as
arch/arm/lib/bootm.c:do_bootm_linux(). I /think/ that creating a new
separate bootz command would require duplicating a lot of code and might
make re-using do_bootm_linux() more complex, although again I'd need to
look at the code in more detail to say for sure.
Are you willing to entertain extending bootm to recognize a third image
format if this makes the patches less invasive, and/or leads to more
maintainable code?
--
nvpublic
next prev parent reply other threads:[~2011-11-08 18:17 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 16:28 [U-Boot] [PATCH v2 1/3] image: Make image_get_fdt work like image_get_{ram_disk, kernel} Stephen Warren
2011-11-01 16:28 ` [U-Boot] [PATCH v2 2/3] image: Support FDTs already loaded at their load address Stephen Warren
2012-03-06 21:18 ` Wolfgang Denk
2011-11-01 16:28 ` [U-Boot] [PATCH v2 3/3] image: Allow images to indicate they're loadable at any address Stephen Warren
2011-11-05 22:20 ` Wolfgang Denk
2011-11-07 16:56 ` Stephen Warren
2011-11-07 17:09 ` Stephen Warren
2011-11-07 19:47 ` Simon Glass
2011-11-07 20:29 ` Wolfgang Denk
2011-11-07 21:17 ` Stephen Warren
2011-11-07 22:11 ` Wolfgang Denk
2011-11-07 22:30 ` Stephen Warren
2011-11-07 23:08 ` Wolfgang Denk
2011-11-08 0:00 ` Stephen Warren
2011-11-08 0:27 ` Wolfgang Denk
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF173F9A5035@HQMAIL01.nvidia.com>
2011-11-07 20:26 ` Wolfgang Denk
2011-11-07 21:04 ` Marek Vasut
2011-11-07 21:38 ` Stephen Warren
2011-11-07 21:59 ` Marek Vasut
2011-11-07 22:08 ` Stephen Warren
2011-11-07 22:27 ` Wolfgang Denk
2011-11-07 22:41 ` Stephen Warren
2011-11-07 23:10 ` Wolfgang Denk
2011-11-07 23:43 ` Stephen Warren
2011-11-07 22:57 ` Nicolas Pitre
2011-11-07 23:25 ` Wolfgang Denk
2011-11-08 0:10 ` Stephen Warren
2011-11-08 0:29 ` Wolfgang Denk
2011-11-08 0:48 ` Nicolas Pitre
2011-11-08 8:38 ` Wolfgang Denk
2011-11-08 11:35 ` Marek Vasut
2011-11-08 11:50 ` Wolfgang Denk
2011-11-08 11:52 ` Marek Vasut
2011-11-08 18:17 ` Stephen Warren [this message]
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF173F9A5424@HQMAIL01.nvidia.com>
2011-11-08 19:44 ` Wolfgang Denk
2011-11-08 21:17 ` Wolfgang Denk
2011-11-08 22:27 ` Stephen Warren
2011-11-08 22:46 ` Wolfgang Denk
2011-11-08 0:35 ` Nicolas Pitre
2011-11-08 1:10 ` Simon Glass
2011-11-08 3:51 ` Nicolas Pitre
2011-11-08 5:37 ` Simon Glass
2011-11-08 8:45 ` Wolfgang Denk
2011-11-08 14:22 ` Loïc Minier
2011-11-08 14:52 ` Jason
2011-11-08 20:18 ` Nicolas Pitre
2011-12-10 22:42 ` Linus Walleij
2011-12-10 22:53 ` Wolfgang Denk
2011-12-10 23:21 ` Linus Walleij
2011-12-12 16:25 ` Stephen Warren
2011-11-08 8:33 ` Wolfgang Denk
2011-11-08 14:26 ` Nicolas Pitre
2011-11-08 15:01 ` Marek Vasut
2011-11-08 15:59 ` Wolfgang Denk
2011-11-08 16:57 ` Detlev Zundel
2011-11-08 20:05 ` Nicolas Pitre
2011-11-07 21:27 ` Stephen Warren
2011-11-07 21:41 ` Nicolas Pitre
2011-11-07 22:42 ` Wolfgang Denk
2011-11-05 18:41 ` [U-Boot] [PATCH v2 1/3] image: Make image_get_fdt work like image_get_{ram_disk, kernel} Marek Vasut
2011-11-05 19:21 ` Simon Glass
2011-11-05 19:39 ` Marek Vasut
2011-11-05 20:38 ` Simon Glass
2011-11-05 20:41 ` Marek Vasut
2011-11-05 20:49 ` Simon Glass
2011-11-05 22:15 ` Wolfgang Denk
2011-11-05 22:18 ` Marek Vasut
2011-11-05 22:06 ` Wolfgang Denk
2011-11-05 21:53 ` Wolfgang Denk
2011-11-05 22:06 ` Marek Vasut
2011-11-05 22:22 ` Wolfgang Denk
2011-11-06 4:52 ` Simon Glass
2011-11-06 8:57 ` Wolfgang Denk
2011-11-05 21:40 ` Wolfgang Denk
2011-11-05 22:06 ` Marek Vasut
2011-11-05 22:24 ` Wolfgang Denk
2011-11-05 22:38 ` Marek Vasut
2011-11-08 14:24 ` Loïc Minier
2011-11-08 16:06 ` Wolfgang Denk
2011-11-08 18:15 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF173F9A5415@HQMAIL01.nvidia.com>
2011-11-08 19:33 ` Wolfgang Denk
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=4EB97234.4000800@nvidia.com \
--to=swarren@nvidia.com \
--cc=u-boot@lists.denx.de \
/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