[U-Boot] [STATUS] v2009.08-rc1 is out
Hi everybody...
v2009.08-rc1 has just been released.
Please help testing, and submit fixes to the remaining problems. Things still missing should be submitted ASAP.
v2009.08-rc1 will also be the base for the "next" branch which I will create soon.
Please use the "next" branch as base for any new work. Note: Please keep in mind that it may be rebased against master every now and then without warning, but I will usually try to avoid this.
Summary of current status:
* Many boards now throw the (expected)
#warning Ethernet driver is deprecated. Please update to use CONFIG_NET_MULTI
messages.
* ARM (as far as present [see below]) shows this:
===== actux4 ===== actux4.c: In function 'board_init': actux4.c:83: warning: left shift count >= width of type actux4.c:83: warning: left shift count >= width of type ===== mv88f6281gtw_ge ===== mv88e61xx.c: In function 'mv88e61xx_switch_initialize': mv88e61xx.c:346: warning: 'idstr' may be used uninitialized in this function ===== rd6281a ===== mv88e61xx.c: In function 'mv88e61xx_busychk_multic': mv88e61xx.c:46: warning: passing argument 4 of 'miiphy_read' from incompatible pointer type mv88e61xx.c: In function 'mv88e61xx_wr_phy': mv88e61xx.c:61: warning: passing argument 4 of 'miiphy_read' from incompatible pointer type mv88e61xx.c:57: warning: unused variable 'reg' mv88e61xx.c: In function 'mv88e61xx_rd_phy': mv88e61xx.c:80: warning: passing argument 4 of 'miiphy_read' from incompatible pointer type mv88e61xx.c:76: warning: unused variable 'reg' mv88e61xx.c: In function 'mv88e61xx_switch_initialize': mv88e61xx.c:346: warning: 'idstr' may be used uninitialized in this function nand_util.c:45:2: warning: #warning Please define CONFIG_SYS_64BIT_VSPRINTF for correct output! ===== sheevaplug ===== nand_util.c:45:2: warning: #warning Please define CONFIG_SYS_64BIT_VSPRINTF for correct output!
* ARM:
many things missing, still waiting for pull request from Jean-Christophe
From my point of view, ARM is currently the biggest problem. Discus-
sion of related patches often happens with big delays, pull requests always come very late. It seems obvious that Jean-Christophe is overloaded and cannot cope any more with all the ARM related work. This is actually no big surprise, as ARM related activites have significantly grown in the last months. Maybe we should split off the most active CPU families and install separate custodians for these, like we did for PowerPC long ago. OMAP and friends (TI) could be one such group, Kirkwood and friends (Marvell) could be another one. Of course we would need to find custodians for these first.
Comments and ideas welcome.
Best regards,
Wolfgang Denk
On Monday 27 July 2009 05:26:07 Wolfgang Denk wrote:
Many boards now throw the (expected)
#warning Ethernet driver is deprecated. Please update to use
CONFIG_NET_MULTI
messages.
i see this on a bunch of Blackfin boards all due to the SMC91111 driver. do you have any immediate/midterm plans to port this driver Ben ? i'm assuming the SMC911X driver doesnt support all the parts that the SMC91111 driver does, so simply jumping away to the SMC911X driver isnt an option ... -mike
Hi Mike,
Mike Frysinger wrote:
On Monday 27 July 2009 05:26:07 Wolfgang Denk wrote:
Many boards now throw the (expected)
#warning Ethernet driver is deprecated. Please update to use
CONFIG_NET_MULTI
messages.
i see this on a bunch of Blackfin boards all due to the SMC91111 driver. do you have any immediate/midterm plans to port this driver Ben ? i'm assuming the SMC911X driver doesnt support all the parts that the SMC91111 driver does, so simply jumping away to the SMC911X driver isnt an option ... -mike
I have it completely ported, and plan to post it as soon as I get a chance. The only thing left to do is port all of the eeprom.c standalone apps (I have one done already so the others shouldn't take much time).
regards, Ben
On Monday 27 July 2009 14:11:21 Ben Warren wrote:
Mike Frysinger wrote:
On Monday 27 July 2009 05:26:07 Wolfgang Denk wrote:
Many boards now throw the (expected)
#warning Ethernet driver is deprecated. Please update to use
CONFIG_NET_MULTI
messages.
i see this on a bunch of Blackfin boards all due to the SMC91111 driver. do you have any immediate/midterm plans to port this driver Ben ? i'm assuming the SMC911X driver doesnt support all the parts that the SMC91111 driver does, so simply jumping away to the SMC911X driver isnt an option ...
I have it completely ported, and plan to post it as soon as I get a chance. The only thing left to do is port all of the eeprom.c standalone apps (I have one done already so the others shouldn't take much time).
ok, that means i dont have to do any work. thanks :) -mike
Mike Frysinger wrote:
On Monday 27 July 2009 14:11:21 Ben Warren wrote:
Mike Frysinger wrote:
On Monday 27 July 2009 05:26:07 Wolfgang Denk wrote:
Many boards now throw the (expected)
#warning Ethernet driver is deprecated. Please update to use
CONFIG_NET_MULTI
messages.
i see this on a bunch of Blackfin boards all due to the SMC91111 driver. do you have any immediate/midterm plans to port this driver Ben ? i'm assuming the SMC911X driver doesnt support all the parts that the SMC91111 driver does, so simply jumping away to the SMC911X driver isnt an option ...
I have it completely ported, and plan to post it as soon as I get a chance. The only thing left to do is port all of the eeprom.c standalone apps (I have one done already so the others shouldn't take much time).
ok, that means i dont have to do any work. thanks :) -mike
Only if testing isn't work for you. ;)
Ben
On Monday 27 July 2009 14:30:05 Ben Warren wrote:
Mike Frysinger wrote:
On Monday 27 July 2009 14:11:21 Ben Warren wrote:
Mike Frysinger wrote:
On Monday 27 July 2009 05:26:07 Wolfgang Denk wrote:
Many boards now throw the (expected)
#warning Ethernet driver is deprecated. Please update to use
CONFIG_NET_MULTI
messages.
i see this on a bunch of Blackfin boards all due to the SMC91111 driver. do you have any immediate/midterm plans to port this driver Ben ? i'm assuming the SMC911X driver doesnt support all the parts that the SMC91111 driver does, so simply jumping away to the SMC911X driver isnt an option ...
I have it completely ported, and plan to post it as soon as I get a chance. The only thing left to do is port all of the eeprom.c standalone apps (I have one done already so the others shouldn't take much time).
ok, that means i dont have to do any work. thanks :)
Only if testing isn't work for you. ;)
it isnt really. i'm taking off for a week or two though, so i wont be able to test until i get back (assuming you post before that). -mike
On 11:11 Mon 27 Jul , Ben Warren wrote:
Hi Mike,
Mike Frysinger wrote:
On Monday 27 July 2009 05:26:07 Wolfgang Denk wrote:
Many boards now throw the (expected)
#warning Ethernet driver is deprecated. Please update to use
CONFIG_NET_MULTI
messages.
i see this on a bunch of Blackfin boards all due to the SMC91111 driver. do you have any immediate/midterm plans to port this driver Ben ? i'm assuming the SMC911X driver doesnt support all the parts that the SMC91111 driver does, so simply jumping away to the SMC911X driver isnt an option ... -mike
I have it completely ported, and plan to post it as soon as I get a chance. The only thing left to do is port all of the eeprom.c standalone apps (I have one done already so the others shouldn't take much time).
I've also done it and the eeprom is working
I'll post it later today wish 2 other patch for net
Best Regards, J.
I get the following compilation errors when I try to compile DaVinci DM355 on the latest U-Boot source. I thought I saw similar issues on the mailing list some time back. Have these been resolved?
3.2/libgcc.a(_udivsi3.o) has EABI version 5, but target u-boot has EABI version 0 arm-none-linux-gnueabi-ld: failed to merge target specific data of file /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_udivsi3.o) arm-none-linux-gnueabi-ld: ERROR: Source object /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_divsi3.o) has EABI version 5, but target u-boot has EABI version 0 arm-none-linux-gnueabi-ld: failed to merge target specific data of file /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_divsi3.o) arm-none-linux-gnueabi-ld: ERROR: Source object /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_umodsi3.o) has EABI version 5, but target u-boot has EABI version 0 arm-none-linux-gnueabi-ld: failed to merge target specific data of file /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_umodsi3.o) arm-none-linux-gnueabi-ld: ERROR: Source object /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_modsi3.o) has EABI version 5, but target u-boot has EABI version 0 arm-none-linux-gnueabi-ld: failed to merge target specific data of file /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_modsi3.o) arm-none-linux-gnueabi-ld: ERROR: Source object /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_dvmd_lnx.o) has EABI version 5, but target u-boot has EABI version 0 arm-none-linux-gnueabi-ld: failed to merge target specific data of file /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_dvmd_lnx.o) /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_dvmd_lnx.o): In function `__aeabi_ldiv0': (.text+0x8): undefined reference to `raise
Thanks, Sandeep
Hi,
aulraj, Sandeep a écrit :
I get the following compilation errors when I try to compile DaVinci DM355 on the latest U-Boot source. I thought I saw similar issues on the mailing list some time back. Have these been resolved?
3.2/libgcc.a(_udivsi3.o) has EABI version 5, but target u-boot has EABI version 0 arm-none-linux-gnueabi-ld: failed to merge target specific data of file /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_udivsi3.o) arm-none-linux-gnueabi-ld: ERROR: Source object /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_divsi3.o) has EABI version 5, but target u-boot has EABI version 0 arm-none-linux-gnueabi-ld: failed to merge target specific data of file /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_divsi3.o) arm-none-linux-gnueabi-ld: ERROR: Source object /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_umodsi3.o) has EABI version 5, but target u-boot has EABI version 0 arm-none-linux-gnueabi-ld: failed to merge target specific data of file /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_umodsi3.o) arm-none-linux-gnueabi-ld: ERROR: Source object /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_modsi3.o) has EABI version 5, but target u-boot has EABI version 0 arm-none-linux-gnueabi-ld: failed to merge target specific data of file /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_modsi3.o) arm-none-linux-gnueabi-ld: ERROR: Source object /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_dvmd_lnx.o) has EABI version 5, but target u-boot has EABI version 0 arm-none-linux-gnueabi-ld: failed to merge target specific data of file /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_dvmd_lnx.o) /opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/libgcc.a(_dvmd_lnx.o): In function `__aeabi_ldiv0': (.text+0x8): undefined reference to `raise
try to add USE_PRIVATE_LIBGCC=yes to you make commande.
Eric
-----Original Message----- From: Eric Bénard [mailto:eric@eukrea.com] Sent: Monday, August 10, 2009 11:26 AM To: Paulraj, Sandeep Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] Compilation erros while trying at compile ARM DaVinci
Hi,
aulraj, Sandeep a écrit :
I get the following compilation errors when I try to compile DaVinci
DM355 on the latest U-Boot source. I thought I saw similar issues on the mailing list some time back. Have these been resolved?
3.2/libgcc.a(_udivsi3.o) has EABI version 5, but target u-boot has EABI
version 0
arm-none-linux-gnueabi-ld: failed to merge target specific data of file
/opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux- gnueabi/4.3.2/libgcc.a(_udivsi3.o)
arm-none-linux-gnueabi-ld: ERROR: Source object
/opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux- gnueabi/4.3.2/libgcc.a(_divsi3.o) has EABI version 5, but target u-boot has EABI version 0
arm-none-linux-gnueabi-ld: failed to merge target specific data of file
/opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux- gnueabi/4.3.2/libgcc.a(_divsi3.o)
arm-none-linux-gnueabi-ld: ERROR: Source object
/opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux- gnueabi/4.3.2/libgcc.a(_umodsi3.o) has EABI version 5, but target u-boot has EABI version 0
arm-none-linux-gnueabi-ld: failed to merge target specific data of file
/opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux- gnueabi/4.3.2/libgcc.a(_umodsi3.o)
arm-none-linux-gnueabi-ld: ERROR: Source object
/opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux- gnueabi/4.3.2/libgcc.a(_modsi3.o) has EABI version 5, but target u-boot has EABI version 0
arm-none-linux-gnueabi-ld: failed to merge target specific data of file
/opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux- gnueabi/4.3.2/libgcc.a(_modsi3.o)
arm-none-linux-gnueabi-ld: ERROR: Source object
/opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux- gnueabi/4.3.2/libgcc.a(_dvmd_lnx.o) has EABI version 5, but target u-boot has EABI version 0
arm-none-linux-gnueabi-ld: failed to merge target specific data of file
/opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux- gnueabi/4.3.2/libgcc.a(_dvmd_lnx.o)
/opt/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-
gnueabi/4.3.2/libgcc.a(_dvmd_lnx.o): In function `__aeabi_ldiv0':
(.text+0x8): undefined reference to `raise
try to add USE_PRIVATE_LIBGCC=yes to you make commande.
[Sandeep] It compiles. Is this some kind of a permanent solution? I see lots of e-mails on arm not including libgcc.
Eric
Hi Sandeep,
try to add USE_PRIVATE_LIBGCC=yes to you make commande.
[Sandeep] It compiles. Is this some kind of a permanent solution? I see lots of e-mails on arm not including libgcc.
It should not be a permanent solution. It is need however as long as
a) ARM on U-Boot forces the ABI to be compiled for to be "-mabi=apcs-gnu" (check cpu/arm*/config.mk) in contrast to the newer GNUEABI
and
b) your toolchain does not have a libgcc compiled for this ABI version (true for recent toolchains which use the newer GNUEABI.
This is my take on the situation. I lost track however why a) is the case. Maybe someone can help my memory here.
Cheers Detlev
Jean-Christophe PLAGNIOL-VILLARD wrote:
On 11:11 Mon 27 Jul , Ben Warren wrote:
Hi Mike,
Mike Frysinger wrote:
On Monday 27 July 2009 05:26:07 Wolfgang Denk wrote:
Many boards now throw the (expected)
#warning Ethernet driver is deprecated. Please update to use
CONFIG_NET_MULTI
messages.
i see this on a bunch of Blackfin boards all due to the SMC91111 driver. do you have any immediate/midterm plans to port this driver Ben ? i'm assuming the SMC911X driver doesnt support all the parts that the SMC91111 driver does, so simply jumping away to the SMC911X driver isnt an option ... -mike
I have it completely ported, and plan to post it as soon as I get a chance. The only thing left to do is port all of the eeprom.c standalone apps (I have one done already so the others shouldn't take much time).
I've also done it and the eeprom is working
I'll post it later today wish 2 other patch for net
Best Regards, J.
What are you planning on posting? It looks to me like you say it works OK.
Ben
Hi everybody...
v2009.08-rc2 has just been released.
Please help testing, and submit fixes to the remaining problems. Things still missing should be submitted ASAP.
v2009.08-rc2 is also be the base for the "next" branch which I just created (still empty so far).
Please use the "next" branch as base for any new work. Note: Please keep in mind that it may be rebased against master every now and then without warning, but I will usually try to avoid this.
Summary of current status:
* Many boards now throw the (expected)
#warning Ethernet driver is deprecated. Please update to use CONFIG_NET_MULTI
messages.
* ARM and PowerPC: mostly compile clean; there are a few issues, responsible s have been notified
Biggest problem area for me is curtrently ARM, where I lose more time trying to moderate patch submissions than I can spend on actually working on code. We need to overcome this situation ASAP.
Comments and ideas welcome.
Best regards,
Wolfgang Denk
On 10:55 Mon 10 Aug , Wolfgang Denk wrote:
Hi everybody...
v2009.08-rc2 has just been released.
Please help testing, and submit fixes to the remaining problems. Things still missing should be submitted ASAP.
v2009.08-rc2 is also be the base for the "next" branch which I just created (still empty so far).
Please use the "next" branch as base for any new work. Note: Please keep in mind that it may be rebased against master every now and then without warning, but I will usually try to avoid this.
Summary of current status:
Many boards now throw the (expected)
#warning Ethernet driver is deprecated. Please update to use CONFIG_NET_MULTI
messages.
ARM and PowerPC: mostly compile clean; there are a few issues, responsible s have been notified
nearly all ppc have warning with gcc 4 and a lots of them fail to build
Biggest problem area for me is curtrently ARM, where I lose more time trying to moderate patch submissions than I can spend on actually working on code. We need to overcome this situation ASAP.
Comments and ideas welcome
yes please let me manage the ARM myself and please pull my patch I do known what I do on ARM very well
Best Regards, J.
Dear Jean-Christophe PLAGNIOL-VILLARD,
In message 20090810085443.GI17045@game.jcrosoft.org you wrote:
- ARM and PowerPC: mostly compile clean; there are a few issues, responsible s have been notified
nearly all ppc have warning with gcc 4 and a lots of them fail to build
I built all PowerPC boards with ELDK 4.0 (gcc4.0.0), ELDK 4.1 (gcc 4.0.0) and ELDK 4.2 (gcc 4.2.2). Not a sinlge board failed, and only very few had unexpected warnings (I consider the "#warning Ethernet driver is deprecated. Please update to use CONFIG_NET_MULT" warning to be an expected one - and even this affects only 1 or 2 PowerPC boards - but about every ARM board).
So could you *please* start providing clear facts? Which board do you claim to fail to build? Which exact tool chain are you using? And what are the exact error messages?
D*mn... I'm asking you these very same questions for at least the 4th time in the last 2 or 3 days.
Please provide FACTS.
Comments and ideas welcome
yes please let me manage the ARM myself and please pull my patch I do known what I do on ARM very well
Even as a custodian you are supposed to accept that you do not have unlimited power.
Best regards,
Wolfgang Denk
Wolfgang Denk wrote:
Summary of current status:
Many boards now throw the (expected)
#warning Ethernet driver is deprecated. Please update to use CONFIG_NET_MULTI
messages.
I found qemu_mips_config is spotted by it: Configuring for qemu-mips board... eth.c:497:2: warning: #warning Ethernet driver is deprecated. Please update to use CONFIG_NET_MULTI
But I don't follow the recent changes including that CONFIG_NET_MULTI migration, nor I don't have enough spare time to look into it, so gave up this time, sorry.
- ARM and PowerPC: mostly compile clean; there are a few issues, responsible s have been notified
For the rest, MIPS builds are pretty in good shape as follows.
skuribay@ubuntu:u-boot.git$ ./MAKEALL mips mips_el Configuring for incaip board... text data bss dec hex filename 147032 6476 20240 173748 2a6b4 ./u-boot Configuring for qemu-mips board... eth.c:497:2: warning: #warning Ethernet driver is deprecated. Please update to use CONFIG_NET_MULTI text data bss dec hex filename 171744 6340 221768 399852 619ec ./u-boot ... on Platinum board variant Configuring for vct board... text data bss dec hex filename 199916 12568 284420 496904 79508 ./u-boot ... on Platinum board variant ... stripped down image variant Configuring for vct board... text data bss dec hex filename 88296 4196 13716 106208 19ee0 ./u-boot ... on Platinum board variant ... on OneNAND board variant Configuring for vct board... text data bss dec hex filename 296608 13728 289764 600100 92824 ./u-boot ... on Platinum board variant ... on OneNAND board variant ... stripped down image variant Configuring for vct board... text data bss dec hex filename 184016 5344 19080 208440 32e38 ./u-boot ... on PlatinumAVC board variant Configuring for vct board... text data bss dec hex filename 118508 5112 14944 138564 21d44 ./u-boot ... on PlatinumAVC board variant ... stripped down image variant Configuring for vct board... text data bss dec hex filename 87816 4196 13716 105728 19d00 ./u-boot ... on PlatinumAVC board variant ... on OneNAND board variant Configuring for vct board... text data bss dec hex filename 215264 6268 20308 241840 3b0b0 ./u-boot ... on PlatinumAVC board variant ... on OneNAND board variant ... stripped down image variant Configuring for vct board... text data bss dec hex filename 183528 5344 19080 207952 32c50 ./u-boot ... on Premium board variant Configuring for vct board... text data bss dec hex filename 199916 12568 284420 496904 79508 ./u-boot ... on Premium board variant ... stripped down image variant Configuring for vct board... text data bss dec hex filename 88296 4196 13716 106208 19ee0 ./u-boot ... on Premium board variant ... on OneNAND board variant Configuring for vct board... text data bss dec hex filename 296608 13728 289764 600100 92824 ./u-boot ... on Premium board variant ... on OneNAND board variant ... stripped down image variant Configuring for vct board... text data bss dec hex filename 184016 5344 19080 208440 32e38 ./u-boot Configuring for purple board... text data bss dec hex filename 147688 6168 18956 172812 2a30c ./u-boot Configuring for dbau1x00 board... text data bss dec hex filename 120928 5172 20680 146780 23d5c ./u-boot Configuring for dbau1x00 board... text data bss dec hex filename 120928 5172 20680 146780 23d5c ./u-boot Configuring for dbau1x00 board... text data bss dec hex filename 120928 5172 20680 146780 23d5c ./u-boot Configuring for dbau1x00 board... text data bss dec hex filename 116936 5256 23352 145544 23888 ./u-boot Configuring for dbau1x00 board... text data bss dec hex filename 116936 5256 23352 145544 23888 ./u-boot Configuring for gth2 board... text data bss dec hex filename 111656 5140 18376 135172 21004 ./u-boot Configuring for dbau1x00 board... text data bss dec hex filename 116936 5256 23352 145544 23888 ./u-boot Configuring for pb1x00 board... text data bss dec hex filename 106460 6004 20488 132952 20758 ./u-boot skuribay@ubuntu:u-boot.git$ skuribay@ubuntu:u-boot.git$ skuribay@ubuntu:u-boot.git$ mips-linux-gnu-gcc --version mips-linux-gnu-gcc (Sourcery G++ Lite 4.3-154) 4.3.3 Copyright (C) 2008 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.
skuribay@ubuntu:u-boot.git$ mips-linux-gnu-as --version GNU assembler (Sourcery G++ Lite 4.3-154) 2.19.51.20090205 Copyright 2008 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License version 3 or later. This program has absolutely no warranty. This assembler was configured for a target of `mips-linux-gnu'. skuribay@ubuntu:u-boot.git$
Hi Shinya,
Shinya Kuribayashi wrote:
Wolfgang Denk wrote:
Summary of current status:
Many boards now throw the (expected)
#warning Ethernet driver is deprecated. Please update to use CONFIG_NET_MULTI
messages.
I found qemu_mips_config is spotted by it: Configuring for qemu-mips board... eth.c:497:2: warning: #warning Ethernet driver is deprecated. Please update to use CONFIG_NET_MULTI
But I don't follow the recent changes including that CONFIG_NET_MULTI migration, nor I don't have enough spare time to look into it, so gave up this time, sorry.
The DM9000 driver uses the old networking API, and needs to be updated. I have it partly done and will be submitting to the ML soon. Hopefully you'll be able to test my patch :)
regards, Ben
Hi,
Ben Warren wrote:
I found qemu_mips_config is spotted by it: Configuring for qemu-mips board... eth.c:497:2: warning: #warning Ethernet driver is deprecated. Please update to use CONFIG_NET_MULTI
But I don't follow the recent changes including that CONFIG_NET_MULTI migration, nor I don't have enough spare time to look into it, so gave up this time, sorry.
The DM9000 driver uses the old networking API, and needs to be updated. I have it partly done and will be submitting to the ML soon. Hopefully you'll be able to test my patch :)
Nice! Once submitted, I'll check it builds on my side.
participants (8)
-
Ben Warren -
Detlev Zundel -
Eric Bénard -
Jean-Christophe PLAGNIOL-VILLARD -
Mike Frysinger -
Paulraj, Sandeep -
Shinya Kuribayashi -
Wolfgang Denk