October 2004 - U-Boot

[U-Boot-Users] [PATCH] common framebuffer for PXA and MPC8xx
by himba 10 Oct '04

10 Oct '04

Hi, I reworked my previous proposal for common framebuffer interface on PXA and MPC8xx (other platforms should find it usefull too). There are some differences in contrast to patch I posted on 08.08.2004. They are: o got rid of two extra header files (pxafb.h and mpc823fb.h) introduced earlier o all common stuff is in include/lcd.h and common/lcd.c o CPU dependent stuff remains in cpu/mpc8xx/lcd.c and cpu/pxa/pxafb.c See my previous post for more details. I tested that patch does not break pxa and 8xx boards with ./MAKEALL [pxa|8xx]. CHANGELOG: Patch by Hinko Kocevar, 21 Aug 2004: Group common framebuffer functions in common/lcd.c Group common framebuffer macros and #defines in include/lcd.h Provide calc_fbsize() for video ATAG regards, himba

2 1

[U-Boot-Users] [Patch]A fix in cfi_flash.c
by Sam Song 10 Oct '04

10 Oct '04

Hi, The following patch makes the sector number next to (RO) in order as usual after protect on operation.Really a samll fix... * Patch by Sam Song, 21 August 2004: - Make (RO) next number display in order after protect on Best regards, Sam ==================================================== diff -purN u-boot-2004-08-18-2000-orig/drivers/cfi_flash.c u-boot-2004-08-18-2000/drivers/cfi_flash.c --- u-boot-2004-08-18-2000-orig/drivers/cfi_flash.c Sat Aug 21 17:10:21 2004 +++ u-boot-2004-08-18-2000/drivers/cfi_flash.c Sat Aug 21 17:17:02 2004 @@ -462,7 +462,7 @@ void flash_print_info (flash_info_t * in if ((i % 5) == 0) printf ("\n "); printf (" %08lX%s", - info->start[i], info->protect[i] ? " (RO)" : " "); + info->start[i], info->protect[i] ? " (RO) " : " "); #endif } putc ('\n'); _________________________________________________________ Do You Yahoo!? 150万曲MP3疯狂搜，带您闯入音乐殿堂 http://music.yisou.com/ 美女明星应有尽有，搜遍美图、艳图和酷图 http://image.yisou.com 1G就是1000兆，雅虎电邮自助扩容！ http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_…

2 1

[U-Boot-Users] [Patch]A typo in README
by Sam Song 10 Oct '04

10 Oct '04

Hi, I need to send several small patches although there is sth wrong with u-boot CVS server.All against u-boot-2004-08-18-2000. * Patch by Sam Song, 21 August 2004: - Fix a typo in README Best regards, Sam ============================================= diff -purN u-boot-2004-08-18-2000-orig/README u-boot-2004-08-18-2000/README --- u-boot-2004-08-18-2000-orig/README Sat Aug 21 17:10:21 2004 +++ u-boot-2004-08-18-2000/README Sat Aug 21 17:14:59 2004 @@ -784,7 +784,7 @@ The following options need to be configu supported (PIP405, MIP405, MPC5200); define CONFIG_USB_UHCI to enable it. define CONFIG_USB_KEYBOARD to enable the USB Keyboard - end define CONFIG_USB_STORAGE to enable the USB + and define CONFIG_USB_STORAGE to enable the USB storage devices. Note: Supported are USB Keyboards and USB Floppy drives _________________________________________________________ Do You Yahoo!? 150万曲MP3疯狂搜，带您闯入音乐殿堂 http://music.yisou.com/ 美女明星应有尽有，搜遍美图、艳图和酷图 http://image.yisou.com 1G就是1000兆，雅虎电邮自助扩容！ http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_…

2 1

[U-Boot-Users] [PATCH] lubbock board
by himba 10 Oct '04

10 Oct '04

Hi, Running ./MAKEALL pxa fails with lubbock board because no LCD panel is configured. It is using SHARP LM8V31 according to specs. I'm supplying fix. Maintainer is CC'ed, just in case. CHANGELOG: Patch by Hinko Kocevar, 21 Aug 2004: Define type of LCD panel if CONFIG_LCD is used regards, himba --- u-boot/include/configs/lubbock.h 2004-01-21 00:12:34.000000000 +0100 +++ lcd-u-boot/include/configs/lubbock.h 2004-08-21 11:37:50.000000000 +0200 @@ -43,6 +43,9 @@ #define CONFIG_PXA250 1 /* This is an PXA250 CPU */ #define CONFIG_LUBBOCK 1 /* on an LUBBOCK Board */ #define CONFIG_LCD 1 +#ifdef CONFIG_LCD +#define CONFIG_SHARP_LM8V31 +#endif #define CONFIG_MMC 1 #define BOARD_LATE_INIT 1

