Sorry for a late response. I was in transit to participate at Linux Conf
Europe/2007, where I should give a speech about multimidia support on
Linux kernel on this Sunday.
The API seems ok to me. I've added it to v4l-dvb tree.
Guys,
Please test if everything remains correct. Although the
En/na Mauro Carvalho Chehab ha escrit:
Sorry for a late response. I was in transit to participate at Linux Conf
And sorry if I piggiback on your reply, but what about finally defining
what these values are supposed to mean (like they were in an older
revision of the dvb api), so that driver
Of course from a kernel perspective it is a simple addition, but where
should we form a userspace perspective decide on which signal strength
function to use?
I don't think an extra interface should be needed here.
For example if a demodulator is unable to provide signal strengths on
his own
Sorry,
My mistake, I was under the impression that read_rf_strength was
already a tuner interface.
So in that case it would be usefull to have included in the tuner interface.
Still policy on whether it is reported to userspace should reside
within the demod driver as outlined below I think.
Henk wrote:
Of course from a kernel perspective it is a simple addition, but where
should we form a userspace perspective decide on which signal strength
function to use?
I don't think an extra interface should be needed here.
Henk,
This is an addition to the *internal* API -- This means
Michael Krufky wrote:
struct dvb_frontend_ops contains a function pointer for reading signal
strength from the demodulator, however, it would also be useful to be
able to read the signal strength from the tuner, itself.
As of now, in dvb_tuner_ops, we only have the following function for
struct dvb_frontend_ops contains a function pointer for reading signal
strength from the demodulator, however, it would also be useful to be
able to read the signal strength from the tuner, itself.
As of now, in dvb_tuner_ops, we only have the following function for status:
int
