January 2005 - U-Boot

FW: Re: [U-Boot-Users] ARM VersatilePB - Fixed flash support
by Peter Pearse 11 Jan '05

11 Jan '05

Peter Pearse wrote: > Shawn > Just to re-assure you - I am testing your patches at present. > > The VersatilePB flash support should be submitted later this week. > > Your other patches for ARM IntegratorCP, ARM926EJS, and ARM946ES next > week. > > Peter > > ------------------------------------------------------------------------- > Peter Pearse ARM > Ltd > Software Engineer 110 Fulbourn > Road > Embedded Software Division > Cambridge > Direct line: +44 (0)1223 400812 > CB19NJ > Fax: +44 (0)1223 400410 United > Kingdom > > ------------------------ Peter.Pearse(a)arm.com > ------------------------- > This e-mail message is intended for the addressee(s) only and may > contain information that is the property of, and/or subject to a > confidentiality agreement between the intended recipient(s), their > organisation and/or the ARM Group of Companies. If you are not an > intended recipient of this e-mail message, you should not read, copy, > forward or otherwise distribute or further disclose the information > in it; misuse of the contents of this e-mail message may violate > various laws in your state, country or jurisdiction. If you have > received this e-mail message in error, please contact the originator > of this e-mail message via e-mail and delete all copies of this > message from your computer or network, thank you.

1 0

RE: [U-Boot-Users] MPC8272ADS PCI limitation in u-boot
by Milligan, Keath 11 Jan '05

11 Jan '05

This seems to be the case. Basically, the issue I am having is that when I attempt to boot Linux, my PCI devices aren't getting mapped properly. Linux attempts to map some, but gives up saying it can not allocate the regions. This would seem to suggest that the firmware/boot-loader needs to deal with it. The same hardware, when connected to a PC, gets mapped and works correctly under x86 Linux. -----Original Message----- From: Rune Torgersen [mailto:runet@innovsys.com] Sent: Monday, January 10, 2005 8:36 AM To: Yuli Barcohen; Milligan, Keath Cc: U-Boot Subject: RE: [U-Boot-Users] MPC8272ADS PCI limitation in u-boot Actually the MPC8266ADS port (MPC8266ADS_config, separate from the rest of the PQII boards) does do PCI initializatiopn (at least a very crude one) It only allocates non-prefetchable memory (even for placess where prefetchable should be used). > -----Original Message----- > From: u-boot-users-admin(a)lists.sourceforge.net > [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf > Of Yuli Barcohen > Sent: Friday, January 07, 2005 17:47 > To: Milligan, Keath > Cc: U-Boot > Subject: Re: [U-Boot-Users] MPC8272ADS PCI limitation in u-boot > > U-Boot port for MPC82xxADS family does not initialise PCI > bridge at all > because it's not necessary for booting the board. Where did > you find PCI > windows initialisations? Regarding the bridge limitations, > AFAIK you can > do what you want but please consult MPC8272 user's guide. > > -- > ============================================================== > ========== > Yuli Barcohen | Phone +972-9-765-1788 | Software > Project Leader > yuli(a)arabellasw.com | Fax +972-9-765-7494 | Arabella > Software, Israel > ============================================================== > ========== > > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > U-Boot-Users mailing list > U-Boot-Users(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/u-boot-users > >

2 1

[U-Boot-Users] Query regarding PCI interrupt controller
by Prathima_Kolar 11 Jan '05

11 Jan '05

Hello all, I am working on a Motorola Power QuiccII 8266 based PCI Mezzanine card. In he file include/configs.MPC8266ADS.h there is a code snippet "#define CFG_PCI_INT 0xF8200000" . We know that CFG_PCI_INT is for the interrupt controller but not able to make out what address to assign it. Can anyone please let me know why the value 0xF8200000 has been given? Thanks & Regards, Prathima Kolar. ************************************************************************** This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated. **************************************************************************

1 0

[U-Boot-Users] [patch] Updating for RPXlite_DW
by Sam Song 11 Jan '05

11 Jan '05

