ATSC PCIe cards

On this page you will find information regarding ATSC PCIe and Mini PCIe devices.

Please be aware that:

• 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:
    • Linux-Media Mailing List (LMML) archives (via vger or .... )
    • or from the older mailing lists (now largely deprecated in favour of the LMML):
      • dvb mailing list archives (via spinics or MARC ... )
      • v4l mailing list archives (via .... )
  • 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!

ATSC PCIe cards

Supported

The following table lists the confirmed working ATSC PCIe cards and provides a brief summary of their features and components:

Vendor and model	Added to kernel	Frontend	Bridge interface	8VSB	QAM	NTSC	Low profile
DViCO FusionHDTV5 Express	2.6.27	LG Innotek TDVS-H062F (NIM) Infineon TUA6034 (tuner) Philips TDA9887 (analog IF demodulator) LG DT3303 (digital demodulator)	Conexant CX23885	✔ Yes	✔ Yes	✘ No	✔ Yes
DViCO FusionHDTV7 Dual Express	2.6.27		Conexant CX23885	✔ Yes	✔ Yes	✘ No	✔ Yes
Hauppauge WinTV-HVR-1250	2.6.27		Conexant CX23885	✔ Yes	✔ Yes	✘ No	✔ Yes
Hauppauge WinTV-HVR-1255				✔ Yes	✔ Yes	✘ No	✔ Yes
Hauppauge WinTV-HVR-1270				✔ Yes	✔ Yes	✘ No	? Unknown
Hauppauge WinTV-HVR-1275				✔ Yes	✔ Yes	✘ No	? Unknown
Hauppauge WinTV-HVR-1800	2.6.25			✔ Yes	✔ Yes	~ Partial1	? Unknown
Hauppauge WinTV-HVR-2250	2.6.37		NXP SAA7164	✔ Yes	✔ Yes	✔ Yes	✔ Yes

• Note 1: The NTSC tuner is unsupported by MythTV.

Unsupported

If you own one or more devices from the following list and you want to help with support development, please contact the Linux-Media Mailing List (LMML). Note that if your device is similar to or contains components for which driver development is currently being undertaken, then it is possible that you will pique the developers' interest and can obtain some assistance that, possibly, leads to full support for your device.

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.

• ASUS My Cinema-EHD3-100/NAQ/FM/AV/MCE RC
• ASUS My Cinema-ES3-100/NAQ/FM/AV/RC
• ASUS My Cinema-PE9400Combo
• ATI/AMD TV Wonder 650 Combo PCI Express
  • MSI Theater 650PRO PCI-Express
  • VisionTek TV Wonder 650 Combo PCIe
• ATI/AMD TV Wonder 600 PCI Express
  • VisionTek TV Wonder HD 600
• AVerMedia AVerTVHD Duet (A188)
• AVerMedia AVerTV Bravo Hybrid PCI-E (H788 and H788D)
• AVerMedia AVerTV Hybrid Speedy PCI-E (H788R)
• AVerMedia AVerTV Hybrid Volar MAX (H826)
• AVerMedia AVerTV Combo PCIe (M780)
• AVerMedia PCIe Combo (OEM) (M791)
• AVerMedia PCIe Combo (OEM) (M792)
• DViCO FusionHDTV7 RT Express
• VBox Cat's Eye 164e
• ViXS PureTV-U model no. ?? reference design:
  • An OEM card, by ASUS, based upon the ViXS reference design can be found in some Media PC systems from big name vendors (like HP etc.)
  • Samsung Combo-210E
  • Vista View Saber DA-1N1-E

ATSC Mini PCIe cards

Supported

• Sundtek MediaTV Pro ATSC (MiniPCIe), analog TV, FM radio, ATSC, Clear QAM Hybrid Mini PCIe device, supported by the manufacturer

Unsupported

• AVerMedia A301, DVB-T works with AVerTV Hybrid+FM Volar A828 driver
• AVerMedia A312 (ATSC)