Hi, Am Donnerstag, den 25.11.2010, 00:56 -0500 schrieb Hooman B.: > Thanks, > > I see the drivers for both TDA18271HDC2 and TDA8290 loaded. > I thought TDA18271HDC2 was the digital channel decoder, isn't it? Is > the "digital channel decoder" different from the digital tuner?? > Should be looking for a different chip?
they are detected by chip IDs. The tda8290 is the IF demodulator for global analog TV. In case of the saa7135 it is an extra chip on the PCB, which most often can also control the tuner over an i2c gate. The tda18271hdc2 is a global hybrid tuner for analog and digital terrestrial TV. It can also provide a FM radio IF. Further processing and stereo separation for that is done on capable bridges like saa7133/35/31e, not on the tda 8290. Yes, for any terrestrial digital TV you need an extra channel decoder and all known details about it. http://linuxtv.org/wiki/index.php/Category:ATSC_PCI_Cards In case of terrestrial ATSC, it must be able to deal with 8VSB modulation. IIRC, on the saa713x we have that tuner only in combination with the tda10048 and DVB-T for now, but other combinations seem to be already around. Hermann > Based on these to chips, I added my card in saa7134_tda8290_callback > to call saa7134_tda8290_18271_callback and here is the output of my > dmesg: > [ 828.879454] dvb_init() allocating 1 frontend > [ 829.180234] nxt200x: nxt200x_readbytes: i2c read error (addr 0x0a, err == > -5) > [ 829.180244] Unknown/Unsupported NXT chip: 00 00 00 00 00 > [ 829.180542] saa7133[0]/dvb: frontend initialization failed > > Hooman > > On Wed, Nov 24, 2010 at 7:21 PM, hermann pitton <hermann-pit...@arcor.de> > wrote: > > > > Hi, > > > > Am Dienstag, den 23.11.2010, 17:34 -0500 schrieb Hooman B.: > >> Hello! > >> I've been trying to get the ATSC tuner in my KWorld PC120-U PCI Hybrid > >> ATSC (17de:a134) > >> to work with the latest v4l drivers from source (in Ubuntu). > >> > >> Right now, everything [capture, analog, radio, even IR] works - except > >> the ATSC tuner (there is no > >> front-end device). But that's the one thing I need working :-( > > > > OK. > > > >> Here's the output of lspci -nnvv > >> ================================================================ > >> 03:01.0 Multimedia controller [0480]: Philips Semiconductors > >> SAA7131/SAA7133/SAA7135 Video Broadcast Decoder [1131:7133] (rev d1) > >> Subsystem: KWorld Computer Co. Ltd. Device [17de:a134] > >> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > >> Stepping- SERR- FastB2B- DisINTx- > >> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > >> <TAbort- <MAbort- >SERR- <PERR- INTx- > >> Latency: 255 (63750ns min, 63750ns max) > >> Interrupt: pin A routed to IRQ 16 > >> Region 0: Memory at fdaff000 (32-bit, non-prefetchable) [size=2K] > >> Capabilities: <access denied> > >> Kernel driver in use: saa7134 > >> Kernel modules: saa7134 > >> ================================================================ > >> > >> This is the most similar card that I forced in saa7134-cards.c: > >> ================================================================ > >> .vendor = PCI_VENDOR_ID_PHILIPS, > >> .device = PCI_DEVICE_ID_PHILIPS_SAA7133, > >> .subvendor = 0x17de, > >> .subdevice = 0xa134, > >> .driver_data = SAA7134_BOARD_MSI_TVATANYWHERE_PLUS, > >> ================================================================ > >> > >> The chips are : SAA7135HL/203 and TDA18271HDC2 > >> > > > > Both variants of the MSI t...@nywhere Plus do not have any support for > > digital TV. > > > > You need to find out the type of digital channel decoder on your board > > at first. > > > > Then you check saa7134-dvb.c, if it is already supported on other cards. > > > > You have to investigate the details of how the channel decoder is > > employed, but with some luck can try with already supported cards. > > > > If i2c traffic locks up and chips disappear from the bus, a cold boot > > might be necessary to continue with testing. > > > > Cheers, > > Hermann > > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