2 1

[U-Boot-Users] [PATCH] cradle board
by himba 10 Oct '04

10 Oct '04

Hi, Running ./MAKEALL pxa produces this warning with cradle board. warning: deprecated use of label at end of compound statement I'm supplying fix. Maintainer is CC'ed, just in case. CHANGELOG: Patch by Hinko Kocevar, 21 Aug 2004: Fix compiler warning about label usage regards, himba --- u-boot/board/cradle/flash.c 2003-09-18 11:21:33.000000000 +0200 +++ lcd-u-boot/board/cradle/flash.c 2004-08-21 10:26:02.000000000 +0200 @@ -133,7 +133,7 @@ info++; } -Done: +Done:; } /*-----------------------------------------------------------------------

2 1

[U-Boot-Users] Proposed change; What do you think?
by Jon Loeliger 10 Oct '04

10 Oct '04

Guys, I'd like to get your opinion on a proposed change to a few files that handle some aspects of the various enetaddr fields as found in asm-ppc/u-boot.h, common/cmd_bdinfo.c and lib_ppc/board.c. In particular, I'd like to propose a shift from having these fields be present when certain boards are #defined to having these fields be present when CONFIG_ETH1ADDR symbols are defined. So, don't take the following as a literal patch. It is just some cut-n-paste diffs to show what I mean. There are only a few boards for which this might make a difference. I'm the bit swizzler for most of them (MPC85xxXDS), but the others include the PN62, the PPCCHAMEONEVB, the 440GX, the GT_6426x. SXNI855T, SVM_SC8xx and possibly the DB64360, DB64460, CATcenter, and OCOTEA boards. The latter define CONFIG_ETH1ADDR but don't have their cases include in places like the coomon/cmd_bdinfo.c. I think this sorr of change would make the handling of the ETH1ADDR, ETH2ADDR and ETH3ADDR more consistent across any platform that defines these fields. Opinions? If you buy this, I'll submit a proper patch, of course. Thanks, jdl --- include/asm-ppc/u-boot.h 2004/04/13 21:42:46 1.1.1.2.2.1 +++ include/asm-ppc/u-boot.h 2004/08/06 10:51:41 @@ -77,25 +77,15 @@ #if defined(CONFIG_HYMOD) hymod_conf_t bi_hymod_conf; /* hymod configuration information */ #endif -#if defined(CFG_GT_6426x) || \ - defined(CONFIG_PN62) || \ - defined(CONFIG_PPCHAMELEONEVB) || \ - defined(CONFIG_SXNI855T) || \ - defined(CONFIG_SVM_SC8xx) || \ - defined(CONFIG_MPC8540ADS) || \ - defined(CONFIG_MPC8555CDS) || \ - defined(CONFIG_MPC8560ADS) || \ - defined(CONFIG_440_GX) +#ifdef CONFIG_ETH1ADDR /* second onboard ethernet port */ unsigned char bi_enet1addr[6]; #endif -#if defined(CFG_GT_6426x) || defined(CONFIG_SVM_SC8xx) || \ - defined(CONFIG_MPC8540ADS) || defined(CONFIG_MPC8560ADS) || \ - defined(CONFIG_MPC8555CDS) || defined(CONFIG_440_GX) +#ifdef CONFIG_ETH2ADDR /* third onboard ethernet port */ unsigned char bi_enet2addr[6]; #endif -#if defined(CONFIG_440_GX) +#ifdef CONFIG_ETH3ADDR unsigned char bi_enet3addr[6]; #endif #if defined(CONFIG_405GP) || defined(CONFIG_405EP) || defined (CONFIG_440_GX) and also: diff -u -r1.1.1.2.2.2 cmd_bdinfo.c --- common/cmd_bdinfo.c 2004/06/17 20:37:25 1.1.1.2.2.2 +++ common/cmd_bdinfo.c 2004/08/06 10:51:40 @@ -83,16 +83,13 @@ for (i=0; i<6; ++i) { printf ("%c%02X", i ? ':' : ' ', bd->bi_enetaddr[i]); } -#if (defined CONFIG_PN62) || (defined CONFIG_PPCHAMELEONEVB) \ - || (defined CONFIG_MPC8540ADS) || (defined CONFIG_MPC8560ADS) \ - || (defined CONFIG_MPC8555CDS) +#ifdef CONFIG_ETH1ADDR puts ("\neth1addr ="); for (i=0; i<6; ++i) { printf ("%c%02X", i ? ':' : ' ', bd->bi_enet1addr[i]); } -#endif /* CONFIG_PN62 */ -#if defined(CONFIG_MPC8540ADS) || defined(CONFIG_MPC8560ADS) \ - || defined(CONFIG_MPC8555CDS) +#endif /* CONFIG_ETH1ADDR */ +#ifdef CONFIG_ETH2ADDR puts ("\neth2addr ="); for (i=0; i<6; ++i) { printf ("%c%02X", i ? ':' : ' ', bd->bi_enet2addr[i]) And one other place over in: diff -u -r1.1.1.2.2.4 board.c --- lib_ppc/board.c 2004/06/17 20:37:41 1.1.1.2.2.4 +++ lib_ppc/board.c 2004/08/06 10:51:41 @@ -772,11 +774,7 @@ load_sernum_ethaddr (); #endif -#if defined(CFG_GT_6426x) || defined(CONFIG_PN62) || defined(CONFIG_PPCHAMELEONEVB) || \ - defined(CONFIG_MPC8540ADS) || \ - defined(CONFIG_MPC8555CDS) || \ - defined(CONFIG_MPC8560ADS) || \ - defined(CONFIG_440_GX) +#ifdef CONFIG_ETH1ADDR /* handle the 2nd ethernet address */ s = getenv ("eth1addr"); @@ -787,11 +785,7 @@ s = (*e) ? e + 1 : e; } #endif -#if defined(CFG_GT_6426x) || \ - defined(CONFIG_MPC8540ADS) || \ - defined(CONFIG_MPC8555CDS) || \ - defined(CONFIG_MPC8560ADS) || \ - defined(CONFIG_440_GX) +#ifdef CONFIG_ETH2ADDR /* handle the 3rd ethernet address */ s = getenv ("eth2addr"); @@ -807,7 +801,7 @@ } #endif -#if defined(CONFIG_440_GX) +#ifdef CONFIG_ETH3ADDR /* handle 4th ethernet address */ s = getenv("eth3addr"); #if defined(CONFIG_XPEDITE1K)

