Date: Fri, 7 Nov 2003 22:36:11 +0100
From: Jean Delvare <khali@linux-fr.org>
To: DI Dr Simon Vogl <simon@voxel.at>
Cc: sensors@Stimpy.netroedge.com, linux-kernel@vger.kernel.org
Subject: Re: I2C parallel port adapters drivers
Message-Id: <20031107223611.173c82cc.khali@linux-fr.org>
In-Reply-To: <3FAB6A8C.9070608@voxel.at>
References: <20031102132342.79920c6f.khali@linux-fr.org>
	<3FAB6A8C.9070608@voxel.at>
Reply-To: sensors@Stimpy.netroedge.com
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1491
Lines: 35


> hi,
> sorry for the late answer.

No problem. After all, you're the first one to answer, too ;)

> you're right, the drivers are very similar, and typically you will
> only use one of them. It is of course possible to integrate them all
> into one physical module, which you are free to do :) This is more or
> less grounded on historic reasons far back in the development of the
> driver where I introduced the different hardware access
> implementations to accomodate the different implementations (and this
> went eventually into the kernel...).
> 
> So I'd say, go ahead and code :)

OK, I'll write a unified driver then. Just one more question. Any reason
to prefer direct I/O access (ELV/Velleman) over parallel-port-style
programming (i2c-philips-par)? I'd say that the second is preferable,
but you might have had a reason to use direct access, that I ignore. If
not, I'll somehow use i2c-philips-par as a base for my unified driver,
which I'll probably call i2c-parport (since it won't be Philips-specific
anymore). That driver would support Philips adapters, ELV, Velleman and
ADM evaluation boards (I have one here for testing).

Thanks a lot for spending some time replying.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/