Marcel Siegert writes: > i also did talk to manu yesterday alot, and i think his idea, > moving frontend stuff to userspace and just implement a > simple read/write register within the kernel, is a nice thing. > it should be forced to become reality imho. i do know there > will be a lot of work todo, but with having this interface, we could > even do a migration to a different api version for those lib users, > without having to change the client application at all. > we were talking about some stuff to implement so that from end users > view everything will be a stable and consistent interface. > you may read on the irc log of #linutx from yesterday at linuxtv.org While I agree that some of the more generic frontend stuff (probably most of dvb_frontend.c) could be handled in user space I am still wondering how you want to handle very card specific features/quirks (also after reading the IRC logs) if you move all the frontend drivers into userspace. The user space library will not only have to know about things like specific GPIO controls (like mentioned in IRC) but things like necessary locking between busses of different logical frontends which belong to the same card. This can not only be necessary for one I2C transfer but around specific command sequences going to different devices. So, would the library have to know those details about each card!? Or did you think of a way to handle this in a more general way? Ralph _______________________________________________ linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
