Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[linux-dvb] dvb/v4l: what's that with the tuners?
- To: linux-dvb@linuxtv.org
- Subject: [linux-dvb] dvb/v4l: what's that with the tuners?
- From: Guido Draheim <guidod-2003-@gmx.de>
- Date: Tue, 10 Jun 2003 23:35:07 +0200
- Content-transfer-encoding: 7bit
- Content-type: text/plain; charset=us-ascii; format=flowed
- Sender: linux-dvb-bounce@linuxtv.org
- User-agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
I am currently debugging problems of `zapping` v4l viewer with the
current dvb/cvs drivers. At the moment I do not quite understand
the sourcecode, it seems just WRONG to me.
in drivers/av7110/av7110.c
(a) VIDIOCGCHAN
here we return
struct video_channel dvb_chan = { 0, "DVB", 1, 3, 1, 1 };
where the third item (= 1) says "we have 1 tuner".
(b) the `zapping` applications does now think it should try to
tune the card to the last freq. (if it would be 0 then it
would just return on the exec path right there). First it
does check the current range of the tuner, and therefore
(c) VIDIOCGTUNER
here we see however:
/* only channel 0 has a tuner */
if(!v->tuner)
return -EINVAL;
that looks plain wrong,
so I decided to patch it up as
/* only channel 0 has a tuner */
if(v->tuner)
return -EINVAL;
(d) now the `zapping` app gets over this part, and tries to
actually...
(e) VIDIOCSFREQ
which fails obviously since that ioctl values is not
handled anywhere, and so it fails here.
what's the reason behind this setup?
-- guido http://google.de/search?q=guidod
GCS/E/S/P C++/++++$ ULHS L++w- N++@ d(+-) s+a- r+@>+++ y++ 5++X- (geekcode)
--
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe linux-dvb" as subject.
Home |
Main Index |
Thread Index