[Top] [All Lists]

Re: i2c-algo-ite and i2c-ite planned for removal

To: "Jean Delvare" <>, "Pete Popov" <>
Subject: Re: i2c-algo-ite and i2c-ite planned for removal
From: "ankur maheshwari" <>
Date: Wed, 21 Jun 2006 11:08:34 +0530
Cc: <>, <>
Original-recipient: rfc822;
References: <><1150406598.1193.73.camel@localhost.localdomain><><1150735558.8413.7.camel@localhost.localdomain> <>
hi all,

I have used once i2c-adap-ite and i2c-algo-ite for ite-8712 chip and it
worked fine for me in MV 2.4.25. Its been an year ago, I asked on same forum
if some one has used it before but I didn't got any reply.

I added this struct definition in a .h (i2c-adap-ite.h) file which we need
to include in i2c-adap-ite.c also program ite-8712 controller pins for i2c

struct iic_ite {
        int iic_base;
        int iic_irq;
        int iic_clock;
        int iic_own;

It worked perfectly fine for me.

It's just an info on ite-chip works, to remove it from kernel tree .....
decision is up to you : ).


----- Original Message -----
From: "Jean Delvare" <>
To: "Pete Popov" <>
Cc: <>; <>
Sent: Tuesday, June 20, 2006 3:38 PM
Subject: Re: i2c-algo-ite and i2c-ite planned for removal

> Hi Pete,
> > > > For historical correctness, this driver was once upon a time usable,
> > > > though it was a few years ago. It was written by MV for some ref
> > > > that had the ITE chip and it did work. That ref board is no longer
> > > > around so it's probably safe to nuke the driver.
> > >
> > > In which kernel version? In every version I checked (2.4.12, 2.4.30,
> > > 2.6.0 and 2.6.16) it wouldn't compile due to struct iic_ite being used
> > > but never defined (and possibly other errors, but I can't test-compile
> > > the driver.)
> >
> > Honestly, I don't remember. I think it was one of the very first 2.6
> > kernels because when MV first released a 2.6 product, 2.6 was still
> > 'experimental'. It's quite possible of course that the driver was never
> > properly merged upstream in the community tree(s). But I do know that it
> > worked in the internal MV tree and an effort was made to get the driver
> > accepted upstream.
> I couldn't find any evidence of this effort. Whatever, past is past, if
> someone fixes the i2c-ite and i2c-algo-ite drivers soon, fine with me,
> if not, the drivers will be deleted (which doesn't mean they can't be
> resurrected later if there is interest and someone takes over
> maintenance.) I'm setting the deadline to September 2006.
> --
> Jean Delvare

<Prev in Thread] Current Thread [Next in Thread>