Hi list, I got the nudge from some folkes chatting with Wolfgang about RESET/AUTOBOOT and did this patch. All for updating RPXlite_DW board. I tried to remove board/RPXlite_dw/README to doc/ but failed. CHANGELOG: * Patch by Sam Song, 11 October 2004: - Add RESET/PREBOOT/AUTOBOOT support for RPXlite_DW board - Adjust CPU:BUS frequency rato 1:1 when core frequency less than 50MHz ===== Best regards, Sam _________________________________________________________ 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_… ? RPXlite_DW_update.patch Index: board/RPXlite_dw/README =================================================================== RCS file: /cvsroot/u-boot/u-boot/board/RPXlite_dw/README,v retrieving revision 1.1 diff -p -u -r1.1 README --- board/RPXlite_dw/README 9 Jun 2004 21:04:49 -0000 1.1 +++ board/RPXlite_dw/README 11 Oct 2004 04:34:07 -0000 @@ -2,11 +2,11 @@ After following the step of Yoo. Jonghoon and Wolfgang Denk, I ported u-boot on RPXlite DW version board: RPXlite_DW or LITE_DW. -There are three differences between the Yoo-ported RPXlite and the RPXlite_DW. +There are at least three differences between the Yoo-ported RPXlite and the RPXlite_DW. -Board(in U-BOOT) version(in EmbeddedPlanet) CPU SDRAM FLASH +Board(in U-Boot) version(in EmbeddedPlanet) CPU SDRAM FLASH RPXlite RPXlite CW 850 16MB 4MB -RPXlite_DW RPXlite DW 823e 64MB 16MB +RPXlite_DW RPXlite DW(EP 823 H1 DW) 823e 64MB 16MB This fireware is specially coded for EmbeddedPlanet Co. Software Development Platform(RPXlite DW),which has a NEC NL6448BC20-08 LCD panel. @@ -17,6 +17,7 @@ It has the following three features: The default setting is 48MHz.To get a 64MHz u-boot,just add '64' in make command,like +make distclean make RPXlite_DW_64_config make all @@ -28,19 +29,21 @@ didn't use EEPROM for ENV is that Planet home.Because of the possibility of using two firewares on this board,I didn't 'disturb' EEPROM.To get NVRAM support,you may use the following build command: +make distclean make RPXlite_DW_NVRAM_config make all 3. LCD panel support -To support the Platform better,I added LCD panel(NL6448BC20-08) function.But bewear of -the fact that once you build this support and program it to FLASH,you should make sure -you put workable kernel and ramdisk at the right place in FLASH or through NFS. -Otherwise, you must erase this fireware manually via BDI2000 or ICE tools.So this -function is used for deployment and demo only.Pls look before you leap. +To support the Platform better,I added LCD panel(NL6448BC20-08) function. +For the convenience of debug, CONFIG_PERBOOT was supported. So you just +perss ENTER if you want to get a serial console in boot downcounting. +Then you can switch to LCD and serial console freely just typing +'run lcd' or 'run ser'. They are only vaild when CONFIG_LCD was enabled. To get a LCD support u-boot,you can do the following: +make distclean make RPXlite_DW_LCD_config make all @@ -68,7 +71,7 @@ make RPXlite_DW_64_LCD_config The boot process by "make RPXlite_DW_config" could be: -U-Boot 1.1.1 (Jun 8 2004 - 11:16:30) +U-Boot 1.1.2 (Aug 29 2004 - 15:11:27) CPU: PPC823EZTnnB2 at 48 MHz: 16 kB I-Cache 8 kB D-Cache Board: RPXlite_DW @@ -84,6 +87,68 @@ u-boot> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +A word on the U-Boot enviroment variable setting and usage : + +In the beginning, you could just need very simple defult environment variable setting, +like[include/configs/RPXlite.h] : + +#define CONFIG_BOOTCOMMAND \ + "bootp; " \ + "setenv bootargs root=/dev/nfs rw nfsroot=$(serverip):$(rootpath) " \ + "ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname)::off; " \ + "bootm" + +This is enough for kernel NFS test. But as debug process goes on, you would expect +to save some time on environment variable setting and u-boot/kernel updating. +So the default environment variable setting would become more complicated. Just like +the one I did in include/configs/RPXlite_DW.h. + +Two u-boot commands, ku and uu, should be careful to use. They were designed to update +kernel and u-boot image file respectively. You must tftp your image to default address +'100000' and then use them correctly. Yeah, you can create your own command to do this +job. :-) The example u-boot image updating process could be : + +u-boot>t 100000 RPXlite_DW_LCD.bin +Using SCC ETHERNET device +TFTP from server 172.16.115.6; our IP address is 172.16.115.7 +Filename 'RPXlite_DW_LCD.bin'. +Load address: 0x100000 +Loading: ############################# +done +Bytes transferred = 144700 (2353c hex) +u-boot>run uu +Un-Protect Flash Sectors 0-4 in Bank # 1 +Erase Flash Sectors 0-4 in Bank # 1 +.... done +Copy to Flash... done +ff000000: 27051956 552d426f 6f742031 2e312e32 '..VU-Boot 1.1.2 +ff000010: 20284175 67203239 20323030 34202d20 (Aug 29 2004 - +ff000020: 31353a32 303a3238 29000000 00000000 15:20:28)....... +ff000030: 00000000 00000000 00000000 00000000 ................ +ff000040: 00000000 00000000 00000000 00000000 ................ +ff000050: 00000000 00000000 00000000 00000000 ................ +ff000060: 00000000 00000000 00000000 00000000 ................ +ff000070: 00000000 00000000 00000000 00000000 ................ +ff000080: 00000000 00000000 00000000 00000000 ................ +ff000090: 00000000 00000000 00000000 00000000 ................ +ff0000a0: 00000000 00000000 00000000 00000000 ................ +ff0000b0: 00000000 00000000 00000000 00000000 ................ +ff0000c0: 00000000 00000000 00000000 00000000 ................ +ff0000d0: 00000000 00000000 00000000 00000000 ................ +ff0000e0: 00000000 00000000 00000000 00000000 ................ +ff0000f0: 00000000 00000000 00000000 00000000 ................ +u-boot updating finished +u-boot> + +Also for environment updating, 'run eu' could let you erase OLD default environment variable +and then use the working u-boot environment setting. + +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Finally, if you want to keep the serial port to possible debug on spot for deployment, you +just need to enable 'DEPLOYMENT' in RPXlite_DW.h as 'DEBUG' does. Only the special string +defined by CONFIG_AUTOBOOT_STOP_STR like 'st' can stop the autoboot. + I'd like to extend my heartfelt gratitute to kind people for helping me work it out. I would particually thank Wolfgang Denk for his nice help. @@ -93,4 +158,4 @@ Sam Song, samsongshu(a)yahoo.com.cn Institute of Electrical Machinery and Controls Shanghai University -June 8,2004 +Oct. 11, 2004 Index: include/configs/RPXlite_DW.h =================================================================== RCS file: /cvsroot/u-boot/u-boot/include/configs/RPXlite_DW.h,v retrieving revision 1.3 diff -p -u -r1.3 RPXlite_DW.h --- include/configs/RPXlite_DW.h 9 Oct 2004 22:45:00 -0000 1.3 +++ include/configs/RPXlite_DW.h 11 Oct 2004 04:34:18 -0000 @@ -45,6 +45,7 @@ */ /* #define DEBUG 1 */ +/* #ifdef DEPLOYMENT 1 */ #undef CONFIG_MPC860 #define CONFIG_MPC823 1 /* This is a MPC823e CPU. */ @@ -59,19 +60,31 @@ #undef CONFIG_8xx_CONS_NONE #define CONFIG_BAUDRATE 9600 /* console default baudrate = 9600bps */ -#ifdef CONFIG_LCD -#define CONFIG_BOOTDELAY 12 /* autoboot after 12 seconds */ +#ifdef DEBUG +#define CONFIG_BOOTDELAY -1 /* autoboot disabled */ #else -#define CONFIG_BOOTDELAY -1 /* autoboot disabled */ +#define CONFIG_BOOTDELAY 6 /* autoboot after 6 seconds */ + +#ifdef DEPLOYMENT +#define CONFIG_BOOT_RETRY_TIME -1 +#define CONFIG_AUTOBOOT_KEYED +#define CONFIG_AUTOBOOT_PROMPT "autoboot in %d seconds (stop with 'st')...\n" +#define CONFIG_AUTOBOOT_STOP_STR "st" +#define CONFIG_ZERO_BOOTDELAY_CHECK +#define CONFIG_RESET_TO_RETRY 1 +#define CONFIG_BOOT_RETRY_MIN 1 +#endif #endif +/* pre-boot commands */ +#define CONFIG_PREBOOT "setenv stdout serial;setenv stdin serial" + #undef CONFIG_BOOTARGS #define CONFIG_EXTRA_ENV_SETTINGS \ "netdev=eth0\0" \ - "nfsargs=setenv bootargs console=ttyS0,9600 root=/dev/nfs rw " \ - "nfsroot=$(serverip):$(rootpath)\0" \ - "ramargs=setenv bootargs console=tty0 console=ttyS0,9600 " \ - "root=/dev/ram rw\0" \ + "nfsargs=setenv bootargs console=tty0 console=ttyS0,9600 " \ + "root=/dev/nfs rw nfsroot=$(serverip):$(rootpath)\0" \ + "ramargs=setenv bootargs console=tty0 root=/dev/ram rw\0" \ "addip=setenv bootargs $(bootargs) " \ "ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask)" \ ":$(hostname):$(netdev):off panic=1\0" \ @@ -82,9 +95,25 @@ "net_nfs=tftp 200000 $(bootfile);run nfsargs addip;bootm\0" \ "gatewayip=172.16.115.254\0" \ "netmask=255.255.255.0\0" \ +<<<<<<< RPXlite_DW.h + "kernel_addr=ff040000\0" \ + "ramdisk_addr=ff200000\0" \ + "ku=era $(kernel_addr) ff1fffff;cp.b 100000 $(kernel_addr) " \ + "$(filesize);md $(kernel_addr);" \ + "echo kernel updating finished\0" \ + "uu=protect off 1:0-4;era 1:0-4;cp.b 100000 ff000000 " \ + "$(filesize);md ff000000;" \ + "echo u-boot updating finished\0" \ + "eu=protect off 1:6;era 1:6;reset\0" \ + "lcd=setenv stdout lcd;setenv stdin lcd\0" \ + "ser=setenv stdout serial;setenv stdin serial\0" \ + "verify=no" + +======= "kernel_addr=ff080000\0" \ "ramdisk_addr=ff200000\0" \ "" +>>>>>>> 1.3 #define CONFIG_BOOTCOMMAND "run flash_self" #define CONFIG_LOADS_ECHO 1 /* echo on for serial download */ @@ -178,8 +207,13 @@ #define CFG_ENV_SIZE 0x8000 /* Total Size of Environment Sector */ #endif +<<<<<<< RPXlite_DW.h +#define CFG_RESET_ADDRESS ((ulong)((((immap_t *)CFG_IMMR)->im_clkrst.res))) + +======= #define CFG_RESET_ADDRESS ((ulong)((((immap_t *)CFG_IMMR)->im_clkrst.res))) +>>>>>>> 1.3 /*----------------------------------------------------------------------- * Cache Configuration */ @@ -254,10 +288,16 @@ /* Up to 48MHz system clock, we use 1:1 SYSTEM/BUS ratio */ #if defined(RPXlite_64MHz) #define CFG_SCCR ( SCCR_TBS | SCCR_EBDF01 ) /* %%%SCCR:0x02020000 */ +<<<<<<< RPXlite_DW.h +#else +#define CFG_SCCR ( SCCR_TBS | SCCR_EBDF00 ) /* %%%SCCR:0x02000000 */ +#endif +======= #else #define CFG_SCCR ( SCCR_TBS | SCCR_EBDF00 ) /* %%%SCCR:0x02000000 */ #endif +>>>>>>> 1.3 /*----------------------------------------------------------------------- * PCMCIA stuff *-----------------------------------------------------------------------

