Re: [U-Boot] CFG_64BIT_xxx and friends

2008-09-09 Thread Haavard Skinnemoen
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

Re: [U-Boot] CFG_64BIT_xxx and friends

2008-09-08 Thread Stefan Roese
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

Re: [U-Boot] CFG_64BIT_xxx and friends

2008-09-08 Thread Haavard Skinnemoen
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

Re: [U-Boot] CFG_64BIT_xxx and friends

2008-09-08 Thread Haavard Skinnemoen
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

Re: [U-Boot] CFG_64BIT_xxx and friends

2008-09-08 Thread Matthias Fuchs
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: #

Re: [U-Boot] CFG_64BIT_xxx and friends

2008-09-06 Thread Wolfgang Denk
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

Re: [U-Boot] CFG_64BIT_xxx and friends

2008-09-06 Thread Jean-Christophe PLAGNIOL-VILLARD
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

Re: [U-Boot] CFG_64BIT_xxx and friends

2008-09-06 Thread Wolfgang Denk
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

[U-Boot] CFG_64BIT_xxx and friends

2008-09-04 Thread Matthias Fuchs
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