Hi! Am Dienstag, den 10.10.2006, 23:52 +0300 schrieb v+dvb@xxxxxx: > On Tue, Oct 10, 2006 at 05:55:42PM +0200, you [hermann pitton] wrote: > > > > The one closer to the motherboard is marked CATV-IN on mine. (1043:4862) > > > > The upper one is marked RF/FM-IN here. > > +--------------+ > 1 =| | > 2 =| | > (3)-| | > +----########--+ > ##PCI### > > I was looking at the manual. It talks about > 1 "FM radio / Digital TV port" > 2 "Analog TV antenna / Cable TV port" > ( 3 "Audio-video port" ) The manual is about the windows driver. (you also can read that you have to remove all other TV cards and their drivers ... ;) Technically on mine only the FM radio input is fix, since this one is routed through an 5.5MHz ceramic filter. > But I guess the exact terminology is not important - what I was trying to > find out was if DVB can use both antenna inputs - and you already answered > that below. Thanks. > > > > If I connect the stronger signal cable to the analog tv input and do not > > > invoke the fm tuning trick, dvb does not work. > > > > With the patch in mercurial master now this is correct. > > And this is different from the > http://www.spinics.net/lists/vfl/msg28220.html patch, right? No. It is exactly about this one. But maybe you should try the recent, since Hartmut had also audio fixes and introduced signal and stereo detection for radio. As known, tuning is still quite slow. > Ok, I'll try that. > > > It won't work anymore on the analog/CATV at all. > > It would have been nice to be able to use one good quality antenna cable fo both > analog tv and dvb (instead of having a splitter to divide the cable in two - > even if that'd mean fm tuner get lousy signal, But I guess one can't have > all at once. Yes, that is another condition where the previous was better, but the tuner is much better on cable-tv than on FreeToAir analog broacast. Now the preference is more for different cable-tv and DVB-T antennas and it follows the m$ behavior to do multi boot OSs users a favour ... BTW, "patch" has a -R option. > > That's the confusing part for me on your card. For what I found on mine > > using radio once does exactly the same as the gpio21 switch now in > > asus_p7131_dual_tuner_init in saa7134-dvb.c. Every time a dvb app uses > > the tuner the antenna switch happens. Also adding a .mute section > > with .gpio 0x0200000 did the trick from the analog side previously. > > Is there anything I can do to further debug this? To be honest, as you described the current symptoms, DVB-T not anymore on the analog input, but still the radio switch is needed to get it to the RF/FM-IN, isn't covered by any clear ideas here yet. (timing?) If I understand your problem correctly, using a dvb app makes the analog input already unusable for DVB-T, but only when triggering the switch a second time, in this case by using radio once, it finally comes to the RF/FM-IN ? (Starting a dvb-app does it the second after radio) To start and close for example kaffeine twice should then have the same effect, as using radio at first. (indicator is firmware loading and setting up plls twice in dmesg) But there is one difference. If the dvb app exits asus_p7131_dual_tuner_sleep switches _back_ to the analog input with saa_clearl(SAA7134_GPIO_GPSTATUS0 >> 2, 0x0200000); Maybe /* comment */ that line to get more identical behaviour to using radio at first. Remember, the layout of your card revision is very different to mine. (also no firmware eeprom and what is under the tuner shielding is not reported) > > Previously both were possible, the one marked here RF/FM-IN only after > > using radio first. Now with the patch in mercurial master and 2.6.19 > > DVB-T on mine is always and only at the RF/FM-IN. > > Ok, thanks for the clarification. > > > Also in your case note the new function name introduced with the > > Pinnacle 310i patch to get the firmware. > > Ok. > > > static int philips_tda1004x_request_firmware(struct dvb_frontend *fe, > > const struct firmware **fw, char *name) > > { > > struct saa7134_dev *dev = fe->dvb->priv; > > return request_firmware(fw, name, &dev->pci->dev); > > } > > Thanks for your reply. > > I don't suppose you have any idea on the analog tv "dsp access error" issue? Hartmut mentioned that the NICAM decoder is quite sensitive for video glitches. Try to force MONO for a while? Else always enable audio_debug=1 on the saa7134 and also force the exact PAL sub-norm. Wrongly detecting PAL-I was/is also a known issue in Scandinavia. Don't forget to apply the tiny patch from yesterday. DVB-T won't work without it. Cheers, Hermann _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
