2.6.10-rc3 for 8xx with I2C config enabled still fails ...

2.6.10-rc3 for 8xx with I2C config enabled still fails ...

[Povolotsky, Alexander]

Hi,

Even so much "touted" ;-) 2.6.10-rc3 FAILS for 8xx with I2C config enabled 
... and our custom MPC885 based board is using a single 24C02 type I2C
EEPROM, connected to the I2C bus ...

Does anyone of you has any input/experience about 2.6.10-rc3 functionality
(this all relates to our card) of:
SPI, HDLC, Entropia, Legerity, watchdog, NAND flash support,
MTD with JFFS2 filesystem support and flash compatibility ??? (Any info will
be much appreciated !)

Thanks,
Alex
****************************************************************
CONFIG_8xx=y
............
............
CONFIG_MTD=y
............
CONFIG_HDLC=y
............
CONFIG_PPP=y
............
CONFIG_I2C=y
...............
  CC      drivers/i2c/busses/i2c-rpx.o
drivers/i2c/busses/i2c-rpx.c:20:32: linux/i2c-algo-8xx.h: No such file or
directory
drivers/i2c/busses/i2c-rpx.c:26: warning: "struct i2c_algo_8xx_data"
declared inside parameter list
drivers/i2c/busses/i2c-rpx.c:26: warning: its scope is only this definition
or declaration,
which is probably not what you want
drivers/i2c/busses/i2c-rpx.c: In function `rpx_iic_init':
drivers/i2c/busses/i2c-rpx.c:34: error: dereferencing pointer to incomplete
type
drivers/i2c/busses/i2c-rpx.c:38: error: dereferencing pointer to incomplete
type
drivers/i2c/busses/i2c-rpx.c:38: error: dereferencing pointer to incomplete
type
drivers/i2c/busses/i2c-rpx.c:39: error: dereferencing pointer to incomplete
type
drivers/i2c/busses/i2c-rpx.c:39: error: dereferencing pointer to incomplete
type
drivers/i2c/busses/i2c-rpx.c:41: error: dereferencing pointer to incomplete
type
drivers/i2c/busses/i2c-rpx.c:42: error: dereferencing pointer to incomplete
type
drivers/i2c/busses/i2c-rpx.c:53: error: dereferencing pointer to incomplete
type
drivers/i2c/busses/i2c-rpx.c:56: error: dereferencing pointer to incomplete
type
drivers/i2c/busses/i2c-rpx.c: At top level:
drivers/i2c/busses/i2c-rpx.c:67: error: variable `rpx_data' has initializer
but
incomplete type
drivers/i2c/busses/i2c-rpx.c:68: error: unknown field `setisr' specified in
initializer
drivers/i2c/busses/i2c-rpx.c:69: warning: excess elements in struct
initializer
drivers/i2c/busses/i2c-rpx.c:69: warning: (near initialization for
`rpx_data')
drivers/i2c/busses/i2c-rpx.c: In function `i2c_rpx_init':
drivers/i2c/busses/i2c-rpx.c:83: warning: passing arg 1 of `rpx_iic_init'
from incompatible pointer type
drivers/i2c/busses/i2c-rpx.c:85: warning: implicit declaration of function
`i2c_8xx_add_bus'
drivers/i2c/busses/i2c-rpx.c: In function `i2c_rpx_exit':
drivers/i2c/busses/i2c-rpx.c:95: warning: implicit declaration of function
`i2c_8xx_del_bus'
drivers/i2c/busses/i2c-rpx.c: At top level:
drivers/i2c/busses/i2c-rpx.c:67: error: storage size of `rpx_data' isn't
known
make[3]: *** [drivers/i2c/busses/i2c-rpx.o] Error 1
make[2]: *** [drivers/i2c/busses] Error 2
make[1]: *** [drivers/i2c] Error 2
make: *** [drivers] Error 2
-----Original Message-----
From: Sam Song [mailto:samlinuxppc@yahoo.com.cn]
Sent: Friday, December 17, 2004 5:32 AM
To: Povolotsky, Alexander; 'linuxppc-embedded@ozlabs.org'
Subject: Re: Error cross-building Linux 2.6 for 8xx

Re: 2.6.10-rc3 for 8xx with I2C config enabled still fails ...

[Tom Rini]

On Fri, Dec 17, 2004 at 11:30:53AM -0500, Povolotsky, Alexander wrote:

> Hi,
> 
> Even so much "touted" ;-) 2.6.10-rc3 FAILS for 8xx with I2C config enabled 
> ... and our custom MPC885 based board is using a single 24C02 type I2C
> EEPROM, connected to the I2C bus ...
> 
> Does anyone of you has any input/experience about 2.6.10-rc3 functionality
> (this all relates to our card) of:
> SPI, HDLC, Entropia, Legerity, watchdog, NAND flash support,
> MTD with JFFS2 filesystem support and flash compatibility ??? (Any info will
> be much appreciated !)

So, your best bet to get 8xx I2C working is to grab the 'latest' from a
2.4 tree that has it working, and move it up.  In doing so, you may want
to kill 'i2c-rpx' and merge it all into the i2c-algo-8xx file.

[snip]
> CONFIG_8xx=y
CONFIG_BROKEN=y
as well.  Not that it's directly relevant (the 8xx breakage is in
something else), but..

-- 
Tom Rini
http://gate.crashing.org/~trini/