| 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: <45775861.9060507@s5r6.in-berlin.de> Date: Thu, 07 Dec 2006 00:55:13 +0100 From: Stefan Richter <stefanr@...6.in-berlin.de> To: Kristian Høgsberg <krh@...hat.com> CC: Alexey Dobriyan <adobriyan@...il.com>, linux-kernel@...r.kernel.org, linux1394-devel <linux1394-devel@...ts.sourceforge.net> Subject: Re: [PATCH 0/3] New firewire stack Kristian Høgsberg wrote: > Stefan Richter wrote: >> You have to look at the matter not only from the POV of API design but >> also of deployment and support. > > My POV here *is* about deployment and support, but from the kernel side > of things. If you commit yourself to long time support for the firewire > stack, would you prefer 4 slightly different streaming drivers with > different user space interfaces, or just one userspace driver with one > userspace interface, that enables the 4 different types of streaming to > be done in userspace? My own preference certainly came across during in the recent thread on linux1394-devel about deprecation dates... :-) > The design of the streaming interfaces have been > focused on enabling all these ad-hoc, in-kernel drivers to move to > userspace, to make it feasible to actually support the stack. -- Stefan Richter -=====-=-==- ==-- --=== http://arcgraph.de/sr/ - 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