* [U-Boot] [STATUS] v2009.11-rc1 is out
@ 2009-10-28 13:42 Wolfgang Denk
2009-10-28 14:53 ` Paulraj, Sandeep
2009-11-03 8:04 ` rhabarber1848
0 siblings, 2 replies; 13+ messages in thread
From: Wolfgang Denk @ 2009-10-28 13:42 UTC (permalink / raw)
To: u-boot
Helleo all,
just in case you did not notice yet: U-Boot v2009.11-rc1 was released
last night.
Summary of state:
ARM: lots of issues:
=====
1) SBC35_A9G20:
nand_util.c:45:2: warning: #warning Please define CONFIG_SYS_64BIT_VSPRINTF for correct output!
m41t94.c: In function 'rtc_reset':
m41t94.c:123: warning: 'return' with a value, in function returning void
2) TNY_A9260.ERR, TNY_A9G20.ERR:
nand_util.c:45:2: warning: #warning Please define CONFIG_SYS_64BIT_VSPRINTF for correct output!
3) apollon:
/bin/sh: /work/wd/tmp-arm/include/config.h: No such file or directory
make: *** [apollon_config] Error 1
System not configured - see README
Out-o-tree build fails
4) cradle:
zlib.c:401:1: warning: "OFF" redefined
In file included from /work/wd/tmp-arm/include/config.h:2,
from /home/wd/git/u-boot/work/include/common.h:37,
from zlib.c:30:
/home/wd/git/u-boot/work/include/configs/cradle.h:337:1: warning: this is the location of the previous definition
5) csb226, impa7:
cs8900.c:112:50: error: macro "get_reg_init_bus" passed 2 arguments, but takes just 1
cs8900.c: In function 'cs8900_reset':
cs8900.c:112: error: 'get_reg_init_bus' undeclared (first use in this function)
cs8900.c:112: error: (Each undeclared identifier is reported only once
cs8900.c:112: error: for each function it appears in.)
cs8900.c:137:37: error: macro "get_reg_init_bus" passed 2 arguments, but takes just 1
cs8900.c: In function 'cs8900_get_enetaddr':
cs8900.c:137: error: 'get_reg_init_bus' undeclared (first use in this function)
cs8900.c:161:33: error: macro "get_reg_init_bus" passed 2 arguments, but takes just 1
cs8900.c: In function 'cs8900_halt':
cs8900.c:161: error: 'get_reg_init_bus' undeclared (first use in this function)
cs8900.c:170:38: error: macro "get_reg_init_bus" passed 2 arguments, but takes just 1
cs8900.c: In function 'cs8900_init':
cs8900.c:170: error: 'get_reg_init_bus' undeclared (first use in this function)
make[1]: *** [/work/wd/tmp-arm/drivers/net/cs8900.o] Error 1
6) imx27lite:
mxcmmc.c: In function 'mxcmci_softreset':
mxcmmc.c:139: warning: dereferencing type-punned pointer will break strict-aliasing rules
mxcmmc.c:140: warning: dereferencing type-punned pointer will break strict-aliasing rules
mxcmmc.c:144: warning: dereferencing type-punned pointer will break strict-aliasing rules
mxcmmc.c:146: warning: dereferencing type-punned pointer will break strict-aliasing rules
mxcmmc.c: In function 'mxcmci_setup_data':
mxcmmc.c:157: warning: dereferencing type-punned pointer will break strict-aliasing rules
mxcmmc.c:158: warning: dereferencing type-punned pointer will break strict-aliasing rules
mxcmmc.c: In function 'mxcmci_start_cmd':
mxcmmc.c:188: warning: dereferencing type-punned pointer will break strict-aliasing rules
mxcmmc.c:190: warning: dereferencing type-punned pointer will break strict-aliasing rules
mxcmmc.c: In function 'mxcmci_read_response':
mxcmmc.c:250: warning: dereferencing type-punned pointer will break strict-aliasing rules
mxcmmc.c:251: warning: dereferencing type-punned pointer will break strict-aliasing rules
mxcmmc.c:255: warning: dereferencing type-punned pointer will break strict-aliasing rules
mxcmmc.c:256: warning: dereferencing type-punned pointer will break strict-aliasing rules
mxcmmc.c:257: warning: dereferencing type-punned pointer will break strict-aliasing rules
mxcmmc.c: In function 'mxcmci_set_clk_rate':
mxcmmc.c:448: warning: dereferencing type-punned pointer will break strict-aliasing rules
mxcmmc.c: In function 'mxcmci_set_ios':
mxcmmc.c:461: warning: dereferencing type-punned pointer will break strict-aliasing rules
mxcmmc.c:463: warning: dereferencing type-punned pointer will break strict-aliasing rules
mxcmmc.c: In function 'mxcmci_init':
mxcmmc.c:475: warning: dereferencing type-punned pointer will break strict-aliasing rules
mxcmmc.c:483: warning: dereferencing type-punned pointer will break strict-aliasing rules
nand_util.c:45:2: warning: #warning Please define CONFIG_SYS_64BIT_VSPRINTF for correct output!
7) lpd7a400:
smc91111_eeprom.c: In function 'smc91111_eeprom':
smc91111_eeprom.c:76: warning: implicit declaration of function 'SMC_inw'
smc91111_eeprom.c:224: warning: implicit declaration of function 'SMC_outw'
smc91111_eeprom.c: In function 'print_macaddr':
smc91111_eeprom.c:278: warning: implicit declaration of function 'SMC_inb'
/work/wd/tmp-arm/examples/standalone/smc91111_eeprom.o: In function `dump_reg':
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:388: undefined reference to `SMC_outw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:389: undefined reference to `SMC_inw'
/work/wd/tmp-arm/examples/standalone/smc91111_eeprom.o: In function `write_eeprom_reg':
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:357: undefined reference to `SMC_outw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:358: undefined reference to `SMC_outw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:360: undefined reference to `SMC_outw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:361: undefined reference to `SMC_outw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:362: undefined reference to `SMC_inw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:362: undefined reference to `SMC_outw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:365: undefined reference to `SMC_inw'
/work/wd/tmp-arm/examples/standalone/smc91111_eeprom.o: In function `read_eeprom_reg':
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:335: undefined reference to `SMC_outw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:336: undefined reference to `SMC_outw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:338: undefined reference to `SMC_outw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:339: undefined reference to `SMC_inw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:339: undefined reference to `SMC_outw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:342: undefined reference to `SMC_inw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:349: undefined reference to `SMC_inw'
/work/wd/tmp-arm/examples/standalone/smc91111_eeprom.o: In function `copy_from_eeprom':
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:257: undefined reference to `SMC_outw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:258: undefined reference to `SMC_inw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:258: undefined reference to `SMC_outw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:261: undefined reference to `SMC_inw'
/work/wd/tmp-arm/examples/standalone/smc91111_eeprom.o: In function `print_macaddr':
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:276: undefined reference to `SMC_outw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:278: undefined reference to `SMC_inb'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:281: undefined reference to `SMC_inb'
/work/wd/tmp-arm/examples/standalone/smc91111_eeprom.o: In function `smc91111_eeprom':
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:76: undefined reference to `SMC_inw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:224: undefined reference to `SMC_outw'
/home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:225: undefined reference to `SMC_outw'
make[1]: *** [/work/wd/tmp-arm/examples/standalone/smc91111_eeprom] Error 1
8) mv88f6281gtw_ge, openrd_base, rd6281a, sheevaplug:
kirkwood_egiga.c: In function 'kwgbe_init':
kirkwood_egiga.c:447: warning: dereferencing type-punned pointer will break strict-aliasing rules
kirkwood_egiga.c: In function 'kwgbe_recv':
kirkwood_egiga.c:608: warning: dereferencing type-punned pointer will break strict-aliasing rules
9) trab:
timer.c: In function 'reset_cpu':
timer.c:208: warning: implicit declaration of function 'disable_vfd'
10) voiceblue:
/work/wd/tmp-arm/board/voiceblue/../../lib_generic/libgeneric.a(string.o): In function `strcmp':
/home/wd/git/u-boot/work/lib_generic/string.c:156: multiple definition of `strcmp'
/work/wd/tmp-arm/board/voiceblue/../../examples/standalone/libstubs.a(stubs.o):/home/wd/git/u-boot/work/include/_exports.h:24: first defined here
11) xaeniax:
smc91111_eeprom.c: In function 'print_macaddr':
smc91111_eeprom.c:278: warning: suggest parentheses around + or - in operand of &
smc91111_eeprom.c:281: warning: suggest parentheses around + or - in operand of &
12) xsengine:
smc91111_eeprom.c: In function 'print_macaddr':
smc91111_eeprom.c:278: warning: suggest parentheses around + or - inside shift
smc91111_eeprom.c:281: warning: suggest parentheses around + or - inside shift
PowerPC: pretty well, problems:
=========
1) AP1000, MPC8536DS, MPC8536DS_NAND, MPC8536DS_SDCARD,
MPC8536DS_SPIFLASH, MPC8544DS, MVBC_P, P2020DS, P2020DS_36BIT,
PM854:
e1000.c: In function 'e1000_transmit':
e1000.c:5027: warning: passing argument 1 of 'virt_to_phys' discards qualifiers from pointer target type
2) BMW:
tigon3.c: In function 'LM_InitializeAdapter':
tigon3.c:1625: warning: dereferencing type-punned pointer will break strict-aliasing rules
tigon3.c: In function 'LM_ResetAdapter':
tigon3.c:2616: warning: dereferencing type-punned pointer will break strict-aliasing rules
tigon3.c:2630: warning: dereferencing type-punned pointer will break strict-aliasing rules
3) EVB64260, P3G4, ZUMA:
mpsc.c: In function 'mpsc_putchar_early':
mpsc.c:121: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c:127: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'mpsc_getchar':
mpsc.c:204: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c:207: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'mpsc_init':
mpsc.c:273: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c:274: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'galbrg_set_baudrate':
mpsc.c:402: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'galbrg_set_CDV':
mpsc.c:416: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c:419: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'galbrg_enable':
mpsc.c:429: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c:431: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'galbrg_disable':
mpsc.c:441: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c:443: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'galbrg_set_clksrc':
mpsc.c:453: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c:456: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'galmpsc_connect':
mpsc.c:585: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c:599: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'galmpsc_route_rx_clock':
mpsc.c:630: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c:637: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'galmpsc_route_tx_clock':
mpsc.c:647: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c:654: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'galmpsc_config_channel_regs':
mpsc.c:685: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c:686: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'galmpsc_set_brkcnt':
mpsc.c:707: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c:710: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'galmpsc_set_tcschar':
mpsc.c:720: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c:723: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'galmpsc_set_char_length':
mpsc.c:733: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c:736: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'galmpsc_set_stop_bit_length':
mpsc.c:746: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c:748: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'galmpsc_set_parity':
mpsc.c:758: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c:767: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'galmpsc_enter_hunt':
mpsc.c:777: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c:779: warning: dereferencing type-punned pointer will break strict-aliasing rules
mpsc.c: In function 'galmpsc_shutdown':
mpsc.c:809: warning: dereferencing type-punned pointer will break strict-aliasing rules
MIPS: OK
======
MIPS-EL: OK
=========
Please architecture and board maintainers: help testing the rmaining
architectures, and fix the raised problems.
Thanks in advance.
Best regards,
Wolfgang Denk
--
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
We fight only when there is no other choice. We prefer the ways of
peaceful contact.
-- Kirk, "Spectre of the Gun", stardate 4385.3
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] [STATUS] v2009.11-rc1 is out
2009-10-28 13:42 [U-Boot] [STATUS] v2009.11-rc1 is out Wolfgang Denk
@ 2009-10-28 14:53 ` Paulraj, Sandeep
2009-10-28 15:58 ` Wolfgang Denk
2009-11-03 8:04 ` rhabarber1848
1 sibling, 1 reply; 13+ messages in thread
From: Paulraj, Sandeep @ 2009-10-28 14:53 UTC (permalink / raw)
To: u-boot
> ARM: lots of issues:
> =====
>
> 1) SBC35_A9G20:
>
> nand_util.c:45:2: warning: #warning Please define
> CONFIG_SYS_64BIT_VSPRINTF for correct output!
> m41t94.c: In function 'rtc_reset':
> m41t94.c:123: warning: 'return' with a value, in function returning
> void
Wolfgang, this is ATMEL and we know there is no custodian for that
>
> 2) TNY_A9260.ERR, TNY_A9G20.ERR:
>
> nand_util.c:45:2: warning: #warning Please define
> CONFIG_SYS_64BIT_VSPRINTF for correct output!
Same here, I can submit simple 1 line patches for these
>
> 3) apollon:
>
> /bin/sh: /work/wd/tmp-arm/include/config.h: No such file or
> directory
> make: *** [apollon_config] Error 1
> System not configured - see README
>
> Out-o-tree build fails
>
> 4) cradle:
>
> zlib.c:401:1: warning: "OFF" redefined
> In file included from /work/wd/tmp-arm/include/config.h:2,
> from /home/wd/git/u-boot/work/include/common.h:37,
> from zlib.c:30:
> /home/wd/git/u-boot/work/include/configs/cradle.h:337:1: warning:
> this is the location of the previous definition
>
> 5) csb226, impa7:
>
> cs8900.c:112:50: error: macro "get_reg_init_bus" passed 2 arguments,
> but takes just 1
> cs8900.c: In function 'cs8900_reset':
> cs8900.c:112: error: 'get_reg_init_bus' undeclared (first use in
> this function)
> cs8900.c:112: error: (Each undeclared identifier is reported only
> once
> cs8900.c:112: error: for each function it appears in.)
> cs8900.c:137:37: error: macro "get_reg_init_bus" passed 2 arguments,
> but takes just 1
> cs8900.c: In function 'cs8900_get_enetaddr':
> cs8900.c:137: error: 'get_reg_init_bus' undeclared (first use in
> this function)
> cs8900.c:161:33: error: macro "get_reg_init_bus" passed 2 arguments,
> but takes just 1
> cs8900.c: In function 'cs8900_halt':
> cs8900.c:161: error: 'get_reg_init_bus' undeclared (first use in
> this function)
> cs8900.c:170:38: error: macro "get_reg_init_bus" passed 2 arguments,
> but takes just 1
> cs8900.c: In function 'cs8900_init':
> cs8900.c:170: error: 'get_reg_init_bus' undeclared (first use in
> this function)
> make[1]: *** [/work/wd/tmp-arm/drivers/net/cs8900.o] Error 1
>
> 6) imx27lite:
>
> mxcmmc.c: In function 'mxcmci_softreset':
> mxcmmc.c:139: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mxcmmc.c:140: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mxcmmc.c:144: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mxcmmc.c:146: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mxcmmc.c: In function 'mxcmci_setup_data':
> mxcmmc.c:157: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mxcmmc.c:158: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mxcmmc.c: In function 'mxcmci_start_cmd':
> mxcmmc.c:188: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mxcmmc.c:190: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mxcmmc.c: In function 'mxcmci_read_response':
> mxcmmc.c:250: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mxcmmc.c:251: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mxcmmc.c:255: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mxcmmc.c:256: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mxcmmc.c:257: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mxcmmc.c: In function 'mxcmci_set_clk_rate':
> mxcmmc.c:448: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mxcmmc.c: In function 'mxcmci_set_ios':
> mxcmmc.c:461: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mxcmmc.c:463: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mxcmmc.c: In function 'mxcmci_init':
> mxcmmc.c:475: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mxcmmc.c:483: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> nand_util.c:45:2: warning: #warning Please define
> CONFIG_SYS_64BIT_VSPRINTF for correct output!
>
> 7) lpd7a400:
>
> smc91111_eeprom.c: In function 'smc91111_eeprom':
> smc91111_eeprom.c:76: warning: implicit declaration of function
> 'SMC_inw'
> smc91111_eeprom.c:224: warning: implicit declaration of function
> 'SMC_outw'
> smc91111_eeprom.c: In function 'print_macaddr':
> smc91111_eeprom.c:278: warning: implicit declaration of function
> 'SMC_inb'
> /work/wd/tmp-arm/examples/standalone/smc91111_eeprom.o: In function
> `dump_reg':
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:388:
> undefined reference to `SMC_outw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:389:
> undefined reference to `SMC_inw'
> /work/wd/tmp-arm/examples/standalone/smc91111_eeprom.o: In function
> `write_eeprom_reg':
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:357:
> undefined reference to `SMC_outw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:358:
> undefined reference to `SMC_outw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:360:
> undefined reference to `SMC_outw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:361:
> undefined reference to `SMC_outw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:362:
> undefined reference to `SMC_inw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:362:
> undefined reference to `SMC_outw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:365:
> undefined reference to `SMC_inw'
> /work/wd/tmp-arm/examples/standalone/smc91111_eeprom.o: In function
> `read_eeprom_reg':
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:335:
> undefined reference to `SMC_outw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:336:
> undefined reference to `SMC_outw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:338:
> undefined reference to `SMC_outw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:339:
> undefined reference to `SMC_inw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:339:
> undefined reference to `SMC_outw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:342:
> undefined reference to `SMC_inw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:349:
> undefined reference to `SMC_inw'
> /work/wd/tmp-arm/examples/standalone/smc91111_eeprom.o: In function
> `copy_from_eeprom':
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:257:
> undefined reference to `SMC_outw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:258:
> undefined reference to `SMC_inw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:258:
> undefined reference to `SMC_outw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:261:
> undefined reference to `SMC_inw'
> /work/wd/tmp-arm/examples/standalone/smc91111_eeprom.o: In function
> `print_macaddr':
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:276:
> undefined reference to `SMC_outw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:278:
> undefined reference to `SMC_inb'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:281:
> undefined reference to `SMC_inb'
> /work/wd/tmp-arm/examples/standalone/smc91111_eeprom.o: In function
> `smc91111_eeprom':
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:76:
> undefined reference to `SMC_inw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:224:
> undefined reference to `SMC_outw'
> /home/wd/git/u-boot/work/examples/standalone/smc91111_eeprom.c:225:
> undefined reference to `SMC_outw'
> make[1]: *** [/work/wd/tmp-arm/examples/standalone/smc91111_eeprom]
> Error 1
>
> 8) mv88f6281gtw_ge, openrd_base, rd6281a, sheevaplug:
>
> kirkwood_egiga.c: In function 'kwgbe_init':
> kirkwood_egiga.c:447: warning: dereferencing type-punned pointer
> will break strict-aliasing rules
> kirkwood_egiga.c: In function 'kwgbe_recv':
> kirkwood_egiga.c:608: warning: dereferencing type-punned pointer
> will break strict-aliasing rules
>
> 9) trab:
>
> timer.c: In function 'reset_cpu':
> timer.c:208: warning: implicit declaration of function 'disable_vfd'
>
> 10) voiceblue:
>
> /work/wd/tmp-
> arm/board/voiceblue/../../lib_generic/libgeneric.a(string.o): In function
> `strcmp':
> /home/wd/git/u-boot/work/lib_generic/string.c:156: multiple
> definition of `strcmp'
> /work/wd/tmp-
> arm/board/voiceblue/../../examples/standalone/libstubs.a(stubs.o):/home/wd
> /git/u-boot/work/include/_exports.h:24: first defined here
>
> 11) xaeniax:
>
> smc91111_eeprom.c: In function 'print_macaddr':
> smc91111_eeprom.c:278: warning: suggest parentheses around + or - in
> operand of &
> smc91111_eeprom.c:281: warning: suggest parentheses around + or - in
> operand of &
>
> 12) xsengine:
>
> smc91111_eeprom.c: In function 'print_macaddr':
> smc91111_eeprom.c:278: warning: suggest parentheses around + or -
> inside shift
> smc91111_eeprom.c:281: warning: suggest parentheses around + or -
> inside shift
>
>
>
>
> PowerPC: pretty well, problems:
> =========
>
> 1) AP1000, MPC8536DS, MPC8536DS_NAND, MPC8536DS_SDCARD,
> MPC8536DS_SPIFLASH, MPC8544DS, MVBC_P, P2020DS, P2020DS_36BIT,
> PM854:
>
> e1000.c: In function 'e1000_transmit':
> e1000.c:5027: warning: passing argument 1 of 'virt_to_phys' discards
> qualifiers from pointer target type
>
> 2) BMW:
>
> tigon3.c: In function 'LM_InitializeAdapter':
> tigon3.c:1625: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> tigon3.c: In function 'LM_ResetAdapter':
> tigon3.c:2616: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> tigon3.c:2630: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
>
> 3) EVB64260, P3G4, ZUMA:
>
> mpsc.c: In function 'mpsc_putchar_early':
> mpsc.c:121: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c:127: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'mpsc_getchar':
> mpsc.c:204: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c:207: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'mpsc_init':
> mpsc.c:273: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c:274: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'galbrg_set_baudrate':
> mpsc.c:402: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'galbrg_set_CDV':
> mpsc.c:416: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c:419: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'galbrg_enable':
> mpsc.c:429: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c:431: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'galbrg_disable':
> mpsc.c:441: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c:443: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'galbrg_set_clksrc':
> mpsc.c:453: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c:456: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'galmpsc_connect':
> mpsc.c:585: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c:599: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'galmpsc_route_rx_clock':
> mpsc.c:630: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c:637: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'galmpsc_route_tx_clock':
> mpsc.c:647: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c:654: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'galmpsc_config_channel_regs':
> mpsc.c:685: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c:686: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'galmpsc_set_brkcnt':
> mpsc.c:707: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c:710: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'galmpsc_set_tcschar':
> mpsc.c:720: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c:723: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'galmpsc_set_char_length':
> mpsc.c:733: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c:736: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'galmpsc_set_stop_bit_length':
> mpsc.c:746: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c:748: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'galmpsc_set_parity':
> mpsc.c:758: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c:767: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'galmpsc_enter_hunt':
> mpsc.c:777: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c:779: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> mpsc.c: In function 'galmpsc_shutdown':
> mpsc.c:809: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
>
>
> MIPS: OK
> ======
>
> MIPS-EL: OK
> =========
>
>
>
> Please architecture and board maintainers: help testing the rmaining
> architectures, and fix the raised problems.
>
> Thanks in advance.
>
> Best regards,
>
> Wolfgang Denk
>
> --
> 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
> We fight only when there is no other choice. We prefer the ways of
> peaceful contact.
> -- Kirk, "Spectre of the Gun", stardate 4385.3
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] [STATUS] v2009.11-rc1 is out
2009-10-28 14:53 ` Paulraj, Sandeep
@ 2009-10-28 15:58 ` Wolfgang Denk
2009-10-28 16:13 ` Paulraj, Sandeep
0 siblings, 1 reply; 13+ messages in thread
From: Wolfgang Denk @ 2009-10-28 15:58 UTC (permalink / raw)
To: u-boot
Dear "Paulraj, Sandeep",
In message <0554BEF07D437848AF01B9C9B5F0BC5D939570C2@dlee01.ent.ti.com> you wrote:
>
> > ARM: lots of issues:
> > =====
> >
> > 1) SBC35_A9G20:
> >
> > nand_util.c:45:2: warning: #warning Please define
> > CONFIG_SYS_64BIT_VSPRINTF for correct output!
> > m41t94.c: In function 'rtc_reset':
> > m41t94.c:123: warning: 'return' with a value, in function returning
> > void
> Wolfgang, this is ATMEL and we know there is no custodian for that
But there is a board maintainer (Albin Tonnerre), and then it falls on
Tom as ARM custodian.
> >
> > 2) TNY_A9260.ERR, TNY_A9G20.ERR:
> >
> > nand_util.c:45:2: warning: #warning Please define
> > CONFIG_SYS_64BIT_VSPRINTF for correct output!
>
> Same here, I can submit simple 1 line patches for these
Thanks, but this is also Albin's bailiwick.
Best regards,
Wolfgang Denk
--
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 release of emotion is what keeps us health. Emotionally
healthy."
"That may be, Doctor. However, I have noted that the healthy release
of emotion is frequently unhealthy for those closest to you."
-- McCoy and Spock, "Plato's Stepchildren", stardate 5784.3
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] [STATUS] v2009.11-rc1 is out
2009-10-28 15:58 ` Wolfgang Denk
@ 2009-10-28 16:13 ` Paulraj, Sandeep
2009-10-31 17:57 ` Tom
2009-11-11 12:36 ` Albin Tonnerre
0 siblings, 2 replies; 13+ messages in thread
From: Paulraj, Sandeep @ 2009-10-28 16:13 UTC (permalink / raw)
To: u-boot
>
> > >
> > > 2) TNY_A9260.ERR, TNY_A9G20.ERR:
> > >
> > > nand_util.c:45:2: warning: #warning Please define
> > > CONFIG_SYS_64BIT_VSPRINTF for correct output!
> >
> > Same here, I can submit simple 1 line patches for these
>
> Thanks, but this is also Albin's bailiwick.
I submitted two 1 line patches
[PATCH] Fix Compliation warning for TNY-A9260 and TNY-A9G20
And
[PATCH] Fix Compliation warning for SBC35-A9G20 board
Tom you can apply these 2 your tree.
>
>
> Best regards,
>
> Wolfgang Denk
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] [STATUS] v2009.11-rc1 is out
2009-10-28 16:13 ` Paulraj, Sandeep
@ 2009-10-31 17:57 ` Tom
2009-11-11 12:36 ` Albin Tonnerre
1 sibling, 0 replies; 13+ messages in thread
From: Tom @ 2009-10-31 17:57 UTC (permalink / raw)
To: u-boot
Paulraj, Sandeep wrote:
>>>> 2) TNY_A9260.ERR, TNY_A9G20.ERR:
>>>>
>>>> nand_util.c:45:2: warning: #warning Please define
>>>> CONFIG_SYS_64BIT_VSPRINTF for correct output!
>>> Same here, I can submit simple 1 line patches for these
>> Thanks, but this is also Albin's bailiwick.
>
> I submitted two 1 line patches
>
> [PATCH] Fix Compliation warning for TNY-A9260 and TNY-A9G20
>
> And
>
> [PATCH] Fix Compliation warning for SBC35-A9G20 board
>
> Tom you can apply these 2 your tree.
>>
>> Best regards,
>>
>> Wolfgang Denk
>>
>
Since these are part of the mainline master, I will get these when
arm/master is updated. I was planning on doing this when 2009.11 was
released on Nov 18.
Do you need this sooner ?
Tom
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] [STATUS] v2009.11-rc1 is out
2009-10-28 13:42 [U-Boot] [STATUS] v2009.11-rc1 is out Wolfgang Denk
2009-10-28 14:53 ` Paulraj, Sandeep
@ 2009-11-03 8:04 ` rhabarber1848
2009-11-03 9:37 ` Detlev Zundel
2009-11-03 13:10 ` Wolfgang Denk
1 sibling, 2 replies; 13+ messages in thread
From: rhabarber1848 @ 2009-11-03 8:04 UTC (permalink / raw)
To: u-boot
Am Wed, 28 Oct 2009 14:42:10 +0100 schrieb Wolfgang Denk:
> just in case you did not notice yet: U-Boot v2009.11-rc1 was released
> last night.
Hi,
I just tested it on my Dbox2 board where U-Boot 2009.08 is working
perfectly well with unchanged config.
But now U-Boot raises an exception during machine check:
=============================================================================
U-Boot 2009.11 (Tuxbox) (Nov 03 2009 - 08:59:24)
CPU: PPC823ZTnnB2 at 66 MHz: 2 kB I-Cache 1 kB D-Cache
Board: DBOX2, Sagem, BMon V1.0
Watchdog enabled
I2C: ready
DRAM: 64 MB
Top of RAM usable for U-Boot at: 04000000
Reserving 201k for U-Boot at: 03fcd000
Reserving 144k for malloc() at: 03fa9000
Reserving 60 Bytes for Board Info at: 03fa8fc4
Reserving 52 Bytes for Global Data at: 03fa8f90
Stack Pointer at: 03fa8f78
New Stack Pointer is: 03fa8f78
Now running in RAM - U-Boot at: 03fcd000
FLASH: 8 MB
FB: ready
Bus Fault @ 0x03fcfe0c, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): regs 03fa8d88 Unknown values in msr
NIP: 03FCFE0C XER: 8000007F LR: 03FCFD98 REGS: 03fa8d88 TRAP: 0200 DAR: 3038B700
MSR: 00001002 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00
GPR00: 30323030 03FA8E78 03FA8F90 00000008 30323030 30376666 00000000 000686CC
GPR08: 03FF56CC 3038B6FC 00000002 000F423F FF002848 00031CBC 03FFB600 03F8D000
GPR16: 00000000 00000000 00000000 00000000 20004000 00000001 60634001 90640170
GPR24: 03FA8F90 00000040 03FCD000 00000000 0006868C 00000001 03FFB678 03FCD000
Call backtrace:
machine check
=============================================================================
The remaining boot messages would be:
In: serial
Out: serial
Err: serial
Net: SCC ETHERNET
LCD: ready
Any pointers where I could start debugging?
Cheers, rhabarber1848
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] [STATUS] v2009.11-rc1 is out
2009-11-03 8:04 ` rhabarber1848
@ 2009-11-03 9:37 ` Detlev Zundel
2009-11-03 10:17 ` rhabarber1848
2009-11-03 10:41 ` [U-Boot] " rhabarber1848
2009-11-03 13:10 ` Wolfgang Denk
1 sibling, 2 replies; 13+ messages in thread
From: Detlev Zundel @ 2009-11-03 9:37 UTC (permalink / raw)
To: u-boot
Hi rhabarber1848,
> I just tested it on my Dbox2 board where U-Boot 2009.08 is working
> perfectly well with unchanged config.
> But now U-Boot raises an exception during machine check:
>
> =============================================================================
> U-Boot 2009.11 (Tuxbox) (Nov 03 2009 - 08:59:24)
>
> CPU: PPC823ZTnnB2 at 66 MHz: 2 kB I-Cache 1 kB D-Cache
> Board: DBOX2, Sagem, BMon V1.0
> Watchdog enabled
> I2C: ready
> DRAM: 64 MB
> Top of RAM usable for U-Boot at: 04000000
> Reserving 201k for U-Boot at: 03fcd000
> Reserving 144k for malloc() at: 03fa9000
> Reserving 60 Bytes for Board Info at: 03fa8fc4
> Reserving 52 Bytes for Global Data at: 03fa8f90
> Stack Pointer at: 03fa8f78
> New Stack Pointer is: 03fa8f78
> Now running in RAM - U-Boot at: 03fcd000
> FLASH: 8 MB
> FB: ready
> Bus Fault @ 0x03fcfe0c, fixup 0x00000000
> Machine check in kernel mode.
> Caused by (from msr): regs 03fa8d88 Unknown values in msr
> NIP: 03FCFE0C XER: 8000007F LR: 03FCFD98 REGS: 03fa8d88 TRAP: 0200 DAR: 3038B700
> MSR: 00001002 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00
>
> GPR00: 30323030 03FA8E78 03FA8F90 00000008 30323030 30376666 00000000 000686CC
> GPR08: 03FF56CC 3038B6FC 00000002 000F423F FF002848 00031CBC 03FFB600 03F8D000
> GPR16: 00000000 00000000 00000000 00000000 20004000 00000001 60634001 90640170
> GPR24: 03FA8F90 00000040 03FCD000 00000000 0006868C 00000001 03FFB678 03FCD000
> Call backtrace:
> machine check
> =============================================================================
>
> The remaining boot messages would be:
>
> In: serial
> Out: serial
> Err: serial
> Net: SCC ETHERNET
> LCD: ready
>
> Any pointers where I could start debugging?
Grepping through my source, I cannot find such a configuration - do you
plan to submit this support here sometime?
Apart from that, I'd strongly start looking for implications of the
recent rewrite of the relocation strategy to code not in mainline.
Given that the last message is "FB:" (also not in mainline), the
corresponding code would be my start for the debugging.
Apart from that you could also use the information in our DULG[1] for
debugging of U-Boot after relocation and use gdb to find the code
corresponding to "0x3fcfe0c". You'll not even need a JTAG debugger for
this address lookup as all neccessary informations are in your dump ;)
Cheers
Detlev
[1] http://www.denx.de/wiki/view/DULG/DebuggingUBoot#Section_10.1.2.
--
Man is a fool, and woman, for tolerating him, is a damned fool
-- Mark Twain
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] [STATUS] v2009.11-rc1 is out
2009-11-03 9:37 ` Detlev Zundel
@ 2009-11-03 10:17 ` rhabarber1848
2009-11-03 10:47 ` Detlev Zundel
2009-11-03 10:41 ` [U-Boot] " rhabarber1848
1 sibling, 1 reply; 13+ messages in thread
From: rhabarber1848 @ 2009-11-03 10:17 UTC (permalink / raw)
To: u-boot
Hi,
Am Tue, 03 Nov 2009 10:37:41 +0100 schrieb Detlev Zundel:
> Grepping through my source, I cannot find such a configuration - do you
> plan to submit this support here sometime?
the code was written by other people and is maintained out-of-uboot-tree
in our public CVS.
After unpacking U-Boot 2009.08 these files are copied into the source
tree: http://cvs.tuxbox.org/tuxbox/boot/u-boot-tuxbox/
Then this patch is applied
http://cvs.tuxbox.org/tuxbox/cdk/Patches/u-boot-2009.08.diff?view=markup
This is the board config used:
http://cvs.tuxbox.org/tuxbox/cdk/config/u-boot.dbox2.h.m4?view=markup
I do not know if the code meets U-Boot coding standards, but it works ;)
Adding the code to the U-Boot tree makes sense but I think I do not have
the needed skills to support it in the future.
> Apart from that, I'd strongly start looking for implications of the
> recent rewrite of the relocation strategy to code not in mainline.
Ah, this is the message I was waiting for. After 2009.08 I did not follow
the coding process due to lack of time so I am sure I missed something.
Do you mean "[TESTING PATCH] ppc: Relocation test patch" from Sep 12th?
Btw, I am using gcc-3.4.6.
> Apart from that you could also use the information in our DULG[1] for
> debugging of U-Boot after relocation and use gdb
I?ll try this as well.
Cheers, rhabarber1848
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] [STATUS] v2009.11-rc1 is out
2009-11-03 9:37 ` Detlev Zundel
2009-11-03 10:17 ` rhabarber1848
@ 2009-11-03 10:41 ` rhabarber1848
1 sibling, 0 replies; 13+ messages in thread
From: rhabarber1848 @ 2009-11-03 10:41 UTC (permalink / raw)
To: u-boot
Am Tue, 03 Nov 2009 10:37:41 +0100 schrieb Detlev Zundel:
> Apart from that, I'd strongly start looking for implications of the
> recent rewrite of the relocation strategy to code not in mainline.
Hi,
with great relieve I can say the removing "*(.fixup)" from the *.lds
files solved the problem:
U-Boot 2009.11 (Tuxbox) (Nov 03 2009 - 11:36:34)
CPU: PPC823ZTnnB2 at 66 MHz: 2 kB I-Cache 1 kB D-Cache
Board: DBOX2, Sagem, BMon V1.0
Watchdog enabled
I2C: ready
DRAM: 64 MB
FLASH: 8 MB
FB: ready
In: serial
Out: serial
Err: serial
Net: SCC ETHERNET
BOOTP broadcast 1
Cheers, rhabarber1848
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] [STATUS] v2009.11-rc1 is out
2009-11-03 10:17 ` rhabarber1848
@ 2009-11-03 10:47 ` Detlev Zundel
2009-11-03 11:03 ` [U-Boot] Support dbox in mainline, was: " rhabarber1848
0 siblings, 1 reply; 13+ messages in thread
From: Detlev Zundel @ 2009-11-03 10:47 UTC (permalink / raw)
To: u-boot
Hi rhabarber1848,
>> Grepping through my source, I cannot find such a configuration - do you
>> plan to submit this support here sometime?
>
> the code was written by other people and is maintained out-of-uboot-tree
> in our public CVS.
So why not move mainline? Usually it's pretty fun to get other peoples
code into mainline *lol*
> After unpacking U-Boot 2009.08 these files are copied into the source
> tree: http://cvs.tuxbox.org/tuxbox/boot/u-boot-tuxbox/
Ah uh, I would even offer some help in the process (like adding a branch
in the u-boot-testing repository), but this instruction is somewhat
unspecific, i.e. I see three boards being supported. If we want to get
the support mainline, we should start with only one of them - including
only the neccessary changes, i.e. cpu/ppc4xx/serial_sicc.c is very
likely not relevant for the dbox :)
> Then this patch is applied
> http://cvs.tuxbox.org/tuxbox/cdk/Patches/u-boot-2009.08.diff?view=markup
>
> This is the board config used:
> http://cvs.tuxbox.org/tuxbox/cdk/config/u-boot.dbox2.h.m4?view=markup
>
> I do not know if the code meets U-Boot coding standards, but it works ;)
> Adding the code to the U-Boot tree makes sense but I think I do not have
> the needed skills to support it in the future.
You will learn the skills while doing it - no problem.
>> Apart from that, I'd strongly start looking for implications of the
>> recent rewrite of the relocation strategy to code not in mainline.
>
> Ah, this is the message I was waiting for. After 2009.08 I did not follow
> the coding process due to lack of time so I am sure I missed something.
> Do you mean "[TESTING PATCH] ppc: Relocation test patch" from Sep 12th?
> Btw, I am using gcc-3.4.6.
This is a rather long story, but it starts with this commit:
commit 858290178f222d998b6425d85cf06822467918f3
Author: Peter Tyser <ptyser@xes-inc.com>
Date: Mon Sep 21 11:20:25 2009 -0500
ppc: Enable full relocation to RAM
The following changes allow U-Boot to fully relocate from flash to
RAM:
- Remove linker scripts' .fixup sections from the .text section
- Add -mrelocatable to PLATFORM_RELFLAGS for all boards
- Define CONFIG_RELOC_FIXUP_WORKS for all boards
Previously, U-Boot would partially relocate, but statically initialized
pointers needed to be manually relocated.
Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
On top of this many fixes have been provided already. Just grep for
"relocat" in "git log".
Cheers
Detlev
--
These days, even the most pure and abstract mathematics is in danger
to be applied.
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] Support dbox in mainline, was: Re: [STATUS] v2009.11-rc1 is out
2009-11-03 10:47 ` Detlev Zundel
@ 2009-11-03 11:03 ` rhabarber1848
0 siblings, 0 replies; 13+ messages in thread
From: rhabarber1848 @ 2009-11-03 11:03 UTC (permalink / raw)
To: u-boot
Am Tue, 03 Nov 2009 11:47:08 +0100 schrieb Detlev Zundel:
>> After unpacking U-Boot 2009.08 these files are copied into the source
>> tree: http://cvs.tuxbox.org/tuxbox/boot/u-boot-tuxbox/
>
> Ah uh, I would even offer some help in the process (like adding a branch
> in the u-boot-testing repository), but this instruction is somewhat
> unspecific, i.e. I see three boards being supported. If we want to get
> the support mainline, we should start with only one of them - including
> only the neccessary changes, i.e. cpu/ppc4xx/serial_sicc.c is very
> likely not relevant for the dbox :)
>
the Dreambox files are not used atm, they were added 5 years ago, I never
cared about them.
The IPBox stuff is used with U-Boot 1.2.0, I do not have plans to upgrade
to a more recent U-Boot version because I do not have the hardware for
testing.
So only the Dbox is left, and yes, merging it will be fun;)
Our code includes functions to read files (config, logos) from a JFFS2
partition, display LCD and framebuffer logos during boot, some unfinished
support for booting from HDD and loading kernels from Squashfs
partitions.
The Squashfs code is based on Squashfs 3.0, it can not be upgrade to 3.3
or 4.x because we use Linux 2.4.37.6, where Squashfs > 3.0 is not
available.
Squashfs support in U-Boot also includes optional LZMA support, but not
the LZMA 4.65-based code from U-Boot, but LZMA 4.40 included in fs/
squashfs/. It is therefore not possible to link both LZMA libs into U-
Boot at compile time. This is not needed for us because the root
filesystem is either Squashfs/LZMA-4.40 or JFFS2/LZMA-4.65.
As hinted before, I do not have much C skills to do necessary cleanups
nor do I want to be mentioned as official maintainer ;)
But the code is in use for many years by lots of users so technically
there should not be many problems.
Cheers, rhabarber1848
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] [STATUS] v2009.11-rc1 is out
2009-11-03 8:04 ` rhabarber1848
2009-11-03 9:37 ` Detlev Zundel
@ 2009-11-03 13:10 ` Wolfgang Denk
1 sibling, 0 replies; 13+ messages in thread
From: Wolfgang Denk @ 2009-11-03 13:10 UTC (permalink / raw)
To: u-boot
Dear rhabarber1848,
In message <hcoo6m$ojo$1@ger.gmane.org> you wrote:
>
> I just tested it on my Dbox2 board where U-Boot 2009.08 is working
> perfectly well with unchanged config.
> But now U-Boot raises an exception during machine check:
>
> =============================================================================
> U-Boot 2009.11 (Tuxbox) (Nov 03 2009 - 08:59:24)
>
> CPU: PPC823ZTnnB2 at 66 MHz: 2 kB I-Cache 1 kB D-Cache
> Board: DBOX2, Sagem, BMon V1.0
This does not seem to be any of the boards supported in mainline. It
does not even show a correct version id, so I'm not surprised that
more bugs are present in this code.
Best regards,
Wolfgang Denk
--
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
Many companies that have made themselves dependent on [the equipment
of a certain major manufacturer] (and in doing so have sold their
soul to the devil) will collapse under the sheer weight of the un-
mastered complexity of their data processing systems.
-- Edsger W. Dijkstra, SIGPLAN Notices, Volume 17, Number 5
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] [STATUS] v2009.11-rc1 is out
2009-10-28 16:13 ` Paulraj, Sandeep
2009-10-31 17:57 ` Tom
@ 2009-11-11 12:36 ` Albin Tonnerre
1 sibling, 0 replies; 13+ messages in thread
From: Albin Tonnerre @ 2009-11-11 12:36 UTC (permalink / raw)
To: u-boot
On Wed, 28 Oct 2009 11:13 -0500, Paulraj, Sandeep wrote :
> >
> > > >
> > > > 2) TNY_A9260.ERR, TNY_A9G20.ERR:
> > > >
> > > > nand_util.c:45:2: warning: #warning Please define
> > > > CONFIG_SYS_64BIT_VSPRINTF for correct output!
> > >
> > > Same here, I can submit simple 1 line patches for these
> >
> > Thanks, but this is also Albin's bailiwick.
>
> I submitted two 1 line patches
>
> [PATCH] Fix Compliation warning for TNY-A9260 and TNY-A9G20
>
> And
>
> [PATCH] Fix Compliation warning for SBC35-A9G20 board
Thanks a lot for this!
Cheers,
--
Albin Tonnerre, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2009-11-11 12:36 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-10-28 13:42 [U-Boot] [STATUS] v2009.11-rc1 is out Wolfgang Denk
2009-10-28 14:53 ` Paulraj, Sandeep
2009-10-28 15:58 ` Wolfgang Denk
2009-10-28 16:13 ` Paulraj, Sandeep
2009-10-31 17:57 ` Tom
2009-11-11 12:36 ` Albin Tonnerre
2009-11-03 8:04 ` rhabarber1848
2009-11-03 9:37 ` Detlev Zundel
2009-11-03 10:17 ` rhabarber1848
2009-11-03 10:47 ` Detlev Zundel
2009-11-03 11:03 ` [U-Boot] Support dbox in mainline, was: " rhabarber1848
2009-11-03 10:41 ` [U-Boot] " rhabarber1848
2009-11-03 13:10 ` Wolfgang Denk
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.