All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Povolotsky, Alexander" <Alexander.Povolotsky@marconi.com>
To: "'Sam Song'" <samlinuxppc@yahoo.com.cn>
Cc: "'Demke, Torsten'" <Torsten.Demke@fci.com>,
	"'linuxppc-embedded@ozlabs.org'" <linuxppc-embedded@ozlabs.org>,
	'Steven Blakeslee' <BlakesleeS@embeddedplanet.com>
Subject: 2.6.10-rc3 for 8xx with I2C config enabled  still fails ...
Date: Fri, 17 Dec 2004 11:30:53 -0500	[thread overview]
Message-ID: <313680C9A886D511A06000204840E1CF0A6473AF@whq-msgusr-02.pit.comms.marconi.com> (raw)

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

             reply	other threads:[~2004-12-17 16:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-17 16:30 Povolotsky, Alexander [this message]
2004-12-17 16:38 ` 2.6.10-rc3 for 8xx with I2C config enabled still fails Tom Rini

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=313680C9A886D511A06000204840E1CF0A6473AF@whq-msgusr-02.pit.comms.marconi.com \
    --to=alexander.povolotsky@marconi.com \
    --cc=BlakesleeS@embeddedplanet.com \
    --cc=Torsten.Demke@fci.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=samlinuxppc@yahoo.com.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.