linux-kernel - Re: Writing a driver for a legacy serial device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200706220131.08954.arnd@arndb.de>
Date:	Fri, 22 Jun 2007 01:31:08 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Jean Delvare <khali@...ux-fr.org>
Cc:	David Woodhouse <dwmw2@...radead.org>,
	Dmitry Torokhov <dtor@...ightbb.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Vojtech Pavlik <vojtech@....cz>
Subject: Re: Writing a driver for a legacy serial device

On Thursday 21 June 2007, Jean Delvare wrote:
> I2C bus drivers have to be implemented in the kernel, so user-space
> isn't an option for me.

Well, you could have an i2c_algorithm that exports a character device
node to user space, and then have a trivial user application that
simply relays between that and the serial port.

It's probably not much different to what you have in the end though.

	Arnd <><
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/