CUSTODIANS: Urgent boarding call for flight 2009.03
Hi Custodians (and everybody else),
can you please check if all urgent patches have been added to the U-Boot master branch?
If anything should still be missing, please respond *now*.
My intention is to push out the 2009.03 release on schedule, i. e. on Saturday, March 21, 2009.
At the moment I am not planning for another release candidate.
Note: after the release is out, I will merge the current "next" branch into "master", so this will be the starting point for the next merge window.
Thanks.
Best regards,
Wolfgang Denk
Signature · 6 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de "There are three principal ways to lose money: wine, women, and en- gineers. While the first two are more pleasant, the third is by far the more certain." -- Baron Rothschild, ca. 1800
Hello Wolfgang,
Quoted 7 lines · Wolfgang Denk
Hi Custodians (and everybody else),
can you please check if all urgent patches have been added to the U-Boot master branch?
If anything should still be missing, please respond *now*.
I miss the following patchseries:
http://lists.denx.de/pipermail/u-boot/2009-March/048916.html
bye
Heiko
Signature · 2 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Dear Heiko Schocher,
Quoted 4 lines · In message <[email protected]> you wrote:
I miss the following patchseries:
http://lists.denx.de/pipermail/u-boot/2009-March/048916.html
Thanks for pointing out (I though this was for "next").
Best regards,
Wolfgang Denk
Signature · 4 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de How come everyone's going so slow if it's called rush hour?
Hi Wolfgang,
Microblaze code is OK - without build errors.
Thanks,
Michal
Quoted 24 lines · Wolfgang Denk
Hi Custodians (and everybody else),
can you please check if all urgent patches have been added to the U-Boot master branch?
If anything should still be missing, please respond *now*.
My intention is to push out the 2009.03 release on schedule, i. e. on Saturday, March 21, 2009.
At the moment I am not planning for another release candidate.
Note: after the release is out, I will merge the current "next" branch into "master", so this will be the starting point for the next merge window.
Thanks.
Best regards,
Wolfgang Denk
[U-Boot] MIPS build status (Re: CUSTODIANS: Urgent boarding call for flight 2009.03)
In reply to Wolfgang DenkHello,
Quoted 7 lines · Wolfgang Denk
If anything should still be missing, please respond *now*.
My intention is to push out the 2009.03 release on schedule, i. e. on Saturday, March 21, 2009.
At the moment I am not planning for another release candidate.
* With GCC 4.2.3, all MIPS targets builds fine without any errors. MAKEALL output is attached.
* But with GCC 4.3.2, you would see hundreds of bitops.h warnings. Besides, some could be compiled (gth2, etc.), but some failed (qemu_mips, etc.). Bitops.h warnings are as follows:
In file included from /home/skuribay/git/u-boot.git/include/linux/bitops.h:69,
from /home/skuribay/git/u-boot.git/include/common.h:36,
from qemu-mips.c:24:/home/skuribay/git/u-boot.git/include/asm/bitops.h: In function 'ext2_find_next_zero_bit':/home/skuribay/git/u-boot.git/include/asm/bitops.h:862: warning: '__fswab32' is static but used in inline function 'ext2_find_next_zero_bit' which is not static /home/skuribay/git/u-boot.git/include/asm/bitops.h:885: warning: '__fswab32' is static but used in inline function 'ext2_find_next_zero_bit' which is not static /home/skuribay/git/u-boot.git/include/asm/bitops.h:887: warning: '__fswab32' is static but used in inline function 'ext2_find_next_zero_bit' which is not static
I have to look into these warnings, but couldn't make it into the upcomming v2009.03 release.
Thanks,
Shinya
---
MAKEALL log with GCC 4.2.3
skuribay at ubuntu:u-boot.git$ ./MAKEALL mips mips_el Configuring for incaip board...
text data bss dec hex filename
144552 6652 20240 171444 29db4 ./u-boot
Configuring for qemu-mips board...
text data bss dec hex filename
158600 6480 221768 386848 5e720 ./u-boot
... on Platinum board variant
Configuring for vct board...
text data bss dec hex filename
196240 12916 284356 493512 787c8 ./u-boot
... on Platinum board variant
... stripped down image variant
Configuring for vct board...
text data bss dec hex filename
87616 4336 13716 105668 19cc4 ./u-boot
... on Platinum board variant
... on OneNAND board variant
Configuring for vct board...
text data bss dec hex filename
290272 14076 287772 592120 908f8 ./u-boot
... on Platinum board variant
... on OneNAND board variant
... stripped down image variant
Configuring for vct board...
text data bss dec hex filename
180592 5484 17116 203192 319b8 ./u-boot
... on PlatinumAVC board variant
Configuring for vct board...
text data bss dec hex filename
117040 5400 14944 137384 218a8 ./u-boot
... on PlatinumAVC board variant
... stripped down image variant
Configuring for vct board...
text data bss dec hex filename
87168 4336 13716 105220 19b04 ./u-boot
... on PlatinumAVC board variant
... on OneNAND board variant
Configuring for vct board...
text data bss dec hex filename
211132 6556 18344 236032 39a00 ./u-boot
... on PlatinumAVC board variant
... on OneNAND board variant
... stripped down image variant
Configuring for vct board...
text data bss dec hex filename
180136 5484 17116 202736 317f0 ./u-boot
... on Premium board variant
Configuring for vct board...
text data bss dec hex filename
196240 12916 284356 493512 787c8 ./u-boot
... on Premium board variant
... stripped down image variant
Configuring for vct board...
text data bss dec hex filename
87616 4336 13716 105668 19cc4 ./u-boot
... on Premium board variant
... on OneNAND board variant
Configuring for vct board...
text data bss dec hex filename
290272 14076 287772 592120 908f8 ./u-boot
... on Premium board variant
... on OneNAND board variant
... stripped down image variant
Configuring for vct board...
text data bss dec hex filename
180592 5484 17116 203192 319b8 ./u-boot
Configuring for purple board...
text data bss dec hex filename
146120 6308 18956 171384 29d78 ./u-boot
Configuring for dbau1x00 board...
text data bss dec hex filename
118524 5292 20680 144496 23470 ./u-boot
Configuring for dbau1x00 board...
text data bss dec hex filename
118524 5292 20680 144496 23470 ./u-boot
Configuring for dbau1x00 board...
text data bss dec hex filename
118524 5292 20680 144496 23470 ./u-boot
Configuring for dbau1x00 board...
text data bss dec hex filename
115540 5376 23352 144268 2338c ./u-boot
Configuring for dbau1x00 board...
text data bss dec hex filename
115540 5376 23352 144268 2338c ./u-boot
Configuring for gth2 board...
text data bss dec hex filename
110900 5284 18376 134560 20da0 ./u-boot
Configuring for dbau1x00 board...
text data bss dec hex filename
115540 5376 23352 144268 2338c ./u-boot
Configuring for pb1x00 board...
text data bss dec hex filename
104600 6144 20488 131232 200a0 ./u-boot
skuribay at ubuntu:u-boot.git$
skuribay at ubuntu:u-boot.git$
skuribay at ubuntu:u-boot.git$ mips-linux-gnu-gcc --version mips-linux-gnu-gcc (Sourcery G++ Lite 4.2-177) 4.2.3
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
[U-Boot] MIPS build status (Re: CUSTODIANS: Urgent boarding call for flight 2009.03)
Dear Shinya,
Quoted 3 lines · In message <[email protected]> you wrote:
* With GCC 4.2.3, all MIPS targets builds fine without any errors. MAKEALL output is attached.
Thanks.
Quoted 3 lines
* But with GCC 4.3.2, you would see hundreds of
bitops.hwarnings. Besides, some could be compiled (gth2, etc.), but some failed (qemu_mips, etc.).Bitops.hwarnings are as follows:
...
Quoted 2 lines
I have to look into these warnings, but couldn't make it into the upcomming v2009.03 release.
I am aware of these issues. There are similar problems for other architectures as well. I agree that wepost-pone such work for the next release.
Thanks a lot.
Best regards,
Wolfgang Denk
Signature · 5 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de The amount of time between slipping on the peel and landing on the pavement is precisely 1 bananosecond.
Quoted 11 lines · Wolfgang Denk
Hi Custodians (and everybody else),
can you please check if all urgent patches have been added to the U-Boot master branch?
If anything should still be missing, please respond *now*.
My intention is to push out the 2009.03 release on schedule, i. e. on Saturday, March 21, 2009.
Quoted 7 lines
At the moment I am not planning for another release candidate.
Note: after the release is out, I will merge the current "next" branch into "master", so this will be the starting point for the next merge window.
For ARM the only pending patch are the OMAP3 usb clock which I wait the new version
and the NetStar
The AVR32 failled to build
Configuring for atstk1002 board...
In file included from cpu.c:25:
/private/u-boot-arm/include/asm/io.h:129: error: conflicting types for 'virt_to_phys'
/private/u-boot-arm/include/asm/io.h:80: error: previous definition of 'virt_to_phys' was here
make[1]: *** [cpu.o] Error 1
make: *** [cpu/at32ap/libat32ap.a] Error 2
make: *** Waiting for unfinished jobs....
In file included from gpio.c:24:
/private/u-boot-arm/include/asm/io.h:129: error: conflicting types for 'virt_to_phys'
/private/u-boot-arm/include/asm/io.h:80: error: previous definition of 'virt_to_phys' was here
make[1]: *** [gpio.o] Error 1
make[1]: In file included from clk.c:24:
/private/u-boot-arm/include/asm/io.h:129: error: conflicting types for 'virt_to_phys'
/private/u-boot-arm/include/asm/io.h:80: error: previous definition of 'virt_to_phys' was here
Haavard could you take a look?
Best Regards,
J.
Quoted 7 lines · Jean-Christophe PLAGNIOL-VILLARD
make[1]: In file included from clk.c:24:
/private/u-boot-arm/include/asm/io.h:129: error: conflicting types for 'virt_to_phys'
/private/u-boot-arm/include/asm/io.h:80: error: previous definition of 'virt_to_phys' was hereHaavard could you take a look?
Latest upstream master builds just fine here...though the last release may be broken because I pushed the fix too late.
Thanks a lot for keeping an eye on things.
Haavard
Quoted 11 lines · Haavard Skinnemoen
Quoted 7 lines · Jean-Christophe PLAGNIOL-VILLARD
make[1]: In file included from clk.c:24:
/private/u-boot-arm/include/asm/io.h:129: error: conflicting types for 'virt_to_phys'
/private/u-boot-arm/include/asm/io.h:80: error: previous definition of 'virt_to_phys' was hereHaavard could you take a look?
Latest upstream master builds just fine here...though the last release may be broken because I pushed the fix too late.
I've try the next branch and it's failled too
cache.c:25:33: error: asm/arch/cacheflush.h: No such file or directory board.c:89:33: error: asm/arch/cacheflush.h: No such file or directory cache.c:25:33: error: asm/arch/cacheflush.h: No such file or directory cache.c: In function 'dcache_clean_range':
cache.c:38: warning: implicit declaration of function 'dcache_clean_line' cache.c:40: warning: implicit declaration of function 'sync_write_buffer' cache.c: In function 'dcache_invalidate_range':
cache.c:54: warning: implicit declaration of function 'dcache_invalidate_line' cache.c: In function 'dcache_flush_range':
cache.c:68: warning: implicit declaration of function 'dcache_flush_line' cache.c: In function 'icache_invalidate_range':
cache.c:84: warning: implicit declaration of function 'icache_invalidate_line' make[1]: *** [cache.o] Error 1
make: *** [cpu/at32ap/libat32ap.a] Error 2
make: *** Waiting for unfinished jobs....
board.c:89:33: error: asm/arch/cacheflush.h: No such file or directory board.c: In function 'dma_alloc_init':
board.c:108: warning: implicit declaration of function 'dcache_invalidate_range'
make[1]: *** [board.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [lib_avr32/libavr32.a] Error 2
Quoted 2 lines
Thanks a lot for keeping an eye on things.
your welcome
Best Regards,
J.
PATCH 1/1 avr32: fix cacheflush.h location introducted by d8f2aa3298610b
---
.../asm-avr32/{ => arch-at32ap700x}/cacheflush.h | 0
1 files changed, 0 insertions(+), 0 deletions(-)
rename include/asm-avr32/{ => arch-at32ap700x}/cacheflush.h (100%)include/asm-avr32/arch-at32ap700x/cacheflush.h renamed from include/asm-avr32/cacheflush.h +0 -0
Signature · 1 line
1.6.1.3
Haavard Skinnemoen
AppliedPATCH 1/1 avr32: fix cacheflush.h location introducted by d8f2aa3298610b
Quoted 1 line · Jean-Christophe PLAGNIOL-VILLARD
Signed-off-by Jean-Christophe PLAGNIOL-VILLARD <[email protected]>
Applied, thanks
Haavard
Quoted 2 lines · Jean-Christophe PLAGNIOL-VILLARD
Quoted 2 lines
Latest upstream master builds just fine here...though the last release may be broken because I pushed the fix too late.
Ah, I see the avr32 master branch is still broken. I've fixed it by pulling from mainline.
Quoted 1 line
I've try the next branch and it's failled too
Right...looks like one of the UC3 patches got mangled somehow. I'll have a look at that.
Haavard
[U-Boot] SH Build status (Re: CUSTODIANS: Urgent boarding call for flight 2009.03)
In reply to Wolfgang DenkDeari Wolfgang.
SH build status(sh2/sh3/sh4) is fine.
My manage boards and some other boards work without problem.
However, there is a problem because the following patches are not taken in.
- [U-Boot] [PATCH to 2008.03] net: sh_eth: Remove sh_eth_reset() from halt function
A title makes a mistake in this.
To be right is 2009.03. I sent the email which already pointed out a mistake.
Best regards,
Nobuhiro
Quoted 35 lines · On Tue, 17 Mar 2009 00:26:55 +0100 Wolfgang Denk <[email protected]> wrote:
Hi Custodians (and everybody else),
can you please check if all urgent patches have been added to the U-Boot master branch?
If anything should still be missing, please respond *now*.
My intention is to push out the 2009.03 release on schedule, i. e. on Saturday, March 21, 2009.
At the moment I am not planning for another release candidate.
Note: after the release is out, I will merge the current "next" branch into "master", so this will be the starting point for the next merge window.
Thanks.
Best regards,
Wolfgang Denk
Signature · 10 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de "There are three principal ways to lose money: wine, women, and en- gineers. While the first two are more pleasant, the third is by far the more certain." -- Baron Rothschild, ca. 1800 _______________________________________________ U-Boot mailing list U-Boot at lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Signature · 5 lines
Nobuhiro Iwamatsu hemamu at t-base.ne.jp iwamatsu at debian.or.jp GPG ID : 3170EBE9
[U-Boot] SH Build status (Re: CUSTODIANS: Urgent boarding call for flight 2009.03)
Dear Nobuhiro Iwamatsu,
Quoted 6 lines · In message <[email protected]> you wrote:
However, there is a problem because the following patches are not taken in.
- [U-Boot] [PATCH to 2008.03] net:sh_eth: Removesh_eth_reset()from halt functionA title makes a mistake in this.
To be right is 2009.03. I sent the email which already pointed out a mistake.
No problem, I will apply this patch later tonight.
Thanks again.
Best regards,
Wolfgang Denk
Signature · 5 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de "May your future be limited only by your dreams." - Christa McAuliffe