Jerry Van Baren [EMAIL PROTECTED] wrote:
Haavard Skinnemoen wrote:
Haavard Skinnemoen [EMAIL PROTECTED] wrote:
That's a bit more than expected. Is this with or without --gc-sections?
Linking with --gc-sections should make simple_strtoull() go away unless
it's actually used.
That's
On Sunday 07 September 2008, Wolfgang Denk wrote:
5) Delete al references to CFG_64BIT_VSPRINTF and CFG_64BIT_STRTOUL
and unconditionally enable it for all boards.
Any takers to submit a patch?
If possible not because it will increase the size of u-boot for board
which not need
Matthias Fuchs [EMAIL PROTECTED] wrote:
Here is the U-Boot size for the PLU405 board (405EP-based) with
and without
#define CFG_64BIT_VSPRINTF
#define CFG_64BIT_STRTOUL
.
without:
# ppc_4xx-size u-boot
textdata bss dec hex filename
289568 17532 301312 608412
Haavard Skinnemoen [EMAIL PROTECTED] wrote:
That's a bit more than expected. Is this with or without --gc-sections?
Linking with --gc-sections should make simple_strtoull() go away unless
it's actually used.
That's assuming the fdt and image code doesn't interpret
CFG_64BIT_VSPRINTF as
Here is the U-Boot size for the PLU405 board (405EP-based) with
and without
#define CFG_64BIT_VSPRINTF
#define CFG_64BIT_STRTOUL
.
without:
# ppc_4xx-size u-boot
textdata bss dec hex filename
289568 17532 301312 608412 9489c u-boot
with 64bit format handling:
#
Dear Matthias,
in message [EMAIL PROTECTED] you wrote:
after testing the recent U-Boot code on a couple of 405EP boards I noticed,
that the memsize in the output of the bdinfo command is always 0x.
This is caused by using 64 types and format directives in printf that only
work
On 01:12 Sun 07 Sep , Wolfgang Denk wrote:
Dear Matthias,
in message [EMAIL PROTECTED] you wrote:
after testing the recent U-Boot code on a couple of 405EP boards I noticed,
that the memsize in the output of the bdinfo command is always 0x.
This is caused by using 64
Dear Jean-Christophe PLAGNIOL-VILLARD,
In message [EMAIL PROTECTED] you wrote:
5) Delete al references to CFG_64BIT_VSPRINTF and CFG_64BIT_STRTOUL
and unconditionally enable it for all boards.
Any takers to submit a patch?
If possible not because it will increase the size of u-boot for
Hi all,
after testing the recent U-Boot code on a couple of 405EP boards I noticed,
that the memsize in the output of the bdinfo command is always 0x.
This is caused by using 64 types and format directives in printf that only
work when CFG_64BIT_VSPRINTF is defined.
So what's the best
9 matches
Mail list logo