public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Cory Tusar <ctusar@videon-central.com>
To: u-boot@lists.denx.de
Subject: [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
Date: Mon, 10 Jan 2005 11:44:13 -0500	[thread overview]
Message-ID: <41E2B0DD.7050306@videon-central.com> (raw)
In-Reply-To: <71555548814716479478431542AA5F8A01B1B517@dlee2k04.ent.ti.com>

Woodruff, Richard wrote:

> 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

Agreed.  After a bit more testing, I found that there were preprocessor 
warnings generated due to symbols being defined multiple times between 
your i2c.h and the omap1510.h (notably inb(), outb() and the like).  I 
came up with pretty much the same solution as you, and am running a 
MAKEALL test now just to be sure there are no issues this time. 
Assuming not, I'll re-send just the above changes as a patch to resolve 
this.

Thanks.

-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

  reply	other threads:[~2005-01-10 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10 16:14 [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 Woodruff, Richard
2005-01-10 16:44 ` Cory Tusar [this message]
2005-01-10 17:24 ` [U-Boot-Users] " Cory Tusar
     [not found] <E1CnmIi-0002Mc-2E@sc8-pr-cvs1.sourceforge.net>
2005-01-10 15:26 ` Cory Tusar
2005-01-10 15:36   ` Jerry Van Baren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41E2B0DD.7050306@videon-central.com \
    --to=ctusar@videon-central.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox