Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 Mar 2010 10:35:36 +0100 (CET)
From:      Joerg Pulz <Joerg.Pulz@frm2.tum.de>
To:        multimedia@freebsd.org
Cc:        Hans Petter Selasky <hselasky@freebsd.org>
Subject:   Cuse4BSD + Webcamd + FE_GET_EVENT ioctl
Message-ID:  <alpine.BSF.2.00.1003021005510.1647@unqrf.nqzva.sez2>

next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Dear Hans,

first i want to thank you again for your hard work and your continuing 
fast support.

I think i discoverd a problem with my siano based DVB-T stick together 
with Cuse4BSD and Webcamd while using VDR (http://www.tvdr.de/).
VDR is using a thread for tuning to new frequencies on channel change when 
neccessary. This thread makes use of the FE_GET_EVENT ioctl on the 
frontend device to continuously empty the frontend event queue. It makes 
no further use of the received events it just emties the queue. As i had 
a problem to switch to channels with a frequency different than the one 
the first channel at VDR startup is on i digged deeper to find the cause.
For now, i'm at the point where i can say that the thread simply hangs at 
the second or third FE_GET_EVENT ioctl and never returns from there.
If i just comment out the FE_GET_EVENT ioctl line in VDR it works normal 
but i'm not sure what happens to the device when the frontend event queue 
reaches the maximum number of events (8 events if i got it right) and 
overflows.

Maybe you can have a look at dvb_frontend_get_event() in
v4l-dvb/linux/drivers/media/dvb/dvb-core/dvb_frontend.c
to see if there is anything that blocks the ioctl forever.
Or you can give me a hint how i can debug this part by myself.

Thanks and kind regards
Joerg

- -- 
The beginning is the most important part of the work.
 				-Plato
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (FreeBSD)

iD8DBQFLjNvrSPOsGF+KA+MRAj3QAJ0dHjRXUnqdHfnOftTv0JpNEXKBEgCgzlW2
Nn6YNCn9JVIx3GI2VfiXHbY=
=VQRu
-----END PGP SIGNATURE-----



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1003021005510.1647>