linux-mips
[Top] [All Lists]

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

To: Jean Delvare <khali@linux-fr.org>
Subject: Re: i2c-algo-ite and i2c-ite planned for removal
From: Pete Popov <ppopov@embeddedalley.com>
Date: Mon, 19 Jun 2006 19:45:58 +0300
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
In-reply-to: <20060616222908.f96e3691.khali@linux-fr.org>
Organization: Embedded Alley Solutions, Inc
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>
Reply-to: ppopov@embeddedalley.com
Sender: linux-mips-bounce@linux-mips.org
On Fri, 2006-06-16 at 22:29 +0200, Jean Delvare wrote:
> Hi Pete,
> 
> > > So basically we have two drivers in the kernel tree for 5 years or so,
> > > which never were usable, and nobody seemed to care. 
> > 
> > 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.

Pete


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