| 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, 27 Oct 2011 10:43:21 +0100 From: Stefan Hajnoczi <stefanha@...il.com> To: Markus Grabner <grabner@....tugraz.at> Cc: devel@...uxdriverproject.org, linux-kernel <linux-kernel@...r.kernel.org>, Greg KH <gregkh@...e.de> Subject: Re: staging: line6 driver status On Thu, Oct 27, 2011 at 10:05 AM, Greg KH <gregkh@...e.de> wrote: > On Thu, Oct 27, 2011 at 09:28:59AM +0100, Stefan Hajnoczi wrote: >> What is the status of the line6 staging driver? There is no TODO file >> so I'm not sure what is blocking it from leaving staging. > > That's a good question. I don't really know the status of the driver at > the moment, does anyone else? I have one question about the design of the driver: Do we really need the sysfs attributes which boil down to MIDI commands? I think a userspace library provides a better interface because the MIDI commands/values vary between device models and bloat the driver. Generic sound recording and MIDI software would talk to the driver. Utilities to control the device could link against the userspace library. By splitting the code into the kernel MIDI/pcm driver and a userspace control library which uses MIDI we can slim down the kernel driver and leave the large variation of MIDI commands/values to a library that the community can improve for specific device models. This will make the driver smaller and easier for review. Stefan -- 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