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: Mon, 1 Dec 2008 19:41:36 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Jonathan Cameron <jic23@....ac.uk> Cc: LKML <linux-kernel@...r.kernel.org>, Dmitry Torokhov <dtor@...l.ru>, David Brownell <david-b@...bell.net>, Jean Delvare <khali@...ux-fr.org>, Ben Nizette <bn@...sdigital.com>, Jonathan Cameron <jic23@....ac.uk>, LM Sensors <lm-sensors@...sensors.org>, spi-devel-general@...ts.sourceforge.net Subject: Re: [Industrial I/O] [0/13] RFC: IIO v3 patchset > have both functions. The sort of devices we are talking typically > communicate over I2C or SPI buses though drivers for rs232 devices etc are > definitely on the cards. Basically we are interested in devices where direct > memory mapped access is not possible. We have I2C and SPI drivers so I assume you will use the lower layers of the stacks to do this ? > For discussion of why these don't fit within existing subsystems see > http://lkml.org/lkml/2008/5/20/135 and the rest of the associated thread. I don't see much there which says why you can't unify all this in a user space library. For RS232/423/.. devices you can go this path if you want (but I would keep it all in userspace anyway) as you can use a line discipline to sit on top of the port and provide another interface (eg the way PPP does) -- 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