From: jimmy liu <jimmyzhmliu@yahoo•com>
To: Li Yang-r58472 <LeoLi@freescale•com>,
embedded linuxppc <linuxppc-embedded@ozlabs•org>
Subject: RE: MPC8260 I2C Problem
Date: Fri, 26 Jan 2007 20:31:02 -0800 (PST) [thread overview]
Message-ID: <453204.70143.qm@web53111.mail.yahoo.com> (raw)
In-Reply-To: <989B956029373F45A0B8AF0297081890087468@zch01exm26.fsl.freescale.net>
I got it.
In the board environment, we have to define the
BOARD_CHIP_NAME. It looks like:
#define BOARD_CHIP_NAME "8260"
--- Li Yang-r58472 <LeoLi@freescale•com> wrote:
> You are talking about the wrong i2c driver. For
> 8260, you need a cpm
> i2c driver, not the i2c-mpc driver.
>
> - Leo
>
> > -----Original Message-----
> > From:
>
linuxppc-embedded-bounces+leoli=freescale.com@ozlabs•org
> >
>
[mailto:linuxppc-embedded-bounces+leoli=freescale.com@ozlabs•org]
> On
> Behalf Of
> > jimmy liu
> > Sent: Friday, January 26, 2007 1:06 AM
> > To: embedded linuxppc
> > Subject: RE: MPC8260 I2C Problem
> >
> > In the arch\ppc\syslib\pq2_devices.c, there has
> the
> > device descriptions.
> > Do I still need manually create the plateform bus
> > tree?
> >
> > --- Li Yang-r58472 <LeoLi@freescale•com> wrote:
> >
> > > > -----Original Message-----
> > > > From:
> > >
> >
>
linuxppc-embedded-bounces+leoli=freescale.com@ozlabs•org
> > > >
> > >
> >
>
[mailto:linuxppc-embedded-bounces+leoli=freescale.com@ozlabs•org]
> > > On
> > > Behalf Of
> > > > jimmy liu
> > > > Sent: Thursday, January 25, 2007 11:22 AM
> > > > To: embedded linuxppc
> > > > Subject: MPC8260 I2C Problem
> > > >
> > > > I download the linux kernel 2.6.19 from
> > > > ftp://ftp.denx.de/pub/linux/ site.
> > > >
> > > > When I add mpc8260 I2C driver to Linux kernel
> > > 2.6.19,
> > > > the init function looks like that
> > > > static int __init fsl_i2c_init(void)
> > > > {
> > > > return driver_register(&fsl_i2c_driver);
> > > > }
> > > > I set the debug on, and found that the
> > > fsl_i2c_probe()
> > > > function is never called, so there is not I2C
> > > device
> > > > enabled, and the user space function
> > > > open("/dev/i2c-0",O_RDWR) always return error.
> I
> > > set
> > > > something wrong? Could somebody help me?
> > >
> > > Do you have an fsl-i2c node in your device tree?
> > >
> > > - Leo
> > >
> >
> >
> >
> >
> >
>
________________________________________________________________________
> ______
> > ______
> > Don't pick lemons.
> > See all the new 2007 cars at Yahoo! Autos.
> > http://autos.yahoo.com/new_cars.html
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs•org
> >
>
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
____________________________________________________________________________________
Looking for earth-friendly autos?
Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.
http://autos.yahoo.com/green_center/
prev parent reply other threads:[~2007-01-27 4:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 3:21 MPC8260 I2C Problem jimmy liu
2007-01-25 3:36 ` Li Yang-r58472
2007-01-25 4:11 ` gear
2007-01-25 17:06 ` jimmy liu
2007-01-26 5:50 ` Li Yang-r58472
2007-01-26 14:53 ` jimmy liu
2007-01-27 4:31 ` jimmy liu [this message]
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=453204.70143.qm@web53111.mail.yahoo.com \
--to=jimmyzhmliu@yahoo$(echo .)com \
--cc=LeoLi@freescale$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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