Zolid Hybrid TV Tuner
Usage:
- Once you have logged in, simply click the edit tab at the top of this page
- Then from within the editing box at the bottom of the editing page, copy the entire contents of this article
- From within the editing box at the bottom of the new device page you are creating, paste the copied content from the "new device copy and paste template"
- Proceed to fill in the information relevant for the device and delete the italic directional comment sections provided by the template (as well as this notice)
First, if possible, we would like a good overall image of what the device looks like (Note: do NOT use proprietary images unless you have obtained permission to do so). Next, provide a brief summary of what the device is and by whom it is provided (include wiki links to the card type and the vendor -- and, ideally, after you have finished editing this page, you should add links from those pages back to this one). The last introductory piece of information is the all important indication of whether or not the device is supported under Linux. Here's an example:
The Hybrid TV Tuner is not supported by Linux.
Note: The page contents menu will automagically build itself, so you need not worry about it
Overview/Features
Discuss the features and facets of the device here. For example:
- PCI Interface
- Hybrid tuner, both DVB and Analog TV are supported
Components Used
List the hardware ICs and modules used by the device here. For example:
- NXP TDA18271 (tuner)
- NXP TDA10048 (demodulator)
- NXP/Philips SAA7131 (A/V decoder and PCI Interface)
Other Images
Use the included code to insert other images if necessary. Add as many high resolution pictures as you can i.e the card, the original box, the remote and, when uploading the files to the wiki, give them detailed specific names. Note: only use images taken by yourself or those 3rd party images for which you have received express written consent (such as from a vendor) that permits their usage. For example:
Identification
Provide here, for PCI/PCIe devices, the relevant output of lspci -vnn
or, in the case of USB devices, lsusb -v
. We're particularly interested in the subsystem ID's. To make a code block simply make the first character of each line a space. For example:
- lspci -vvvnnxxx
04:09.0 Multimedia controller [0480]: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder [1131:7133] (rev d1) Subsystem: Philips Semiconductors Device [1131:2004] 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: 32 (21000ns min, 8000ns max) Interrupt: pin A routed to IRQ 17 Region 0: Memory at fdcfe000 (32-bit, non-prefetchable) [size=2K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Kernel driver in use: saa7134 Kernel modules: saa7134 00: 31 11 33 71 06 00 90 02 d1 00 80 04 00 20 00 00 10: 00 e0 cf fd 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 31 11 04 20 30: 00 00 00 00 40 00 00 00 00 00 00 00 ff 01 54 20 40: 01 00 02 06 00 20 00 1c 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Making it Work
Is it supported under Linux? Are there experimental drivers? Does it partially work or identify as another card? (if yes, add this information below) It is not supported by Linux. The subsystem has two matches, both reference boards: Philips TOUGH DVB-T reference design and Philips EUROPA V3 reference design. This can be found in CARDLIST.saa7134.
When loading the saa7134 module with the card parameter 156 (Hauppauge WinTV-HVR1110r3 DVB-T/Hybrid) with firmware installed (see below), the card seems to work, but fails when scanning DVB channels.
Firmware
Is there any firmware specific information for this device? if so, list it here. If your device doesn't require a firmware, simply mention that this is the case. The card needs firmware for the TDA10048.
Drivers
Provide the details of where the drivers and patches and necessary tools are available. The card uses the built-in V4L drivers.
Sample Kernel Output
Provide the relevant portion of dmesg here. For example:
# dmesg
2009-05-31 20:42:51 sander-desktop kernel [ 4169.257239] saa7134 ALSA driver for DMA sound unloaded 2009-05-31 20:42:59 sander-desktop kernel [ 4177.629232] saa7130/34: v4l2 driver version 0.2.15 loaded 2009-05-31 20:42:59 sander-desktop kernel [ 4177.629291] saa7133[0]: found at 0000:04:09.0, rev: 209, irq: 17, latency: 32, mmio: 0xfdcfe000 2009-05-31 20:42:59 sander-desktop kernel [ 4177.629297] saa7133[0]: subsystem: 1131:2004, board: UNKNOWN/GENERIC [card=0,autodetected] 2009-05-31 20:42:59 sander-desktop kernel [ 4177.629548] saa7133[0]: board init: gpio is 4400100 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792034] saa7133[0]: i2c eeprom 00: 31 11 04 20 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792044] saa7133[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792051] saa7133[0]: i2c eeprom 20: 01 40 01 02 03 01 01 03 08 ff 00 b2 ff ff ff ff 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792057] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792064] saa7133[0]: i2c eeprom 40: ff 35 00 c0 96 10 03 32 21 05 ff ff ff ff ff ff 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792070] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792076] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792083] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792089] saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792095] saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792102] saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792108] saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792114] saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792120] saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792127] saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792133] saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792610] saa7133[0]: registered device video0 [v4l2] 2009-05-31 20:42:59 sander-desktop kernel [ 4177.792631] saa7133[0]: registered device vbi0 2009-05-31 20:42:59 sander-desktop kernel [ 4177.800153] saa7134 ALSA driver for DMA sound loaded 2009-05-31 20:42:59 sander-desktop kernel [ 4177.800183] saa7133[0]/alsa: saa7133[0] at 0xfdcfe000 irq 17 registered as card -2
Remote Control Support
Discuss support for the remote control here. I haven't tested this yet.
External Links
Provide a link to the vendor's product page here along with any other external link to information that is generally helpful in relation to the device. For example:
The vender Zolid doesn't have a website.
Finally, add anything else that you think might be relevant under an appropriate heading.
Very last thing is add a catergory. (Remove the nowiki tags). For example
[[Category:DVB-T PCI Devices]]