2 2

[U-Boot-Users] MII Ethernet Support
by Rodel Miguel 11 Jan '05

11 Jan '05

Hi Group, I am having trouble on how to configure my network interface which support MII. I am using ARM920T-based board. My ethernet controller is based on DEC 21143 but only supports MII media attachment. I wonder why the dc21143 was not generalized to support MII attachments too? Can someone please tell me how they have developed their driver for the said chip with MII interface only? Thank you very much for your time. Best Regards, Rodel

1 0

[U-Boot-Users] dataflash
by C. Michael Sundius 11 Jan '05

11 Jan '05

I noticed that there is some support for the amtel's dataflash (serial flash) in u-boot but it doesn't seem as though it can stand alone without the normal parallel flash.. I see that the Amtel board that is supported by u-boot seems to have both parallel flash and serial flash... am I understanding this right or no... anyone have any experience in supporting a board with only serial flash? btw the board that I'm using has hardware in it to copy a simple primary bootloader into sram at reset and then starts executing from there... anyway I was hoping I could just write a lower level driver for my particular serial flash / spi bus and use existing higher level support for the dataflash, but it doesn't seem to work quite well without the parallel flash (flinfo_t) support.. if anyone has any ideas, I'd sure appreciate it... thanks C Michael Sundius Solico Group LLC 232 Nevada St San Francisco, CA 94110 msundius(a)sundius.com (415)608-0121

