Difference between revisions of "DVB-T PCIe Cards"

From LinuxTVWiki
Jump to: navigation, search
(Unsupported DVB-T PCIe Cards:)
(Unsupported DVB-T PCIe Cards:)
(15 intermediate revisions by 4 users not shown)
Line 11: Line 11:
 
* [[Hauppauge]] [[Hauppauge WinTV-HVR-1200|WinTV-HVR-1200]] <sup id="fn_1_back">[[#fn_1|1]]</sup>
 
* [[Hauppauge]] [[Hauppauge WinTV-HVR-1200|WinTV-HVR-1200]] <sup id="fn_1_back">[[#fn_1|1]]</sup>
 
* [[Hauppauge]] [[Hauppauge WinTV-HVR-1700|WinTV-HVR-1700]] <sup id="fn_1_back">[[#fn_1|1,]]</sup> <sup id="fn_2_back">[[#fn_2|2]]</sup>  
 
* [[Hauppauge]] [[Hauppauge WinTV-HVR-1700|WinTV-HVR-1700]] <sup id="fn_1_back">[[#fn_1|1,]]</sup> <sup id="fn_2_back">[[#fn_2|2]]</sup>  
* [[TerraTec]] [[TerraTec Cinergy 2400i DVB-T|Cinergy 2400i DVB-T]]: Works with a patch for the [[NGene_devices|NGene]]-driver.
+
* [[TerraTec]] [[TerraTec Cinergy 2400i DVB-T|Cinergy 2400i DVB-T]]
 
* [[Hauppauge]] [[Hauppauge_WinTV-HVR-2200|WinTV-HVR-2200]] <sup id="fn_1_back">[[#fn_1|1]]</sup> Needs binary blob firmware and drivers from linuxtv.org git tree (not in mainline kernel yet)
 
* [[Hauppauge]] [[Hauppauge_WinTV-HVR-2200|WinTV-HVR-2200]] <sup id="fn_1_back">[[#fn_1|1]]</sup> Needs binary blob firmware and drivers from linuxtv.org git tree (not in mainline kernel yet)
 
* [[TerraTec]] [[TerraTec Cinergy T PCIe dual|Cinergy T PCIe dual]]  
 
* [[TerraTec]] [[TerraTec Cinergy T PCIe dual|Cinergy T PCIe dual]]  
 
<cite id="fn_1">[[#fn_1_back|Note 1:]] </cite> Support is currently limited to digital TV mode only.  Analog support (both analog TV & A/V input) will be added to the CX23885/7 driver soon; which will enable preview analog video support. <br>  
 
<cite id="fn_1">[[#fn_1_back|Note 1:]] </cite> Support is currently limited to digital TV mode only.  Analog support (both analog TV & A/V input) will be added to the CX23885/7 driver soon; which will enable preview analog video support. <br>  
 
<cite id="fn_2">[[#fn_2_back|Note 2:]] </cite>Hauppauge's analog mpeg encoder support is also contingent upon further development of the driver for the CX23417 encoder.
 
<cite id="fn_2">[[#fn_2_back|Note 2:]] </cite>Hauppauge's analog mpeg encoder support is also contingent upon further development of the driver for the CX23417 encoder.
 +
  
 
==== Experimental Support: ====
 
==== Experimental Support: ====
 +
* [[Compro Technology|Compro]] VideoMate E850F
 
* [[DViCO]] [[DViCO FusionHDTV DVB-T Dual Express|FusionHDTV DVB-T Dual Express]]
 
* [[DViCO]] [[DViCO FusionHDTV DVB-T Dual Express|FusionHDTV DVB-T Dual Express]]
 
* [[Leadtek]] [[Leadtek WinFast PxDVR3200 H|WinFast PxDVR3200 H]]
 
* [[Leadtek]] [[Leadtek WinFast PxDVR3200 H|WinFast PxDVR3200 H]]
Line 39: Line 41:
 
* [[Blackgold]] [[Blackgold BGT3540|BGT3540]]
 
* [[Blackgold]] [[Blackgold BGT3540|BGT3540]]
 
* [[X3M Digital]] [[X3M Digital HPCe2100|HPCe2100]]
 
* [[X3M Digital]] [[X3M Digital HPCe2100|HPCe2100]]
* [[MSI]] [[TV@nywhere E-Duo]]
+
* [[MSI]] [[MSI TV@nywhere E-Duo|TV@nywhere E-Duo]]
 +
* [[DVBSky_T9580_(PCIe)|DVBSky T9580]], receiver for DVB-T/T2/C/S/S2
 +
* [[DVBSky_T9580_(PCIe)|Mystique SaTeCaBiX]], recevier for DVB-T/T2/C/S/S2 identical to [[DVBSky_T9580_(PCIe)|DVBSky T9580]]
  
 
== DVB-T PCIe Mini Cards ==
 
== DVB-T PCIe Mini Cards ==
Line 53: Line 57:
 
* LifeView LR535
 
* LifeView LR535
 
* Lite-On TVT-1060
 
* Lite-On TVT-1060
 +
* [[AVerMedia A373 MiniCard Dual DVB-T]]
  
 
[[Category:PCIe| ]]
 
[[Category:PCIe| ]]
 
[[Category:DVB-T| ]]
 
[[Category:DVB-T| ]]
 
[[Category:DVB-T PCIe Cards| ]]
 
[[Category:DVB-T PCIe Cards| ]]

Revision as of 00:45, 1 November 2013

On this page you will find information regarding DVB-T PCIe and PCIe Mini Card 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!



DVB-T PCIe Cards

Supported DVB-T PCIe Cards:

Note 1: Support is currently limited to digital TV mode only. Analog support (both analog TV & A/V input) will be added to the CX23885/7 driver soon; which will enable preview analog video support.
Note 2: Hauppauge's analog mpeg encoder support is also contingent upon further development of the driver for the CX23417 encoder.


Experimental Support:

Unsupported DVB-T PCIe Cards:

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(se) developer's 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 line/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 even garnering a response -- that's a distinct by-product of the fact that there are only 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 arrange to hire someone who can.

DVB-T PCIe Mini Cards

Supported DVB-T PCIe Mini Cards

Unsupported DVB-T PCIe Mini Cards:

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(se) developer's 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 line/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 even garnering a response -- that's a distinct by-product of the fact that there are only 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 arrange to hire someone who can.