* [U-Boot-Users] RFC: New uImage format bindings
@ 2007-12-19 14:11 Marian Balakowicz
2007-12-19 14:50 ` Darcy Watkins
0 siblings, 1 reply; 2+ messages in thread
From: Marian Balakowicz @ 2007-12-19 14:11 UTC (permalink / raw)
To: u-boot
Hi,
Attaches is a draft of proposed bindings for New uImage format.
It's a early RFC, please review and comment.
Cheers,
Marian
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: New-uImage-format.txt
Url: http://lists.denx.de/pipermail/u-boot/attachments/20071219/c7092c83/attachment.txt
^ permalink raw reply [flat|nested] 2+ messages in thread
* [U-Boot-Users] RFC: New uImage format bindings
2007-12-19 14:11 [U-Boot-Users] RFC: New uImage format bindings Marian Balakowicz
@ 2007-12-19 14:50 ` Darcy Watkins
0 siblings, 0 replies; 2+ messages in thread
From: Darcy Watkins @ 2007-12-19 14:50 UTC (permalink / raw)
To: u-boot
Hello,
I like the idea, but I think that the FTD blob for a specific board
should normally reside on that board somewhere alongside the U-Boot
image itself. This should be part of the board support package for the
board. Having it in the uImage optionally helps when you want to
override what is in the board itself, but having the FDT blob normally
be part of the U-Boot board support allows one new style uImage to be
able to run on any member of a whole family of compatible boards (e.g.
different populated variants such as amount of memory, peripherals, etc
- this info per variant is entered into the FDT blob for the board's
variant).
There also needs to be provision for a "requires" type verb. For
example, the new uImage blob with a kernel could have "requires
PPC405EP" if it has been built with chip specific optimizations
compatible only with PPC405EP. If it is loaded onto a PPC405GP based
board, the U-Boot could detect the incompatibility and issue an error
message instead of try to boot the incompatible kernel. This could also
be used as part of auto selection amongst multiple kernel images if each
image is so tagged and there is also an order of preference (and implied
fallback order).
The 'requires' verb could also be used for a lot of other cool stuff
(e.g. firmware image upgrade / backout schemes), but I think we should
keep it simple, first focusing on what is needed to make boot / no-boot
decisions and perhaps selection of boot arguments.
Regards,
Darcy
--snip!--
Attaches is a draft of proposed bindings for New uImage format.
It's a early RFC, please review and comment.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-12-19 14:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-12-19 14:11 [U-Boot-Users] RFC: New uImage format bindings Marian Balakowicz
2007-12-19 14:50 ` Darcy Watkins
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.