1 0

RE: [U-Boot-Users] MPC8272ADS PCI limitation in u-boot
by Rune Torgersen 10 Jan '05

10 Jan '05

I have seen that exact problem multiple times. I found one good way to get that fixed on out internal 8265 port to a custom board. I found that on our 8265 board, all IO resources have the lowest bit set. Changing m8260_find_bridges (in 2.6.9) to (arch/ppc/syslib/m8260_pci.c (psuedo patch) pci_init_resource(&hose->io_resource, MPC826x_PCI_LOWER_IO, MPC826x_PCI_UPPER_IO, - IORESOURCE_IO, "PCI I/O"); + IORESOURCE_IO | 1, "PCI I/O"); // the 1 added so IO areas work. Helped for me. Now it newer compalins about resources. Also had to make sure that memory map for PCI matched between u-boot and linux. Still havent gotten around to fix the allocation under u-boot (or linux) to allocate prefetchable memory where needed. > -----Original Message----- > From: Milligan, Keath [mailto:kmilligan@austin.polycom.com] > Sent: Monday, January 10, 2005 13:19 > To: Rune Torgersen; Yuli Barcohen; Milligan, Keath > Cc: U-Boot > Subject: RE: [U-Boot-Users] MPC8272ADS PCI limitation in u-boot > > This seems to be the case. Basically, the issue I am having > is that when I > attempt to boot Linux, my PCI devices aren't getting mapped > properly. Linux > attempts to map some, but gives up saying it can not allocate > the regions. > This would seem to suggest that the firmware/boot-loader > needs to deal with > it. > > The same hardware, when connected to a PC, gets mapped and > works correctly > under x86 Linux. > > -----Original Message----- > From: Rune Torgersen [mailto:runet@innovsys.com] > Sent: Monday, January 10, 2005 8:36 AM > To: Yuli Barcohen; Milligan, Keath > Cc: U-Boot > Subject: RE: [U-Boot-Users] MPC8272ADS PCI limitation in u-boot > > Actually the MPC8266ADS port (MPC8266ADS_config, separate > from the rest > of the PQII boards) does do PCI initializatiopn (at least a very crude > one) It only allocates non-prefetchable memory (even for placess where > prefetchable should be used). > > > -----Original Message----- > > From: u-boot-users-admin(a)lists.sourceforge.net > > [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf > > Of Yuli Barcohen > > Sent: Friday, January 07, 2005 17:47 > > To: Milligan, Keath > > Cc: U-Boot > > Subject: Re: [U-Boot-Users] MPC8272ADS PCI limitation in u-boot > > > > U-Boot port for MPC82xxADS family does not initialise PCI > > bridge at all > > because it's not necessary for booting the board. Where did > > you find PCI > > windows initialisations? Regarding the bridge limitations, > > AFAIK you can > > do what you want but please consult MPC8272 user's guide. > > > > -- > > ============================================================== > > ========== > > Yuli Barcohen | Phone +972-9-765-1788 | Software > > Project Leader > > yuli(a)arabellasw.com | Fax +972-9-765-7494 | Arabella > > Software, Israel > > ============================================================== > > ========== > > > > > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by: Beat the post-holiday blues > > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > > It's fun and FREE -- well, > almost....http://www.thinkgeek.com/sfshirt > > _______________________________________________ > > U-Boot-Users mailing list > > U-Boot-Users(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/u-boot-users > > > > > >

