> I think that multiple opens should be handled by userspace library using > for example shm, becouse it adds unnecessary complexity to driver which > should contain only some hooks, if needed. Doesn't work as there is hardware available which actually can do multiple captures in parallel. You simply can't handle this without driver support. I'm pretty sure using a userspace lib + "only some hooks in the driver" is much more complex than supporting multiple opens in the first place. The driver has to keep track of multiple contexts anyway, and if you switch them using "only some hooks" or if you keep track of them using multiple file handles makes no big difference to the driver. Gerd -- Protecting the children is a good way to get a lot of adults who cant stand up for themselves. -- seen in some sig on /.
