Hi Oliver. Just wanted to post a status note that I was too busy to get anything useful done. Next weekend should be okay though, finally. So far I've decided to go with a rather conservative locking instead of a more finer grained one because in the end it'll make things easier to handle and won't introduce new problems. In more detail: - a slot is locked as long as the kernel thread is processing it or if some user ioctl needs access to it - reading won't introduce any new locks because it doesn't access the h/w directly and thus doesn't need locks (only works on the slot ringbuffer) I hope that this will work out and the longer lock in the kernel thread won't introduce new trouble. For the underlying implementations like budget_[av|ci] this means they are save from concurrent accesses to one slot but concurrent accesses to different slots are still possible and have to be taken care of there. Nevertheless this is rather irrelevant at the moment because there is no driver using dvb_ca_en50221 yet which provides more than one slot afaik. Ok... as soon as I have something tested and ready, I'll let you know. So long, matthias. _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