1 0

[U-Boot-Users] ARM VersatilePB - Fixed flash support
by Philippe Robin 10 Jan '05

10 Jan '05

Greetings, I have attached a patch fixing flash support with Versatile Boards: CHANGELOG Entry: * Patch by Philippe Robin, 28 Sept 2004: - Fix Flash support for Versatile. Regards, Philippe

4 5

[U-Boot-Users] [Patch] Support for AMD db1550 board
by Leif Lindholm 10 Jan '05

10 Jan '05

Hi This patch adds support for the AMD db1550 board to u-boot. It is implemented as a flavor of the au1x00 family. Since I have not tested the pcmcia/ide stuff, this board has CONFIG_BOOTCOMMAND and CONFIG_COMMANDS ifdef:d to different values than the rest of the boards in the family. Also, the memory setup differs a bit from earlier boards, due to this board being equipped with DDR SDRAM. This has lead to quite a large memsetup.S (heavily ifdef:d). It also includes some code taken from AMD:s version of YAMON for this board (with their permission), for enabling cache and doing some preloads before reconfiguring the flash controller to correct values. This precaution may be a good idea on the other boards as well, but since I have not tested it on them, this part is ifdef:d CONFIG_DBAU1550. I have included the "new" version of mkconfig, which now accepts a "$6" specifying endianess. This software is only tested in little endian mode. This patch also contains some minor changes allowing for setting CPU clock frequency in only one place (instead of three) and calculating the correct divisor for the uart based on this. regards / Leif

