[U-Boot-Users] [PATCH 00/13] new uImage patchset1 - cleanup

Marian Balakowicz
2008-01-15T10:06:59Z

Wolfgang Denk wrote:
> In message <20080111142744.8025.82931.stgit@hekate.izotz.org> you wrote:
>> This is a first set of patches that provides a initial cleanup and code
>> rearrangements before the proper new uImage format implementation.
>>
>> API is defined for the current (old) image related processing, and it'is being
>> introduced in place of the direct header access.
>
> Can you please comment a bit about the current state of these patches?
>
> Is this just a RFC, or tested code?

It has been tested on lite5200b board. Tests covering bootm (single na
multi component images), autoscr, iminfo, imls.

> Does the code compile? For which boards / architectures?

Yes, it does. MAKEALL builds were run for ppc, mips, arm and coldfire
(although not all targets, as some of them are broken in the baseline
code). I have also attempted to build on i386, but the i386 target
builds are broken as well, I have just verified that modified files do
compile. Other architectures were skipped due to lack of the toolchains.

It would be good if other architecture maintainers could help testing
new uImage patches, as the changes are cross platform. Another good
verification would be booting OS other than linux. But, as there are
more significant changes coming, it may have more sens to wait with
the detailed tests until crucial modifications are finished.

> How much does it change the memory footprint?

Here is the build output for lite5200b_LOWBOOT configuration and with
the patches applied:

text data bss dec hex filename
222739 13120 305152 541011 84153 ./u-boot

Note, that patches enable DEBUG in do_bootm() and PPC variant of
do_bootm_linux(), with those disabled we get:

text data bss dec hex filename
222011 13080 305152 540243 83e53 ./u-boot

and the same configuration build for the 1.3.1 baseline:

text data bss dec hex filename
221463 13040 305408 539911 83d07 ./u-boot

Best Regards,
Marian