* Leadtek Winfast TV2100
@ 2009-11-08 17:11 Pavle Predic
2009-11-08 22:35 ` hermann pitton
0 siblings, 1 reply; 12+ messages in thread
From: Pavle Predic @ 2009-11-08 17:11 UTC (permalink / raw)
To: video4linux-list
Did anyone manage to get this card working on Linux? I got the picture out of the box, but it's impossible to get any sound from the damned thing. The card is not on CARDLIST.saa7134, but I assume a similar card/tuner combination can be used. But which? By the way, I got the speakers connected directly to card output, I'm not even trying to get it working with my sound card. I can hear clicks when loading/unloading modules, so it's alive but not set up properly.
Any info would be greatly appreciated. Perhaps someone knows of another card that is similar to this one?
Card info:
Chipset: saa7134
Tuner: Tvision TVF88T5-B/DFF
Card numbers that produce picture (modprobe saa7134 card=$n): 3, 7, 10, 16, 34, 35, 45, 46, 47, 48, 51, 63, 64, 68
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Leadtek Winfast TV2100
2009-11-08 17:11 Leadtek Winfast TV2100 Pavle Predic
@ 2009-11-08 22:35 ` hermann pitton
2009-11-20 14:11 ` Pavle Predic
0 siblings, 1 reply; 12+ messages in thread
From: hermann pitton @ 2009-11-08 22:35 UTC (permalink / raw)
To: Pavle Predic; +Cc: video4linux-list
Hi Pavle,
Am Sonntag, den 08.11.2009, 17:11 +0000 schrieb Pavle Predic:
> Did anyone manage to get this card working on Linux? I got the picture out of the box, but it's impossible to get any sound from the damned thing. The card is not on CARDLIST.saa7134, but I assume a similar card/tuner combination can be used. But which? By the way, I got the speakers connected directly to card output, I'm not even trying to get it working with my sound card. I can hear clicks when loading/unloading modules, so it's alive but not set up properly.
>
> Any info would be greatly appreciated. Perhaps someone knows of another card that is similar to this one?
>
> Card info:
> Chipset: saa7134
> Tuner: Tvision TVF88T5-B/DFF
> Card numbers that produce picture (modprobe saa7134 card=$n): 3, 7, 10, 16, 34, 35, 45, 46, 47, 48, 51, 63, 64, 68
that is not enough information yet.
The correct tuner for this one is tuner=69.
Only with this one you will have also radio support.
Since you mail from an UK mail provider, this tuner is not expected to
work with PAL-I TV stereo sound there, but radio would work.
Else, if neither amux = TV nor amux = LINE1 or LINE2 (LINE inputs for TV
sound are only found on saa7130 chips, except there is also an extra TV
mono section directly from the tuner) work for TV sound, most often an
external audio mux is in the way and needs to be configured correctly
with saa7134 gpio pins. Looking also at the minor chips on the card with
more than 3 pins can reveal such a mux.
There is also a software test on such hardware, succeeding in most
cases.
By default, external analog audio input is looped through to analog
audio out, on which you are listening, if the driver is unloaded.
On a saa7134 chip, on saa7130 are some known specials, you should hear
the incoming sound directly on your headphones or what else you might be
using directly connected to your card, trying on LINE1 and LINE2 for
that.
If not, you can expect that such a mux chip needs to be treated
correctly.
The DScaler (deinterlace.sf.net) regspy.exe often can help to identify
such gpios in use, else you must trace lines and resistors on it.
In general, an absolute minimum is to provide related "dmesg" after
loading the driver _without_ having tried on other cards previously.
Please read more on the linuxtv.org wiki about adding support for a new
card.
Cheers,
Hermann
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Leadtek Winfast TV2100
2009-11-08 22:35 ` hermann pitton
@ 2009-11-20 14:11 ` Pavle Predic
2009-11-21 0:21 ` hermann pitton
0 siblings, 1 reply; 12+ messages in thread
From: Pavle Predic @ 2009-11-20 14:11 UTC (permalink / raw)
To: hermann pitton; +Cc: video4linux-list
Hi Hermann,
Thank you so much for your help. I didn't really get most of what you said (way to technical for me), but at least I know now which tuner I should use, so I'll keep testing with tuner 69 and see if I get results.
BTW, I'm not from UK - I'm from Serbia and I'm trying to make the card work for my cable tv which uses PAL BG (at least so they say).
I'll report back after testing on tuner 69 (I'll simply try all card ids with this tuner id). In the meantime here's some more info:
dmesg:
[ 9.829338] saa7130/34: v4l2 driver version 0.2.15 loaded
[ 9.829408] saa7134 0000:00:08.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 9.829419] saa7130[0]: found at 0000:00:08.0, rev: 1, irq: 17, latency: 64, mmio: 0xfdffe000
[ 9.829428] saa7130[0]: subsystem: 107d:6f3a, board: UNKNOWN/GENERIC [card=0,autodetected]
[ 9.829458] saa7130[0]: board init: gpio is 6200c
[ 9.829465] IRQ 17/saa7130[0]: IRQF_DISABLED is not guaranteed on shared IRQs
[ 9.980513] saa7130[0]: i2c eeprom 00: 7d 10 3a 6f 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
[ 9.980532] saa7130[0]: i2c eeprom 10: 0c ff 82 0e ff 20 ff ff ff ff ff ff ff ff ff ff
[ 9.980547] saa7130[0]: i2c eeprom 20: 01 40 02 03 03 02 01 03 08 ff 00 8c ff ff ff ff
[ 9.980562] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 9.980578] saa7130[0]: i2c eeprom 40: 50 89 00 c2 00 00 02 30 02 ff ff ff ff ff ff ff
[ 9.980593] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 9.980608] saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 9.980623] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 9.980639] saa7130[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 9.980654] saa7130[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 9.980670] saa7130[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 9.980685] saa7130[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 9.980701] saa7130[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 9.980716] saa7130[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 9.980731] saa7130[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 9.980747] saa7130[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 9.980876] saa7130[0]: registered device video0 [v4l2]
[ 9.980908] saa7130[0]: registered device vbi0
lsmod:
saa7134 135552 0
ir_common 47172 1 saa7134
v4l2_common 14308 1 saa7134
videodev 31040 2 saa7134,v4l2_common
videobuf_dma_sg 11340 1 saa7134
videobuf_core 16164 2 saa7134,videobuf_dma_sg
tveeprom 10720 1 saa7134
i2c_core 20844 4 i2c_viapro,saa7134,v4l2_common,tveeprom
lspci:
00:08.0 Multimedia controller [0480]: Philips Semiconductors SAA7130 Video Broadcast Decoder [1131:7130] (rev 01)
Subsystem: LeadTek Research Inc. Device [107d:6f3a]
Flags: bus master, medium devsel, latency 64, IRQ 17
Memory at fdffe000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
Kernel driver in use: saa7134
Kernel modules: saa7134
Thanks again,
Pavle.
________________________________
From: hermann pitton <hermann-pitton@arcor.de>
To: Pavle Predic <pavle.predic@yahoo.co.uk>
Cc: video4linux-list@redhat.com
Sent: Sun, 8 November, 2009 23:35:08
Subject: Re: Leadtek Winfast TV2100
Hi Pavle,
Am Sonntag, den 08.11.2009, 17:11 +0000 schrieb Pavle Predic:
> Did anyone manage to get this card working on Linux? I got the picture out of the box, but it's impossible to get any sound from the damned thing. The card is not on CARDLIST.saa7134, but I assume a similar card/tuner combination can be used. But which? By the way, I got the speakers connected directly to card output, I'm not even trying to get it working with my sound card. I can hear clicks when loading/unloading modules, so it's alive but not set up properly.
>
> Any info would be greatly appreciated. Perhaps someone knows of another card that is similar to this one?
>
> Card info:
> Chipset: saa7134
> Tuner: Tvision TVF88T5-B/DFF
> Card numbers that produce picture (modprobe saa7134 card=$n): 3, 7, 10, 16, 34, 35, 45, 46, 47, 48, 51, 63, 64, 68
that is not enough information yet.
The correct tuner for this one is tuner=69.
Only with this one you will have also radio support.
Since you mail from an UK mail provider, this tuner is not expected to
work with PAL-I TV stereo sound there, but radio would work.
Else, if neither amux = TV nor amux = LINE1 or LINE2 (LINE inputs for TV
sound are only found on saa7130 chips, except there is also an extra TV
mono section directly from the tuner) work for TV sound, most often an
external audio mux is in the way and needs to be configured correctly
with saa7134 gpio pins. Looking also at the minor chips on the card with
more than 3 pins can reveal such a mux.
There is also a software test on such hardware, succeeding in most
cases.
By default, external analog audio input is looped through to analog
audio out, on which you are listening, if the driver is unloaded.
On a saa7134 chip, on saa7130 are some known specials, you should hear
the incoming sound directly on your headphones or what else you might be
using directly connected to your card, trying on LINE1 and LINE2 for
that.
If not, you can expect that such a mux chip needs to be treated
correctly.
The DScaler (deinterlace.sf.net) regspy.exe often can help to identify
such gpios in use, else you must trace lines and resistors on it.
In general, an absolute minimum is to provide related "dmesg" after
loading the driver _without_ having tried on other cards previously.
Please read more on the linuxtv.org wiki about adding support for a new
card.
Cheers,
Hermann
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Leadtek Winfast TV2100
2009-11-20 14:11 ` Pavle Predic
@ 2009-11-21 0:21 ` hermann pitton
2009-11-21 9:07 ` Terry Wu
0 siblings, 1 reply; 12+ messages in thread
From: hermann pitton @ 2009-11-21 0:21 UTC (permalink / raw)
To: Pavle Predic; +Cc: video4linux-list
Hi Pavle,
Am Freitag, den 20.11.2009, 14:11 +0000 schrieb Pavle Predic:
> Hi Hermann,
>
> Thank you so much for your help. I didn't really get most of what you
> said (way to technical for me), but at least I know now which tuner I
> should use, so I'll keep testing with tuner 69 and see if I get
> results.
that one should be right, especially for analog radio.
> BTW, I'm not from UK - I'm from Serbia and I'm trying to make the card
> work for my cable tv which uses PAL BG (at least so they say).
Lots of people are on the move these days, therefore it is important to
know too, what they might carry with them. That tuner should be fine
then.
> I'll report back after testing on tuner 69 (I'll simply try all card
> ids with this tuner id). In the meantime here's some more info:
Better is to follow the advice how you can narrow down such stuff.
As far I know, we have not destroyed a single device yet on the saa7134
driver, but to go over all possibilities, concerning voltage and gpios,
has some risks and is not the shortest way to come closer.
Thanks for your input.
Cheers,
Hermann
> dmesg:
>
> [ 9.829338] saa7130/34: v4l2 driver version 0.2.15 loaded
> [ 9.829408] saa7134 0000:00:08.0: PCI INT A -> GSI 17 (level, low)
> -> IRQ 17
> [ 9.829419] saa7130[0]: found at 0000:00:08.0, rev: 1, irq: 17,
> latency: 64, mmio: 0xfdffe000
> [ 9.829428] saa7130[0]: subsystem: 107d:6f3a, board:
> UNKNOWN/GENERIC [card=0,autodetected]
> [ 9.829458] saa7130[0]: board init: gpio is 6200c
> [ 9.829465] IRQ 17/saa7130[0]: IRQF_DISABLED is not guaranteed on
> shared IRQs
> [ 9.980513] saa7130[0]: i2c eeprom 00: 7d 10 3a 6f 54 20 1c 00 43
> 43 a9 1c 55 d2 b2 92
> [ 9.980532] saa7130[0]: i2c eeprom 10: 0c ff 82 0e ff 20 ff ff ff
> ff ff ff ff ff ff ff
> [ 9.980547] saa7130[0]: i2c eeprom 20: 01 40 02 03 03 02 01 03 08
> ff 00 8c ff ff ff ff
> [ 9.980562] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [ 9.980578] saa7130[0]: i2c eeprom 40: 50 89 00 c2 00 00 02 30 02
> ff ff ff ff ff ff ff
> [ 9.980593] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [ 9.980608] saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [ 9.980623] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [ 9.980639] saa7130[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [ 9.980654] saa7130[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [ 9.980670] saa7130[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [ 9.980685] saa7130[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [ 9.980701] saa7130[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [ 9.980716] saa7130[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [ 9.980731] saa7130[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [ 9.980747] saa7130[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [ 9.980876] saa7130[0]: registered device video0 [v4l2]
> [ 9.980908] saa7130[0]: registered device vbi0
>
>
> lsmod:
>
> saa7134 135552 0
> ir_common 47172 1 saa7134
> v4l2_common 14308 1 saa7134
> videodev 31040 2 saa7134,v4l2_common
> videobuf_dma_sg 11340 1 saa7134
> videobuf_core 16164 2 saa7134,videobuf_dma_sg
> tveeprom 10720 1 saa7134
> i2c_core 20844 4
> i2c_viapro,saa7134,v4l2_common,tveeprom
>
> lspci:
>
> 00:08.0 Multimedia controller [0480]: Philips Semiconductors SAA7130
> Video Broadcast Decoder [1131:7130] (rev 01)
> Subsystem: LeadTek Research Inc. Device [107d:6f3a]
> Flags: bus master, medium devsel, latency 64, IRQ 17
> Memory at fdffe000 (32-bit, non-prefetchable) [size=1K]
> Capabilities: [40] Power Management version 1
> Kernel driver in use: saa7134
> Kernel modules: saa7134
>
> Thanks again,
>
> Pavle.
>
>
>
>
>
> ______________________________________________________________________
> From: hermann pitton <hermann-pitton@arcor.de>
> To: Pavle Predic <pavle.predic@yahoo.co.uk>
> Cc: video4linux-list@redhat.com
> Sent: Sun, 8 November, 2009 23:35:08
> Subject: Re: Leadtek Winfast TV2100
>
> Hi Pavle,
>
> Am Sonntag, den 08.11.2009, 17:11 +0000 schrieb Pavle Predic:
> > Did anyone manage to get this card working on Linux? I got the
> picture out of the box, but it's impossible to get any sound from the
> damned thing. The card is not on CARDLIST.saa7134, but I assume a
> similar card/tuner combination can be used. But which? By the way, I
> got the speakers connected directly to card output, I'm not even
> trying to get it working with my sound card. I can hear clicks when
> loading/unloading modules, so it's alive but not set up properly.
> >
> > Any info would be greatly appreciated. Perhaps someone knows of
> another card that is similar to this one?
> >
> > Card info:
> > Chipset: saa7134
> > Tuner: Tvision TVF88T5-B/DFF
> > Card numbers that produce picture (modprobe saa7134 card=$n): 3, 7,
> 10, 16, 34, 35, 45, 46, 47, 48, 51, 63, 64, 68
>
> that is not enough information yet.
>
> The correct tuner for this one is tuner=69.
>
> Only with this one you will have also radio support.
>
> Since you mail from an UK mail provider, this tuner is not expected to
> work with PAL-I TV stereo sound there, but radio would work.
>
> Else, if neither amux = TV nor amux = LINE1 or LINE2 (LINE inputs for
> TV
> sound are only found on saa7130 chips, except there is also an extra
> TV
> mono section directly from the tuner) work for TV sound, most often
> an
> external audio mux is in the way and needs to be configured correctly
> with saa7134 gpio pins. Looking also at the minor chips on the card
> with
> more than 3 pins can reveal such a mux.
>
> There is also a software test on such hardware, succeeding in most
> cases.
>
> By default, external analog audio input is looped through to analog
> audio out, on which you are listening, if the driver is unloaded.
>
> On a saa7134 chip, on saa7130 are some known specials, you should hear
> the incoming sound directly on your headphones or what else you might
> be
> using directly connected to your card, trying on LINE1 and LINE2 for
> that.
>
> If not, you can expect that such a mux chip needs to be treated
> correctly.
>
> The DScaler (deinterlace.sf.net) regspy.exe often can help to identify
> such gpios in use, else you must trace lines and resistors on it.
>
> In general, an absolute minimum is to provide related "dmesg" after
> loading the driver _without_ having tried on other cards previously.
>
> Please read more on the linuxtv.org wiki about adding support for a
> new
> card.
>
> Cheers,
> Hermann
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Leadtek Winfast TV2100
2009-11-21 0:21 ` hermann pitton
@ 2009-11-21 9:07 ` Terry Wu
2009-11-21 19:53 ` Pavle Predic
0 siblings, 1 reply; 12+ messages in thread
From: Terry Wu @ 2009-11-21 9:07 UTC (permalink / raw)
To: hermann pitton; +Cc: video4linux-list
Hi,
There are many models of TV2100.
Different model uses different TV tuner.
The tuner 69 is TUNER_TNF_5335MF.
Make sure the tuner in your TV2100 card is the TNF_5335MF.
Maybe the tuner in your TV2100 card is not supported by current
v4l-dvb driver yet (linux\include\media\tuner.h).
Terry
2009/11/21 hermann pitton <hermann-pitton@arcor.de>:
> Hi Pavle,
>
> Am Freitag, den 20.11.2009, 14:11 +0000 schrieb Pavle Predic:
>> Hi Hermann,
>>
>> Thank you so much for your help. I didn't really get most of what you
>> said (way to technical for me), but at least I know now which tuner I
>> should use, so I'll keep testing with tuner 69 and see if I get
>> results.
>
> that one should be right, especially for analog radio.
>
>> BTW, I'm not from UK - I'm from Serbia and I'm trying to make the card
>> work for my cable tv which uses PAL BG (at least so they say).
>
> Lots of people are on the move these days, therefore it is important to
> know too, what they might carry with them. That tuner should be fine
> then.
>
>> I'll report back after testing on tuner 69 (I'll simply try all card
>> ids with this tuner id). In the meantime here's some more info:
>
> Better is to follow the advice how you can narrow down such stuff.
>
> As far I know, we have not destroyed a single device yet on the saa7134
> driver, but to go over all possibilities, concerning voltage and gpios,
> has some risks and is not the shortest way to come closer.
>
> Thanks for your input.
>
> Cheers,
> Hermann
>
>> dmesg:
>>
>> [ 9.829338] saa7130/34: v4l2 driver version 0.2.15 loaded
>> [ 9.829408] saa7134 0000:00:08.0: PCI INT A -> GSI 17 (level, low)
>> -> IRQ 17
>> [ 9.829419] saa7130[0]: found at 0000:00:08.0, rev: 1, irq: 17,
>> latency: 64, mmio: 0xfdffe000
>> [ 9.829428] saa7130[0]: subsystem: 107d:6f3a, board:
>> UNKNOWN/GENERIC [card=0,autodetected]
>> [ 9.829458] saa7130[0]: board init: gpio is 6200c
>> [ 9.829465] IRQ 17/saa7130[0]: IRQF_DISABLED is not guaranteed on
>> shared IRQs
>> [ 9.980513] saa7130[0]: i2c eeprom 00: 7d 10 3a 6f 54 20 1c 00 43
>> 43 a9 1c 55 d2 b2 92
>> [ 9.980532] saa7130[0]: i2c eeprom 10: 0c ff 82 0e ff 20 ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980547] saa7130[0]: i2c eeprom 20: 01 40 02 03 03 02 01 03 08
>> ff 00 8c ff ff ff ff
>> [ 9.980562] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980578] saa7130[0]: i2c eeprom 40: 50 89 00 c2 00 00 02 30 02
>> ff ff ff ff ff ff ff
>> [ 9.980593] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980608] saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980623] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980639] saa7130[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980654] saa7130[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980670] saa7130[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980685] saa7130[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980701] saa7130[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980716] saa7130[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980731] saa7130[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980747] saa7130[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980876] saa7130[0]: registered device video0 [v4l2]
>> [ 9.980908] saa7130[0]: registered device vbi0
>>
>>
>> lsmod:
>>
>> saa7134 135552 0
>> ir_common 47172 1 saa7134
>> v4l2_common 14308 1 saa7134
>> videodev 31040 2 saa7134,v4l2_common
>> videobuf_dma_sg 11340 1 saa7134
>> videobuf_core 16164 2 saa7134,videobuf_dma_sg
>> tveeprom 10720 1 saa7134
>> i2c_core 20844 4
>> i2c_viapro,saa7134,v4l2_common,tveeprom
>>
>> lspci:
>>
>> 00:08.0 Multimedia controller [0480]: Philips Semiconductors SAA7130
>> Video Broadcast Decoder [1131:7130] (rev 01)
>> Subsystem: LeadTek Research Inc. Device [107d:6f3a]
>> Flags: bus master, medium devsel, latency 64, IRQ 17
>> Memory at fdffe000 (32-bit, non-prefetchable) [size=1K]
>> Capabilities: [40] Power Management version 1
>> Kernel driver in use: saa7134
>> Kernel modules: saa7134
>>
>> Thanks again,
>>
>> Pavle.
>>
>>
>>
>>
>>
>> ______________________________________________________________________
>> From: hermann pitton <hermann-pitton@arcor.de>
>> To: Pavle Predic <pavle.predic@yahoo.co.uk>
>> Cc: video4linux-list@redhat.com
>> Sent: Sun, 8 November, 2009 23:35:08
>> Subject: Re: Leadtek Winfast TV2100
>>
>> Hi Pavle,
>>
>> Am Sonntag, den 08.11.2009, 17:11 +0000 schrieb Pavle Predic:
>> > Did anyone manage to get this card working on Linux? I got the
>> picture out of the box, but it's impossible to get any sound from the
>> damned thing. The card is not on CARDLIST.saa7134, but I assume a
>> similar card/tuner combination can be used. But which? By the way, I
>> got the speakers connected directly to card output, I'm not even
>> trying to get it working with my sound card. I can hear clicks when
>> loading/unloading modules, so it's alive but not set up properly.
>> >
>> > Any info would be greatly appreciated. Perhaps someone knows of
>> another card that is similar to this one?
>> >
>> > Card info:
>> > Chipset: saa7134
>> > Tuner: Tvision TVF88T5-B/DFF
>> > Card numbers that produce picture (modprobe saa7134 card=$n): 3, 7,
>> 10, 16, 34, 35, 45, 46, 47, 48, 51, 63, 64, 68
>>
>> that is not enough information yet.
>>
>> The correct tuner for this one is tuner=69.
>>
>> Only with this one you will have also radio support.
>>
>> Since you mail from an UK mail provider, this tuner is not expected to
>> work with PAL-I TV stereo sound there, but radio would work.
>>
>> Else, if neither amux = TV nor amux = LINE1 or LINE2 (LINE inputs for
>> TV
>> sound are only found on saa7130 chips, except there is also an extra
>> TV
>> mono section directly from the tuner) work for TV sound, most often
>> an
>> external audio mux is in the way and needs to be configured correctly
>> with saa7134 gpio pins. Looking also at the minor chips on the card
>> with
>> more than 3 pins can reveal such a mux.
>>
>> There is also a software test on such hardware, succeeding in most
>> cases.
>>
>> By default, external analog audio input is looped through to analog
>> audio out, on which you are listening, if the driver is unloaded.
>>
>> On a saa7134 chip, on saa7130 are some known specials, you should hear
>> the incoming sound directly on your headphones or what else you might
>> be
>> using directly connected to your card, trying on LINE1 and LINE2 for
>> that.
>>
>> If not, you can expect that such a mux chip needs to be treated
>> correctly.
>>
>> The DScaler (deinterlace.sf.net) regspy.exe often can help to identify
>> such gpios in use, else you must trace lines and resistors on it.
>>
>> In general, an absolute minimum is to provide related "dmesg" after
>> loading the driver _without_ having tried on other cards previously.
>>
>> Please read more on the linuxtv.org wiki about adding support for a
>> new
>> card.
>>
>> Cheers,
>> Hermann
>
>
>
> --
> video4linux-list mailing list
> Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/video4linux-list
>
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Leadtek Winfast TV2100
2009-11-21 9:07 ` Terry Wu
@ 2009-11-21 19:53 ` Pavle Predic
0 siblings, 0 replies; 12+ messages in thread
From: Pavle Predic @ 2009-11-21 19:53 UTC (permalink / raw)
To: Terry Wu, hermann pitton; +Cc: video4linux-list
Hey Terry,
Thanks for your input. Yes it would seem that my tuner is not supported (it's a YMEC Tvision TVF88T5-B/DFF), and neither is my board. But I was hoping that an existing board/tuner combination might do the job.
@Hermann - I tried card IDs 1-150 with tuner=69 and - alas - didn't get sound. Interestingly enough, almost all card ids produce a picture with this tuner. Also, I noticed that with some board IDs I'm getting clicks when muting/unmuting or switching channels, but no broadcast sound whatsoever...:(
I also tried running regspy.exe (after booting to Windows) and performed the test as described on dscaler site. But the results are way to cryptic for me...I have no clue how to use this. So I'll paste it here, and maybe someone will be able to draw a conclusion:
SAA7130 Card [0]:
Vendor ID: 0x1131
Device ID: 0x7130
Subsystem ID: 0x6f3a107d
7 states dumped
----------------------------------------------------------------------------------
SAA7130 Card - State 0:
SAA7134_GPIO_GPMODE: 80000009 * (10000000 00000000 00000000 00001001)
SAA7134_GPIO_GPSTATUS: 0606200c * (00000110 00000110 00100000 00001100)
SAA7134_ANALOG_IN_CTRL1: c1 (11000001)
SAA7134_ANALOG_IO_SELECT: 3b * (00111011)
SAA7134_VIDEO_PORT_CTRL0: 00000000 (00000000 00000000 00000000 00000000)
SAA7134_VIDEO_PORT_CTRL4: 00000000 (00000000 00000000 00000000 00000000)
SAA7134_VIDEO_PORT_CTRL8: 00 (00000000)
SAA7134_I2S_OUTPUT_SELECT: 00 (00000000)
SAA7134_I2S_OUTPUT_FORMAT: 01 (00000001)
SAA7134_I2S_OUTPUT_LEVEL: 00 (00000000)
SAA7134_I2S_AUDIO_OUTPUT: 01 (00000001)
SAA7134_TS_PARALLEL: 04 (00000100)
SAA7134_TS_PARALLEL_SERIAL: 00 (00000000)
SAA7134_TS_SERIAL0: 00 (00000000)
SAA7134_TS_SERIAL1: 00 (00000000)
SAA7134_TS_DMA0: 00 (00000000)
SAA7134_TS_DMA1: 00 (00000000)
SAA7134_TS_DMA2: 00 (00000000)
SAA7134_SPECIAL_MODE: 01 (00000001)
Changes: State 0 -> State 1:
SAA7134_GPIO_GPMODE: 80000009 -> 8000000d (-------- -------- -------- -----0--)
SAA7134_GPIO_GPSTATUS: 0606200c -> 00062000 (-----11- -------- -------- ----11--)
SAA7134_ANALOG_IO_SELECT: 3b -> 00 (--111-11)
3 changes
----------------------------------------------------------------------------------
SAA7130 Card - State 1:
SAA7134_GPIO_GPMODE: 8000000d (10000000 00000000 00000000 00001101) (was: 80000009)
SAA7134_GPIO_GPSTATUS: 00062000 * (00000000 00000110 00100000 00000000) (was: 0606200c)
SAA7134_ANALOG_IN_CTRL1: c1 * (11000001)
SAA7134_ANALOG_IO_SELECT: 00 * (00000000) (was: 3b)
SAA7134_VIDEO_PORT_CTRL0: 00000000 (00000000 00000000 00000000 00000000)
SAA7134_VIDEO_PORT_CTRL4: 00000000 (00000000 00000000 00000000 00000000)
SAA7134_VIDEO_PORT_CTRL8: 00 (00000000)
SAA7134_I2S_OUTPUT_SELECT: 00 (00000000)
SAA7134_I2S_OUTPUT_FORMAT: 01 (00000001)
SAA7134_I2S_OUTPUT_LEVEL: 00 (00000000)
SAA7134_I2S_AUDIO_OUTPUT: 01 (00000001)
SAA7134_TS_PARALLEL: 04 (00000100)
SAA7134_TS_PARALLEL_SERIAL: 00 (00000000)
SAA7134_TS_SERIAL0: 00 (00000000)
SAA7134_TS_SERIAL1: 00 (00000000)
SAA7134_TS_DMA0: 00 (00000000)
SAA7134_TS_DMA1: 00 (00000000)
SAA7134_TS_DMA2: 00 (00000000)
SAA7134_SPECIAL_MODE: 01 (00000001)
Changes: State 1 -> State 2:
SAA7134_GPIO_GPSTATUS: 00062000 -> 00062008 (-------- -------- -------- ----0---)
SAA7134_ANALOG_IN_CTRL1: c1 -> 83 (-1----0-)
SAA7134_ANALOG_IO_SELECT: 00 -> 09 (----0--0)
3 changes
----------------------------------------------------------------------------------
SAA7130 Card - State 2:
SAA7134_GPIO_GPMODE: 8000000d (10000000 00000000 00000000 00001101)
SAA7134_GPIO_GPSTATUS: 00062008 (00000000 00000110 00100000 00001000) (was: 00062000)
SAA7134_ANALOG_IN_CTRL1: 83 * (10000011) (was: c1)
SAA7134_ANALOG_IO_SELECT: 09 (00001001) (was: 00)
SAA7134_VIDEO_PORT_CTRL0: 00000000 (00000000 00000000 00000000 00000000)
SAA7134_VIDEO_PORT_CTRL4: 00000000 (00000000 00000000 00000000 00000000)
SAA7134_VIDEO_PORT_CTRL8: 00 (00000000)
SAA7134_I2S_OUTPUT_SELECT: 00 (00000000)
SAA7134_I2S_OUTPUT_FORMAT: 01 (00000001)
SAA7134_I2S_OUTPUT_LEVEL: 00 (00000000)
SAA7134_I2S_AUDIO_OUTPUT: 01 (00000001)
SAA7134_TS_PARALLEL: 04 (00000100)
SAA7134_TS_PARALLEL_SERIAL: 00 (00000000)
SAA7134_TS_SERIAL0: 00 (00000000)
SAA7134_TS_SERIAL1: 00 (00000000)
SAA7134_TS_DMA0: 00 (00000000)
SAA7134_TS_DMA1: 00 (00000000)
SAA7134_TS_DMA2: 00 (00000000)
SAA7134_SPECIAL_MODE: 01 (00000001)
Changes: State 2 -> State 3:
SAA7134_ANALOG_IN_CTRL1: 83 -> c8 (-0--0-11)
1 changes
----------------------------------------------------------------------------------
SAA7130 Card - State 3:
SAA7134_GPIO_GPMODE: 8000000d (10000000 00000000 00000000 00001101)
SAA7134_GPIO_GPSTATUS: 00062008 * (00000000 00000110 00100000 00001000)
SAA7134_ANALOG_IN_CTRL1: c8 * (11001000) (was: 83)
SAA7134_ANALOG_IO_SELECT: 09 * (00001001)
SAA7134_VIDEO_PORT_CTRL0: 00000000 (00000000 00000000 00000000 00000000)
SAA7134_VIDEO_PORT_CTRL4: 00000000 (00000000 00000000 00000000 00000000)
SAA7134_VIDEO_PORT_CTRL8: 00 (00000000)
SAA7134_I2S_OUTPUT_SELECT: 00 (00000000)
SAA7134_I2S_OUTPUT_FORMAT: 01 (00000001)
SAA7134_I2S_OUTPUT_LEVEL: 00 (00000000)
SAA7134_I2S_AUDIO_OUTPUT: 01 (00000001)
SAA7134_TS_PARALLEL: 04 (00000100)
SAA7134_TS_PARALLEL_SERIAL: 00 (00000000)
SAA7134_TS_SERIAL0: 00 (00000000)
SAA7134_TS_SERIAL1: 00 (00000000)
SAA7134_TS_DMA0: 00 (00000000)
SAA7134_TS_DMA1: 00 (00000000)
SAA7134_TS_DMA2: 00 (00000000)
SAA7134_SPECIAL_MODE: 01 (00000001)
Changes: State 3 -> State 4:
SAA7134_GPIO_GPSTATUS: 00062008 -> 04062004 (-----0-- -------- -------- ----10--)
SAA7134_ANALOG_IN_CTRL1: c8 -> c1 (----1--0) (same as 0, 1)
SAA7134_ANALOG_IO_SELECT: 09 -> 00 (----1--1) (same as 1)
3 changes
----------------------------------------------------------------------------------
SAA7130 Card - State 4:
SAA7134_GPIO_GPMODE: 8000000d (10000000 00000000 00000000 00001101)
SAA7134_GPIO_GPSTATUS: 04062004 * (00000100 00000110 00100000 00000100) (was: 00062008)
SAA7134_ANALOG_IN_CTRL1: c1 (11000001) (was: c8)
SAA7134_ANALOG_IO_SELECT: 00 (00000000) (was: 09)
SAA7134_VIDEO_PORT_CTRL0: 00000000 (00000000 00000000 00000000 00000000)
SAA7134_VIDEO_PORT_CTRL4: 00000000 (00000000 00000000 00000000 00000000)
SAA7134_VIDEO_PORT_CTRL8: 00 (00000000)
SAA7134_I2S_OUTPUT_SELECT: 00 (00000000)
SAA7134_I2S_OUTPUT_FORMAT: 01 (00000001)
SAA7134_I2S_OUTPUT_LEVEL: 00 (00000000)
SAA7134_I2S_AUDIO_OUTPUT: 01 (00000001)
SAA7134_TS_PARALLEL: 04 (00000100)
SAA7134_TS_PARALLEL_SERIAL: 00 (00000000)
SAA7134_TS_SERIAL0: 00 (00000000)
SAA7134_TS_SERIAL1: 00 (00000000)
SAA7134_TS_DMA0: 00 (00000000)
SAA7134_TS_DMA1: 00 (00000000)
SAA7134_TS_DMA2: 00 (00000000)
SAA7134_SPECIAL_MODE: 01 (00000001)
Changes: State 4 -> State 5:
SAA7134_GPIO_GPSTATUS: 04062004 -> 02062000 (-----10- -------- -------- -----1--)
1 changes
----------------------------------------------------------------------------------
SAA7130 Card - State 5:
SAA7134_GPIO_GPMODE: 8000000d (10000000 00000000 00000000 00001101)
SAA7134_GPIO_GPSTATUS: 02062000 * (00000010 00000110 00100000 00000000) (was: 04062004)
SAA7134_ANALOG_IN_CTRL1: c1 (11000001)
SAA7134_ANALOG_IO_SELECT: 00 * (00000000)
SAA7134_VIDEO_PORT_CTRL0: 00000000 (00000000 00000000 00000000 00000000)
SAA7134_VIDEO_PORT_CTRL4: 00000000 (00000000 00000000 00000000 00000000)
SAA7134_VIDEO_PORT_CTRL8: 00 (00000000)
SAA7134_I2S_OUTPUT_SELECT: 00 (00000000)
SAA7134_I2S_OUTPUT_FORMAT: 01 (00000001)
SAA7134_I2S_OUTPUT_LEVEL: 00 (00000000)
SAA7134_I2S_AUDIO_OUTPUT: 01 (00000001)
SAA7134_TS_PARALLEL: 04 (00000100)
SAA7134_TS_PARALLEL_SERIAL: 00 (00000000)
SAA7134_TS_SERIAL0: 00 (00000000)
SAA7134_TS_SERIAL1: 00 (00000000)
SAA7134_TS_DMA0: 00 (00000000)
SAA7134_TS_DMA1: 00 (00000000)
SAA7134_TS_DMA2: 00 (00000000)
SAA7134_SPECIAL_MODE: 01 (00000001)
Changes: State 5 -> Register Dump:
SAA7134_GPIO_GPSTATUS: 02062000 -> 06062008 (-----0-- -------- -------- ----0---)
SAA7134_ANALOG_IO_SELECT: 00 -> 02 (------0-)
2 changes
=================================================================================
SAA7130 Card - Register Dump:
SAA7134_GPIO_GPMODE: 8000000d (10000000 00000000 00000000 00001101)
SAA7134_GPIO_GPSTATUS: 06062008 (00000110 00000110 00100000 00001000) (was: 02062000)
SAA7134_ANALOG_IN_CTRL1: c1 (11000001)
SAA7134_ANALOG_IO_SELECT: 02 (00000010) (was: 00)
SAA7134_VIDEO_PORT_CTRL0: 00000000 (00000000 00000000 00000000 00000000)
SAA7134_VIDEO_PORT_CTRL4: 00000000 (00000000 00000000 00000000 00000000)
SAA7134_VIDEO_PORT_CTRL8: 00 (00000000)
SAA7134_I2S_OUTPUT_SELECT: 00 (00000000)
SAA7134_I2S_OUTPUT_FORMAT: 01 (00000001)
SAA7134_I2S_OUTPUT_LEVEL: 00 (00000000)
SAA7134_I2S_AUDIO_OUTPUT: 01 (00000001)
SAA7134_TS_PARALLEL: 04 (00000100)
SAA7134_TS_PARALLEL_SERIAL: 00 (00000000)
SAA7134_TS_SERIAL0: 00 (00000000)
SAA7134_TS_SERIAL1: 00 (00000000)
SAA7134_TS_DMA0: 00 (00000000)
SAA7134_TS_DMA1: 00 (00000000)
SAA7134_TS_DMA2: 00 (00000000)
SAA7134_SPECIAL_MODE: 01 (00000001)
end of dump
Here is the order in which I performed the test:State 6
State 0 - viewing software off
State 1 - tuner mode
State 2 - composite mode
State 3 - s video mode
State 4 - radio mode
State 5 - tuner mode (again)
Final dump - viewing software off (again)
Thanks to everyone for your help.
Pavle.
________________________________
From: Terry Wu <terrywu2009@gmail.com>
To: hermann pitton <hermann-pitton@arcor.de>
Cc: Pavle Predic <pavle.predic@yahoo.co.uk>; video4linux-list@redhat.com
Sent: Sat, 21 November, 2009 10:07:05
Subject: Re: Leadtek Winfast TV2100
Hi,
There are many models of TV2100.
Different model uses different TV tuner.
The tuner 69 is TUNER_TNF_5335MF.
Make sure the tuner in your TV2100 card is the TNF_5335MF.
Maybe the tuner in your TV2100 card is not supported by current
v4l-dvb driver yet (linux\include\media\tuner.h).
Terry
2009/11/21 hermann pitton <hermann-pitton@arcor.de>:
> Hi Pavle,
>
> Am Freitag, den 20.11.2009, 14:11 +0000 schrieb Pavle Predic:
>> Hi Hermann,
>>
>> Thank you so much for your help. I didn't really get most of what you
>> said (way to technical for me), but at least I know now which tuner I
>> should use, so I'll keep testing with tuner 69 and see if I get
>> results.
>
> that one should be right, especially for analog radio.
>
>> BTW, I'm not from UK - I'm from Serbia and I'm trying to make the card
>> work for my cable tv which uses PAL BG (at least so they say).
>
> Lots of people are on the move these days, therefore it is important to
> know too, what they might carry with them. That tuner should be fine
> then.
>
>> I'll report back after testing on tuner 69 (I'll simply try all card
>> ids with this tuner id). In the meantime here's some more info:
>
> Better is to follow the advice how you can narrow down such stuff.
>
> As far I know, we have not destroyed a single device yet on the saa7134
> driver, but to go over all possibilities, concerning voltage and gpios,
> has some risks and is not the shortest way to come closer.
>
> Thanks for your input.
>
> Cheers,
> Hermann
>
>> dmesg:
>>
>> [ 9.829338] saa7130/34: v4l2 driver version 0.2.15 loaded
>> [ 9.829408] saa7134 0000:00:08.0: PCI INT A -> GSI 17 (level, low)
>> -> IRQ 17
>> [ 9.829419] saa7130[0]: found at 0000:00:08.0, rev: 1, irq: 17,
>> latency: 64, mmio: 0xfdffe000
>> [ 9.829428] saa7130[0]: subsystem: 107d:6f3a, board:
>> UNKNOWN/GENERIC [card=0,autodetected]
>> [ 9.829458] saa7130[0]: board init: gpio is 6200c
>> [ 9.829465] IRQ 17/saa7130[0]: IRQF_DISABLED is not guaranteed on
>> shared IRQs
>> [ 9.980513] saa7130[0]: i2c eeprom 00: 7d 10 3a 6f 54 20 1c 00 43
>> 43 a9 1c 55 d2 b2 92
>> [ 9.980532] saa7130[0]: i2c eeprom 10: 0c ff 82 0e ff 20 ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980547] saa7130[0]: i2c eeprom 20: 01 40 02 03 03 02 01 03 08
>> ff 00 8c ff ff ff ff
>> [ 9.980562] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980578] saa7130[0]: i2c eeprom 40: 50 89 00 c2 00 00 02 30 02
>> ff ff ff ff ff ff ff
>> [ 9.980593] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980608] saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980623] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980639] saa7130[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980654] saa7130[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980670] saa7130[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980685] saa7130[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980701] saa7130[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980716] saa7130[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980731] saa7130[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980747] saa7130[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff
>> ff ff ff ff ff ff ff
>> [ 9.980876] saa7130[0]: registered device video0 [v4l2]
>> [ 9.980908] saa7130[0]: registered device vbi0
>>
>>
>> lsmod:
>>
>> saa7134 135552 0
>> ir_common 47172 1 saa7134
>> v4l2_common 14308 1 saa7134
>> videodev 31040 2 saa7134,v4l2_common
>> videobuf_dma_sg 11340 1 saa7134
>> videobuf_core 16164 2 saa7134,videobuf_dma_sg
>> tveeprom 10720 1 saa7134
>> i2c_core 20844 4
>> i2c_viapro,saa7134,v4l2_common,tveeprom
>>
>> lspci:
>>
>> 00:08.0 Multimedia controller [0480]: Philips Semiconductors SAA7130
>> Video Broadcast Decoder [1131:7130] (rev 01)
>> Subsystem: LeadTek Research Inc. Device [107d:6f3a]
>> Flags: bus master, medium devsel, latency 64, IRQ 17
>> Memory at fdffe000 (32-bit, non-prefetchable) [size=1K]
>> Capabilities: [40] Power Management version 1
>> Kernel driver in use: saa7134
>> Kernel modules: saa7134
>>
>> Thanks again,
>>
>> Pavle.
>>
>>
>>
>>
>>
>> ______________________________________________________________________
>> From: hermann pitton <hermann-pitton@arcor.de>
>> To: Pavle Predic <pavle.predic@yahoo.co.uk>
>> Cc: video4linux-list@redhat.com
>> Sent: Sun, 8 November, 2009 23:35:08
>> Subject: Re: Leadtek Winfast TV2100
>>
>> Hi Pavle,
>>
>> Am Sonntag, den 08.11.2009, 17:11 +0000 schrieb Pavle Predic:
>> > Did anyone manage to get this card working on Linux? I got the
>> picture out of the box, but it's impossible to get any sound from the
>> damned thing. The card is not on CARDLIST.saa7134, but I assume a
>> similar card/tuner combination can be used. But which? By the way, I
>> got the speakers connected directly to card output, I'm not even
>> trying to get it working with my sound card. I can hear clicks when
>> loading/unloading modules, so it's alive but not set up properly.
>> >
>> > Any info would be greatly appreciated. Perhaps someone knows of
>> another card that is similar to this one?
>> >
>> > Card info:
>> > Chipset: saa7134
>> > Tuner: Tvision TVF88T5-B/DFF
>> > Card numbers that produce picture (modprobe saa7134 card=$n): 3, 7,
>> 10, 16, 34, 35, 45, 46, 47, 48, 51, 63, 64, 68
>>
>> that is not enough information yet.
>>
>> The correct tuner for this one is tuner=69.
>>
>> Only with this one you will have also radio support.
>>
>> Since you mail from an UK mail provider, this tuner is not expected to
>> work with PAL-I TV stereo sound there, but radio would work.
>>
>> Else, if neither amux = TV nor amux = LINE1 or LINE2 (LINE inputs for
>> TV
>> sound are only found on saa7130 chips, except there is also an extra
>> TV
>> mono section directly from the tuner) work for TV sound, most often
>> an
>> external audio mux is in the way and needs to be configured correctly
>> with saa7134 gpio pins. Looking also at the minor chips on the card
>> with
>> more than 3 pins can reveal such a mux.
>>
>> There is also a software test on such hardware, succeeding in most
>> cases.
>>
>> By default, external analog audio input is looped through to analog
>> audio out, on which you are listening, if the driver is unloaded.
>>
>> On a saa7134 chip, on saa7130 are some known specials, you should hear
>> the incoming sound directly on your headphones or what else you might
>> be
>> using directly connected to your card, trying on LINE1 and LINE2 for
>> that.
>>
>> If not, you can expect that such a mux chip needs to be treated
>> correctly.
>>
>> The DScaler (deinterlace.sf.net) regspy.exe often can help to identify
>> such gpios in use, else you must trace lines and resistors on it.
>>
>> In general, an absolute minimum is to provide related "dmesg" after
>> loading the driver _without_ having tried on other cards previously.
>>
>> Please read more on the linuxtv.org wiki about adding support for a
>> new
>> card.
>>
>> Cheers,
>> Hermann
>
>
>
> --
> video4linux-list mailing list
> Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/video4linux-list
>
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Leadtek Winfast TV2100
2010-01-09 17:14 ` hermann pitton
2010-01-09 22:48 ` hermann pitton
@ 2010-01-10 21:26 ` dz-tor
1 sibling, 0 replies; 12+ messages in thread
From: dz-tor @ 2010-01-10 21:26 UTC (permalink / raw)
To: hermann pitton; +Cc: Pavle Predic, video4linux-list, LMML, Terry Wu
Hi,
On 09.01.2010 18:14, hermann pitton wrote:
> Hi,
>
> Am Samstag, den 09.01.2010, 17:23 +0100 schrieb dz-tor:
>
>> Hi Pavle,
>>
>> On 09.01.2010 15:46, Pavle Predic wrote:
>>
>>> Hey Darek,
>>>
>>> Great job of making the card work. I was really thrilled when I saw
>>> your post. However, I am a total newbie, so I couldn't apply the
>>> changes you wrote about. Could you please be a bit more specific? What
>>> I did is downloaded the driver from here:
>>> http://dl.bytesex.org/releases/video4linux/saa7134-0.2.12.tar.gz and
>>> made the changes to those two files, as described. But I have no clue
>>> how to compile it. I installed linux-headers for my kernel version and
>>> tried to run make, but I'm getting an error. Are there any
>>> configuration options that I need to set in Makefile or Make.config?
>>>
>> I'm not sure whether downloading and compiling driver is good idea. v4l
>> drivers (which includes saa7134) are included in mainline kernel, so
>> compiling kernel is what you have to do. From what I know, in Debian
>> there should be package in repositories with kernel sources
>> (linux-source or similar) - this option you should use if you want to
>> stick to the kernel version provided by your distribution. Another
>> option is to download kernel sources from kernel.org and use them (I've
>> done so - I'm using latest stable release). Here you have link to how-to
>> about kernel compiling:
>> https://help.ubuntu.com/6.10/ubuntu/installation-guide/i386/kernel-baking.html.
>> It's for Ubuntu, but for you it should be also applicable (on bottom
>> there is also link to Debian documentation).
>>
>> Before compilation you should make changes which I gave earlier. All
>> files which should be modified are in
>> <kernel_src_path>/drivers/media/video/saa7134/ directory. Have in mind
>> that what I've done is that I've changed existing card configuration -
>> it's not proper solution. When I'll manage remote control to work, I'll
>> try to prepare patch with new card configuration. You can apply my
>> changes now or wait until I'll prepare the patch.
>>
>> Regards,
>> Darek
>>
> Great!
>
> So Pavle's regspy results and following my instructions did the trick.
>
> Patches must go to LMML<linux-media@vger.kernel.org> and be against
> latest v4l-dvb master at linuxtv.org.
>
Done
> You can use what I prepared already yesterday for testing and is
> attached. You have only to change the clock and use LINE1 for external
> audio input. I suggest to use also LINE1 for mute then, gpio 0x08 is
> that input anyway.
>
> We can send that modified patch already and add IR support later.
>
> You must find the up/down gpio and with mask_keycode = 0x000000
> all the other gpios which do change on keypresses and create unique
> keycodes. Then you either need to add a new keytable or can use an
> already existing one.
>
I understand what have to be done to get support for remote control -
problem lays somewhere else. Later I'll send more details with code and
outputs from dmesg and description of the problem.
Regards,
Darek
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Leadtek Winfast TV2100
2010-01-09 17:14 ` hermann pitton
@ 2010-01-09 22:48 ` hermann pitton
2010-01-10 21:26 ` dz-tor
1 sibling, 0 replies; 12+ messages in thread
From: hermann pitton @ 2010-01-09 22:48 UTC (permalink / raw)
To: dz-tor; +Cc: Pavle Predic, video4linux-list, LMML, Terry Wu
Hi,
sorry, there is a typo in the gpio mask on previously attached patch you
might use against current v4l-dvb with your further findings.
Mask 0x0d is sufficient and we don't need any 0xe0d :(
You might also consider to start with vmux = 3 for Composite1 and vmux =
0 for Composite2, that is expected to be over the S-Video connector and
should work too.
Does save some plugging around with two composite input devices, if
S-Video is not in use.
good night,
Hermann
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Leadtek Winfast TV2100
2010-01-09 16:23 ` dz-tor
@ 2010-01-09 17:14 ` hermann pitton
2010-01-09 22:48 ` hermann pitton
2010-01-10 21:26 ` dz-tor
0 siblings, 2 replies; 12+ messages in thread
From: hermann pitton @ 2010-01-09 17:14 UTC (permalink / raw)
To: dz-tor; +Cc: Pavle Predic, video4linux-list, LMML, Terry Wu
[-- Attachment #1: Type: text/plain, Size: 18603 bytes --]
Hi,
Am Samstag, den 09.01.2010, 17:23 +0100 schrieb dz-tor:
> Hi Pavle,
>
> On 09.01.2010 15:46, Pavle Predic wrote:
> > Hey Darek,
> >
> > Great job of making the card work. I was really thrilled when I saw
> > your post. However, I am a total newbie, so I couldn't apply the
> > changes you wrote about. Could you please be a bit more specific? What
> > I did is downloaded the driver from here:
> > http://dl.bytesex.org/releases/video4linux/saa7134-0.2.12.tar.gz and
> > made the changes to those two files, as described. But I have no clue
> > how to compile it. I installed linux-headers for my kernel version and
> > tried to run make, but I'm getting an error. Are there any
> > configuration options that I need to set in Makefile or Make.config?
> I'm not sure whether downloading and compiling driver is good idea. v4l
> drivers (which includes saa7134) are included in mainline kernel, so
> compiling kernel is what you have to do. From what I know, in Debian
> there should be package in repositories with kernel sources
> (linux-source or similar) - this option you should use if you want to
> stick to the kernel version provided by your distribution. Another
> option is to download kernel sources from kernel.org and use them (I've
> done so - I'm using latest stable release). Here you have link to how-to
> about kernel compiling:
> https://help.ubuntu.com/6.10/ubuntu/installation-guide/i386/kernel-baking.html.
> It's for Ubuntu, but for you it should be also applicable (on bottom
> there is also link to Debian documentation).
>
> Before compilation you should make changes which I gave earlier. All
> files which should be modified are in
> <kernel_src_path>/drivers/media/video/saa7134/ directory. Have in mind
> that what I've done is that I've changed existing card configuration -
> it's not proper solution. When I'll manage remote control to work, I'll
> try to prepare patch with new card configuration. You can apply my
> changes now or wait until I'll prepare the patch.
>
> Regards,
> Darek
Great!
So Pavle's regspy results and following my instructions did the trick.
Patches must go to LMML <linux-media@vger.kernel.org> and be against
latest v4l-dvb master at linuxtv.org.
You can use what I prepared already yesterday for testing and is
attached. You have only to change the clock and use LINE1 for external
audio input. I suggest to use also LINE1 for mute then, gpio 0x08 is
that input anyway.
We can send that modified patch already and add IR support later.
You must find the up/down gpio and with mask_keycode = 0x000000
all the other gpios which do change on keypresses and create unique
keycodes. Then you either need to add a new keytable or can use an
already existing one.
Yes, saa7130 chips have only mono TV sound.
Cheers,
Hermann
>
> >
> > Cheers,
> >
> > Pavle.
> >
> > PS My kernel is 2.6.26-2-686 (it's a Debian Lenny 503 system). Here is
> > the output produced by make:
> >
> > debian:/home/pavle/saa7134-0.2.12# make
> > make -C /lib/modules/2.6.26-2-686/build
> > SUBDIRS=/home/pavle/saa7134-0.2.12 modules
> > make[1]: Entering directory `/usr/src/linux-headers-2.6.26-2-686'
> > CC [M] /home/pavle/saa7134-0.2.12/video-buf.o
> > In file included from /home/pavle/saa7134-0.2.12/media/video-buf.h:19,
> > from /home/pavle/saa7134-0.2.12/video-buf.c:33:
> > /home/pavle/saa7134-0.2.12/linux/videodev.h:68: error: field
> > 'class_dev' has incomplete type
> > /home/pavle/saa7134-0.2.12/linux/videodev.h:87: warning: 'struct
> > class_device_attribute' declared inside parameter list
> > /home/pavle/saa7134-0.2.12/linux/videodev.h:87: warning: its scope is
> > only this definition or declaration, which is probably not what you want
> > /home/pavle/saa7134-0.2.12/linux/videodev.h: In function
> > 'video_device_create_file':
> > /home/pavle/saa7134-0.2.12/linux/videodev.h:89: error: implicit
> > declaration of function 'class_device_create_file'
> > /home/pavle/saa7134-0.2.12/linux/videodev.h: At top level:
> > /home/pavle/saa7134-0.2.12/linux/videodev.h:93: warning: 'struct
> > class_device_attribute' declared inside parameter list
> > /home/pavle/saa7134-0.2.12/linux/videodev.h: In function
> > 'video_device_remove_file':
> > /home/pavle/saa7134-0.2.12/linux/videodev.h:95: error: implicit
> > declaration of function 'class_device_remove_file'
> > /home/pavle/saa7134-0.2.12/video-buf.c: At top level:
> > /home/pavle/saa7134-0.2.12/video-buf.c:46: error: expected ')' before
> > string constant
> > /home/pavle/saa7134-0.2.12/video-buf.c: In function
> > 'videobuf_vmalloc_to_sg':
> > /home/pavle/saa7134-0.2.12/video-buf.c:68: error: 'struct scatterlist'
> > has no member named 'page'
> > /home/pavle/saa7134-0.2.12/video-buf.c: In function
> > 'videobuf_pages_to_sg':
> > /home/pavle/saa7134-0.2.12/video-buf.c:96: error: 'struct scatterlist'
> > has no member named 'page'
> > /home/pavle/saa7134-0.2.12/video-buf.c:104: error: 'struct
> > scatterlist' has no member named 'page'
> > /home/pavle/saa7134-0.2.12/video-buf.c: In function 'videobuf_vm_nopage':
> > /home/pavle/saa7134-0.2.12/video-buf.c:1099: error: 'NOPAGE_SIGBUS'
> > undeclared (first use in this function)
> > /home/pavle/saa7134-0.2.12/video-buf.c:1099: error: (Each undeclared
> > identifier is reported only once
> > /home/pavle/saa7134-0.2.12/video-buf.c:1099: error: for each function
> > it appears in.)
> > /home/pavle/saa7134-0.2.12/video-buf.c:1102: error: 'NOPAGE_OOM'
> > undeclared (first use in this function)
> > /home/pavle/saa7134-0.2.12/video-buf.c: At top level:
> > /home/pavle/saa7134-0.2.12/video-buf.c:1119: error: unknown field
> > 'nopage' specified in initializer
> > /home/pavle/saa7134-0.2.12/video-buf.c:1119: warning: initialization
> > from incompatible pointer type
> > make[2]: *** [/home/pavle/saa7134-0.2.12/video-buf.o] Error 1
> > make[1]: *** [_module_/home/pavle/saa7134-0.2.12] Error 2
> > make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-2-686'
> > make: *** [default] Error 2
> >
> >
> > ------------------------------------------------------------------------
> > *From:* dz-tor <dz-tor@wp.pl>
> > *To:* hermann pitton <hermann-pitton@arcor.de>
> > *Cc:* terrywu2009@gmail.com; pavle.predic@yahoo.co.uk;
> > video4linux-list@redhat.com
> > *Sent:* Fri, 8 January, 2010 23:56:54
> > *Subject:* Re: Leadtek Winfast TV2100
> >
> > Hi,
> >
> > My friend helped me a little and we managed card to work, i.e. TV
> > (only mono, I suppose that stereo is not available for this card),
> > s-video, composite and radio works fine.
> >
> > We've tried setting audio_clock to both values (32.11 MHz ->
> > .audio_clock=0x187de7 and 24.576MHz -> .audio_clock=0x200000) and both
> > works - for me it seems, that for 32.11 MHz sound is better (i.e. louder).
> >
> > Now I have only one problem with ir. We succeeded to enable it, but
> > reading from it is bit weird - sometimes when I press the key, no
> > event is generated, sometimes 2 (key pressed/released) and sometimes
> > more. Have any clue what can cause that?
> >
> > Output from dmesg when module is loaded:
> > [32627.844221] saa7130/34: v4l2 driver version 0.2.15 loaded
> > [32627.844294] saa7130[0]: found at 0000:01:09.0, rev: 1, irq: 17,
> > latency: 32, mmio: 0xe7001000
> > [32627.844303] saa7130[0]: subsystem: 107d:6f3a, board: Proteus Pro
> > [philips reference design] [card=1,insmod option]
> > [32627.844340] saa7130[0]: board init: gpio is 60a08
> > [32627.844351] saa7130[0]: gpio: mode=0x0000000 in=0x0060a0c
> > out=0x0000000 [pre-init]
> > [32627.844901] input: saa7134 IR (Proteus Pro [philip as
> > /devices/pci0000:00/0000:00:08.0/0000:01:09.0/input/input15
> > [32627.845064] IRQ 17/saa7130[0]: IRQF_DISABLED is not guaranteed on
> > shared IRQs
> > [32628.028017] saa7130[0]: i2c eeprom 00: 7d 10 3a 6f 54 20 1c 00 43
> > 43 a9 1c 55 d2 b2 92
> > [32628.028029] saa7130[0]: i2c eeprom 10: 0c ff 82 0e ff 20 ff ff ff
> > ff ff ff ff ff ff ff
> > [32628.028038] saa7130[0]: i2c eeprom 20: 01 40 02 03 03 02 01 03 08
> > ff 00 8c ff ff ff ff
> > [32628.028047] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff
> > ff ff ff ff ff ff ff
> > [32628.028056] saa7130[0]: i2c eeprom 40: 50 89 00 c2 00 00 02 30 02
> > ff ff ff ff ff ff ff
> > [32628.028064] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff
> > ff ff ff ff ff ff ff
> > [32628.028073] saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff
> > ff ff ff ff ff ff ff
> > [32628.028082] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff
> > ff ff ff ff ff ff ff
> > [32628.028091] saa7130[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff
> > ff ff ff ff ff ff ff
> > [32628.028099] saa7130[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff
> > ff ff ff ff ff ff ff
> > [32628.028108] saa7130[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff
> > ff ff ff ff ff ff ff
> > [32628.028117] saa7130[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff
> > ff ff ff ff ff ff ff
> > [32628.028126] saa7130[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff
> > ff ff ff ff ff ff ff
> > [32628.028134] saa7130[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff
> > ff ff ff ff ff ff ff
> > [32628.028143] saa7130[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff
> > ff ff ff ff ff ff ff
> > [32628.028152] saa7130[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff
> > ff ff ff ff ff ff ff
> > [32628.028163] i2c i2c-2: Invalid 7-bit address 0x7a
> > [32628.036120] tuner 2-0061: chip found @ 0xc2 (saa7130[0])
> > [32628.044037] tuner-simple 2-0061: creating new instance
> > [32628.044044] tuner-simple 2-0061: type set to 69 (Tena TNF 5335 and
> > similar models)
> > [32628.052058] saa7130[0]: gpio: mode=0x000000d in=0x0060a00
> > out=0x0000008 [mute]
> > [32628.052178] saa7130[0]: registered device video1 [v4l2]
> > [32628.052205] saa7130[0]: registered device vbi0
> > [32628.052232] saa7130[0]: registered device radio0
> >
> >
> > For testing we've used existing card (card=1 - Proteus Pro) with tuner
> > 69. When everything will be working ok, my friend will try to add new
> > card definition and generate the patch. Below you can find actual code
> > modified by us:
> >
> > saa7134-cards.c
> > struct saa7134_board saa7134_boards[] = {
> > ...
> > [SAA7134_BOARD_PROTEUS_PRO] = {
> > /* /me */
> > .name = "Proteus Pro [philips reference design]",
> > .audio_clock = 0x00187de7,
> > .tuner_type = TUNER_TNF_5335MF,
> > .radio_type = UNSET,
> > .tuner_addr = ADDR_UNSET,
> > .radio_addr = ADDR_UNSET,
> >
> > .gpiomask = 0x0d,
> > .inputs = {{
> > .name = name_comp1,
> > .vmux = 3,
> > .amux = LINE2,
> > .gpio = 0x08,
> > },{
> > .name = name_tv,
> > .vmux = 1,
> > .amux = LINE1,
> > .tv = 1,
> > },{
> > .name = name_tv_mono,
> > .vmux = 1,
> > .amux = LINE1,
> > .tv = 1,
> > },{
> > .name = name_svideo,
> > .vmux = 8,
> > .amux = LINE2,
> > .gpio = 0x08,
> > }},
> > .radio = {
> > .name = name_radio,
> > .amux = LINE1,
> > .gpio = 0x04,
> > },
> > .mute = {
> > .name = name_mute,
> > .amux = TV,
> > .gpio = 0x08,
> > },
> > },
> >
> > int saa7134_board_init1(struct saa7134_dev *dev)
> > {
> > ...
> > case SAA7134_BOARD_PROTEUS_PRO:
> > dev->has_remote = SAA7134_REMOTE_GPIO;
> > break;
> >
> >
> > saa7134-input.c
> > int saa7134_input_init1(struct saa7134_dev *dev)
> > {
> > case SAA7134_BOARD_PROTEUS_PRO:
> > ir_codes = &ir_codes_avermedia_table;
> > mask_keycode = 0x000000;
> > polling = 50; // ms
> >
> > Regards,
> > Darek
> >
> > On 08.01.2010 20:34, hermann pitton wrote:
> > > Hi,
> > >
> > > Am Sonntag, den 03.01.2010, 16:37 +0100 schrieb dz-tor:
> > >
> > >> Hi,
> > >>
> > >> I want to ask whether you are working on this 'issue'. I'm
> > interested in
> > >> the subject, as I'm owner of this card and cannot get this stuff to
> > work
> > >> - I've picture, no sound. Earlier you have written, that you can
> > provide
> > >> patches for testing. If offer is still actual, I can test them.
> > >> Currently I'm using kernel 2.6.31, but if it's a problem I can
> > switch to
> > >> 2.6.32.
> > >>
> > >> As I wrote earlier I have the same card - Winfast TV2100 with FM, tv
> > >> norm used in my country is PAL (I'm from Poland).
> > >>
> > >> Regards,
> > >> Darek
> > >>
> > > please have a look at the xtal/oscillator close to the saa713x chip.
> > >
> > > It can have two different values. See README.saa7134 in Documentation.
> > >
> > > I'll provide a patch with best guessing based on the regspy.exe results
> > > then, assuming all is connected to LINE2 and routed through the external
> > > mux chip as a start. If that fails, we try with LINE1 next.
> > >
> > > Cheers,
> > > Hermann
> > >
> > >
> > >
> > >>>
> > >>>> Hey guys,
> > >>>>
> > >>>> Let me start by thanking you both for all your help. Unfortunately,
> > >>>> there isn't much I can do with the data you provided - it's way too
> > >>>> technical for me. I'd be happy to do any tests and apply any patches,
> > >>>> but I would need some instructions - but only if you have time; I
> > >>>> really don't want to burden you with this.
> > >>>>
> > >>>> Thanks again,
> > >>>>
> > >>>> Pavle.
> > >>>>
> > >>>>
> > >>>>
> > >>>> ________________________________
> > >>>> From: hermann pitton<hermann-pitton@arcor.de
> > <mailto:hermann-pitton@arcor.de>>
> > >>>> To: Terry Wu<terrywu2009@gmail.com <mailto:terrywu2009@gmail.com>>
> > >>>> Cc: pavle.predic@yahoo.co.uk <mailto:pavle.predic@yahoo.co.uk>;
> > video4linux-list@redhat.com <mailto:video4linux-list@redhat.com>
> > >>>> Sent: Sat, 28 November, 2009 4:09:28
> > >>>> Subject: Re: Re: Leadtek Winfast TV2100
> > >>>>
> > >>>> Hi Terry Wu,
> > >>>>
> > >>>> Am Donnerstag, den 26.11.2009, 10:33 +0800 schrieb Terry Wu:
> > >>>>
> > >>>>> Hi,
> > >>>>>
> > >>>>> Here are the subsystem IDs for different TV2100 models:
> > >>>>> Subsystem ID:0x6f30107d, TVF8533-BDF (PAL BG/DK)
> > >>>>> Subsystem ID:0x6f32107d, TVF5533-MF (NTSC)
> > >>>>> Subsystem ID:0x6f3a107d, TVF88T5-B/DFF (PAL BG/DK, FM)
> > >>>>>
> > >>>>> Terry
> > >>>>>
> > >>>> better is to become active on it.
> > >>>>
> > >>>> we can most likely help about how to match such tuners fine,
> > >>>> if any doubts left, but the best is to send just patches with having
> > >>>> such hardware to test on.
> > >>>>
> > >>>> Compared to the early tda9887 stuff on LeadTek devices, LeadTek was
> > >>>> pioneering and we have that in mind, it should be fairly easy for
> > those.
> > >>>>
> > >>>> Let's know the other way round too, where you have still concerns
> > doing
> > >>>> so.
> > >>>>
> > >>>> Cheers,
> > >>>> Hermann
> > >>>>
> > >>>>
> > >>>>> 2009/11/23 hermann pitton<hermann-pitton@arcor.de
> > <mailto:hermann-pitton@arcor.de>>:
> > >>>>>
> > >>>>>> Hi, thanks again!
> > >>>>>>
> > >>>>>> Am Montag, den 23.11.2009, 09:42 +0800 schrieb Terry Wu:
> > >>>>>>
> > >>>>>>> Hi,
> > >>>>>>>
> > >>>>>>> Please refer to the attached JPEG file for the GPIO
> > >>>>>>>
> > >>>> settings of
> > >>>>
> > >>>>>>> TV2100 with FM (PCB:B).
> > >>>>>>>
> > >>>>>>> Let me know if you need the information of TV2100 without FM
> > >>>>>>> (PCB:A, TVF8533-BDF).
> > >>>>>>>
> > >>>>>>> Terry Wu
> > >>>>>>>
> > >>>>>> On a first look, if we start to count gpios from zero, we tell
> > >>>>>>
> > >>>> the same.
> > >>>>
> > >>>>>> The TVF8533_BDF I would have to look up. It is four to five
> > >>>>>>
> > >>>> years back.
> > >>>>
> > >>>>>> If it uses that minor number TI chip without radio support, we
> > >>>>>>
> > >>>> treat it
> > >>>>
> > >>>>>> as tuner=69 too currently.
> > >>>>>>
> > >>>>>> For all such older can tuners, widely different about the globe,
> > >>>>>>
> > >>>> counts,
> > >>>>
> > >>>>>> that we don't have any way to detect them. So first working,
> > >>>>>>
> > >>>> either NTSC
> > >>>>
> > >>>>>> or PAL, sits in the pool position and others have to think twice.
> > >>>>>>
> > >>>>>> OEMs do code tuners into eeprom content, some do not at all,
> > >>>>>>
> > >>>> such doing
> > >>>>
> > >>>>>> it are in competition and don't follow the rules of the main chip
> > >>>>>> manufacturer, Philips/NXP in that case, and go their own ways.
> > >>>>>>
> > >>>>>> So tuner tables are unstable across manufacturers.
> > >>>>>>
> > >>>>>> We often can't help that much in such cases, but implementing
> > >>>>>>
> > >>>> their own
> > >>>>
> > >>>>>> tuner eeprom detection into the linux drivers is of course still
> > >>>>>> welcome. Hauppauge does it very successfully since years.
> > >>>>>>
> > >>>>>> We can't do much about it, if OEMs don't follow Philips or whom
> > >>>>>>
> > >>>> ever on
> > >>>>
> > >>>>>> such.
> > >>>>>>
> > >>>>>> Thanks,
> > >>>>>> Hermann
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>> 2009/11/23 Terry Wu<terrywu2009@gmail.com
> > <mailto:terrywu2009@gmail.com>>:
> > >>>>>>>
> > >>>>>>>> Hi,
> > >>>>>>>>
> > >>>>>>>> The TVF88T5-BDFF data sheet is attached.
> > >>>>>>>>
> > >>>>>>>> Terry Wu
> > >>>>>>>>
> > >>>>>>>> 11/17/2003 06:39 PM 72,010 TVF5531-MF.pdf
> > >>>>>>>> 03/12/2008 11:37 AM 555,285 TVF5533-MF-.pdf
> > >>>>>>>> 02/24/2004 02:19 PM 120,727 TVF5533-MF.pdf
> > >>>>>>>> 12/30/2003 06:59 PM 91,577 TVF5831-MFF.pdf
> > >>>>>>>> 09/26/2005 10:20 AM 156,853 TVF78P3-MFF.pdf
> > >>>>>>>> 11/17/2003 06:39 PM 67,947 TVF8531-BDF.pdf
> > >>>>>>>> 11/17/2003 06:39 PM 67,715 TVF8531-DIF.pdf
> > >>>>>>>> 03/12/2008 11:37 AM 509,340 TVF8533-BDF.pdf
> > >>>>>>>> 03/12/2008 11:37 AM 507,295 TVF8533-DIF.pdf
> > >>>>>>>> 12/30/2003 06:59 PM 87,921 TVF8831-BDFF.pdf
> > >>>>>>>> 12/30/2003 06:59 PM 87,624 TVF8831-DIFF.pdf
> > >>>>>>>> 09/26/2005 10:20 AM 176,525 TVF88P3-CFF.pdf
> > >>>>>>>> 03/24/2006 10:48 AM 460,941 TVF88T5-BDFF.pdf
> > >>>>>>>> 02/24/2004 02:19 PM 132,304 TVF9533-BDF.pdf
> > >>>>>>>> 02/24/2004 02:19 PM 120,940 TVF9533-DIF.pdf
> > >>>>>>>> 03/12/2008 11:37 AM 458,967 TVF99T5-BDFF.pdf
> > >>>>>>>>
> > >>>>>>>>
[-- Attachment #2: saa7134_testing_support_for_Leadtek_2100FM.patch --]
[-- Type: text/x-patch, Size: 2164 bytes --]
diff -r b6b82258cf5e linux/drivers/media/video/saa7134/saa7134-cards.c
--- a/linux/drivers/media/video/saa7134/saa7134-cards.c Thu Dec 31 19:14:54 2009 -0200
+++ b/linux/drivers/media/video/saa7134/saa7134-cards.c Fri Jan 08 21:48:53 2010 +0100
@@ -5359,7 +5359,47 @@
.vmux = 8,
} },
},
-
+ [SAA7134_BOARD_LEADTEK_WINFAST_TV2100FM] = {
+ .name = "Leadtek Winfast 2100FM",
+ .audio_clock = 0x00200000,
+ .tuner_type = TUNER_TNF_5335MF,
+ .radio_type = UNSET,
+ .tuner_addr = ADDR_UNSET,
+ .radio_addr = ADDR_UNSET,
+ .gpiomask = 0xe0d,
+ .inputs = {{
+ .name = name_tv,
+ .vmux = 1,
+ .amux = LINE2,
+ .gpio = 0x00,
+ .tv = 1,
+ }, {
+ .name = name_comp1,
+ .vmux = 0,
+ .amux = LINE2,
+ .gpio = 0x08,
+ }, {
+ .name = name_comp2,
+ .vmux = 3,
+ .amux = LINE2,
+ .gpio = 0x08,
+ }, {
+ .name = name_svideo,
+ .vmux = 8,
+ .amux = LINE2,
+ .gpio = 0x08,
+ } },
+ .radio = {
+ .name = name_radio,
+ .amux = LINE2,
+ .gpio = 0x04,
+ },
+ .mute = {
+ .name = name_mute,
+ .amux = LINE2,
+ .gpio = 0x08,
+ },
+ },
};
const unsigned int saa7134_bcount = ARRAY_SIZE(saa7134_boards);
@@ -6510,6 +6550,12 @@
.subdevice = 0x6655,
.driver_data = SAA7134_BOARD_LEADTEK_WINFAST_DTV1000S,
}, {
+ .vendor = PCI_VENDOR_ID_PHILIPS,
+ .device = PCI_DEVICE_ID_PHILIPS_SAA7130,
+ .subvendor = 0x107d,
+ .subdevice = 0x6f3a,
+ .driver_data = SAA7134_BOARD_LEADTEK_WINFAST_TV2100FM,
+ }, {
/* --- boards without eeprom + subsystem ID --- */
.vendor = PCI_VENDOR_ID_PHILIPS,
.device = PCI_DEVICE_ID_PHILIPS_SAA7134,
diff -r b6b82258cf5e linux/drivers/media/video/saa7134/saa7134.h
--- a/linux/drivers/media/video/saa7134/saa7134.h Thu Dec 31 19:14:54 2009 -0200
+++ b/linux/drivers/media/video/saa7134/saa7134.h Fri Jan 08 21:48:53 2010 +0100
@@ -300,6 +300,7 @@
#define SAA7134_BOARD_ZOLID_HYBRID_PCI 173
#define SAA7134_BOARD_ASUS_EUROPA_HYBRID 174
#define SAA7134_BOARD_LEADTEK_WINFAST_DTV1000S 175
+#define SAA7134_BOARD_LEADTEK_WINFAST_TV2100FM 176
#define SAA7134_MAXBOARDS 32
#define SAA7134_INPUT_MAX 8
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Leadtek Winfast TV2100
2010-01-09 14:46 ` Pavle Predic
@ 2010-01-09 16:23 ` dz-tor
2010-01-09 17:14 ` hermann pitton
0 siblings, 1 reply; 12+ messages in thread
From: dz-tor @ 2010-01-09 16:23 UTC (permalink / raw)
To: Pavle Predic; +Cc: video4linux-list
Hi Pavle,
On 09.01.2010 15:46, Pavle Predic wrote:
> Hey Darek,
>
> Great job of making the card work. I was really thrilled when I saw
> your post. However, I am a total newbie, so I couldn't apply the
> changes you wrote about. Could you please be a bit more specific? What
> I did is downloaded the driver from here:
> http://dl.bytesex.org/releases/video4linux/saa7134-0.2.12.tar.gz and
> made the changes to those two files, as described. But I have no clue
> how to compile it. I installed linux-headers for my kernel version and
> tried to run make, but I'm getting an error. Are there any
> configuration options that I need to set in Makefile or Make.config?
I'm not sure whether downloading and compiling driver is good idea. v4l
drivers (which includes saa7134) are included in mainline kernel, so
compiling kernel is what you have to do. From what I know, in Debian
there should be package in repositories with kernel sources
(linux-source or similar) - this option you should use if you want to
stick to the kernel version provided by your distribution. Another
option is to download kernel sources from kernel.org and use them (I've
done so - I'm using latest stable release). Here you have link to how-to
about kernel compiling:
https://help.ubuntu.com/6.10/ubuntu/installation-guide/i386/kernel-baking.html.
It's for Ubuntu, but for you it should be also applicable (on bottom
there is also link to Debian documentation).
Before compilation you should make changes which I gave earlier. All
files which should be modified are in
<kernel_src_path>/drivers/media/video/saa7134/ directory. Have in mind
that what I've done is that I've changed existing card configuration -
it's not proper solution. When I'll manage remote control to work, I'll
try to prepare patch with new card configuration. You can apply my
changes now or wait until I'll prepare the patch.
Regards,
Darek
>
> Cheers,
>
> Pavle.
>
> PS My kernel is 2.6.26-2-686 (it's a Debian Lenny 503 system). Here is
> the output produced by make:
>
> debian:/home/pavle/saa7134-0.2.12# make
> make -C /lib/modules/2.6.26-2-686/build
> SUBDIRS=/home/pavle/saa7134-0.2.12 modules
> make[1]: Entering directory `/usr/src/linux-headers-2.6.26-2-686'
> CC [M] /home/pavle/saa7134-0.2.12/video-buf.o
> In file included from /home/pavle/saa7134-0.2.12/media/video-buf.h:19,
> from /home/pavle/saa7134-0.2.12/video-buf.c:33:
> /home/pavle/saa7134-0.2.12/linux/videodev.h:68: error: field
> 'class_dev' has incomplete type
> /home/pavle/saa7134-0.2.12/linux/videodev.h:87: warning: 'struct
> class_device_attribute' declared inside parameter list
> /home/pavle/saa7134-0.2.12/linux/videodev.h:87: warning: its scope is
> only this definition or declaration, which is probably not what you want
> /home/pavle/saa7134-0.2.12/linux/videodev.h: In function
> 'video_device_create_file':
> /home/pavle/saa7134-0.2.12/linux/videodev.h:89: error: implicit
> declaration of function 'class_device_create_file'
> /home/pavle/saa7134-0.2.12/linux/videodev.h: At top level:
> /home/pavle/saa7134-0.2.12/linux/videodev.h:93: warning: 'struct
> class_device_attribute' declared inside parameter list
> /home/pavle/saa7134-0.2.12/linux/videodev.h: In function
> 'video_device_remove_file':
> /home/pavle/saa7134-0.2.12/linux/videodev.h:95: error: implicit
> declaration of function 'class_device_remove_file'
> /home/pavle/saa7134-0.2.12/video-buf.c: At top level:
> /home/pavle/saa7134-0.2.12/video-buf.c:46: error: expected ')' before
> string constant
> /home/pavle/saa7134-0.2.12/video-buf.c: In function
> 'videobuf_vmalloc_to_sg':
> /home/pavle/saa7134-0.2.12/video-buf.c:68: error: 'struct scatterlist'
> has no member named 'page'
> /home/pavle/saa7134-0.2.12/video-buf.c: In function
> 'videobuf_pages_to_sg':
> /home/pavle/saa7134-0.2.12/video-buf.c:96: error: 'struct scatterlist'
> has no member named 'page'
> /home/pavle/saa7134-0.2.12/video-buf.c:104: error: 'struct
> scatterlist' has no member named 'page'
> /home/pavle/saa7134-0.2.12/video-buf.c: In function 'videobuf_vm_nopage':
> /home/pavle/saa7134-0.2.12/video-buf.c:1099: error: 'NOPAGE_SIGBUS'
> undeclared (first use in this function)
> /home/pavle/saa7134-0.2.12/video-buf.c:1099: error: (Each undeclared
> identifier is reported only once
> /home/pavle/saa7134-0.2.12/video-buf.c:1099: error: for each function
> it appears in.)
> /home/pavle/saa7134-0.2.12/video-buf.c:1102: error: 'NOPAGE_OOM'
> undeclared (first use in this function)
> /home/pavle/saa7134-0.2.12/video-buf.c: At top level:
> /home/pavle/saa7134-0.2.12/video-buf.c:1119: error: unknown field
> 'nopage' specified in initializer
> /home/pavle/saa7134-0.2.12/video-buf.c:1119: warning: initialization
> from incompatible pointer type
> make[2]: *** [/home/pavle/saa7134-0.2.12/video-buf.o] Error 1
> make[1]: *** [_module_/home/pavle/saa7134-0.2.12] Error 2
> make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-2-686'
> make: *** [default] Error 2
>
>
> ------------------------------------------------------------------------
> *From:* dz-tor <dz-tor@wp.pl>
> *To:* hermann pitton <hermann-pitton@arcor.de>
> *Cc:* terrywu2009@gmail.com; pavle.predic@yahoo.co.uk;
> video4linux-list@redhat.com
> *Sent:* Fri, 8 January, 2010 23:56:54
> *Subject:* Re: Leadtek Winfast TV2100
>
> Hi,
>
> My friend helped me a little and we managed card to work, i.e. TV
> (only mono, I suppose that stereo is not available for this card),
> s-video, composite and radio works fine.
>
> We've tried setting audio_clock to both values (32.11 MHz ->
> .audio_clock=0x187de7 and 24.576MHz -> .audio_clock=0x200000) and both
> works - for me it seems, that for 32.11 MHz sound is better (i.e. louder).
>
> Now I have only one problem with ir. We succeeded to enable it, but
> reading from it is bit weird - sometimes when I press the key, no
> event is generated, sometimes 2 (key pressed/released) and sometimes
> more. Have any clue what can cause that?
>
> Output from dmesg when module is loaded:
> [32627.844221] saa7130/34: v4l2 driver version 0.2.15 loaded
> [32627.844294] saa7130[0]: found at 0000:01:09.0, rev: 1, irq: 17,
> latency: 32, mmio: 0xe7001000
> [32627.844303] saa7130[0]: subsystem: 107d:6f3a, board: Proteus Pro
> [philips reference design] [card=1,insmod option]
> [32627.844340] saa7130[0]: board init: gpio is 60a08
> [32627.844351] saa7130[0]: gpio: mode=0x0000000 in=0x0060a0c
> out=0x0000000 [pre-init]
> [32627.844901] input: saa7134 IR (Proteus Pro [philip as
> /devices/pci0000:00/0000:00:08.0/0000:01:09.0/input/input15
> [32627.845064] IRQ 17/saa7130[0]: IRQF_DISABLED is not guaranteed on
> shared IRQs
> [32628.028017] saa7130[0]: i2c eeprom 00: 7d 10 3a 6f 54 20 1c 00 43
> 43 a9 1c 55 d2 b2 92
> [32628.028029] saa7130[0]: i2c eeprom 10: 0c ff 82 0e ff 20 ff ff ff
> ff ff ff ff ff ff ff
> [32628.028038] saa7130[0]: i2c eeprom 20: 01 40 02 03 03 02 01 03 08
> ff 00 8c ff ff ff ff
> [32628.028047] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [32628.028056] saa7130[0]: i2c eeprom 40: 50 89 00 c2 00 00 02 30 02
> ff ff ff ff ff ff ff
> [32628.028064] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [32628.028073] saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [32628.028082] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [32628.028091] saa7130[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [32628.028099] saa7130[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [32628.028108] saa7130[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [32628.028117] saa7130[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [32628.028126] saa7130[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [32628.028134] saa7130[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [32628.028143] saa7130[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [32628.028152] saa7130[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff
> [32628.028163] i2c i2c-2: Invalid 7-bit address 0x7a
> [32628.036120] tuner 2-0061: chip found @ 0xc2 (saa7130[0])
> [32628.044037] tuner-simple 2-0061: creating new instance
> [32628.044044] tuner-simple 2-0061: type set to 69 (Tena TNF 5335 and
> similar models)
> [32628.052058] saa7130[0]: gpio: mode=0x000000d in=0x0060a00
> out=0x0000008 [mute]
> [32628.052178] saa7130[0]: registered device video1 [v4l2]
> [32628.052205] saa7130[0]: registered device vbi0
> [32628.052232] saa7130[0]: registered device radio0
>
>
> For testing we've used existing card (card=1 - Proteus Pro) with tuner
> 69. When everything will be working ok, my friend will try to add new
> card definition and generate the patch. Below you can find actual code
> modified by us:
>
> saa7134-cards.c
> struct saa7134_board saa7134_boards[] = {
> ...
> [SAA7134_BOARD_PROTEUS_PRO] = {
> /* /me */
> .name = "Proteus Pro [philips reference design]",
> .audio_clock = 0x00187de7,
> .tuner_type = TUNER_TNF_5335MF,
> .radio_type = UNSET,
> .tuner_addr = ADDR_UNSET,
> .radio_addr = ADDR_UNSET,
>
> .gpiomask = 0x0d,
> .inputs = {{
> .name = name_comp1,
> .vmux = 3,
> .amux = LINE2,
> .gpio = 0x08,
> },{
> .name = name_tv,
> .vmux = 1,
> .amux = LINE1,
> .tv = 1,
> },{
> .name = name_tv_mono,
> .vmux = 1,
> .amux = LINE1,
> .tv = 1,
> },{
> .name = name_svideo,
> .vmux = 8,
> .amux = LINE2,
> .gpio = 0x08,
> }},
> .radio = {
> .name = name_radio,
> .amux = LINE1,
> .gpio = 0x04,
> },
> .mute = {
> .name = name_mute,
> .amux = TV,
> .gpio = 0x08,
> },
> },
>
> int saa7134_board_init1(struct saa7134_dev *dev)
> {
> ...
> case SAA7134_BOARD_PROTEUS_PRO:
> dev->has_remote = SAA7134_REMOTE_GPIO;
> break;
>
>
> saa7134-input.c
> int saa7134_input_init1(struct saa7134_dev *dev)
> {
> case SAA7134_BOARD_PROTEUS_PRO:
> ir_codes = &ir_codes_avermedia_table;
> mask_keycode = 0x000000;
> polling = 50; // ms
>
> Regards,
> Darek
>
> On 08.01.2010 20:34, hermann pitton wrote:
> > Hi,
> >
> > Am Sonntag, den 03.01.2010, 16:37 +0100 schrieb dz-tor:
> >
> >> Hi,
> >>
> >> I want to ask whether you are working on this 'issue'. I'm
> interested in
> >> the subject, as I'm owner of this card and cannot get this stuff to
> work
> >> - I've picture, no sound. Earlier you have written, that you can
> provide
> >> patches for testing. If offer is still actual, I can test them.
> >> Currently I'm using kernel 2.6.31, but if it's a problem I can
> switch to
> >> 2.6.32.
> >>
> >> As I wrote earlier I have the same card - Winfast TV2100 with FM, tv
> >> norm used in my country is PAL (I'm from Poland).
> >>
> >> Regards,
> >> Darek
> >>
> > please have a look at the xtal/oscillator close to the saa713x chip.
> >
> > It can have two different values. See README.saa7134 in Documentation.
> >
> > I'll provide a patch with best guessing based on the regspy.exe results
> > then, assuming all is connected to LINE2 and routed through the external
> > mux chip as a start. If that fails, we try with LINE1 next.
> >
> > Cheers,
> > Hermann
> >
> >
> >
> >>>
> >>>> Hey guys,
> >>>>
> >>>> Let me start by thanking you both for all your help. Unfortunately,
> >>>> there isn't much I can do with the data you provided - it's way too
> >>>> technical for me. I'd be happy to do any tests and apply any patches,
> >>>> but I would need some instructions - but only if you have time; I
> >>>> really don't want to burden you with this.
> >>>>
> >>>> Thanks again,
> >>>>
> >>>> Pavle.
> >>>>
> >>>>
> >>>>
> >>>> ________________________________
> >>>> From: hermann pitton<hermann-pitton@arcor.de
> <mailto:hermann-pitton@arcor.de>>
> >>>> To: Terry Wu<terrywu2009@gmail.com <mailto:terrywu2009@gmail.com>>
> >>>> Cc: pavle.predic@yahoo.co.uk <mailto:pavle.predic@yahoo.co.uk>;
> video4linux-list@redhat.com <mailto:video4linux-list@redhat.com>
> >>>> Sent: Sat, 28 November, 2009 4:09:28
> >>>> Subject: Re: Re: Leadtek Winfast TV2100
> >>>>
> >>>> Hi Terry Wu,
> >>>>
> >>>> Am Donnerstag, den 26.11.2009, 10:33 +0800 schrieb Terry Wu:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> Here are the subsystem IDs for different TV2100 models:
> >>>>> Subsystem ID:0x6f30107d, TVF8533-BDF (PAL BG/DK)
> >>>>> Subsystem ID:0x6f32107d, TVF5533-MF (NTSC)
> >>>>> Subsystem ID:0x6f3a107d, TVF88T5-B/DFF (PAL BG/DK, FM)
> >>>>>
> >>>>> Terry
> >>>>>
> >>>> better is to become active on it.
> >>>>
> >>>> we can most likely help about how to match such tuners fine,
> >>>> if any doubts left, but the best is to send just patches with having
> >>>> such hardware to test on.
> >>>>
> >>>> Compared to the early tda9887 stuff on LeadTek devices, LeadTek was
> >>>> pioneering and we have that in mind, it should be fairly easy for
> those.
> >>>>
> >>>> Let's know the other way round too, where you have still concerns
> doing
> >>>> so.
> >>>>
> >>>> Cheers,
> >>>> Hermann
> >>>>
> >>>>
> >>>>> 2009/11/23 hermann pitton<hermann-pitton@arcor.de
> <mailto:hermann-pitton@arcor.de>>:
> >>>>>
> >>>>>> Hi, thanks again!
> >>>>>>
> >>>>>> Am Montag, den 23.11.2009, 09:42 +0800 schrieb Terry Wu:
> >>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> Please refer to the attached JPEG file for the GPIO
> >>>>>>>
> >>>> settings of
> >>>>
> >>>>>>> TV2100 with FM (PCB:B).
> >>>>>>>
> >>>>>>> Let me know if you need the information of TV2100 without FM
> >>>>>>> (PCB:A, TVF8533-BDF).
> >>>>>>>
> >>>>>>> Terry Wu
> >>>>>>>
> >>>>>> On a first look, if we start to count gpios from zero, we tell
> >>>>>>
> >>>> the same.
> >>>>
> >>>>>> The TVF8533_BDF I would have to look up. It is four to five
> >>>>>>
> >>>> years back.
> >>>>
> >>>>>> If it uses that minor number TI chip without radio support, we
> >>>>>>
> >>>> treat it
> >>>>
> >>>>>> as tuner=69 too currently.
> >>>>>>
> >>>>>> For all such older can tuners, widely different about the globe,
> >>>>>>
> >>>> counts,
> >>>>
> >>>>>> that we don't have any way to detect them. So first working,
> >>>>>>
> >>>> either NTSC
> >>>>
> >>>>>> or PAL, sits in the pool position and others have to think twice.
> >>>>>>
> >>>>>> OEMs do code tuners into eeprom content, some do not at all,
> >>>>>>
> >>>> such doing
> >>>>
> >>>>>> it are in competition and don't follow the rules of the main chip
> >>>>>> manufacturer, Philips/NXP in that case, and go their own ways.
> >>>>>>
> >>>>>> So tuner tables are unstable across manufacturers.
> >>>>>>
> >>>>>> We often can't help that much in such cases, but implementing
> >>>>>>
> >>>> their own
> >>>>
> >>>>>> tuner eeprom detection into the linux drivers is of course still
> >>>>>> welcome. Hauppauge does it very successfully since years.
> >>>>>>
> >>>>>> We can't do much about it, if OEMs don't follow Philips or whom
> >>>>>>
> >>>> ever on
> >>>>
> >>>>>> such.
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Hermann
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> 2009/11/23 Terry Wu<terrywu2009@gmail.com
> <mailto:terrywu2009@gmail.com>>:
> >>>>>>>
> >>>>>>>> Hi,
> >>>>>>>>
> >>>>>>>> The TVF88T5-BDFF data sheet is attached.
> >>>>>>>>
> >>>>>>>> Terry Wu
> >>>>>>>>
> >>>>>>>> 11/17/2003 06:39 PM 72,010 TVF5531-MF.pdf
> >>>>>>>> 03/12/2008 11:37 AM 555,285 TVF5533-MF-.pdf
> >>>>>>>> 02/24/2004 02:19 PM 120,727 TVF5533-MF.pdf
> >>>>>>>> 12/30/2003 06:59 PM 91,577 TVF5831-MFF.pdf
> >>>>>>>> 09/26/2005 10:20 AM 156,853 TVF78P3-MFF.pdf
> >>>>>>>> 11/17/2003 06:39 PM 67,947 TVF8531-BDF.pdf
> >>>>>>>> 11/17/2003 06:39 PM 67,715 TVF8531-DIF.pdf
> >>>>>>>> 03/12/2008 11:37 AM 509,340 TVF8533-BDF.pdf
> >>>>>>>> 03/12/2008 11:37 AM 507,295 TVF8533-DIF.pdf
> >>>>>>>> 12/30/2003 06:59 PM 87,921 TVF8831-BDFF.pdf
> >>>>>>>> 12/30/2003 06:59 PM 87,624 TVF8831-DIFF.pdf
> >>>>>>>> 09/26/2005 10:20 AM 176,525 TVF88P3-CFF.pdf
> >>>>>>>> 03/24/2006 10:48 AM 460,941 TVF88T5-BDFF.pdf
> >>>>>>>> 02/24/2004 02:19 PM 132,304 TVF9533-BDF.pdf
> >>>>>>>> 02/24/2004 02:19 PM 120,940 TVF9533-DIF.pdf
> >>>>>>>> 03/12/2008 11:37 AM 458,967 TVF99T5-BDFF.pdf
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>>>
> >
> >
> >
>
>
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Leadtek Winfast TV2100
2010-01-08 22:56 ` dz-tor
@ 2010-01-09 14:46 ` Pavle Predic
2010-01-09 16:23 ` dz-tor
0 siblings, 1 reply; 12+ messages in thread
From: Pavle Predic @ 2010-01-09 14:46 UTC (permalink / raw)
To: dz-tor; +Cc: video4linux-list
Hey Darek,
Great job of making the card work. I was really thrilled when I saw your post. However, I am a total newbie, so I couldn't apply the changes you wrote about. Could you please be a bit more specific? What I did is downloaded the driver from here: http://dl.bytesex.org/releases/video4linux/saa7134-0.2.12.tar.gz and made the changes to those two files, as described. But I have no clue how to compile it. I installed linux-headers for my kernel version and tried to run make, but I'm getting an error. Are there any configuration options that I need to set in Makefile or Make.config?
Cheers,
Pavle.
PS My kernel is 2.6.26-2-686 (it's a Debian Lenny 503 system). Here is the output produced by make:
debian:/home/pavle/saa7134-0.2.12# make
make -C /lib/modules/2.6.26-2-686/build SUBDIRS=/home/pavle/saa7134-0.2.12 modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.26-2-686'
CC [M] /home/pavle/saa7134-0.2.12/video-buf.o
In file included from /home/pavle/saa7134-0.2.12/media/video-buf.h:19,
from /home/pavle/saa7134-0.2.12/video-buf.c:33:
/home/pavle/saa7134-0.2.12/linux/videodev.h:68: error: field 'class_dev' has incomplete type
/home/pavle/saa7134-0.2.12/linux/videodev.h:87: warning: 'struct class_device_attribute' declared inside parameter list
/home/pavle/saa7134-0.2.12/linux/videodev.h:87: warning: its scope is only this definition or declaration, which is probably not what you want
/home/pavle/saa7134-0.2.12/linux/videodev.h: In function 'video_device_create_file':
/home/pavle/saa7134-0.2.12/linux/videodev.h:89: error: implicit declaration of function 'class_device_create_file'
/home/pavle/saa7134-0.2.12/linux/videodev.h: At top level:
/home/pavle/saa7134-0.2.12/linux/videodev.h:93: warning: 'struct class_device_attribute' declared inside parameter list
/home/pavle/saa7134-0.2.12/linux/videodev.h: In function 'video_device_remove_file':
/home/pavle/saa7134-0.2.12/linux/videodev.h:95: error: implicit declaration of function 'class_device_remove_file'
/home/pavle/saa7134-0.2.12/video-buf.c: At top level:
/home/pavle/saa7134-0.2.12/video-buf.c:46: error: expected ')' before string constant
/home/pavle/saa7134-0.2.12/video-buf.c: In function 'videobuf_vmalloc_to_sg':
/home/pavle/saa7134-0.2.12/video-buf.c:68: error: 'struct scatterlist' has no member named 'page'
/home/pavle/saa7134-0.2.12/video-buf.c: In function 'videobuf_pages_to_sg':
/home/pavle/saa7134-0.2.12/video-buf.c:96: error: 'struct scatterlist' has no member named 'page'
/home/pavle/saa7134-0.2.12/video-buf.c:104: error: 'struct scatterlist' has no member named 'page'
/home/pavle/saa7134-0.2.12/video-buf.c: In function 'videobuf_vm_nopage':
/home/pavle/saa7134-0.2.12/video-buf.c:1099: error: 'NOPAGE_SIGBUS' undeclared (first use in this function)
/home/pavle/saa7134-0.2.12/video-buf.c:1099: error: (Each undeclared identifier is reported only once
/home/pavle/saa7134-0.2.12/video-buf.c:1099: error: for each function it appears in.)
/home/pavle/saa7134-0.2.12/video-buf.c:1102: error: 'NOPAGE_OOM' undeclared (first use in this function)
/home/pavle/saa7134-0.2.12/video-buf.c: At top level:
/home/pavle/saa7134-0.2.12/video-buf.c:1119: error: unknown field 'nopage' specified in initializer
/home/pavle/saa7134-0.2.12/video-buf.c:1119: warning: initialization from incompatible pointer type
make[2]: *** [/home/pavle/saa7134-0.2.12/video-buf.o] Error 1
make[1]: *** [_module_/home/pavle/saa7134-0.2.12] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-2-686'
make: *** [default] Error 2
________________________________
From: dz-tor <dz-tor@wp.pl>
To: hermann pitton <hermann-pitton@arcor.de>
Cc: terrywu2009@gmail.com; pavle.predic@yahoo.co.uk; video4linux-list@redhat.com
Sent: Fri, 8 January, 2010 23:56:54
Subject: Re: Leadtek Winfast TV2100
Hi,
My friend helped me a little and we managed card to work, i.e. TV (only mono, I suppose that stereo is not available for this card), s-video, composite and radio works fine.
We've tried setting audio_clock to both values (32.11 MHz -> .audio_clock=0x187de7 and 24.576MHz -> .audio_clock=0x200000) and both works - for me it seems, that for 32.11 MHz sound is better (i.e. louder).
Now I have only one problem with ir. We succeeded to enable it, but reading from it is bit weird - sometimes when I press the key, no event is generated, sometimes 2 (key pressed/released) and sometimes more. Have any clue what can cause that?
Output from dmesg when module is loaded:
[32627.844221] saa7130/34: v4l2 driver version 0.2.15 loaded
[32627.844294] saa7130[0]: found at 0000:01:09.0, rev: 1, irq: 17, latency: 32, mmio: 0xe7001000
[32627.844303] saa7130[0]: subsystem: 107d:6f3a, board: Proteus Pro [philips reference design] [card=1,insmod option]
[32627.844340] saa7130[0]: board init: gpio is 60a08
[32627.844351] saa7130[0]: gpio: mode=0x0000000 in=0x0060a0c out=0x0000000 [pre-init]
[32627.844901] input: saa7134 IR (Proteus Pro [philip as /devices/pci0000:00/0000:00:08.0/0000:01:09.0/input/input15
[32627.845064] IRQ 17/saa7130[0]: IRQF_DISABLED is not guaranteed on shared IRQs
[32628.028017] saa7130[0]: i2c eeprom 00: 7d 10 3a 6f 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
[32628.028029] saa7130[0]: i2c eeprom 10: 0c ff 82 0e ff 20 ff ff ff ff ff ff ff ff ff ff
[32628.028038] saa7130[0]: i2c eeprom 20: 01 40 02 03 03 02 01 03 08 ff 00 8c ff ff ff ff
[32628.028047] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[32628.028056] saa7130[0]: i2c eeprom 40: 50 89 00 c2 00 00 02 30 02 ff ff ff ff ff ff ff
[32628.028064] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[32628.028073] saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[32628.028082] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[32628.028091] saa7130[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[32628.028099] saa7130[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[32628.028108] saa7130[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[32628.028117] saa7130[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[32628.028126] saa7130[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[32628.028134] saa7130[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[32628.028143] saa7130[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[32628.028152] saa7130[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[32628.028163] i2c i2c-2: Invalid 7-bit address 0x7a
[32628.036120] tuner 2-0061: chip found @ 0xc2 (saa7130[0])
[32628.044037] tuner-simple 2-0061: creating new instance
[32628.044044] tuner-simple 2-0061: type set to 69 (Tena TNF 5335 and similar models)
[32628.052058] saa7130[0]: gpio: mode=0x000000d in=0x0060a00 out=0x0000008 [mute]
[32628.052178] saa7130[0]: registered device video1 [v4l2]
[32628.052205] saa7130[0]: registered device vbi0
[32628.052232] saa7130[0]: registered device radio0
For testing we've used existing card (card=1 - Proteus Pro) with tuner 69. When everything will be working ok, my friend will try to add new card definition and generate the patch. Below you can find actual code modified by us:
saa7134-cards.c
struct saa7134_board saa7134_boards[] = {
...
[SAA7134_BOARD_PROTEUS_PRO] = {
/* /me */
.name = "Proteus Pro [philips reference design]",
.audio_clock = 0x00187de7,
.tuner_type = TUNER_TNF_5335MF,
.radio_type = UNSET,
.tuner_addr = ADDR_UNSET,
.radio_addr = ADDR_UNSET,
.gpiomask = 0x0d,
.inputs = {{
.name = name_comp1,
.vmux = 3,
.amux = LINE2,
.gpio = 0x08,
},{
.name = name_tv,
.vmux = 1,
.amux = LINE1,
.tv = 1,
},{
.name = name_tv_mono,
.vmux = 1,
.amux = LINE1,
.tv = 1,
},{
.name = name_svideo,
.vmux = 8,
.amux = LINE2,
.gpio = 0x08,
}},
.radio = {
.name = name_radio,
.amux = LINE1,
.gpio = 0x04,
},
.mute = {
.name = name_mute,
.amux = TV,
.gpio = 0x08,
},
},
int saa7134_board_init1(struct saa7134_dev *dev)
{
...
case SAA7134_BOARD_PROTEUS_PRO:
dev->has_remote = SAA7134_REMOTE_GPIO;
break;
saa7134-input.c
int saa7134_input_init1(struct saa7134_dev *dev)
{
case SAA7134_BOARD_PROTEUS_PRO:
ir_codes = &ir_codes_avermedia_table;
mask_keycode = 0x000000;
polling = 50; // ms
Regards,
Darek
On 08.01.2010 20:34, hermann pitton wrote:
> Hi,
>
> Am Sonntag, den 03.01.2010, 16:37 +0100 schrieb dz-tor:
>
>> Hi,
>>
>> I want to ask whether you are working on this 'issue'. I'm interested in
>> the subject, as I'm owner of this card and cannot get this stuff to work
>> - I've picture, no sound. Earlier you have written, that you can provide
>> patches for testing. If offer is still actual, I can test them.
>> Currently I'm using kernel 2.6.31, but if it's a problem I can switch to
>> 2.6.32.
>>
>> As I wrote earlier I have the same card - Winfast TV2100 with FM, tv
>> norm used in my country is PAL (I'm from Poland).
>>
>> Regards,
>> Darek
>>
> please have a look at the xtal/oscillator close to the saa713x chip.
>
> It can have two different values. See README.saa7134 in Documentation.
>
> I'll provide a patch with best guessing based on the regspy.exe results
> then, assuming all is connected to LINE2 and routed through the external
> mux chip as a start. If that fails, we try with LINE1 next.
>
> Cheers,
> Hermann
>
>
>
>>>
>>>> Hey guys,
>>>>
>>>> Let me start by thanking you both for all your help. Unfortunately,
>>>> there isn't much I can do with the data you provided - it's way too
>>>> technical for me. I'd be happy to do any tests and apply any patches,
>>>> but I would need some instructions - but only if you have time; I
>>>> really don't want to burden you with this.
>>>>
>>>> Thanks again,
>>>>
>>>> Pavle.
>>>>
>>>>
>>>>
>>>> ________________________________
>>>> From: hermann pitton<hermann-pitton@arcor.de>
>>>> To: Terry Wu<terrywu2009@gmail.com>
>>>> Cc: pavle.predic@yahoo.co.uk; video4linux-list@redhat.com
>>>> Sent: Sat, 28 November, 2009 4:09:28
>>>> Subject: Re: Re: Leadtek Winfast TV2100
>>>>
>>>> Hi Terry Wu,
>>>>
>>>> Am Donnerstag, den 26.11.2009, 10:33 +0800 schrieb Terry Wu:
>>>>
>>>>> Hi,
>>>>>
>>>>> Here are the subsystem IDs for different TV2100 models:
>>>>> Subsystem ID:0x6f30107d, TVF8533-BDF (PAL BG/DK)
>>>>> Subsystem ID:0x6f32107d, TVF5533-MF (NTSC)
>>>>> Subsystem ID:0x6f3a107d, TVF88T5-B/DFF (PAL BG/DK, FM)
>>>>>
>>>>> Terry
>>>>>
>>>> better is to become active on it.
>>>>
>>>> we can most likely help about how to match such tuners fine,
>>>> if any doubts left, but the best is to send just patches with having
>>>> such hardware to test on.
>>>>
>>>> Compared to the early tda9887 stuff on LeadTek devices, LeadTek was
>>>> pioneering and we have that in mind, it should be fairly easy for those.
>>>>
>>>> Let's know the other way round too, where you have still concerns doing
>>>> so.
>>>>
>>>> Cheers,
>>>> Hermann
>>>>
>>>>
>>>>> 2009/11/23 hermann pitton<hermann-pitton@arcor.de>:
>>>>>
>>>>>> Hi, thanks again!
>>>>>>
>>>>>> Am Montag, den 23.11.2009, 09:42 +0800 schrieb Terry Wu:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Please refer to the attached JPEG file for the GPIO
>>>>>>>
>>>> settings of
>>>>
>>>>>>> TV2100 with FM (PCB:B).
>>>>>>>
>>>>>>> Let me know if you need the information of TV2100 without FM
>>>>>>> (PCB:A, TVF8533-BDF).
>>>>>>>
>>>>>>> Terry Wu
>>>>>>>
>>>>>> On a first look, if we start to count gpios from zero, we tell
>>>>>>
>>>> the same.
>>>>
>>>>>> The TVF8533_BDF I would have to look up. It is four to five
>>>>>>
>>>> years back.
>>>>
>>>>>> If it uses that minor number TI chip without radio support, we
>>>>>>
>>>> treat it
>>>>
>>>>>> as tuner=69 too currently.
>>>>>>
>>>>>> For all such older can tuners, widely different about the globe,
>>>>>>
>>>> counts,
>>>>
>>>>>> that we don't have any way to detect them. So first working,
>>>>>>
>>>> either NTSC
>>>>
>>>>>> or PAL, sits in the pool position and others have to think twice.
>>>>>>
>>>>>> OEMs do code tuners into eeprom content, some do not at all,
>>>>>>
>>>> such doing
>>>>
>>>>>> it are in competition and don't follow the rules of the main chip
>>>>>> manufacturer, Philips/NXP in that case, and go their own ways.
>>>>>>
>>>>>> So tuner tables are unstable across manufacturers.
>>>>>>
>>>>>> We often can't help that much in such cases, but implementing
>>>>>>
>>>> their own
>>>>
>>>>>> tuner eeprom detection into the linux drivers is of course still
>>>>>> welcome. Hauppauge does it very successfully since years.
>>>>>>
>>>>>> We can't do much about it, if OEMs don't follow Philips or whom
>>>>>>
>>>> ever on
>>>>
>>>>>> such.
>>>>>>
>>>>>> Thanks,
>>>>>> Hermann
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 2009/11/23 Terry Wu<terrywu2009@gmail.com>:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> The TVF88T5-BDFF data sheet is attached.
>>>>>>>>
>>>>>>>> Terry Wu
>>>>>>>>
>>>>>>>> 11/17/2003 06:39 PM 72,010 TVF5531-MF.pdf
>>>>>>>> 03/12/2008 11:37 AM 555,285 TVF5533-MF-.pdf
>>>>>>>> 02/24/2004 02:19 PM 120,727 TVF5533-MF.pdf
>>>>>>>> 12/30/2003 06:59 PM 91,577 TVF5831-MFF.pdf
>>>>>>>> 09/26/2005 10:20 AM 156,853 TVF78P3-MFF.pdf
>>>>>>>> 11/17/2003 06:39 PM 67,947 TVF8531-BDF.pdf
>>>>>>>> 11/17/2003 06:39 PM 67,715 TVF8531-DIF.pdf
>>>>>>>> 03/12/2008 11:37 AM 509,340 TVF8533-BDF.pdf
>>>>>>>> 03/12/2008 11:37 AM 507,295 TVF8533-DIF.pdf
>>>>>>>> 12/30/2003 06:59 PM 87,921 TVF8831-BDFF.pdf
>>>>>>>> 12/30/2003 06:59 PM 87,624 TVF8831-DIFF.pdf
>>>>>>>> 09/26/2005 10:20 AM 176,525 TVF88P3-CFF.pdf
>>>>>>>> 03/24/2006 10:48 AM 460,941 TVF88T5-BDFF.pdf
>>>>>>>> 02/24/2004 02:19 PM 132,304 TVF9533-BDF.pdf
>>>>>>>> 02/24/2004 02:19 PM 120,940 TVF9533-DIF.pdf
>>>>>>>> 03/12/2008 11:37 AM 458,967 TVF99T5-BDFF.pdf
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>
>
>
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Leadtek Winfast TV2100
2010-01-08 19:34 ` hermann pitton
@ 2010-01-08 22:56 ` dz-tor
2010-01-09 14:46 ` Pavle Predic
0 siblings, 1 reply; 12+ messages in thread
From: dz-tor @ 2010-01-08 22:56 UTC (permalink / raw)
To: hermann pitton; +Cc: video4linux-list
Hi,
My friend helped me a little and we managed card to work, i.e. TV (only
mono, I suppose that stereo is not available for this card), s-video,
composite and radio works fine.
We've tried setting audio_clock to both values (32.11 MHz ->
.audio_clock=0x187de7 and 24.576MHz -> .audio_clock=0x200000) and both
works - for me it seems, that for 32.11 MHz sound is better (i.e. louder).
Now I have only one problem with ir. We succeeded to enable it, but
reading from it is bit weird - sometimes when I press the key, no event
is generated, sometimes 2 (key pressed/released) and sometimes more.
Have any clue what can cause that?
Output from dmesg when module is loaded:
[32627.844221] saa7130/34: v4l2 driver version 0.2.15 loaded
[32627.844294] saa7130[0]: found at 0000:01:09.0, rev: 1, irq: 17,
latency: 32, mmio: 0xe7001000
[32627.844303] saa7130[0]: subsystem: 107d:6f3a, board: Proteus Pro
[philips reference design] [card=1,insmod option]
[32627.844340] saa7130[0]: board init: gpio is 60a08
[32627.844351] saa7130[0]: gpio: mode=0x0000000 in=0x0060a0c
out=0x0000000 [pre-init]
[32627.844901] input: saa7134 IR (Proteus Pro [philip as
/devices/pci0000:00/0000:00:08.0/0000:01:09.0/input/input15
[32627.845064] IRQ 17/saa7130[0]: IRQF_DISABLED is not guaranteed on
shared IRQs
[32628.028017] saa7130[0]: i2c eeprom 00: 7d 10 3a 6f 54 20 1c 00 43 43
a9 1c 55 d2 b2 92
[32628.028029] saa7130[0]: i2c eeprom 10: 0c ff 82 0e ff 20 ff ff ff ff
ff ff ff ff ff ff
[32628.028038] saa7130[0]: i2c eeprom 20: 01 40 02 03 03 02 01 03 08 ff
00 8c ff ff ff ff
[32628.028047] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[32628.028056] saa7130[0]: i2c eeprom 40: 50 89 00 c2 00 00 02 30 02 ff
ff ff ff ff ff ff
[32628.028064] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[32628.028073] saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[32628.028082] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[32628.028091] saa7130[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[32628.028099] saa7130[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[32628.028108] saa7130[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[32628.028117] saa7130[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[32628.028126] saa7130[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[32628.028134] saa7130[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[32628.028143] saa7130[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[32628.028152] saa7130[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[32628.028163] i2c i2c-2: Invalid 7-bit address 0x7a
[32628.036120] tuner 2-0061: chip found @ 0xc2 (saa7130[0])
[32628.044037] tuner-simple 2-0061: creating new instance
[32628.044044] tuner-simple 2-0061: type set to 69 (Tena TNF 5335 and
similar models)
[32628.052058] saa7130[0]: gpio: mode=0x000000d in=0x0060a00
out=0x0000008 [mute]
[32628.052178] saa7130[0]: registered device video1 [v4l2]
[32628.052205] saa7130[0]: registered device vbi0
[32628.052232] saa7130[0]: registered device radio0
For testing we've used existing card (card=1 - Proteus Pro) with tuner
69. When everything will be working ok, my friend will try to add new
card definition and generate the patch. Below you can find actual code
modified by us:
saa7134-cards.c
struct saa7134_board saa7134_boards[] = {
...
[SAA7134_BOARD_PROTEUS_PRO] = {
/* /me */
.name = "Proteus Pro [philips reference design]",
.audio_clock = 0x00187de7,
.tuner_type = TUNER_TNF_5335MF,
.radio_type = UNSET,
.tuner_addr = ADDR_UNSET,
.radio_addr = ADDR_UNSET,
.gpiomask = 0x0d,
.inputs = {{
.name = name_comp1,
.vmux = 3,
.amux = LINE2,
.gpio = 0x08,
},{
.name = name_tv,
.vmux = 1,
.amux = LINE1,
.tv = 1,
},{
.name = name_tv_mono,
.vmux = 1,
.amux = LINE1,
.tv = 1,
},{
.name = name_svideo,
.vmux = 8,
.amux = LINE2,
.gpio = 0x08,
}},
.radio = {
.name = name_radio,
.amux = LINE1,
.gpio = 0x04,
},
.mute = {
.name = name_mute,
.amux = TV,
.gpio = 0x08,
},
},
int saa7134_board_init1(struct saa7134_dev *dev)
{
...
case SAA7134_BOARD_PROTEUS_PRO:
dev->has_remote = SAA7134_REMOTE_GPIO;
break;
saa7134-input.c
int saa7134_input_init1(struct saa7134_dev *dev)
{
case SAA7134_BOARD_PROTEUS_PRO:
ir_codes = &ir_codes_avermedia_table;
mask_keycode = 0x000000;
polling = 50; // ms
Regards,
Darek
On 08.01.2010 20:34, hermann pitton wrote:
> Hi,
>
> Am Sonntag, den 03.01.2010, 16:37 +0100 schrieb dz-tor:
>
>> Hi,
>>
>> I want to ask whether you are working on this 'issue'. I'm interested in
>> the subject, as I'm owner of this card and cannot get this stuff to work
>> - I've picture, no sound. Earlier you have written, that you can provide
>> patches for testing. If offer is still actual, I can test them.
>> Currently I'm using kernel 2.6.31, but if it's a problem I can switch to
>> 2.6.32.
>>
>> As I wrote earlier I have the same card - Winfast TV2100 with FM, tv
>> norm used in my country is PAL (I'm from Poland).
>>
>> Regards,
>> Darek
>>
> please have a look at the xtal/oscillator close to the saa713x chip.
>
> It can have two different values. See README.saa7134 in Documentation.
>
> I'll provide a patch with best guessing based on the regspy.exe results
> then, assuming all is connected to LINE2 and routed through the external
> mux chip as a start. If that fails, we try with LINE1 next.
>
> Cheers,
> Hermann
>
>
>
>>>
>>>> Hey guys,
>>>>
>>>> Let me start by thanking you both for all your help. Unfortunately,
>>>> there isn't much I can do with the data you provided - it's way too
>>>> technical for me. I'd be happy to do any tests and apply any patches,
>>>> but I would need some instructions - but only if you have time; I
>>>> really don't want to burden you with this.
>>>>
>>>> Thanks again,
>>>>
>>>> Pavle.
>>>>
>>>>
>>>>
>>>> ________________________________
>>>> From: hermann pitton<hermann-pitton@arcor.de>
>>>> To: Terry Wu<terrywu2009@gmail.com>
>>>> Cc: pavle.predic@yahoo.co.uk; video4linux-list@redhat.com
>>>> Sent: Sat, 28 November, 2009 4:09:28
>>>> Subject: Re: Re: Leadtek Winfast TV2100
>>>>
>>>> Hi Terry Wu,
>>>>
>>>> Am Donnerstag, den 26.11.2009, 10:33 +0800 schrieb Terry Wu:
>>>>
>>>>> Hi,
>>>>>
>>>>> Here are the subsystem IDs for different TV2100 models:
>>>>> Subsystem ID:0x6f30107d, TVF8533-BDF (PAL BG/DK)
>>>>> Subsystem ID:0x6f32107d, TVF5533-MF (NTSC)
>>>>> Subsystem ID:0x6f3a107d, TVF88T5-B/DFF (PAL BG/DK, FM)
>>>>>
>>>>> Terry
>>>>>
>>>> better is to become active on it.
>>>>
>>>> we can most likely help about how to match such tuners fine,
>>>> if any doubts left, but the best is to send just patches with having
>>>> such hardware to test on.
>>>>
>>>> Compared to the early tda9887 stuff on LeadTek devices, LeadTek was
>>>> pioneering and we have that in mind, it should be fairly easy for those.
>>>>
>>>> Let's know the other way round too, where you have still concerns doing
>>>> so.
>>>>
>>>> Cheers,
>>>> Hermann
>>>>
>>>>
>>>>> 2009/11/23 hermann pitton<hermann-pitton@arcor.de>:
>>>>>
>>>>>> Hi, thanks again!
>>>>>>
>>>>>> Am Montag, den 23.11.2009, 09:42 +0800 schrieb Terry Wu:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Please refer to the attached JPEG file for the GPIO
>>>>>>>
>>>> settings of
>>>>
>>>>>>> TV2100 with FM (PCB:B).
>>>>>>>
>>>>>>> Let me know if you need the information of TV2100 without FM
>>>>>>> (PCB:A, TVF8533-BDF).
>>>>>>>
>>>>>>> Terry Wu
>>>>>>>
>>>>>> On a first look, if we start to count gpios from zero, we tell
>>>>>>
>>>> the same.
>>>>
>>>>>> The TVF8533_BDF I would have to look up. It is four to five
>>>>>>
>>>> years back.
>>>>
>>>>>> If it uses that minor number TI chip without radio support, we
>>>>>>
>>>> treat it
>>>>
>>>>>> as tuner=69 too currently.
>>>>>>
>>>>>> For all such older can tuners, widely different about the globe,
>>>>>>
>>>> counts,
>>>>
>>>>>> that we don't have any way to detect them. So first working,
>>>>>>
>>>> either NTSC
>>>>
>>>>>> or PAL, sits in the pool position and others have to think twice.
>>>>>>
>>>>>> OEMs do code tuners into eeprom content, some do not at all,
>>>>>>
>>>> such doing
>>>>
>>>>>> it are in competition and don't follow the rules of the main chip
>>>>>> manufacturer, Philips/NXP in that case, and go their own ways.
>>>>>>
>>>>>> So tuner tables are unstable across manufacturers.
>>>>>>
>>>>>> We often can't help that much in such cases, but implementing
>>>>>>
>>>> their own
>>>>
>>>>>> tuner eeprom detection into the linux drivers is of course still
>>>>>> welcome. Hauppauge does it very successfully since years.
>>>>>>
>>>>>> We can't do much about it, if OEMs don't follow Philips or whom
>>>>>>
>>>> ever on
>>>>
>>>>>> such.
>>>>>>
>>>>>> Thanks,
>>>>>> Hermann
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 2009/11/23 Terry Wu<terrywu2009@gmail.com>:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> The TVF88T5-BDFF data sheet is attached.
>>>>>>>>
>>>>>>>> Terry Wu
>>>>>>>>
>>>>>>>> 11/17/2003 06:39 PM 72,010 TVF5531-MF.pdf
>>>>>>>> 03/12/2008 11:37 AM 555,285 TVF5533-MF-.pdf
>>>>>>>> 02/24/2004 02:19 PM 120,727 TVF5533-MF.pdf
>>>>>>>> 12/30/2003 06:59 PM 91,577 TVF5831-MFF.pdf
>>>>>>>> 09/26/2005 10:20 AM 156,853 TVF78P3-MFF.pdf
>>>>>>>> 11/17/2003 06:39 PM 67,947 TVF8531-BDF.pdf
>>>>>>>> 11/17/2003 06:39 PM 67,715 TVF8531-DIF.pdf
>>>>>>>> 03/12/2008 11:37 AM 509,340 TVF8533-BDF.pdf
>>>>>>>> 03/12/2008 11:37 AM 507,295 TVF8533-DIF.pdf
>>>>>>>> 12/30/2003 06:59 PM 87,921 TVF8831-BDFF.pdf
>>>>>>>> 12/30/2003 06:59 PM 87,624 TVF8831-DIFF.pdf
>>>>>>>> 09/26/2005 10:20 AM 176,525 TVF88P3-CFF.pdf
>>>>>>>> 03/24/2006 10:48 AM 460,941 TVF88T5-BDFF.pdf
>>>>>>>> 02/24/2004 02:19 PM 132,304 TVF9533-BDF.pdf
>>>>>>>> 02/24/2004 02:19 PM 120,940 TVF9533-DIF.pdf
>>>>>>>> 03/12/2008 11:37 AM 458,967 TVF99T5-BDFF.pdf
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>
>
>
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2010-01-10 21:26 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-11-08 17:11 Leadtek Winfast TV2100 Pavle Predic
2009-11-08 22:35 ` hermann pitton
2009-11-20 14:11 ` Pavle Predic
2009-11-21 0:21 ` hermann pitton
2009-11-21 9:07 ` Terry Wu
2009-11-21 19:53 ` Pavle Predic
2010-01-03 15:37 dz-tor
2010-01-08 19:34 ` hermann pitton
2010-01-08 22:56 ` dz-tor
2010-01-09 14:46 ` Pavle Predic
2010-01-09 16:23 ` dz-tor
2010-01-09 17:14 ` hermann pitton
2010-01-09 22:48 ` hermann pitton
2010-01-10 21:26 ` dz-tor
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.