| 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
| ||
|
Date: Thu, 21 Jun 2007 20:38:43 +0200 From: Jean Delvare <khali@...ux-fr.org> To: David Woodhouse <dwmw2@...radead.org> Cc: 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 Hi David, On Thu, 21 Jun 2007 22:47:12 +0800, David Woodhouse wrote: > On Thu, 2007-06-21 at 11:33 +0200, Jean Delvare wrote: > > OK. This leads me to a question: is it OK for me to add support for my > > non-input device to inputattach, or is a separate, dedicated helper > > tool preferred? Both ways are fine with me, I don't know what the > > input subsystem maintainers expect. > > You might do better to implement it as a line discipline instead. > Or just do it in userspace. What exactly are you trying to do? I am writing a driver for a TAOS evaluation module. This device is a limited SMBus master, connecting to the serial port. The evaluation chip is connected to the SMBus. In my case this is a TSL2550 light sensor, but virtually all compatible TAOS evaluation modules could be supported. I2C bus drivers have to be implemented in the kernel, so user-space isn't an option for me. I just posted a first (working) version of my driver, if you want to take a look: http://lists.lm-sensors.org/pipermail/i2c/2007-June/001508.html Thanks, -- Jean Delvare - 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/
Powered by blists - more mailing lists