linux-mips
[Top] [All Lists]

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

To: Pete Popov <ppopov@embeddedalley.com>
Subject: Re: i2c-algo-ite and i2c-ite planned for removal
From: Jean Delvare <khali@linux-fr.org>
Date: Tue, 20 Jun 2006 12:08:36 +0200
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
In-reply-to: <1150735558.8413.7.camel@localhost.localdomain>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20060615225723.012c82be.khali@linux-fr.org> <1150406598.1193.73.camel@localhost.localdomain> <20060616222908.f96e3691.khali@linux-fr.org> <1150735558.8413.7.camel@localhost.localdomain>
Sender: linux-mips-bounce@linux-mips.org
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 board
> > > 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>