> Andreas Share wrote: >>> [ ... rcu.c vs. NPTL ... ] >> no problem for me, and because i think most other user uses lirc or the >> remote plugin to control vdr it is only a minor problem. So i still use >> rcu without the locks and wait until you use a NPTL enabled linux;) > > Ok, so I finally switched to kernel 2.6 and the dvb-kernel driver > for good, and now I get the problems with rcu.c, too. > > I have modified rcu.c so that it now does all actual data > transmission in the Action() function, so no more locking > is necessary. Simply dropping the locking caused lots of > errors like > > ERROR (rcu.c,188): Invalid argument > > when background and foreground thread tried to access the > interface at the same time. > > Maybe you'd like to take a look at the attached patch. > > Klaus I have had the same error messages here, but i have not seen any side effect the last month. But your solution is the better way, i have tested it with NPTL, including key-learnig, works fine:) thank you Andreas
