October 2004 - U-Boot

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

09 Oct '04

All: General question, in the specific processor (Blackfin BF533) that I am using, the on-board RTC can have a 32768 days, and defaults to starting at 01Jan1970. This means that RTC rollover will occur around Fri, 19-Sep-2059 11:59pm. On Sat 20-Sep-2059, the date will be displayed as Thur 01-Jan-1970. Should I add extra complexity, to extend things past this? I see issues in other code that will roll over around 19Jan2038, so I would expect that others are not concerned about it? -Robin

4 4

[U-Boot-Users] ATA driver in U-Boot
by Victor Wren 08 Oct '04

08 Oct '04

I am not sure if this is off-topic, because I'm unsure of the division of labor. Is there any reason that U-Boot needs ATA support compiled in? I ask because I'm trying to speed up booting on a small system with a hard drive. U-Boot waits for the devices to become available, scanning the ATA bus, before proceeding to load the Linux kernel. It appears to me that the kernel then does the same thing again, whereas if it went ahead and went straight to loading the kernel, it would give the drive another second or two to spin up and be ready for a bus scan. Given that the kernel is being loaded out of flash (with all drivers compiled in), and that the only reference to the IDE drive that U-Boot really knows about is a commandline parameter passed to the kernel, would it cause any conspicuous problems to remove ATA support from U-Boot, or does the kernel depend on hardware information that U-Boot is providing (I notice there's a "U-Boot" section in the kernel config)? Thanks, Victor Wren

3 2

RE: [U-Boot-Users] Unable to run hello_world
by Smith, Craig 08 Oct '04

08 Oct '04

>>## Ready for binary (kermit) download to 0x00040000 at 19200 bps... >>## Total Size = 0x000022b0 = 8880 Bytes My hello_world.bin (for ppc) is 66280 bytes. Have you tried the s-record format? What terminal program are you using? minicom won't work...at least I can't get it to. Regards, -Craig

2 1

[U-Boot-Users] U-Boot for IXP425 Little-endian
by Herb Radford 08 Oct '04

08 Oct '04

I'm going to be using an IXP425 for u-boot and a kernel but in order to re-use existing software I want to use BOTH u-boot and the kernel in little-endian. Is there someone who has done this for this target or is working on it? I'll do it myself, but I thought I'd ask first. Regards, Herb --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.769 / Virus Database: 516 - Release Date: 9/24/2004

3 2

[U-Boot-Users] Re: how to run hello_world
by Farrukh Masood 08 Oct '04

08 Oct '04

Hi! Please tell me where can i find hello_world.bin file and where should it be put on the host system to be accessible from u-boot based target system with tftpboot command. It will be quite helpful for me if you can stepwise describe the procedure as I am unable to understand it from the denx tutorial. thanks alot Regards Chishti Wolfgang Denk <wd(a)denx.de> wrote: In message <20041007160300.20228.qmail(a)web25404.mail.ukl.yahoo.com> you wrote: > > As described in u-boot readme file, to run hello_world example we have to write "loads", but this command doesnt seem to work with me and give the following msg > > Unknown command 'loads' - try 'help' Then it seems this command was not enabled in your board configuration. But you can load the file using TFTP as well. > and when i give the command go 40004 Hello World! This is a test. > > following error msg appears Ummm.. did you really expect that some magic code would spring into life and do something reasonable when you jump to this address after --------------------------------- Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish.

3 2

RE: [U-Boot-Users] Re: how to run hello_world
by Smith, Craig 08 Oct '04

08 Oct '04

>>Please tell me where can i find hello_world.bin file In the "examples" directory. >>and where should it be put on >>the host system to be accessible from u-boot based target system with tftpboot command. That depends on how your tftp server was set up. See http://www.denx.de/twiki/bin/view/DULG/SystemSetup#Section_4.6. >>It will be quite helpful for me if you can stepwise describe the procedure as I >>am unable to understand it from the denx tutorial. The procedure is already described "stepwise". See http://www.denx.de/twiki/bin/view/DULG/UBootStandalone#Section_5.12.1. Now, everyone, all together..."Please don't post HTML", that's a good way to get your message ignored. Regards, -Craig

1 0

[U-Boot-Users] u-boot on floppy from x86
by Shakthi Kannan 08 Oct '04

08 Oct '04

Greetings! I read that u-boot can be installed on a floppy and can be booted from the floppy. Is it possible on an x86 (Intel PII) system? I downloaded u-boot-1.1.1. The README says that u-boot can be used for i386 CPUs and architecture. But, the Makefile has only one entry for i386 for AMD SC520 CDP. I need to do "make <arch>_config" first and not sure which one I should do for an x86 target system. My main objective is to write my own commands in the u-boot monitor source program, and test it when u-boot boots the system. Any suggestions? Thanks, Shaks _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com

2 2

[U-Boot-Users] compiling error
by Alessio Raccis 08 Oct '04

08 Oct '04

Hi all, I'm a newbie in u-boot, then sorry for all my fool questions. I'm trying to compile u-boot for smdk2410, but I have an error. This is what I have: .............. make[1]: Leaving directory `/root/u-boot-0.4.8_new/drivers' make[1]: Entering directory `/root/u-boot-0.4.8_new/drivers/sk98lin' arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -Wall -Wstrict-prototypes -I. -DSK_USE_CSUM -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -c -o skge.o skge.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -Wall -Wstrict-prototypes -I. -DSK_USE_CSUM -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -c -o skaddr.o skaddr.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -Wall -Wstrict-prototypes -I. -DSK_USE_CSUM -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -c -o skgehwt.o skgehwt.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -Wall -Wstrict-prototypes -I. -DSK_USE_CSUM -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -c -o skgeinit.o skgeinit.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -Wall -Wstrict-prototypes -I. -DSK_USE_CSUM -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -c -o skgepnmi.o skgepnmi.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -Wall -Wstrict-prototypes -I. -DSK_USE_CSUM -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -c -o skgesirq.o skgesirq.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -Wall -Wstrict-prototypes -I. -DSK_USE_CSUM -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -c -o ski2c.o ski2c.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -Wall -Wstrict-prototypes -I. -DSK_USE_CSUM -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -c -o sklm80.o sklm80.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -Wall -Wstrict-prototypes -I. -DSK_USE_CSUM -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -c -o skqueue.o skqueue.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -Wall -Wstrict-prototypes -I. -DSK_USE_CSUM -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -c -o skrlmt.o skrlmt.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -Wall -Wstrict-prototypes -I. -DSK_USE_CSUM -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -c -o sktimer.o sktimer.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -Wall -Wstrict-prototypes -I. -DSK_USE_CSUM -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -c -o skvpd.o skvpd.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -Wall -Wstrict-prototypes -I. -DSK_USE_CSUM -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -c -o skxmac2.o skxmac2.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -Wall -Wstrict-prototypes -I. -DSK_USE_CSUM -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -c -o skcsum.o skcsum.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -Wall -Wstrict-prototypes -I. -DSK_USE_CSUM -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -c -o uboot_skb.o uboot_skb.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -Wall -Wstrict-prototypes -I. -DSK_USE_CSUM -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0x33F80000 -I/root/u-boot-0.4.8_new/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -c -o uboot_drv.o uboot_drv.c In file included from /root/u-boot-0.4.8_new/include/common.h:40, from uboot_drv.c:26: /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include/stdarg.h:43: parse error before `__gnuc_va_list' /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include/stdarg.h:43: warning: data definition has no type or storage class /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include/stdarg.h:110: parse error before `va_list' /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include/stdarg.h:110: warning: data definition has no type or storage class In file included from uboot_drv.c:26: /root/u-boot-0.4.8_new/include/common.h:438: parse error before `va_list' /root/u-boot-0.4.8_new/include/common.h:438: warning: function declaration isn't a prototype /root/u-boot-0.4.8_new/include/common.h:468: parse error before `va_list' /root/u-boot-0.4.8_new/include/common.h:468: warning: function declaration isn't a prototype make[1]: *** [uboot_drv.o] Error 1 make[1]: Leaving directory `/root/u-boot-0.4.8_new/drivers/sk98lin' make: *** [subdirs] Error 1 these are my compilers: gcc-3.2.2-5 gcc-c++-3.2.2-5 libgcc-3.2.2-5 gcc-g77-3.2.2-5 gcc-java-3.2.2-5 gcc-objc-3.2.2-5 and these are my glibc glibc-common-2.3.2-5 glibc-2.3.2-5 glibc-devel-2.3.2-5 glibc-kernheaders-2.4-8.10 thanks in advance for the help !! best regards @le

4 5

RE: [U-Boot-Users] compile
by Friedrich, Lars 08 Oct '04

08 Oct '04

> can metrowerks's codewarrior complile the u-boot? > i want to port the u-boot to my arm lpc2210 in linux , but > the board don't give the jtag driver that can write/read > flash in linux ,so i want to complile the u-boot in > codewarrior and write into flash by jtag in windows a) The AXD Debugger is able to load the compiled u-boot loader even if it was not compiled with Metrowerks Codewarrior. Of course, you have to select to load *.* and not *.axf files. So there is no need to compile it under Metrowerks. b) I'm quite sure that gdb can communicate with your JTAG interface, if the AXD debugger can do so. The AXD Debugger uses the Arm/Angel protocol and the gdb can do so, too. If the gdb has ARM support compiled in, it automatically adds the necessary RDI entries for Arm/Angel support via ethernet and serial interface. Therefore you can load u-boot into memory via JTAG, execute it and use u-boot to write to flash. Best regards, Lars Friedrich

1 0

RE: [U-Boot-Users] RTL8139 compilation error
by Santoso, Yusdi 08 Oct '04

08 Oct '04

What value should I put in then? Is this the PCI_IO_BASE? Or 0x0000 ? Hm...I'm not so familiar with PPC, does it have separate IO and Mem instruction like in x86 or the same address as in MC68000? Thanks, Yusdi -----Original Message----- From: wd(a)denx.de [mailto:wd@denx.de] Sent: Friday, October 08, 2004 2:20 AM To: Santoso, Yusdi Cc: u-boot-users(a)lists.sourceforge.net Subject: Re: [U-Boot-Users] RTL8139 compilation error In message <16808BEAD68708489AE865F48D8793890301D4(a)AMSE2K02.adaptec.com> you wrote: > > So how do you get this _IO_BASE? Should I define it in the > "include/config/<board>.h" ? Yes. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd(a)denx.de One of the advantages of being a captain is being able to ask for ad- vice without necessarily having to take it. -- Kirk, "Dagger of the Mind", stardate 2715.2

2 1