On Wed, 2002-03-27 at 19:59, Marian Jancar wrote: > No, it is just the way around :) The capturing hw (both video and audio) > is > too variable. There is no easy way to write kernel driver or api that > would > export the hw functions to userspace in unified simple, sane and > complete > way. Userspace part of the driver can keep more stable ap(b)i to apps > when > for example new hw with unexpected features appears and allows kernel > driver changes, that you may want to do for whatever reason > (effectivity, security, etc). That's exactly what a kernel API should do. Using a userspace API to be able to change the kernel API without problems just moves the problem and still doesn't bring us anywhere. Besides, v4l2 does a pretty nice job, imho. Ronald -- - .-. - /V\ | Ronald Bultje <rbultje@xxxxxxxxxxxxxxxxxxx> - // \\ | Running: Linux 2.4.18-XFS and OpenBSD 3.0 - /( )\ | http://ronald.bitfreak.net/ - ^^-^^