3 2

[U-Boot-Users] RE: [U-Boot-CVS] u-boot/drivers omap24xx_i2c.c,NONE,1.1 Makefile,1.29,1.30 ns16550.c,1.6,1.7 serial.c,1.5,1.6
by Woodruff, Richard 10 Jan '05

10 Jan '05

Sorry, I ran into the build problem long ago and fixed it locally. I was preparing to resubmit a patch with a lot of additions and this one fix....as I was thinking Wolfgang had bypassed it. I believe the real fix I used was in the driver itself not above. Its much simpler and I think the correct one. Regards, Richard W. The File drivers/omap2420_i2c.c needs to look like this: ----------------------------------------------------------- #include <common.h> #ifdef CONFIG_DRIVER_OMAP24XX_I2C #include <asm/arch/i2c.h> #include <asm/io.h> #define inw(a) __raw_readw(a) #define outw(a,v) __raw_writew(a,v) ----------------------------------------------------------- previously it WRONGLY looked like: #include <common.h> #include <asm/arch/i2c.h> #include <asm/io.h> #define inw(a) __raw_readw(a) #define outw(a,v) __raw_writew(a,v) #ifdef CONFIG_DRIVER_OMAP24XX_I2C > -----Original Message----- > From: Cory Tusar [mailto:ctusar@videon-central.com] > Sent: Monday, January 10, 2005 9:27 AM > To: [u-boot] U-Boot users list > Cc: Woodruff, Richard > Subject: Re: [U-Boot-CVS] u-boot/drivers omap24xx_i2c.c,NONE,1.1 > Makefile,1.29,1.30 ns16550.c,1.6,1.7 serial.c,1.5,1.6 > > Wolfgang Denk wrote: > > Update of /cvsroot/u-boot/u-boot/drivers > > In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv8979/drivers > > > > Modified Files: > > Makefile ns16550.c serial.c > > Added Files: > > omap24xx_i2c.c > > Log Message: > > * Patches by Richard Woodruff, 01 Oct 2004: > > add support for the TI OMAP2420 processor and its H4 reference > > board > > > > * Patch by Christian Pellegrin, 24 Sep 2004: > > Added support for NE2000 compatible (DP8390, DP83902) NICs. > > This changeset, notably omap24xx_i2c.c, breaks (ARM-only?) non-omap24xx > builds. The attached patch relocates the omap24xx-specific i2c header > information from asm-arm/arch-arm1136/i2c.h to include/omap24xx_i2c.h. > > Patch was generated against current CVS sources. > > -Cory > > > -- > Cory T. Tusar > Embedded Systems Engineer > Videon Central, Inc. > 2171 Sandy Drive > State College, PA 16801 > (814) 235-1111 x316 > (814) 235-1118 fax > > "Debugging is twice as hard as writing the code in the first place. > Therefore, if you write the code as cleverly as possible, you are, > by definition, not smart enough to debug it." --Brian W. Kernighan

2 2