From: Pete Popov <ppopov@embeddedalley.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: i2c-algo-ite and i2c-ite planned for removal
Date: Mon, 19 Jun 2006 19:45:58 +0300 [thread overview]
Message-ID: <1150735558.8413.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20060616222908.f96e3691.khali@linux-fr.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
next prev parent reply other threads:[~2006-06-19 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 20:57 i2c-algo-ite and i2c-ite planned for removal Jean Delvare
2006-06-15 21:23 ` Pete Popov
2006-06-16 20:29 ` Jean Delvare
2006-06-19 16:45 ` Pete Popov [this message]
2006-06-20 10:08 ` Jean Delvare
[not found] ` <110701c694f4$f1412fb0$f301a8c0@procsys>
2006-06-22 11:22 ` Ralf Baechle
2006-06-22 10:59 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2006-06-16 17:10 Shane McDonald
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=1150735558.8413.7.camel@localhost.localdomain \
--to=ppopov@embeddedalley.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox