DVB-T PCI cards: Difference between revisions
(use templates regarding support, remove opinion comment) |
m (add note about seeing particular device article) |
||
Line 4: | Line 4: | ||
<br> |
<br> |
||
==Supported DVB-T PCI Cards== |
==Supported DVB-T PCI Cards== |
||
The following table lists the confirmed working DVB-T PCI cards and provides a brief summary of their features and components. |
The following table lists the confirmed working DVB-T PCI cards and provides a brief summary of their features and components. If you need more technical information on a device, have a look at its specific wiki article. |
||
<br> |
|||
<br> |
<br> |
||
{| border=1 cellpadding=2 cellspacing=0 valign="top" |
{| border=1 cellpadding=2 cellspacing=0 valign="top" |
Revision as of 16:10, 21 August 2007
On this page you will find information regarding DVB-T PCI cards.
- The information contained here is likely non-exhaustive and, despite best efforts to do otherwise, may contain errors. (Please help to keep these lists up-to-date so that they are useful for everyone!)
- If your device is not listed, try:
- searching the existing mailing list archives:
- searching for information with Google or other internet search engine
- by posting a question about the device directly to the LMML (but please do conduct a search first, as it may already have been discussed!)
- Note: when it comes to support, it is generally a good idea to try the current V4L-DVB sources because some device drivers can be very new and thus may have not made their way into the mainstream kernel.
- In any regard, in respect to the above listed suggestions, you may find it to be the case that your device is actually already supported or that experimental support is available.
- Because the component constitution on many devices are often similar or identical, there may be devices that are unlisted but may actually work with the existing driver framework for previously supported devices. In such a case, your non-listed but working device will likely be reported in your system messages as being one of those previously supported devices. If you encounter such an occurrence, please do report your success on the LMML so that proper detection/identification of your device can be added within the drivers.
- Lastly, it bears worth repeating the request: Please help to keep these lists up-to-date so that they are useful for everyone!
Supported DVB-T PCI Cards
The following table lists the confirmed working DVB-T PCI cards and provides a brief summary of their features and components. If you need more technical information on a device, have a look at its specific wiki article.
Manufacturer Model number |
Supports | Tuner / Chips | Connectors | Notes | Pictures |
Asus DVB-T+analog[1] |
DVB, VDR?? (VDR not tried) |
|
|
|
[2] |
AVerMedia AVerMedia AVerTV DVB-T (A761) [3] |
DVB, VDR [4] |
|
|
[5] | |
AVerMedia AVerMedia AVerTV DVB-T 771 (A771) [7]
|
DVB, VDR possible [8] [9], [10] [11]
|
|
|
[12][13] | |
AVerMedia AVerMedia AVerTV DVB-T 777 (A16AR) |
DVB, VDR ab 2.6.17-rc1 |
|
|
||
AVerMedia [15]
|
Not yet |
|
|
[16] | |
AVerMedia |
Yes
|
|
|
|
|
AVerMedia AVerMedia_AVerTV_DVB-T_Super_007 [18]
|
Yes (with patch)
|
|
|
|
|
ChainTech DTT 1000 PCI [19] |
DVB, VDR (lt. c't 11/2004) |
|
|
[20] | |
Club 3D ZAP-TV2202 |
DVB, Analogue | Philips SAA7131 |
|
|
|
Compro VideoMate DVB-T200 PCI |
DVB kernel 2.6.17 | Philips SAA7134 |
|
(to get the irda working correctly you may find this mail useful [23] )
|
|
GDI Black Gold [25] |
S-Video support works (Small patch which is now in CVS). DVB doesn't work. | Conexant CX23881-19/Front End CX22702/Tuner Philips TU1216/TDA10046 demodulator |
|
Like this, but slightly longer with a heat sink. | |
Hama DVB-T PCI-Karte [26]
|
DVB, VDR possible [27] (lt. c't 11/2004) |
Fusion 878A |
|
|
[28] |
Hauppauge
Old WinTV-NOVA-T PCI |
DVB, VDR | Philips |
|
|
|
Hauppauge New WinTV-NOVA-T PCI |
Works with patches from [31] or >= kernel 2.6.12 | Conexant cx2388x |
|
|
[32] |
Hauppauge WinTV-NOVA-T-500 |
works with v4l-dvb hg from 2006-09-20 [34] or kernel >= 2.6.19 | DiBcom DiB0700 |
|
|
|
Hauppauge new WinTV-HVR-1300 (since 07/2005) [35]
(HVR-1100 is similiar to HVR-1300, but without MPEG hardware encoder)
|
Digital & Analogue working in repository [36]. Encoder support being worked on. | Conexant cx2388x |
|
|
[37] |
Hauppauge new WinTV-HVR-1110 (since 09/2006) [38]
(HVR-1110 is similiar to HVR-1100, but with a triangular shape and a Philips TDA10046 chipset)
|
DVB-T and Analog | Philips SAA7134 |
|
|
|
KNC1 KNC1 TV-Station DVB-T [40] |
DVB, ? | Philips SAA7146 |
|
||
KWorld V-Stream Xpert DVB-T PCI [41] |
DVB, VDR possible [42] New card:[43]
Full support :[[44]] |
Conexant CX23883 |
|
|
[45] |
KWorld |
DVB, analogue | Philips SAA7134 |
|
|
|
KWorld |
DVB, analogue |
|
|
||
Leadtek |
DVB | Conexant based system see LR6650 |
|
|
[49] |
LifeView |
DVB-T only | Philips SAA7134 |
|
|
|
LifeView |
DVB-T and Analog | Philips SAA7135 |
|
|
|
LifeView |
DVB-T, Satellite and Analog | Philips SAA7134 |
|
|
|
LifeView |
DVB-T and Analog |
|
|
| |
LifeView |
DVB-T and Analog HW encoder |
|
|
|
|
Lorenzen |
DVB, VDR | Philips |
|
|
(Old Design): [55] |
Medion CTX953 | DVB-T, analog |
|
|
|
|
Nebula DigiTV PCI [57] |
DVB,VDR NXT6000 demod supported by recent kernels, mt352 demod will be supported by kernels >= 2.6.14-rc1. |
Demod Chip Old board: |
|
|
[58] |
NPG Real DVB-T [59] |
Doesn't seem to work. | Conexant CX23880-19 CX22702-25 |
|
|
|
Pinnacle PCTV DVB-T PCI 250i [60] |
No support yet |
|
|
[61]
| |
Pinnacle PCTV MediaCenter 300i [62] |
DVB works with patches from [63], but see this thread [64] for recent regression post 2.6.12
Everyone seems happy using Hartmut's Patch [65] with more recent kernels. Check the associated thread for more info... July 2006: Worked out of the box with recent kernel 2.6.17 Debian unstable! |
Philips SAA7134 |
|
|
[66][67]
|
Pinnacle PCTV MediaCenter 310i [68] |
DVB works with Debian AMD64 testing
Worked out of the box with recent kernel 2.6.20 |
Philips SAA7134 |
|
| |
Pinnacle PCTV Dual DVB-T Pro PCI / 2000i [69]
|
Not working so far (Oct.2006). Shows up as three unknown PCI devices ID 0040, 0041, 0042 with subsystems 0044. Manufacturer Pinnacle Systems Inc. detected correctly. | 2x Zarlink ZL10353 2x Microtune MT2060 |
|
|
[70] |
Satelco Satelco PCI [71] |
? | ? |
|
. | [72] |
TechniSat AirStar 2 PCI / Air2PC DVB [73] |
DVB, VDR possible[74][75] |
? |
|
|
[76] |
TechnoTrend TT-DVB-T 1200
|
DVB, VDR |
? |
|
|
. |
TechnoTrend TT-DVB-T 1500
|
DVB, VDR |
Philips SAA7146
Tuner: Philips TDA10046H |
|
|
. |
TechnoTrend | DVB, VDR | Philips |
|
||
TechnoTrend TT-PCline Budget3 TA1000
|
? | ? |
|
|
[79] |
TerraTec Cinergy 1200 DVB-T [80] |
DVB, VDR | Philips SAA7146 Tuner: Philips TDA10046H |
|
||
TerraTec Cinergy 1400 DVB-T [81] |
DVB, VDR | Tuner: Thomson TT 7579 Chipset Connexant CX88XX |
|
|
[[82]]
|
TerraTec TerraTec Cinergy HT PCI [83] |
DVB-T, Analog TV, Radio | Tuner: Thomson TT 7579 Chipset SAA7134 |
|
|
|
TwinHan VisionDTV Ter PCI [84]
|
DVB, VDR possible [85] (lt. c't 11/2004) |
Fusion 878A |
|
|
[86]
|
TwinHan DTV Ter PCI (A&D) [87]
|
Works ok with FC4 latest 2.6 kernel and cx88xx option card=42.
|
|
Hybrid (DVB-T & analog TV)
|
| |
TwinHan 3506 Hybrid
|
Works ok with FC7 latest 2.6 kernel and saa7134 module, card=109.
|
2 Chips:
|
|
Hybrid (DVB-T & analog TV)
|
Currently Unsupported DVB-T PCI cards
However, please note that inquiries to the mailing list:
- Should NOT be treated as an order drop-off queue. You're soliciting help from volunteer developers who work on V4L-DVB matters in their spare time, and such work can be non-trivial (i.e. requiring even thousands of hours work). So being demanding is one sure route to being ignored. (Honestly, this point really shouldn't even need to be written, but you'd be surprised at the number of irrational individuals who write into the mailing list demanding this or that).
- May pass without garnering a response—a distinct byproduct of the fact that there are a limited number of developers, whom might be able to help, that are associated with the project. Often times, even if they wished to help, their energies are entirely tied up with other projects. In such cases, the best path might be to try to spearhead the driver development for your device yourself, or hire someone who can.