3 5

[U-Boot-Users] [patch] trivial parameter type fix for NetSetTimeout
by Andreas Engel 09 Oct '04

09 Oct '04

Attached is a trivial patch not worth mentioning in the ChangeLog. As NetSetTimeout just stores the timeout value in an ulong variable, the value itself should be ulong too. Regards, Andreas

2 1

Re: [U-Boot-Users] Re: how to run hello_world
by Robin Getz 09 Oct '04

09 Oct '04

Wolfgang Denk wrote: >I thought the description on this page was pretty explicit... The only think I don't see (and have been looking for a standalone app that I am writing, is the difference between load address and entry address. In the hello_world.c application, it's configured to run at address 0x00040004, but the load address is 0x00040000 - why in this case is there a 4 byte difference. => tftp 40000 /tftpboot/hello_world.bin ... => go 40004 This is another test. I assume that this is a toolchain issue, and may be offtopic for this list. A slightly different issue - I know that you can load up an elf image as a standalone app as well, but I don't seem to be able to pass it any command line args. => tftp 1000000 /tftpboot/hello_world => bootelf this is another test fails, becuase U-boot trys to pass "this is another test" to bootelf, and it doesn't like it. -Robin

2 1

[U-Boot-Users] problem about pci target mode
by liuyong 09 Oct '04

09 Oct '04

my cpu is 440gx, and my board is like ocotea. the u-boot version is 1.1.1. I want to configure the board works at the target mode. I check the register sdr0_sdstp1 is 0x80010980, so i am sure that PAE and PHCE is disabled, and only PISE is enabled. But the register sdr0_xcr, sdr0_xpllc and sdr0_xplld is 0, which is initialized with sdr0_sdstp1. the host cannot recognsie the board as a PCI device. Maybe i forget to configure some registers, somebody help me. 　　　　　　　　liuyong 　　　　　　　　ly(a)ncic.ac.cn 　　　　　　　　　　2004-10-09

1 0

Re: [U-Boot-Users] RTC Question
by Robin Getz 09 Oct '04

09 Oct '04

Wolfgang Denk wrote: >How could you fix this? As you suggested - just a simple offset (exactly the same will need to go into the Linux kernel). If the overflow occurs - (if you see a date less then 18Sept1974, assume roll over has occurred, add 4 years, 9 months, and 17 days). This will set things to the same day of the week structure as the roll over date (19Sep2058 is a Thursday, and so is 19Sept1974). This also should handle the leap years calculations properly. After this it is a simple matter of just adding 84 years to the return value or display of the function. >U-Boot will probably not even be running when the rollover happens, so it >has zero chance to notice. U-boot may not have to be alive when rollover occurs to have an issue - for a contrived example that has less chance of actually happening than me willing the lotto, if you set U-Boot up to check a network connection monthly for updates, after 2058 it stops checking, because U-boot believes that Oct2058 never occurs. However, by doing the above, all than happens is delaying things until 2087, and then you run into the same problem. But since I plan on being dead by then, I am OK with that. (I'd like to be around in 50 years, but not 80). -Robin

1 0