| 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
| ||
|
Message-ID: <20081028154918.GA5630@mediacenter> Date: Tue, 28 Oct 2008 10:49:18 -0500 From: Shawn Bohrer <shawn.bohrer@...il.com> To: Greg Kroah-Hartman <gregkh@...e.de> Cc: David Schleef <ds@...leef.org>, Frank Mori Hess <fmhess@...rs.sourceforge.net>, Ian Abbott <abbotti@....co.uk>, linux-kernel@...r.kernel.org, Wolfgang Beiter <w.beiter@....at>, Guenter Gebhardt <g.gebhardt@...lhaus.de> Subject: staging: me4000 and relation to other data acquisition devices I have some questions about the user-kernel interface of the me4000 driver. From my looking through the code it seems specific to the me4000 hardware which does concern me since there are hundreds of different data acquisition devices from many different vendors. In my opinion it would beneficial if at the very least all of these devices shared a common device interface. Additionally there is the out of tree Comedi project: http://comedi.org Which supports this hardware, and many more, with a generic device interface. There may be other reason not to merge Comedi (I know they have a desire to maintain support of their RT support), but I can't help but feel that merging the me4000 driver without thinking about the hundreds of other devices out there is a mistake. -- Shawn -- 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