matthieu castet a écrit :
Hi,
With my current kernel (2.6.32), if my dvb device is removed while in use, I
got [1].
After checking the source code, the problem seems to happen also in master :
If there are users (for example users == -2) :
- dvb_unregister_frontend :
- stop kernel thread with
Hi Matthieu,
Em Sat, 27 Mar 2010 23:04:58 +0100
matthieu castet escreveu:
> Etiquetas: NonJunk, unknown-1
> From: matthieu castet
> To: linux-media@vger.kernel.org
> Subject: [PATCH] fix dvb frontend lockup
> Date: Sat, 27 Mar 2010 23:04:58 +0100
> Sender: linux-media-ow.
matthieu castet a écrit :
matthieu castet a écrit :
Hi,
With my current kernel (2.6.32), if my dvb device is removed while in
use, I got [1].
After checking the source code, the problem seems to happen also in
master :
If there are users (for example users == -2) :
- dvb_unregister_fronte
matthieu castet a écrit :
Hi,
With my current kernel (2.6.32), if my dvb device is removed while in
use, I got [1].
After checking the source code, the problem seems to happen also in
master :
If there are users (for example users == -2) :
- dvb_unregister_frontend :
- stop kernel thread w
Hi,
With my current kernel (2.6.32), if my dvb device is removed while in use, I
got [1].
After checking the source code, the problem seems to happen also in master :
If there are users (for example users == -2) :
- dvb_unregister_frontend :
- stop kernel thread with dvb_frontend_stop :
- fep
