Ronald Bultje wrote: > > (no flame intended) > > I'm thinking exactly the other way around - a good driver doesn't need a > toplevel library to function well. Since every grabber is different, > they could never use the same lib, unless the lib is just a "give a > function to the ioctl-call" toplevel-library, which doesn't add anything > and just gives overhead. The app can just as well call the ioctl > directly. 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). Marian Jancar
