[linux-dvb] dvb fronted: LOCK but no data received.

[linux-dvb] dvb fronted: LOCK but no data received.

[Andrea]

Hi,

I'd like to understand the behavior and meaning of the LOCK returned by the fronted.

If I open the fronted in readonly, and ask for the INFO, it is possible that I get a LOCK but no 
data is actually received.

This because the fronted receives data ONLY while it is opened in READ/WRITE.

In dvb_frontend.c, in dvb_frontend_open, the fronted is started via
dvb_frontend_start
only if it opened in READ/WRITE.

I see it as a misbehavior:

1) either a LOCK should NOT be returned
2) or the frontend should be started in any case (even if READ only)

Which ioctl call should I use to know if the fronted is currently active?

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] dvb fronted: LOCK but no data received.

[Andrea]

 > Hi,
 >
 > I'd like to understand the behavior and meaning of the LOCK returned by the fronted.
 >
 > If I open the fronted in readonly, and ask for the INFO, it is possible that I get a LOCK but no
 > data is actually received.
 >
 > This because the fronted receives data ONLY while it is opened in READ/WRITE.
 >
 > In dvb_frontend.c, in dvb_frontend_open, the fronted is started via
 > dvb_frontend_start
 > only if it opened in READ/WRITE.
 >
 > I see it as a misbehavior:
 >
 > 1) either a LOCK should NOT be returned
 > 2) or the frontend should be started in any case (even if READ only)
 >
 > Which ioctl call should I use to know if the fronted is currently active?

Anybody has an opinion about that?
I know, I cant spell frontend properly :-),

but other than that, what would be the correct behavior when opening the frontend in readonly?

Andrea

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb