https://www.linuxtv.org/wiki/api.php?action=feedcontributions&user=Js&feedformat=atomLinuxTVWiki - User contributions [en]2024-03-19T13:42:19ZUser contributionsMediaWiki 1.39.6https://www.linuxtv.org/wiki/index.php?title=Template_talk:USB_Device_Data&diff=36513Template talk:USB Device Data2020-08-29T18:11:02Z<p>Js: /* Editing instructions */</p>
<hr />
<div>Hi, I would like to add/change information regarding some DVB-T usb sticks, but I don't have the edit button on this page. The "view source" page shows me this error message: "You do not have permission to edit pages in the Template namespace."<br />
--[[User:Basic.Master|Basic.Master]] 11:51, 24 March 2012 (CET)<br />
<br />
== Can't add infos about 1b80:d3a4 Afatech - here they are ==<br />
<br />
I wanted to add infos about the DVB-T stick "1b80:d3a4" but couldn't as I don't have write access in the template namespace. [[User:Klaush|Klaush]] 17:21, 1 March 2013 (CET)<br />
<br />
Anyway, here are the infos I wanted to add, maybe someone with write access to the Template namespace can add this (hope I got the template filled out correctly):<br />
<br />
<noinclude><br />
==== auvisio DV-Stick 252.pro 1b80:d3a4 (shown as Afatech) ====<br />
{{DeviceDisplayMedium|auvisio DV-Stick 252.pro}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=auvisio DV-Stick 252.pro 1b80:d3a4<br />
| vendor=auvisio<br />
| device=DV-Stick 252.pro<br />
| standard=DVB-T, DAB, DAB+<br />
| supported=.<br />
| pic=<br />
| url=http://www.pearl.de/a-PX1340-1604.shtml?query=auvisio+dab+<br />
| hostinterface=USB2.0<br />
| usbid=1b80:d3a4<br />
| hw=[[RealTek RTL2832U]]<br />
| tuner=Fitipower FC0013<br />
| demodulator=RTL2832U<br />
| usbbridge=RTL2832U<br />
| fw=<br />
| comment=<br />
Used a pristine linux-3.7.9 kernel together with a slightly patched V4L sources as mentioned in [http://www.dfragos.me/2012/11/installation-of-rtl2832u-chip-based-dvb-t-usb-stick.html] did work (had to add "#define USB_PID_KWORLD2_TURBOX_USB2_DVB_T 0xd3a4" to the end of linux/drivers/media/dvb-core/dvb-usb-ids.h and <pre>{ DVB_USB_DEVICE(USB_VID_KWORLD_2, 0xd3a4,<br />
+ &rtl2832u_props, "Realtek 2832U USB DVB-T Stick RC", NULL) },</pre> immediately after <pre>static const struct usb_device_id rtl28xxu_id_table[] = {</pre> inside linux/drivers/media/usb/dvb-usb-v2/rtl28xxu.c.<br />
Afterwards, plugging in the DVB-T stick loads the drivers, /dev/dvb/adapter0 is visible and usable by tvheadend.<br />
BTW, works with gnuradio as well as SDR.<br />
}}<br />
<br />
</includeonly><br />
<br />
<br />
==== AverMedia AVerTV Red HD+ (A850T) 07ca:850b ====<br />
{{DeviceDisplayMedium|AverMedia AVerTV Red HD+ (A850T) 07ca:850b}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=AverMedia AVerTV Red HD+ (A850T) 07ca:850b<br />
| vendor=[[AVerMedia]]<br />
| device=[[AverMedia AVerTV Red HD+ | AVerTV Red HD+]]<br />
| standard=DVB-T<br />
| supported={{yes}}<br />
| pic=<br />
| pic=<br />
| url=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=07ca:850b<br />
| hw=af9013<br />
| tuner=MXL5005S<br />
| demodulator=<br />
| usbbridge=af9013<br />
| fw=dvb-usb-af9015.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><br />
<br />
== Geniatech T230C2 ==<br />
<br />
I don't have permission to update, but a couple of changes suggested for the Geniatech T230C2:<br />
<br />
- Note support added in kernel 5.4<br />
<br />
- Remove link to crazycat driver as this device is now supported by official media_build, and crazycat driver no longer builds on latest debian<br />
<br />
== Editing instructions ==<br />
I follow "''How do I add a new device?''" chapter but there is no checkbox called "''Enable section editing via edit links''" in my preferences. Other editing general options have no effect: Neither "''Enable section editing by right clicking on section titles''" nor "''Edit pages on double click''". --[[User:Narcisgarcia|Narcisgarcia]] ([[User talk:Narcisgarcia|talk]]) 06:35, 25 August 2020 (UTC)<br />
<br />
: The section edit links should be there unconditionally, I updated the instructions. --[[User:Js|js]] ([[User talk:Js|talk]]) 18:10, 29 August 2020 (UTC)</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Template:USB_Device_Data&diff=36512Template:USB Device Data2020-08-29T18:08:22Z<p>Js: /* How do I add a new device? */ remove obsolete editing hints</p>
<hr />
<div><noinclude><br />
<br />
== Introduction to this page ==<br />
<br />
The data contained in this template is slowly replacing the collection of tables in the [[DVB-T_USB Devices]] article.<br />
<br />
The main purpose is to collect the available information on devices that now is scattered around on device/chipset/driver pages, and at the same time make it accessible from all those places.<br />
Having a "single copy" will hopefully ease updating information on devices and drivers.<br />
<br />
== How do I add a new device? ==<br />
<br />
{{note|Freshly created user accounts need to wait one day before they gain permission to edit templates.}}<br />
<br />
First open two more browser tabs. One tab with this page, so that you can read up on the instructions while you are editing, and one tap with [[USB_Devices_ListData/Helper]], a reference page where there is a List of all the devices that are stored on this page. There you can check on how data will be shown in the tables.<br />
<br />
Second identify a section where your device would fit in. This is not technically needed but it will help you when using an existing device as template for your new device.<br />
<br />
Click on the [edit] link on the right of that section's title.<br />
<br />
Look at the data of a device that is already there, and look at the reference page and the instructions to make sure you understand what the fields mean and where they show up.<br />
<br />
Now either copy an existing device's data or copy the cut'n paste template from the instructions and fill in your device's data.<br />
<br />
The most important field is the '''did''' as it will allow you to select that specific device on your device page. Having the '''did''' repeated in the subsection header will allow your browser to jump to the right place if you click the edit icon in a table.<br />
<br />
{{note|If you edit the data below, you may have to outsmart your browser-cache and the rendering cache of the wiki. Otherwise your changes might not appear in the table renderings. }}<br />
<br />
== How do I show the data on a Device/Vendor/... page ? ==<br />
<br />
{{note| The mental crutch that I use to visualize the data in my head is a ''simple spread'' sheet with ''one row per device'' and ''one column per property'' (like Vendor, Name, support status ...).}}<br />
<br />
Keeping all the information in one place of course means that there will be lots of details that most users don't care about.<br />
Using some minor template voodoo, it is possible to select a limited subset of data fields per device and thus construct tables with a small subset of columns. If you think of it as a spread sheet you may have only a couple of columns shown. (Some examples are currently shown on [[HLPlayground2]] (Warning: HUGE Page!..but look at how tiny the source is.))<br />
<br />
Still, usually you will not want to have all the devices listed.<br />
<br />
With some more template voodoo and the help of the ParserFunctions/StringFunctions extension it is possible to select <br />
subsets of the data by their content. Think of it as only showing rows in your spread sheet if they contain certain elements.<br />
E.g. Only show devices that use a certain tuner or only show devices by a certain vendor.<br />
( If you are interested in the Details, go to [[Template:List of Device List Templates]] )<br />
<br />
Some examples are currently shown on [[HLPlayground2/rowselection]] and [[HLPlayground2/doubleselection]] and in the next section...<br />
<br />
=== Usage Examples on device pages ===<br />
<br />
Low detail:<br />
<pre><br />
{{Device_List_Low_Detail/Header<br />
| content = <br />
{{USB_Device_Data<br />
|renderwith=Device_List_Low_Detail/Row<br />
|selatt1=did<br />
|selval1=msi-digivox-mini-ii-v3<br />
}}<br />
}}<br />
</pre><br />
<br />
{{note| As you can see ''did'' is set as selection attribute and ''msi-digivox-mini-ii-v3'' as selection value. This used to be a [[MSI DigiVox mini II V3.0|simple device]] but the vendor started selling a completely different device with the same name and a different USB ID. We changed the existing device's did by appending the USB ID and since the selection is done by searching for a substring, that table above will now produce both, the old and the new device. Neat, isn't it?}}<br />
<br />
If you want to show some more detail you can change ''Low'' to ''Medium'' in '''both''' template names. (The ''/Header'' and ''/Row'' template.)<br />
<br />
<pre><br />
{{Device_List_Medium_Detail/Header<br />
| content = <br />
{{USB_Device_Data<br />
|renderwith=Device_List_Medium_Detail/Row<br />
|selatt1=did<br />
|selval1=msi-digivox-mini-ii-v3<br />
}}<br />
}}<br />
</pre><br />
<br />
There is also a set of templates for ''Full'' details if you want to get the fields that are meant for filtering only, like the ''did'' field itself.<br />
<br />
== Syntax and Semantics ==<br />
<br />
Here is a cut'n paste template for new devices. (Don't forget use the same ''XxXxXxXxXxXxX'' in all three places.)<br />
<pre><br />
&lt;/includeonly&gt;&lt;noinclude&gt;<br />
==== XxXxXxXxXxXxX ====<br />
{{DeviceDisplayMedium|XxXxXxXxXxXxX}}<br />
&lt;/noinclude&gt;&lt;includeonly&gt;<br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=XxXxXxXxXxXxX<br />
| vendor=<br />
| device=<br />
| standard=<br />
| supported=<br />
| pic=<br />
| url=<br />
| hostinterface=<br />
| usbid=<br />
| hw=<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=<br />
| fw=<br />
| comment=<br />
}}<br />
<br />
</pre><br />
<br />
{| class="wikitable"<br />
| ''did'' || a device ID that makes it possible to render just this one device in a table and to jump directly to the device on this page. As matching in the selection templates is done on substrings you need to make sure that the did's are unique and disjoint. Also try to only use lowercase letters, numbers, and the dash "-". The ''did'' is not meant to be shown to average reading-only users of the wiki but rather be used by editors. So we can dispense with nice form and concentrate on function<br />
<pre> msi-digivox-mini-ii-v3-15a4-9016 </pre><br />
|- <br />
| ''vendor'' || the device manufacturer/vendor. E.g. [[Hauppauge]]. Feel free to make it a link to the vendor page in the wiki. E.g. by writing <br />
<pre> [[Hauppauge]] </pre><br />
|- <br />
| ''device'' || the device name. E.g. [[TerraTec Cinergy T USB XXS|Cinergy T XXS]]. This is also the place to put a link to a device page. Since most device pages contain the vendor in the page title, you may have to give the page title and the device name separately like this <br />
<pre> [[TerraTec Cinergy T USB XXS|Cinergy T XXS]] </pre><br />
|- <br />
| ''standard'' || the broadcasting standard or standards that the device supports E.g. Possible values would be the analog encodings "ANALOG-PAL" "ANALOG-NTSC" "ANALOG-SECAM" as well as digital encodings "DVB-T" "DVB-C" "DVB-C2" "DVB-S" "DVB-S2" "DVB-H" "DVB-SH" "ATSC" "ATSC-M/H" "ISDB-S" "ISDB-T" "1seg" "ISDB-C" "SBTVD/ISDB-Tb" "DMB-T/H" "ADTB-T" "CMMB" "DMB-T" "T-DMB" "S-DMB" "MediaFLO". Even "FM-RADIO" and "AM-RADIO" could be included in this list. <br />
Im most cases however it will simply be<br />
<pre> DVB-T </pre><br />
|-<br />
| ''supported'' || support status. <br />
<pre> {{yes}} or {{no}} </pre><br />
if there is no further detail but I'd prefer something like <br />
<pre> {{Supported in Kernel|since=2.6.25|file=drivers/media/dvb/dvb-usb/dib0700_devices.c}} </pre><br />
if supported by vanilla kernel since version 2.6.25 (the entry will be linked to the kernel source repository)<br />
<pre> {{Supported in HG|since=2009-01-31}} </pre><br />
for support in main line mercurial repository<br />
<pre> {{Supported in HG Branch|since=2009-01-31|branchurl=http://linuxtv.org/hg/~anttip/af9015/}} </pre><br />
for support in certain branch<br />
<pre> {{Supported in External|since=2009-01-31|url=http://mcentral.de/wiki/index.php5/Em2880}} </pre><br />
for support somewhere else<br />
|-<br />
| ''pic'' || preferably an image uploaded to the wiki (using 120px width). Like this: <pre>[[image:Dvb-t-usb-msi-digivox-ii-rev3-001.jpg|120px]]</pre>Links to (not embedding of) external pictures are OK in a pinch, but those might disappear any time as some vendors only keep the current devices on their page and every older Device vanishes. Please, please, please, if you own a device that doesn't have a picture yet, take one and upload it. Even a blurry picture taken with a mobile phone camera is better than nothing. However, do not upload pictures that you downloaded from a vendor page without asking for permission to use it here. Taking a picture of a device that you own is the better choice and other users will greatly benefit from it.<br />
|-<br />
| ''url'' || link to the manufacturers/vendors page for that device. but also links to linux user experience pages, forum articles or mailing list achives regarding this device.<br />
|-<br />
| ''hostinterface'' || interface supported. E.g. "USB1.1" and "USB2.0" but also "ISA" "PCI32" "PCI64" "PCI-X" "PCIe" "PCCARD" "CardBus" "ExpressCard" "IEEE1394" Currently most devices have<br />
<pre> USB2.0 </pre><br />
|-<br />
| ''hw'' || summary of the hardware (human readable). this field holds the hardware data during transition from older tables of devices also also allows to add hw related information beyond tuner, demodulator and usb bridge.<br />
|-<br />
| ''usbid'' || usb id. 4 hex digits, colon, 4 hex digits. lower case. e.g. <br />
<pre> 12ba:f001 </pre><br />
If your device changes its USB ID after having its firmware uploaded please only add the "cold" id. The one shown before firmware upload. The warm id should go the the device's page.<br />
|-<br />
|<br />
* ''tuner''<br />
* ''demodulator''<br />
* ''usbbridge'' <br />
| machine readable component names for implementing filters based on this. E.g. af9015, vt7045, mt2060. Check out the [[Afatech AF9015]] page for a table that filters for usbbridge == af9015<br />
|-<br />
| ''fw'' || firmware file name. a link if it isn't included with most linux distributions.<br />
|-<br />
| ''comment'' || human readable comments. if those comments stretch several lines, it is time to make a device page. :-)<br />
|}<br />
<br />
== Data ==<br />
Click on Edit to see the data.<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
=== unsupported devices ===<br />
</noinclude><includeonly><br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== anysee-e7-all ====<br />
{{DeviceDisplayMedium|anysee-e7-all}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=anysee-e7-all<br />
| vendor=[[Anysee]]<br />
| device=[[Anysee E7|E7]]<br />
| standard=DVB-T, DVB-T2, DVB-C, DVB-C2, DVB-S, DVB-S2<br />
| supported={{no}}<br />
| pic=[[Image:Anysee_T7_T2C.JPG|122px|Anysee E7 T2C]]<br />
| url=[http://www.anysee.com/eng/product/anyseeE7_main.php]<br />
| hostinterface=USB2.0<br />
| usbid=1c73:861f<br />
| hw=<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=<br />
| fw=N/A<br />
| comment=This is a generic entry for the Anysee E7 line. If you have details for a particular device, please feel free to clone this entry and add the details.<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== conceptronic-ctvdigdual-v2 ====<br />
{{DeviceDisplayMedium|conceptronic-ctvdigdual-v2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=conceptronic-ctvdigdual-v2<br />
| vendor=Conceptronic<br />
| device=Digital Dual TV Receiver CTVDIGDUAL_V2<br />
| standard=DVB-T<br />
| supported={{no}}<br />
| pic=<br />
| url=[http://www.conceptronic.net/Site/desktopdefault.aspx?tabindex=1&tabid=242&cid=40&gid=4050&pid=CTVDIGDUAL_V2]<br />
| hostinterface=USB2.0<br />
| usbid=1b80:e410<br />
| hw=Afatech/ITETech IT9135<br />
| tuner=it9135<br />
| demodulator=it9135<br />
| usbbridge=it9135<br />
| fw=<br />
| comment=Dual tuner. Tested with kernel 2.6.34<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== agk-10314 ====<br />
{{DeviceDisplayMedium|agk-10314}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=agk-10314<br />
| vendor=Agk<br />
| device=10314<br />
| standard=DVB-T<br />
| supported={{no}}<br />
| pic=<br />
| url=[http://www.mail-archive.com/linux-media@vger.kernel.org/msg16480.html]<br />
| hostinterface=USB2.0<br />
| usbid=1d19:1103<br />
| hw=[[RealTek RTL2832U]]<br />
| tuner=rtl2832u<br />
| demodulator=<br />
| usbbridge=<br />
| fw=<br />
| comment=<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== artec-atsc-t14a ====<br />
{{DeviceDisplayMedium|artec-atsc-t14a}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=artec-atsc-t14a<br />
| vendor=[[Artec]]<br />
| device=[[Artec T14A|T14A]]<br />
| standard=ATSC<br />
| supported={{no}}<br />
| pic=<br />
| url=[http://www.linuxtv.org/pipermail/linux-dvb/2007-February/016134.html] <br />
| hostinterface=USB2.0<br />
| usbid=05d8:810d<br />
| hw=Microtune MT2060, LG DT3303, Cypress FX2 (CY7C68013)<br />
| tuner=mt2060<br />
| demodulator=dt3303<br />
| usbbridge=cypressfx2<br />
| fw=<br />
| comment=warm id 05d8:810e<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
=== avermedia a8xx series ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== avermedia-a800 ====<br />
{{DeviceDisplayMedium|avermedia-a800}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=avermedia-a800<br />
| vendor=[[AVerMedia]]<br />
| device=AVerTV DVB-T USB 2.0 A800<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13|file=drivers/media/dvb/dvb-usb/a800.c}}<br />
| pic=<br />
| url=[http://www.avermedia.com/avertv/Product/ProductDetail.aspx?Id=163&tab=APDriver]<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=07ca:a800<br />
| hw=[[DiBcom DiB3000|DiBcom 3000P]] dvb-usb-a800.ko<br />
| tuner=<br />
| demodulator=dib3000m<br />
| usbbridge=<br />
| fw=dvb-usb-avertv-a800-02.fw<br />
| comment=Remote control handling is different to the one used in the other DiBusb clones and many essential keys do not work at all (with X.org and linux kernels 2.6.17 and 2.6.18). warm id: 07ca:a801<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== avermedia-a835 ====<br />
{{DeviceDisplayMedium|avermedia-a835}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=avermedia-a835<br />
| vendor=[[AVerMedia]]<br />
| device=AVerTV AverTV Volar HD & HD PRO (A835)<br />
| standard=DVB-T<br />
| supported={{yes}} (unofficial)<br />
| pic=[http://www.avermedia.com/avertv/Upload/ProductImages/140/Box-A8351.jpg]<br />
| url=[http://www.avermedia.com/avertv/product/ProductDetail.aspx?Id=508]<br />
| hostinterface=USB2.0<br />
| usbid=07ca:a835<br />
| hw=[[Afatech AF9035|AF 9035]]<br />
| tuner=NXP TDA18218HN<br />
| demodulator=af9035<br />
| usbbridge=af9035<br />
| fw=[http://xgazza.altervista.org/Linux/DVB/dvb-usb-af9035-01.fw]<br />
| comment=Newer kernels supported via this way [http://forum.ubuntu-it.org/index.php/topic,384436.msg3370690.html#msg3370690]. 2.6.32 kernel possible after minor patch [http://dl.dropbox.com/u/1848772/tda18218_kernel_pre_2.6.35.patch]. Tested with 2.6.32-5-kirkwood.<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== avermedia-a835b ====<br />
{{DeviceDisplayMedium|avermedia-a835b}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=AVerMedia AVerTV Volar Green HD 07ca:3835<br />
| vendor=[[AVerMedia]]<br />
| device=AVerTV AverTV Volar HD & HD PRO & Volar Green (A835B)<br />
| standard=DVB-T<br />
| supported={{yes}}<br />
| pic=[http://avertv.avermedia.com/Upload/ProductImages/Box-AVerTV%20Volar%20Green%20HD-WE1_300.jpg]<br />
| url=[http://avertv.avermedia.com/Product/ProductDetail.aspx?Id=519&device=2]<br />
| hostinterface=USB2.0<br />
| usbid=07ca:3835<br />
| hw=[[IT913X]]<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=<br />
| fw=[https://github.com/OpenELEC/dvb-firmware/raw/master/firmware/dvb-usb-it9135-02.fw]<br />
| comment=Device successfully installed on kernel 3.13.0 (Mythbuntu 14.04). This device looks identical to the A835 and has the same model number on the box but has a different chip inside.<br />
Note: Do NOT use the firmware http://palosaari.fi/linux/v4l-dvb/firmware/IT9135/ Because with this incorrect firmware downloaded, the USB device reset will fail (dmesg shows: "FRM Failed to reboot device..."). The correct firmware is here: https://github.com/OpenELEC/dvb-firmware/raw/master/firmware/dvb-usb-it9135-02.fw (5817 bytes).<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== avermedia-td110 ====<br />
{{DeviceDisplayMedium|avermedia-td110}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=AVerMedia AVerTV Volar HD 2 07ca:a110<br />
| vendor=[[AVerMedia]]<br />
| device=AVerTV AverTV Volar HD 2 (TD110)<br />
| standard=DVB-T<br />
| supported={{yes}}, could need build kernel with linuxtv to works.<br />
| pic=[https://d164vpkda9uyv1.cloudfront.net/web_upload/consumer/product/gallery/TD110_gallery_3.jpg]<br />
| url=[https://www.avermedia.com/sp/tv_more/product/tv/avertv_volar_hd_2]<br />
| hostinterface=USB2.0<br />
| usbid=07ca:a110<br />
| hw=[[IT913X]]<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=<br />
| fw=[https://github.com/OpenELEC/dvb-firmware/raw/master/firmware/dvb-usb-it9135-02.fw]<br />
| comment=Same device as A835B, but it could need linuxtv to works.<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== Avermedia-A835B(1835) ====<br />
{{DeviceDisplayMedium|Avermedia-A835B(1835)}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=Avermedia-A835B(1835)<br />
| vendor=[[AVerMedia]]<br />
| device=AverTV Volar HD PRO A835B(1835)<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=3.11-2|file=drivers/media/usb/dvb-usb-v2/it913x.c}}<br />
| pic=[[image:dvb-t-avermedia-avertv-volar-hd-pro-A835B-1835-01.jpg|120px]] [[http://avertv.avermedia.com/Upload/ProductImages/140/Box-A835-AVerTV%20Volar%20HD%20Pro_WE.JPG]]<br />
| url=[http://avertv.avermedia.com/Product/ProductDetail.aspx?Id=507&device=2] [https://sites.google.com/site/danieldebastesdumppage/open-source/averttv-volar-hd-pro]<br />
| hostinterface=USB2.0<br />
| usbid=07ca:1835<br />
| hw=it913x: Chip Version 02 Chip Type 9135<br />
| tuner=Type 38<br />
| demodulator=<br />
| usbbridge=<br />
| fw=[[https://sites.google.com/site/danieldebastesdumppage/open-source/averttv-volar-hd-pro/dvb-usb-it9135-02.fw?attredirects=0&d=1|dvb-usb-it9135-02.fw]]<br />
| comment=Firmware extracted from the Windows driver on the companion CD-ROM. <br />
Model : A835 as of the box, A835B as detected by the kernel.<br />
Remote control not tested.<br />
Probably supported by older kernels too (not searched).<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== avermedia-a825 ====<br />
{{DeviceDisplayMedium|avermedia-a825}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=avermedia-a825<br />
| vendor=[[AVerMedia]]<br />
| device=AVerTV A825/TwinStar<br />
| standard=DVB-T<br />
| supported={{no}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=<br />
| hw=[[Afatech AF9035|AF 9035]]<br />
| tuner=<br />
| demodulator=af9035<br />
| usbbridge=af9035<br />
| fw=<br />
| comment=Dual AF9035 based. At this stage, AfaTech will not release full specifications, and so these cards are likely to remain unsupported.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== avermedia h800 ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== avermedia-h830 ====<br />
{{DeviceDisplayMedium|avermedia-h830}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=avermedia-h830<br />
| vendor=[[AVerMedia]]<br />
| device=AVerTV Hybrid Volar HD (H830)<br />
| standard=DVB-T<br />
| supported={{no}}<br />
| pic=[http://www.avermedia.com/avertv/Upload/ProductImages/AVerTV%20Hybrid%20Volar%20HD%20(H830)%20Box%20300.jpg]<br />
| url=[http://www.avermedia.com/avertv/Product/ProductDetail.aspx?Id=501&tab=APDriver]<br />
| hostinterface=USB2.0<br />
| usbid=07ca:0830<br />
| hw=<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=<br />
| fw=<br />
| comment=Written H830 on device. [http://www.avermedia.com/avertv/Product/ProductDetail.aspx?Id=501&tab=APDriver Official driver] Support neither FM nor Remote Control. Tested on Ubuntu 10.04 with kernel 2.6.32-32-generic.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== avermedia-h830d ====<br />
{{DeviceDisplayMedium|avermedia-h830d}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=avermedia-h830d<br />
| vendor=[[AVerMedia]]<br />
| device=AVerTV Volar Video Capture USB (H830D)<br />
| standard=DVB-T<br />
| supported={{no}}<br />
| pic=[http://www.avermedia.com/avertv/Upload/ProductImages/Pro-H830D-AVerTV%20Volar%20Video%20Capture%20USB-300.jpg]<br />
| url=[http://www.avermedia.com/avertv/Product/ProductDetail.aspx?Id=503&tab=APDriver]<br />
| hostinterface=USB2.0<br />
| usbid=07ca:1830<br />
| hw=<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=<br />
| fw=<br />
| comment=Written H830 on device. Tried with Ubuntu 10.04, Kernel 2.6.32-25-generic (x86_64), but no luck. In dmesg I see:<br />
[ 2625.662599] usb 5-2: new full speed USB device using uhci_hcd and address 1<br><br />
[ 2625.838880] usb 5-2: configuration #1 chosen from 1 choice<br><br />
<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== AF9005 Devices ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== ansonic-stick ====<br />
{{DeviceDisplayMedium|ansonic-stick}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=ansonic-stick<br />
| vendor=Ansonic<br />
| device=DVB-T USB1.1 stick<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.25|file=drivers/media/dvb/dvb-usb/af9005.c}}<br />
| pic=<br />
| url=[http://www.mail-archive.com/linux-dvb@linuxtv.org/msg28726.html]<br />
| hostinterface=USB1.1<br />
| usbid=10b9:6000<br />
| comment=<br />
| tuner=<br />
| demodulator=af9005<br />
| usbbridge=af9005<br />
| hw=[[Afatech AF9005]]<br />
| fw=af9005.fw<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== allnet-all2006 ====<br />
{{DeviceDisplayMedium|allnet-all2006}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=allnet-all2006<br />
| vendor=Allnet<br />
| device=ALL2006 USB DVB-T Stick<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.23 or .25?|file=drivers/media/dvb/dvb-usb/af9005.c}}<br />
| pic=<br />
| url=[http://www.allnet.de/product_info_allnet.php?cPath=_&products_id=99975]<br />
| hostinterface=USB1.1<br />
| usbid=<br />
| comment=The tuner sensitivity is less than impressive.<br />
| tuner=<br />
| demodulator=af9005<br />
| usbbridge=af9005<br />
| hw=[[Afatech AF9005]]<br />
| fw=[http://ventoso.org/luca/af9005/af9005.fw af9005.fw]<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== delock93168 ====<br />
{{DeviceDisplayMedium|delock93168}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=delock93168<br />
| vendor=Delock<br />
| device=USB2.0 DVB-T Receiver Nr.93168<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.23 or .25?|file=drivers/media/dvb/dvb-usb/af9005.c}}<br />
| pic=<br />
| url=[http://delock.de/produkte/gruppen/Multimedia/USB20_DVB-T_Empfnger_93168.html]<br />
| hostinterface=USB1.1<br />
| usbid=<br />
| comment=<br />
| tuner=<br />
| demodulator=af9005<br />
| usbbridge=af9005<br />
| hw=[[Afatech AF9005]]<br />
| fw=[http://ventoso.org/luca/af9005/af9005.fw af9005.fw]<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== Easy TV A05 ====<br />
{{DeviceDisplayMedium|easytv-a05}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=easytv-a05<br />
| vendor=EasyTV<br />
| device=EasyTV USB DVB-T Dongle<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.25|file=drivers/media/dvb/dvb-usb/af9005.c}}<br />
| pic=<br />
| url=[http://images.google.co.uk/images?q=easytv%20a05]<br />
| hostinterface=USB1.1<br />
| usbid=<br />
| comment=<br />
| tuner=<br />
| demodulator=af9005<br />
| usbbridge=af9005<br />
| hw=[[Afatech AF9005]]<br />
| fw=af9005.fw<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== ridata-t100 ====<br />
{{DeviceDisplayMedium|ridata-t100}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=ridata-t100<br />
| vendor=Ridata<br />
| device=USB DVB-T Stick T100<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.23 or .25?|file=drivers/media/dvb/dvb-usb/af9005.c}}<br />
| pic=<br />
| url=[http://www.ritek.com/p2-pro5-lp.asp]<br />
| hostinterface=USB1.1<br />
| usbid=<br />
| comment=<br />
| tuner=<br />
| demodulator=af9005<br />
| usbbridge=af9005<br />
| hw=[[Afatech AF9005]]<br />
| fw=[http://ventoso.org/luca/af9005/af9005.fw af9005.fw]<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== terratec-txe-rev1 ====<br />
{{DeviceDisplayMedium|terratec-txe-rev1}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-txe-rev1<br />
| vendor=[[TerraTec]]<br />
| device=[[TerraTec Cinergy T USB XE|Cinergy T USB XE (rev1)]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.23|file=drivers/media/dvb/dvb-usb/af9005.c}}<br />
| pic=[[image:Dvb-t-usb-terratec-cinergy-t-usb-xe-001.jpg|120px]]<br />
| url=[http://www.terratec.net/en/products/Cinergy_T_USB_XE_1672.html]<br />
| hostinterface=USB1.1<br />
| usbid=0ccd:0055<br />
| tuner=<br />
| demodulator=af9005<br />
| usbbridge=af9005<br />
| hw=[[Afatech AF9005]]<br />
| fw=[http://ventoso.org/luca/af9005/af9005.fw af9005.fw] or [http://ventoso.org/luca/af9005/af9005.fw-6.11.23.01 af9005.fw-6.11.23.01] (rename it to af9005.fw!)<br />
| comment=The AF9005 version has the CE Symbol on the device<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== AF9015 Devices ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== afatech-9015-9016 ====<br />
{{DeviceDisplayMedium|afatech-9015-9016}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=afatech-9015-9016<br />
| vendor=Afatech<br />
| device=AF9015 DVB-T USB2.0 stick<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=15a4:9015 15a4:9016<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== avermedia-a309 ====<br />
{{DeviceDisplayMedium|avermedia-a309}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=avermedia-a309<br />
| vendor=[[AVerMedia]]<br />
| device=A309 Mini Card<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=07ca:a309<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== alcor-dtv-duo ====<br />
{{DeviceDisplayMedium|alcor-dtv-duo}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=alcor-dtv-duo<br />
| vendor=Alcor<br />
| device=DTV DUO<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.37}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=15a4:9016<br />
| hw=[[Afatech AF9015|Afatech AF9015A + AF9013]], 2x MxL5007T (3f)<br />
| tuner=mxl5007t<br />
| demodulator=af9013<br />
| usbbridge=af9015<br />
| fw=dvd-usb-af9015.fw (5.1.0.0)<br />
| comment=Dual tuner. Tested with kernel 2.6.37<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== avermedia-a815 ====<br />
{{DeviceDisplayMedium|avermedia-a815}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=avermedia-a815<br />
| vendor=[[AVerMedia]]<br />
| device=[[AVerMedia AVerTV Digi Volar X (A815)|AVerTV Digi Volar X (A815)]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=[[image:Volar_x.png|120px]]<br />
| url=[http://homefree.avermedia.com/avertv/Upload/ProductImages/A815_Datasheet_EN_20121102.pdf]<br />
| hostinterface=USB2.0<br />
| usbid=07ca:a815<br />
| hw=[[Afatech AF9015|Afatech AF9015-NT*]], MXL5003S<br />
| tuner=[[MXL5003S]]<br />
| demodulator=[[Afatech AF9015|af9015]]<br />
| usbbridge=af9015<br />
| fw=[http://palosaari.fi/linux/v4l-dvb/firmware/af9015/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== avermedia-a850 ====<br />
{{DeviceDisplayMedium|avermedia-a850}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=avermedia-a850<br />
| vendor=[[AVerMedia]]<br />
| device=AVerTV Volar Black HD (A850)<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.30-rc1}}<br />
| pic=[[Image:AVerMedia_AVerTV_Volar_Black_HD_(A850).png|120px]]<br />
| url=[http://www.avermedia.eu/avertv/SP/Product/ProductDetail.aspx?Id=431]<br />
| hostinterface=USB2.0<br />
| usbid=07ca:850a<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== avermedia-a805 ====<br />
{{DeviceDisplayMedium|avermedia-a805}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=avermedia-a805<br />
| vendor=[[AVerMedia]]<br />
| device=AVerTV Volar GPS 805 (A805)<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.31}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=07ca:a805<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== conceptronic-ctvdigrcu ====<br />
{{DeviceDisplayMedium|conceptronic-ctvdigrcu}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=conceptronic-ctvdigrcu<br />
| vendor=Conceptronic<br />
| device=USB2.0 DVB-T CTVDIGRCU V3.0<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.31}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1b80:e397<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
==== dikom-ultimate ====<br />
{{DeviceDisplayMedium|dikom-ultimate}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dikom-ultimate<br />
| vendor=Dikom<br />
| device=USB-DVB-T Ultimate<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.30}}<br />
| pic=<br />
| url=[http://www.dikom.it/catalogo.aspx?Prod=245]<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=<br />
| hw=[[Afatech AF9015]], [[Quantek QT1010]]<br />
| tuner=qt1010<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=also sold as "PEAK 203244AGPK DVB-T Digital TV USB Stick" and "KWorld USB DVB-T TV Stick II (VS-DVB-T 395U)" and others.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== digitalnow-tinytwin-v1 ====<br />
{{DeviceDisplayMedium|digitalnow-tinytwin-v1}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=digitalnow-tinytwin-v1<br />
| vendor=DigitalNow<br />
| device=[[DigitalNow TinyTwin DVB-T Receiver|TinyTwin DVB-T Receiver]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=13d3:3226<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=No longer available.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== digitalnow-tinytwin-v2 ====<br />
{{DeviceDisplayMedium|digitalnow-tinytwin-v2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=digitalnow-tinytwin-v2<br />
| vendor=DigitalNow<br />
| device=[[DigitalNow TinyTwin DVB-T Receiver|TinyTwin DVB-T Receiver V2]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.34}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1b80:e402<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=No longer available.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== digitalnow-tinytwin-v3 ====<br />
{{DeviceDisplayMedium|digitalnow-tinytwin-v3}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=digitalnow-tinytwin-v3<br />
| vendor=DigitalNow<br />
| device=[[DigitalNow TinyTwin DVB-T Receiver|TinyTwin DVB-T Receiver V3]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.37}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1f4D:9016<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=No longer available.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== digittrade-stick ====<br />
{{DeviceDisplayMedium|digittrade-stick}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=digittrade-stick<br />
| vendor=DIGITTRADE<br />
| device=DVB-T Stick<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.??}}<br />
| pic=<br />
| url=[http://www.digittrade.de/shop/product_info.php/info/p66_DIGITTRADE-DVB-T-Stick-USB-2-0-1-1-Windows-Linux-MAC-Eee-PC.html]<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== fujitsu-siemens-slim ====<br />
{{DeviceDisplayMedium|fujitsu-siemens-slim}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=fujitsu-siemens-slim<br />
| vendor=Fujitsu-Siemens<br />
| device=Slim Mobile USB DVB-T<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=[[Image:Fujitsu.JPG|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=07ca:8150<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== geniatech-t328b ====<br />
{{DeviceDisplayMedium|geniatech-t328b}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=geniatech-t328b<br />
| vendor=[[Geniatech]]<br />
| device=T328B<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=[[image:Geniatech_t328b.png|120px]]<br />
| url=[http://www.geniatech.com/pa/t328b.htm]<br />
| hostinterface=USB2.0<br />
| usbid=15a4:9016<br />
| hw=[[Afatech AF9015]], [[Microtune MT2060]]<br />
| tuner=mt2060<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== genius-tvgo-t03-af9015 ====<br />
{{DeviceDisplayMedium|genius-tvgo-t03-af9015}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=genius-tvgo-t03-af9015<br />
| vendor=Genius<br />
| device=[[Genius TVGo DVB-T03|TVGo DVB-T03]] (af9015 version)<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.31}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0458:4012<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=also sold with fc0012 + rtl2832u chipset.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== hama-usb2stick ====<br />
{{DeviceDisplayMedium|hama-usb2stick}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=hama-usb2stick<br />
| vendor=[[Hama]]<br />
| device=[[Hama DVB-T USB2 Stick|DVB-T USB2 Stick]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_HG|since=2008-09}}<br />
| pic=[[image:HamaDVB_T-USB2-Stick.jpg|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=<br />
| hw=[[Afatech AF9015]] (declared as 9016, working as [[Afatech AF9015|AF9015]])<br />
| tuner=mt2060<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== kworld-395u ====<br />
{{DeviceDisplayMedium|kworld-395u}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=kworld-395u<br />
| vendor=[[KWorld]]<br />
| device=USB DVB-T TV Stick II (VS-DVB-T 395U)<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.29}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1b80:e396 1b80:e39b 1b80:e395<br />
| hw=Afatech AF9013/[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=support for usbids 1b80:e39b 1b80:e395 added in 2.6.30<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== kworld-399u-dual ====<br />
{{DeviceDisplayMedium|kworld-399u-dual}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=kworld-399u-dual<br />
| vendor=[[KWorld]]<br />
| device=[[KWorld USB Dual DVB-T TV Stick (DVB-T 399U)|USB Dual DVB-T TV Stick (DVB-T 399U)]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=[[Image:KWorld_USB_Dual_DVB-T_TV_Stick_(DVB-T_399U).png|120px]]<br />
| url=[http://global.kworld-global.com/main/prod_in.aspx?mnuid=1248&modid=6&pcid=44&ifid=17&prodid=73]<br />
| hostinterface=USB2.0<br />
| usbid=1b80:e399 1b80:e400<br />
| hw=Afatech AF9013/[[Afatech AF9015]]/2x [[MXL5003S]]<br />
| tuner=mxl5003s<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=support for 1b80:e400 added in 2.6.32<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== kworld-pc160-2t ====<br />
{{DeviceDisplayMedium|kworld-pc160-2t}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=kworld-pc160-2t<br />
| vendor=[[KWorld]]<br />
| device=[[KWorld DVB-T PC160-2T|PlusTV Dual DVB-T PCI (DVB-T PC160-2T)]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=[[image:Kworld pc160.jpg|120px]]<br />
| url=<br />
| hostinterface=PCI32<br />
| usbid=1b80:c160<br />
| hw=Afatech AF9013/[[Afatech AF9015]]/2x [[MXL5003S]]<br />
| tuner=mxl5003s<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== kworld-mc810 ====<br />
{{DeviceDisplayMedium|kworld-mc810}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=kworld-mc810<br />
| vendor=[[KWorld]]<br />
| device=Digial MC-810<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.31}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1b80:c810<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== leadtek-dtv-gold ====<br />
{{DeviceDisplayMedium|leadtek-dtv-gold}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=leadtek-dtv-gold<br />
| vendor=[[Leadtek]]<br />
| device=[[Leadtek WinFast DTV Dongle Gold|WinFast DTV Dongle Gold]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=[[Image:Leadtek_gold.jpg|100px]]<br />
| url=[http://www.leadtek.com/eng/multimedia/overview.asp?lineid=6&pronameid=407&check=f]<br />
| hostinterface=USB2.0<br />
| usbid=0413:6029<br />
| hw=[[Afatech AF9015]], [[NXP/Philips_TDA182xx|NXP/Philips TDA18271]]<br />
| tuner=tda18271<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=dvb-usb-af9015.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== lifeview-lv5t ====<br />
{{DeviceDisplayMedium|lifeview-lv5t}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=lifeview-lv5t<br />
| vendor=[[LifeView]]<br />
| device=LV5T<br />
| standard=DVB-T<br />
| supported={{Supported_in_HG|since=2008-09}}<br />
| pic=<br />
| url=[http://www.lifeview.hk/e/product/product_detail.asp?sku=14]<br />
| hostinterface=USB2.0<br />
| usbid=<br />
| hw=[[Afatech AF9015]], [[NXP/Philips_TDA182xx|NXP/Philips TDA18271HD/C1]]<br />
| tuner=tda18271<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw] (latest one works)<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== msi-digivox-duo ====<br />
{{DeviceDisplayMedium|msi-digivox-duo}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=msi-digivox-duo<br />
| vendor=[[MSI]]<br />
| device=DIGIVOX Duo<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=<br />
| url=[http://eu.msi.com/index.php?func=proddesc&maincat_no=132&prod_no=1409]<br />
| hostinterface=USB2.0<br />
| usbid=1462:8801<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=dual tuner<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== msi-digivox-mini-ii-v3-15a4-9016 ====<br />
{{DeviceDisplayMedium|msi-digivox-mini-ii-v3-15a4-9016}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=msi-digivox-mini-ii-v3-15a4-9016<br />
| vendor=[[MSI]]<br />
| device=[[MSI DigiVox mini II V3.0|DIGIVOX mini II V3.0 (AF9015/MT2060 version) aka. K-Vox]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=[[image:Dvb-t-usb-msi-digivox-ii-rev3-001.jpg|120px]]<br />
| url=[http://www.msi.com/index.php?func=proddesc&prod_no=1262&maincat_no=132&cat2_no=260]<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=15a4:9016<br />
| hw=[[Afatech AF9015]], [[Microtune MT2060]]<br />
| tuner=mt2060<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=Manufacturer changed device but kept name, ARGH!! See device page for details.<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== msi-digivox-mini-ii-v3-1d19-1101 ====<br />
{{DeviceDisplayMedium|msi-digivox-mini-ii-v3-1d19-1101}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=msi-digivox-mini-ii-v3-1d19-1101<br />
| vendor=[[MSI]]<br />
| device=[[MSI DigiVox mini II V3.0|DIGIVOX mini II V3.0 (RTL2832 version) also. DigiVox mini deluxe]]<br />
| standard=DVB-T<br />
| supported={{yes}} somewhat. see device page<br />
| pic=[[image:Dvb-t-usb-msi-digivox-ii-rev3-001.jpg|120px]]<br />
| url=[http://www.msi.com/index.php?func=proddesc&prod_no=1262&maincat_no=132&cat2_no=260]<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=1d19:1101<br />
| hw=[[RealTek RTL2832U]], FCI FC2580 <br />
| tuner=fc2580<br />
| demodulator=<br />
| usbbridge=rtl2832<br />
| fw=n/a<br />
| comment=Manufacturer changed device but kept name, ARGH!! See device page for details.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== msi-digivox-mini-iii ====<br />
{{DeviceDisplayMedium|msi-digivox-mini-iii}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=msi-digivox-mini-iii<br />
| vendor=[[MSI]]<br />
| device=[[MSI DIGIVOX mini III|DIGIVOX mini III]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=[[image:MSI_DIGIVOX_mini_III.jpg|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1462:8807<br />
| hw=[[Afatech AF9015|Afatech AF9015A]], [[NXP/Philips_TDA182xx|NXP/Philips TDA18211HD]]<br />
| tuner=tda18271<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== peak-203244 ====<br />
{{DeviceDisplayMedium|peak-203244}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=peak-203244<br />
| vendor=Peak<br />
| device=203244AGPK DVB-T Digital TV USB Stick<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.30}}<br />
| pic=[[Image:Peak-203244agpk.jpg|120px]]<br />
| url=[http://www.peakhardware.com/products/productdetail.asp?PAID=390]<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=<br />
| hw=[[Afatech AF9015]], [[Quantek QT1010]]<br />
| tuner=qt1010?<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=Identifies as "KWorld USB DVB-T TV Stick II (VS-DVB-T 395U)". Board has "DVBT-395U REV D" stamped on it, beneath casing.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== pinnacle-71e ====<br />
{{DeviceDisplayMedium|pinnacle-71e}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=pinnacle-71e<br />
| vendor=[[Pinnacle]]<br />
| device=PCTV 71e<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=2304:022b<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=dvb-usb-af9015.fw<br />
| comment=Sometimes called "Pinnacle Dazzle 71e"<br />
}}<br />
</includeonly><noinclude><br />
==== sveon-stv22-dual-usb2 ====<br />
{{DeviceDisplayMedium|sveon-stv22-dual-usb2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=sveon-stv22-dual-usb2<br />
| vendor=[[Sveon]]<br />
| device=[[Sveon STV22]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=3.1}}<br />
| pic=[[Image:sveonstv22.png|120px]]<br />
| url=[http://www.sveon.com/fichaSTV22.html]<br />
| hostinterface=USB2.0<br />
| usbid=1b80:0x401<br />
| hw=Afatech AF9013/[[Afatech AF9015]]/2x [[MXL5003S]]<br />
| tuner=mxl5003s<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=KWorld USB Dual DVB-T TV Stick (DVB-T 399U) clone<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== szforward-eztv859 ====<br />
{{DeviceDisplayMedium|szforward-eztv859}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=szforward-eztv859<br />
| vendor=Shenzhen Forward Video<br />
| device=EzTV859<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=<br />
| url=[http://www.szforwardvideo.com/product/Pro_4_7.html] [http://www.made-in-china.com/china-products/productviewoMhxCZOdyfcR/Wand-TV-DVB-T-Stick-A15-.html]<br />
| hostinterface=USB2.0<br />
| usbid=<br />
| hw=[[Afatech AF9015]]<br />
| tuner=mt2060<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=sold under lots of different names like "WandTV", "EzTV A15", "EzTV DUTV007A" - '''Note, some may now be AF9035, which are UNSUPPORTED'''<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== telstar-starstick2 ====<br />
{{DeviceDisplayMedium|telstar-starstick2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=telstar-starstick2<br />
| vendor=Telstar<br />
| device=Starstick 2<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=10b9:8000<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== terratec-trc-mk2 ====<br />
{{DeviceDisplayMedium|terratec-trc-mk2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-trc-mk2<br />
| vendor=[[TerraTec]]<br />
| device=[[TerraTec Cinergy T USB RC|Cinergy T USB RC (mk II)]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.37}}<br />
| pic=[[image:Dvb-t-usb-terratec-cinergy-T-RC-mk2-001.jpg|120px]]<br />
| url=[http://www.terratec.net/en/products/Cinergy_T_Stick_RC_97818.html]<br />
| hostinterface=USB2.0<br />
| usbid=0ccd:0097<br />
| hw=[[Afatech AF9015|Afatech AF9015A]] + TDA18218HN + EM24C02A<br />
| tuner=TDA18218HN<br />
| demodulator=af9015A<br />
| usbbridge=af9015A<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== terratec-txe-rev2 ====<br />
{{DeviceDisplayMedium|terratec-txe-rev2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-txe-rev2<br />
| vendor=[[TerraTec]]<br />
| device=[[TerraTec Cinergy T USB XE|Cinergy T USB XE (rev2)]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=[[image:Dvb-t-usb-terratec-cinergy-t-usb-xe-001.jpg|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0ccd:0069<br />
| hw=[[Afatech AF9015|Afatech AF9015A]], Freescale mc44s803<br />
| tuner=mc44s803<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=The AF9015 version has the CE Symbol on the sticker<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== terratec-dual-rc ====<br />
{{DeviceDisplayMedium|terratec-dual-rc}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-dual-rc<br />
| vendor=[[TerraTec]]<br />
| device=[[TerraTec Cinergy T USB Dual RC|Cinergy T USB Dual RC]]<br />
| standard=DVB-T<br />
| supported= {{Supported in Kernel|since=2.6.37|file=drivers/media/dvb/dvb-usb/af9015.c}}<br />
| pic=<br />
| url=[http://www.terratec.net/de/produkte/Cinergy_T_Stick_Dual_RC_102260.html]<br />
| hostinterface=USB2.0<br />
| usbid=0ccd:0099<br />
| hw=[[Afatech AF9015|Afatech AF9013A]], MaxLinear MxL5007T<br />
| tuner=MaxLinear MxL5007T<br />
| demodulator=af9013<br />
| usbbridge=af9013<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=Dual Receivers (one for viewing and one for recording [http://linux.terratec.de/tv_en.html TerraTec Linux Driver Information]<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== tevion-dk-5203 ====<br />
{{DeviceDisplayMedium|tevion-dk-5203}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=tevion-dk-5203<br />
| vendor=Tevion<br />
| device=DK-5203<br />
| standard=DVB-T<br />
| supported={{Supported_in_HG|since=2008-09}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=<br />
| hw=[[Afatech AF9015]]<br />
| tuner=tda18271<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=also sold as Elements DK-5203<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== trekstor-dvb-t-usb ====<br />
{{DeviceDisplayMedium|trekstor-dvb-t-usb}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=trekstor-dvb-t-usb<br />
| vendor=TrekStor<br />
| device=DVB-T USB Stick<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.30}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=15a4:901b<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== tvisto-t523 ====<br />
{{DeviceDisplayMedium|tvisto-dvbusb-white}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=tvisto-t523<br />
| vendor=TVISTO<br />
| device=[[TVISTO_DVB-T_USB|TVT-DVBTUSB]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=[[Image:Tvisto_USB_DVB-T_15a4-9016.png|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=15a4:9016<br />
| hw=[[Afatech AF9015]], [[Quantek QT1010]]<br />
| tuner=qt1010<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=In the reverse shows "DVB-T TV STICK T523".<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== tvisto-dvbusb-black ====<br />
{{DeviceDisplayMedium|tvisto-dvbusb-black}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=tvisto-dvbusb-black<br />
| vendor=TVISTO<br />
| device=[[TVISTO_DVB-T_USB|TVT-DVBTUSB]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=[[Image:TVISTO_new_black_DVB-T_USB.png|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=<br />
| hw=[[Afatech AF9015|Afatech AF9015]], [[Microtune_MT2060|Microtune MT2060]]<br />
| tuner=mt2060<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== tvisto-unknown ====<br />
{{DeviceDisplayMedium|tvisto-unknown}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=tvisto-unknown<br />
| vendor=TVISTO<br />
| device=[[TVISTO_DVB-T_USB|TVT-DVBTUSB]]<br />
| standard=DVB-T<br />
| supported=?<br />
| pic=[[Image:Tvisto-unknown.png|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=<br />
| hw=<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=<br />
| fw=<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== twinhan-ad-tu700 ====<br />
{{DeviceDisplayMedium|twinhan-ad-tu700}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=twinhan-ad-tu700<br />
| vendor=TwinHan<br />
| device=AzureWave AD-TU700(704J)<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=13d3:3237<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== xtensions-xd-380 ====<br />
{{DeviceDisplayMedium|xtensions-xd-380}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=xtensions-xd-380<br />
| vendor=Xtensions<br />
| device=XD-380<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1ae7:0381<br />
| hw=[[Afatech AF9015]]<br />
| tuner=<br />
| demodulator=af9015<br />
| usbbridge=af9015<br />
| fw=[http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ dvb-usb-af9015.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== terratec-cinergy-t-stick-rc-hd ====<br />
{{DeviceDisplayMedium|terratec-cinergy-t-stick-rc-hd}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-cinergy-t-stick-rc-hd<br />
| vendor=[[TerraTec]]<br />
| device=Cinergy T Stick RC HD<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.37-rc6}}<br />
| pic=[[image:TerraTec-Cinergy-T-Stick-RC-HD.png|120px]]<br />
| url=[http://www.terratec.net/fr/produkte/Cinergy_T_Stick_RC_HD_97881.html]<br />
| hostinterface=USB2.0<br />
| usbid=0CCD:0097<br />
| hw=[[Afatech AF9015]], Tuner TDA18218<br />
| tuner=TDA18218<br />
| demodulator=af9015<br />
| usbbridge=af901x<br />
| fw=dvb-usb-af9015.fw<br />
| comment=Also known as "Cinergy T RC MKII". On this version the outer package says "Cinergy T RC" and a label on the stick itself says "MKII". Support for new tuner TDA18218 [http://www.spinics.net/lists/linux-media/msg22084.html] is working with 2.6.37-rc6. <br />
}}<br />
<br />
</includeonly><noinclude><br />
==== terratec-cinergy-t-stick-rc-hd-rev3 ====<br />
{{DeviceDisplayMedium|terratec-cinergy-t-stick-rc-hd-rev3}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-cinergy-t-stick-rc-hd-rev3<br />
| vendor=[[TerraTec]]<br />
| device=Cinergy T Stick RC HD (rev3)<br />
| standard=DVB-T<br />
| supported={{Supported in External|since=2012-05-07|url=http://www.linuxtv.org/wiki/index.php/TerraTec_Cinergy_T_USB_RC_HD}} <br />
| pic=[[image:Terratec_Cinergy_T_USB_RC_HD_front.jpg|120px]]<br />
| url=[]<br />
| hostinterface=USB2.0<br />
| usbid=0CCD:00D3<br />
| hw=[[RealTek RTL2832U]], Tuner E4000<br />
| tuner=E4000<br />
| fw=none<br />
| comment=working with linux-libre 3.2.1 and Ambrosa's RTL2832U driver patched with the USB id. RC not tested. <br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== AF9035 Devices ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== asus-my-cinema-u3100-mini-plus ====<br />
{{DeviceDisplayMedium|asus-my-cinema-u3100-mini-plus}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=asus-my-cinema-u3100-mini-plus<br />
| vendor=[[ASUS]]<br />
| device=[[Asus U3100 Mini plus DVB-T|My Cinema U3100 Mini Plus DVBT Tuner]]<br />
| standard=DVB-T<br />
| supported={{yes}},{{Supported in Kernel|since=3.7}}<br />
| pic=[[image:Asus_U3100_Mini_plus_DVB-T_01.JPG|120px]]<br />
| url=[http://www.asus.com/Multimedia/TV_Tuner/My_CinemaU3100MINI_PLUSTRC/]<br />
| hostinterface=USB2.0<br />
| usbid=0b05:1779<br />
| hw=[[Afatech AF9035]]<br />
| tuner=FCI2580<br />
| demodulator=af9033<br />
| usbbridge=af9035<br />
| fw=[http://palosaari.fi/linux/v4l-dvb/firmware/af9035/]<br />
| comment=There's an [[ASUS My Cinema-U3100 Mini|older device]] by almost the same name (without the "plus"), which is dib7xxx based and works out of the box.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== asus-my-cinema-u3100-mini-plus-v2 ====<br />
{{DeviceDisplayMedium|asus-my-cinema-u3100-mini-plus-v2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=asus-my-cinema-u3100-mini-plus-v2<br />
| vendor=[[ASUS]]<br />
| device=[[Asus U3100 Mini Plus V2|My Cinema U3100 Mini Plus V2]]<br />
| standard=DVB-T<br />
| supported={{yes}}<br />
| pic=[[image:Dvb-t_asus_u3100mini_plus_v2.JPG|120px]]<br />
| url=[http://www.asus.com/Multimedia/ASUS_U3100MINI_PLUS_V2_Digital_TV_Stick/]<br />
| hostinterface=USB2.0<br />
| usbid=1b80:d393<br />
| hw=[[RealTek RTL2832U|Afatech DVB-T receiver [RTL2832U]]]<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=<br />
| fw=<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== terratec-cinergy-t-stick-af9035 ====<br />
{{DeviceDisplayMedium|terratec-cinergy-t-stick-af9035}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-cinergy-t-stick-af9035<br />
| vendor=[[TerraTec]]<br />
| device=[[TerraTec Cinergy T Stick|Cinergy T Stick]]<br />
| standard=DVB-T<br />
| supported={{yes}}, but see device page for details.<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0ccd:00aa<br />
| hw=[[Afatech AF9035]], TUA9001<br />
| tuner=tua9001<br />
| demodulator=af9035<br />
| usbbridge=af903x<br />
| fw=<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== ezcap-afatech-9035 ====<br />
{{DeviceDisplayMedium|ezcap-afatech-9035}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=ezcap-afatech-9035<br />
| vendor=EzCap<br />
| device=[[EzCap_DVB_T_Stick|DVB-T USB2.0 stick]]<br />
| standard=DVB-T<br />
| supported={{yes}}, but see device page for details.<br />
| pic=[[Image:EzTV_USB_DVB-T_internals_3243.jpg|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=15a4:1001<br />
| hw=[[Afatech AF9035]]<br />
| tuner=fc0011<br />
| demodulator=af9035<br />
| usbbridge=af903x<br />
| fw=<br />
| comment=Sold as '''Infinity PC-TV Nano DVB-T USB stick''' (at least in Croatia) and as '''Blaze HDTV Tuner''' in Australia. An '''EzCAP USB 2.0 DVB-T Stick''' exist with rtl2832u chipset.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== msi-digivox-mini-hybrid ====<br />
{{DeviceDisplayMedium|msi-digivox-mini-hybrid}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=msi-digivox-mini-hybrid<br />
| vendor=[[MSI]]<br />
| device=DIGIVOX mini Hybrid<br />
| standard=DVB-T, ANALOG<br />
| supported={{no}}<br />
| pic=[http://de.msi.com/pic/product/five_pictures1_100045_20110512165012.jpg]<br />
| url=[http://de.msi.com/product/mm/DigiVox-mini-Hybrid.html]<br />
| hostinterface=USB2.0<br />
| usbid=1d6b:0001 or 15a4:1003<br />
| hw=[[Afatech AF9035]], Trident AVF4910B<br />
| tuner=xc3028L<br />
| demodulator=af9035<br />
| usbbridge=af903x<br />
| fw=<br />
| comment=Product number S36-0400132-K36. Sometimes called "DIGIVOX mini II Hybrid". This device is also called ":Zolid Hybrid TV Stick, sold by the Aldi in the Netherlands. [[Image:Digivox-mini-hybrid-top.jpg|120px]] [[Image:Digivox-mini-hybrid-bottom.jpg|120px]]<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== avermedia-a867 ====<br />
{{DeviceDisplayMedium|avermedia-a867}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=avermedia-a867<br />
| vendor=[[AVerMedia]]<br />
| device=AVerTV Volar HD Nano (A867)<br />
| standard=DVB-T<br />
| supported={{yes}}, using (unstable) driver from avermedia<br />
| pic=[[http://www.avermedia.com/avertv/Upload/ProductImages/A867R+RMWEB.jpg]] [[Image:avermedia-a867r+rc.jpg|120px]]<br />
| url=[http://www.avermedia.com/avertv/product/ProductDetail.aspx?Id=516]<br />
| hostinterface=USB2.0<br />
| usbid=07ca:0337 07ca:1867<br />
| hw=[[Afatech AF9035]]<br />
| tuner=mxl5007t<br />
| demodulator=af9035<br />
| usbbridge=af903x<br />
| fw=<br />
| comment=The hardware internals list may not be correct - the original driver (from avermedia) contains references to AF9007 and mxl5007(t). USB device 0x1867 is confirmed to have tuner mxl5007t. The original driver seems to not cope well with the usb device removal, though the playback worked. [[Image:avermedia-a867r-internals-front.jpg|120px]] [[Image:avermedia-a867r-internals-rear.jpg|120px]]<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== terratec-t6 ====<br />
{{DeviceDisplayMedium|terratec-t6}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-t6<br />
| vendor=[[TerraTec]]<br />
| device=[[TerraTec_T6_Dual_DVB-T_Stick|T6 Dual DVB-T Stick]]<br />
| standard=DVB-T<br />
| supported={{yes}}, but see device section for details<br />
| pic=[[Image:terratec-t6+rc.jpg|120px]]<br />
| url=[http://www.terratec.net/en/products/TERRATEC_T6_147823.html?premium=1]<br />
| hostinterface=USB2.0<br />
| usbid=0ccd:10b3<br />
| hw=[[Afatech AF9035]]<br />
| tuner=fc0012 (2 off)<br />
| demodulator=af9035+af9033<br />
| usbbridge=af9035<br />
| fw=<br />
| comment=rc seems not to work atm.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== terratec-tc2 ====<br />
{{DeviceDisplayMedium|terratec-tc2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-t6<br />
| vendor=[[TerraTec]]<br />
| device=[[TerraTec_Cinergy_TC2_DVB-T2_Stick|Cinergy TC2 DVB-T2 Stick]]<br />
| standard=DVB-T<br />
| supported={{no}}, but see device section for details<br />
| pic=<br />
| url=[https://www.terratec.de/details.php?artnr=193534]<br />
| hostinterface=USB2.0<br />
| usbid=0ccd:10b2<br />
| hw=[[Afatech AF9035]], it9303<br />
| tuner=fc0012 (2 off)<br />
| demodulator=af9035+it9303<br />
| usbbridge=af9035<br />
| fw=<br />
| comment=patch available https://cesbo.com/forum/topic/3557-terratec-electronic-gmbh-cinergy-tc2-stick/.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== Anysee E30 Devices ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== anysee-e30-dvb-t ====<br />
{{DeviceDisplayMedium|anysee-e30-dvb-t}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=anysee-e30-dvb-t<br />
| vendor=[[Anysee]]<br />
| device=[[Anysee E30|E30]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.27}}<br />
| pic=<br />
| url=[http://www.anysee.com/eng/product/anyseeE30.php]<br />
| hostinterface=USB2.0<br />
| usbid=1c73:861f or 04b4:861f<br />
| comment=Need clarification which "usbid" comes with which E30 device.<br />
| tuner=<br />
| demodulator=mt352 zl10353<br />
| usbbridge=<br />
| hw=mt352 or zl10353 demodulator<br />
| fw=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== anysee-e30-plus-dvb-t ====<br />
{{DeviceDisplayMedium|anysee-e30-plus-dvb-t}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=anysee-e30-plus-dvb-t<br />
| vendor=[[Anysee]]<br />
| device=[[Anysee E30|E30 Plus]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.27}}<br />
| pic=<br />
| url=[http://www.anysee.com/eng/product/anyseeE30Plus.php]<br />
| hostinterface=USB2.0<br />
| usbid=1c73:861f or 04b4:861f<br />
| comment=<br />
| tuner=<br />
| demodulator=zl10353<br />
| usbbridge=<br />
| hw=zl10353 demodulator<br />
| fw=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== anysee-e30-combo-plus-dvb-tc ====<br />
{{DeviceDisplayMedium|anysee-e30-combo-plus-dvb-tc}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=anysee-e30-combo-plus-dvb-tc<br />
| vendor=[[Anysee]]<br />
| device=[[Anysee E30|E30 Combo Plus]]<br />
| standard=DVB-T DVB-C<br />
| supported={{Supported_in_Kernel|since=2.6.28}}<br />
| pic=<br />
| url=[http://www.anysee.com/eng/product/anyseeE30ComboPlus.php]<br />
| hostinterface=USB2.0<br />
| usbid=1c73:861f or 04b4:861f<br />
| comment=Does DVB-T and DVB-C depending on ''anysee.ko'' module parameter ''delsys='' (0=DVB-C, 1=DVB-T).<br />
| tuner=<br />
| demodulator=zl10353 tda10023<br />
| usbbridge=<br />
| hw=zl10353 or tda10023 demodulator<br />
| fw=<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
=== au6610 devices ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== sigmatek-dvb-110 ====<br />
{{DeviceDisplayMedium|sigmatek-dvb-110}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=sigmatek-dvb-110<br />
| vendor=Sigmatek<br />
| device=DVB-110<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.21}}<br />
| pic=[[image:Sigmatek DVB-110 001 stripped.jpg|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=058f:6610<br />
| hw=Qtuantek QT1010 tuner, Zarlink ZL10353 (Intel CE 6353) demodulator and Alcor Micro AU6610 DVB-T USB controller<br />
| tuner=qt1010<br />
| demodulator=zl10353<br />
| usbbridge=au6610<br />
| fw=none needed<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== EC168 devices ===<br />
* Tvisto DVB-T USB<br />
* Genius TVGo DVB-T02PRO<br />
* ...<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
<br />
==== tvisto-dvbusb-ec168 ====<br />
{{DeviceDisplayMedium|tvisto-dvbusb-ec168}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=tvisto-dvbusb-ec168<br />
| vendor=[[TVISTO]]<br />
| device=[[TVISTO_DVB-T_USB|TVT-DVBTUSB]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.33|file=drivers/media/dvb/dvb-usb/ec168.c}} <br />
| pic=[[Image:Tvisto_USB_DVB-T_15a4-9016.png|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=18b4:fffa<br />
| hw=[[MXL5003S]], [[E3C EC168]]<br />
| tuner=mxl5003s<br />
| demodulator=ec168<br />
| usbbridge=ec168<br />
| fw=<br />
| comment=It has [[MXL5003S]] and a [[E3C EC168]] X***98501T" (I couldn't read all numbers, they were deleted). In reverse (inside in the circuit) It has "4407 ver 2.0"<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== genius-tvgo-t02-ec168 ====<br />
{{DeviceDisplayMedium|genius-tvgo-t02-ec168}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=genius-tvgo-t02-ec168<br />
| vendor=Genius<br />
| device=[[Genius TVGo DVB-T02PRO|TVGo DVB-T02]]<br />
| standard=DVB-T<br />
| supported={{no}}<br />
| pic=[[Image:Genius_-_TVGo_DVB-T02Q_MCE_pcb_front.jpg|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0458:400f<br />
| hw=[[E3C EC168]], [[Microtune MT2060|MT2060]]<br />
| tuner=mt2061f<br />
| demodulator=ec168<br />
| usbbridge=ec168<br />
| fw=<br />
| comment=EC168 is supported only for usb ID 18b4:xxxx and only in combination with tuner MXL5003S since Kernel=2.6.33<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== IT9135 Devices ===<br />
{{DeviceDisplayMedium|IT9135}}<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== digitalnow-tinytwin-v3a ====<br />
{{DeviceDisplayMedium|digitalnow-tinytwin-v3a}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=digitalnow-tinytwin-v3a<br />
| vendor=DigitalNow<br />
| device=[[DigitalNow TinyTwin DVB-T Receiver|TinyTwin DVB-T Receiver V3a]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=3.15}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=048d:9006<br />
| hw=[[ITE IT9135|IT9135]]<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=IT9135<br />
| fw=[http://palosaari.fi/linux/v4l-dvb/firmware/IT9135/ dvb-usb-it9135-02.fw]<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== kworld-ub499-2t-9135 ====<br />
{{DeviceDisplayMedium|kworld-ub499-2t-9135}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=kworld-ub499-2t-9135<br />
| vendor=[[KWorld]]<br />
| device=[[Kworld UB499-2T|UB499-2T]]<br />
| standard=DVB-T<br />
| supported=See Device page. IT9135 {{Yes}} from Kernel 3.2<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=048d:9135<br />
| hw=[[ITE IT9135]]<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=IT9135<br />
| fw=dvb-usb-it9135-01.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== kworld-ub499-2t-9137 ====<br />
{{DeviceDisplayMedium|kworld-ub499-2t-9137}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=kworld-ub499-2t-9137<br />
| vendor=[[KWorld]]<br />
| device=[[Kworld UB499-2T|UB499-2T T09]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=3.2}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1b80:e409<br />
| hw=[[ITE IT9135|IT9137]]<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=IT9137<br />
| fw=dvb-usb-it9137-01.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== szforward-eztv868 ====<br />
{{DeviceDisplayMedium|szforward-eztv868}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=szforward-eztv868<br />
| vendor=Shenzhen Forward Video<br />
| device=EzTV868<br />
| standard=DVB-T<br />
| supported=See [[Kworld UB499-2T|UB499-2T]]<br />
| pic=<br />
| url=[http://www.szforwardvideo.com/product/Pro_9_7.html] [http://forwardvideo.manufacturer.globalsources.com/si/6008824871654/pdtl/USB-DVB/1024000074/USB-DVB-T-Device.htm]<br />
| hostinterface=USB2.0<br />
| usbid=048d:9006<br />
| hw=ITE IT9135<br />
| tuner=IT9135<br />
| demodulator=IT9135<br />
| usbbridge=<br />
| fw=<br />
| comment=Has the labels "MinTV DVB-T, digital terrestrial TV Stick" and "MinTV-DVB-T Stick" and no other markings on the case.<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== zolid-mini-dvb-t-stick-v1 ====<br />
{{DeviceDisplayMedium|zolid-mini-dvb-t-stick-v1}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=zolid-mini-dvb-t-stick-v1<br />
| vendor=ITE Inc.<br />
| device=Zolid Mini DVB-T Stick<br>Version 1<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=3.2}}<br>Chip Version 1<br />
| pic=[[image:Mini.jpg|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=048d:9135<br />
| hw=[[ITE IT9135|IT9135]]<br />
| tuner=IT9135_38<br />
| demodulator=IT9135<br />
| usbbridge=IT9135<br />
| fw=from 3.3<br>dvb-usb-it9135-01.fw<br>Kernel 3.2 uses<br>dvb-usb-it9137-01.fw<br />
| comment= Markings Mini DVB T <br />
}}<br />
<br />
</includeonly><noinclude><br />
==== zolid-mini-dvb-t-stick-v2 ====<br />
{{DeviceDisplayMedium|zolid-mini-dvb-t-stick-v2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=zolid-mini-dvb-t-stick-v2<br />
| vendor=ITE Inc.<br />
| device=[[Zolid Mini DVB-T Stick]]<br>Version 2<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=3.4}}<br>Chip Version 2<br />
| pic=[[image:Zolid-DVB-T-USB-Tuner-Top-C-512.png|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=048d:9135<br />
| hw=[[ITE IT9135|IT9135]]<br />
| tuner=IT9135_60<br />
| demodulator=IT9135<br />
| usbbridge=IT9135<br />
| fw=dvb-usb-it9135-02.fw <br />
| comment= Markings HDTV USB DVB -T<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== ite-9005-dvb-t-stick ====<br />
{{DeviceDisplayMedium|ite-9005-dvb-t-stick}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=ite-9005-dvb-t-stick<br />
| vendor=ITE Inc.<br />
| device=Generic 9005 Device<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=3.3}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=048d:9005<br />
| hw=[[ITE IT9135|IT9135]]<br />
| tuner=IT9135_38<br />
| demodulator=IT9135<br />
| usbbridge=IT9135<br />
| fw=dvb-usb-it9135-01.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== ite-9006-dvb-t-stick ====<br />
{{DeviceDisplayMedium|ite-9006-dvb-t-stick}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=ite-9006-dvb-t-stick<br />
| vendor=ITE Inc.<br />
| device=Generic 9006 Device<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=3.3}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=048d:9006<br />
| hw=[[ITE IT9135|IT9135]]<br />
| tuner=IT9135_60<br />
| demodulator=IT9135<br />
| usbbridge=IT9135<br />
| fw=dvb-usb-it9135-02.fw<br />
| comment= Marking Various - RTK<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== sveon-stv22-dual-dvb-t-hdtv ====<br />
{{DeviceDisplayMedium|sveon-stv22-dual-dvb-t-hdtv}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=sveon-stv22-dual-dvb-t-hdtv<br />
| vendor=Sveon<br />
| device=STV22 Dual DVB-T HDTV<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=3.2}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1b80:e411<br />
| hw=[[ITE IT9135|IT9137]]<br />
| tuner=IT9135_38<br />
| demodulator=IT9135<br />
| usbbridge=IT9137<br />
| fw=dvb-usb-it9137-01.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== Intel CE6230 based receivers ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== intel-ce9500-reference ====<br />
{{DeviceDisplayMedium|intel-ce9500-reference}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=intel-ce9500-reference<br />
| vendor=[[Intel]]<br />
| device=[[Noname CE6230 OEM|CE9500 reference design / CE6230 noname devices]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.30|file=drivers/media/dvb/dvb-usb/ce6230.c}}<br />
| pic=[[image:Intel CE6230 1.jpg|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=8086:9500<br />
| hw=mxl5003s, ce6230 (zl10353)<br />
| tuner=mxl5003s<br />
| demodulator=zl10353<br />
| usbbridge=ce6230<br />
| fw=none needed<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== avermedia-a310 ====<br />
{{DeviceDisplayMedium|avermedia-a310}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=avermedia-a310<br />
| vendor=[[AVerMedia]]<br />
| device=A310 USB 2.0 DVB-T tuner<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.30}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=07ca:a310<br />
| hw=mxl5003s, zl10353<br />
| tuner=mxl5003s<br />
| demodulator=zl10353<br />
| usbbridge=ce6230<br />
| fw=none needed<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== TerraTec Cinergy T² ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== terratec-cinergy-t2 ====<br />
{{DeviceDisplayMedium|terratec-cinergy-t2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-cinergy-t2<br />
| vendor=[[TerraTec]]<br />
| device=[[TerraTec_Cinergy_T2|Cinergy T2]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.12}}<br />
| pic=<br />
| url=[http://tvde.terratec.net/modules.php?op=modload&name=News&file=article&sid=238]<br />
| hostinterface=USB2.0<br />
| usbid=0ccd:0038<br />
| hw=[[Zarlink MT352]]<br />
| tuner=<br />
| demodulator=mt352<br />
| usbbridge=<br />
| fw=<br />
| comment=Aka. "Cinergy T²" (T-square).<br />
}}<br />
<br />
</includeonly><noinclude><br />
=== cxusb ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== medion-md95700 ====<br />
{{DeviceDisplayMedium|medion-md95700}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=medion-md95700<br />
| vendor=Medion<br />
| device=MD95700 (MDUSBTV-HYBRID)<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1660:0932<br />
| hw=<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=<br />
| fw=none<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== dvico-fusion-hdtv-5-gold ====<br />
{{DeviceDisplayMedium|dvico-fusion-hdtv-5-gold}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dvico-fusion-hdtv-5-gold<br />
| vendor=[[DViCO]]<br />
| device=[[DViCO FusionHDTV 5 USB Gold|FusionHDTV 5 USB Gold]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.16}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0fe9:d500<br />
| hw=<br />
| tuner=lgh064f<br />
| demodulator=lgdt3303<br />
| usbbridge=<br />
| fw=dvb-usb-bluebird-01.fw<br />
| comment=warm usbid 0fe9:d700<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== dvico-fusion-hdtv-dual-1 ====<br />
{{DeviceDisplayMedium|dvico-fusion-hdtv-dual-1}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dvico-fusion-hdtv-dual-1<br />
| vendor=[[DViCO]]<br />
| device=[[DViCO FusionHDTV DVB-T Dual USB|FusionHDTV DVB-T Dual USB]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.16}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0fe9:db50<br />
| hw=<br />
| tuner=dee1601<br />
| demodulator=dee1601<br />
| usbbridge=<br />
| fw=<br />
| comment=warm usbid 0fe9:db51<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== dvico-fusion-hdtv-lgz201 ====<br />
{{DeviceDisplayMedium|dvico-fusion-hdtv-lgz201}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dvico-fusion-hdtv-lgz201<br />
| vendor=[[DViCO]]<br />
| device=[[DViCO FusionHDTV DVB-T USB (LGZ201)|FusionHDTV DVB-T USB (LGZ201)]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.16}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0fe9:db00<br />
| hw=<br />
| tuner=lgz201<br />
| demodulator=mt352<br />
| usbbridge=<br />
| fw=dvb-usb-bluebird-01.fw<br />
| comment=0fe9:db01<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== dvico-fusion-hdtv-th7579 ====<br />
{{DeviceDisplayMedium|dvico-fusion-hdtv-th7579}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dvico-fusion-hdtv-th7579<br />
| vendor=[[DViCO]]<br />
| device=[[DViCO FusionHDTV DVB-T USB (TH7579)|FusionHDTV DVB-T USB (TH7579)]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.16}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0fe9:db10<br />
| hw=<br />
| tuner=dtt7579<br />
| demodulator=mt352<br />
| usbbridge=<br />
| fw=dvb-usb-bluebird-01.fw<br />
| comment=0fe9:db11<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== digitalnow-dee1601-dual ====<br />
{{DeviceDisplayMedium|digitalnow-dee1601-dual}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=digitalnow-dee1601-dual<br />
| vendor=[[DigitalNow]]<br />
| device=DVB-T Dual USB<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.16}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0fe9:db54<br />
| hw=<br />
| tuner=dee1601<br />
| demodulator=dee1601<br />
| usbbridge=<br />
| fw=<br />
| comment=warm usbid 0fe9:db54<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== dvico-fusion-hdtv-dual-2 ====<br />
{{DeviceDisplayMedium|dvico-fusion-hdtv-dual-2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dvico-fusion-hdtv-dual-2<br />
| vendor=[[DViCO]]<br />
| device=[[DViCO FusionHDTV DVB-T Dual Digital 2|FusionHDTV DVB-T Dual Digital 2]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.19}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0fe9:db58<br />
| hw=<br />
| tuner=dee1601<br />
| demodulator=dee1601<br />
| usbbridge=<br />
| fw=<br />
| comment=warm usbid 0fe9:db59<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== dvico-fusion-hdtv-dual-4-rev1 ====<br />
{{DeviceDisplayMedium|dvico-fusion-hdtv-dual-4-rev1}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dvico-fusion-hdtv-dual-4-rev1<br />
| vendor=[[DViCO]]<br />
| device=[[FusionHDTV DVB-T Dual Digital 4|FusionHDTV DVB-T Dual Digital 4]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.25}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0fe9:db78<br />
| hw=<br />
| tuner=xc3028<br />
| demodulator=zl10353<br />
| usbbridge=<br />
| fw=none needed<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== dvico-fusion-hdtv-nano-1 ====<br />
{{DeviceDisplayMedium|dvico-fusion-hdtv-nano-1}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dvico-fusion-hdtv-nano-1<br />
| vendor=[[DViCO]]<br />
| device=[[DViCO FusionHDTV DVB-T NANO|FusionHDTV DVB-T NANO]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.25}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0fe9:db70<br />
| hw=<br />
| tuner=xc3028<br />
| demodulator=zl10353<br />
| usbbridge=<br />
| fw=none needed<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== dvico-fusion-hdtv-nano-2 ====<br />
{{DeviceDisplayMedium|dvico-fusion-hdtv-nano-2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dvico-fusion-hdtv-nano-2<br />
| vendor=[[DViCO]]<br />
| device=[[DViCO FusionHDTV DVB-T NANO2 w/o firmware|FusionHDTV DVB-T NANO2 w/o firmware]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.25}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0fe9:db70<br />
| hw=<br />
| tuner=xc3028<br />
| demodulator=mt352 or zl10353<br />
| usbbridge=<br />
| fw=dvb-usb-bluebird-02.fw<br />
| comment=0fe9:db71<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== avermedia-a868 ====<br />
{{DeviceDisplayMedium|avermedia-a868}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=avermedia-a868<br />
| vendor=[[AVerMedia]]<br />
| device=AVerTVHD Volar (A868R)<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.27}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=07ca:a868<br />
| hw=<br />
| tuner=mxl5003s<br />
| demodulator=lgdt3303<br />
| usbbridge=<br />
| fw=none needed<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== dvico-fusion-hdtv-dual-4-rev2 ====<br />
{{DeviceDisplayMedium|dvico-fusion-hdtv-dual-4-rev2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dvico-fusion-hdtv-dual-4-rev2<br />
| vendor=[[DViCO]]<br />
| device=[[DViCO FusionHDTV DVB-T Dual Digital 4 (rev 2)|FusionHDTV DVB-T Dual Digital 4 (rev 2)]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.28}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0fe9:db98<br />
| hw=<br />
| tuner=dib0070<br />
| demodulator=dib7000p<br />
| usbbridge=<br />
| fw=none needed<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== [[DiBcom DiB7xxx|DiB0700]] USB2.0 DVB-T devices ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
<br />
==== dibcom-stk7700p-ref ====<br />
{{DeviceDisplayMedium|dibcom-stk7700p-ref}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dibcom-stk7700p-ref<br />
| vendor=[[DiBcom]]<br />
| device=STK7700P reference design<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.19}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=10b8:1e14<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== dibcom-stk7700pc-ref ====<br />
{{DeviceDisplayMedium|dibcom-stk7700pc-ref}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dibcom-stk7700pc-ref<br />
| vendor=[[DiBcom]]<br />
| device=STK7700PC reference design<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.20}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000m<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
==== kaiserbaas-Netbook-TvStick-STK7770P ====<br />
{{DeviceDisplayMedium|kaiserbaas-Netbook-TvStick-STK7770P}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=kaiserbaas-Netbook-TvStick-STK7770P<br />
| vendor=Kaiser Baas<br />
| device=TVStick KBA01007-KB<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.32}}<br />
| pic=[[Image:KB_TVStick.jpeg|120px]]<br />
| hostinterface=USB2.0<br />
| usbid=10b8:1e80<br />
| hw=DiB7770P<br />
| tuner=<br />
| url=[http://www.kaiserbaas.com/kaiser-baas-product-page/tv-tuners/usb-hd-tvstick-tuner-netbook]<br />
| demodulator=dib7000m<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment= This is a clone of the 'DiBcom STK7770P reference design' This netbook version comes with 2gb of storage on the USB and a 28 key slim ir remote control [[http://www.linuxtv.org/wiki/index.php/File:Kaiserbaas-ir-remote.jpeg (image)]]. This remote control is NOT supported by the current DIB0070 driver (at 2.6.35.22) [[http://www.linuxtv.org/pipermail/linux-dvb/2010-November/032782.html]].<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
==== hauppauge-nova-t-stick ====<br />
{{DeviceDisplayMedium|hauppauge-nova-t-stick}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=hauppauge-nova-t-stick<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge WinTV-NOVA-T-Stick|Nova-T Stick]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.19}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2040:7050 2040:7060<br />
| hw=DiB7700M or DiB7700P, MT2060<br />
| tuner=mt2060<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=2040:7060 added in 2.6.20. There are several [[Hauppauge WinTV-NOVA-T-Stick|variants]] by the same name.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== avermedia-avertv-volar ====<br />
{{DeviceDisplayMedium|avermedia-avertv-volar}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=avermedia-avertv-volar<br />
| vendor=[[AVerMedia]]<br />
| device=AVerTV DVB-T Volar<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.19}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=07ca:a807 07ca:b808<br />
| hw=<br />
| tuner=dib0070<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=07ca:b808 since 2.6.20<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== hauppauge-nova-t500-dual ====<br />
{{DeviceDisplayMedium|hauppauge-nova-t500-dual}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=hauppauge-nova-t500-dual<br />
| vendor=[[Hauppauge]]<br />
| device=Nova-T 500 Dual DVB-T<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.19}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2040:9941 2040:9950<br />
| hw=<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
<br />
<br />
</includeonly><noinclude><br />
==== compro-videomate-u500 ====<br />
{{DeviceDisplayMedium|compro-videomate-u500}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=compro-videomate-u500<br />
| vendor=Compro<br />
| device=Videomate U500<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.20}}<br />
| pic=<br />
| url=[http://www.comprousa.com/en/product/u500/u500.html]<br />
| hostinterface=USB2.0<br />
| usbid=185b:1e78 185b:1e80<br />
| hw=<br />
| tuner=mt2060<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=185b:1e80 added in 2.6.24<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== uniwill-stk7700p ====<br />
{{DeviceDisplayMedium|uniwill-stk7700p}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=uniwill-stk7700p<br />
| vendor=Uniwill<br />
| device=STK7700P based (Hama and others)<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.20}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1584:6003<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== leadtek-stk7700p ====<br />
{{DeviceDisplayMedium|leadtek-stk7700p}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=leadtek-stk7700p<br />
| vendor=[[Leadtek]]<br />
| device=Winfast DTV Dongle (STK7700P based)<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.20}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0413:6f00 0413:6f01<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=0413:6f01 added in 2.6.26<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
==== pinnacle-pctv-2000e ====<br />
{{DeviceDisplayMedium|pinnacle-pctv-2000e}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=pinnacle-pctv-2000e<br />
| vendor=[[Pinnacle]]<br />
| device=[[Pinnacle PCTV Dual DVB-T Diversity (2000e)|PCTV 2000e]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.24}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2304:022c<br />
| hw=DiB7700P, Dib 7000P, 2 * MT2266<br />
| tuner=mt2266<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=Dual tuner device. The diversity feature is not supported yet.<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== pinnacle-pctv-dual-diversity-stick ====<br />
{{DeviceDisplayMedium|pinnacle-pctv-dual-diversity-stick}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=pinnacle-pctv-dual-diversity-stick<br />
| vendor=[[Pinnacle]]<br />
| device=[[Pinnacle PCTV Dual DVB-T Diversity Stick (2001e)|PCTV 2001e Dual DVB-T Diversity Stick]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.24}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2304:0229<br />
| hw=DiB0700, 2 * DiB7070P<br />
| tuner=dib0070<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=Dual tuner device. The diversity feature is not supported yet. <br />
}}<br />
<br />
</includeonly><noinclude><br />
==== pctv-2002e ====<br />
{{DeviceDisplayMedium|pctv-2002e}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=pctv-2002e<br />
| vendor=<br />
| device=[[PCTV 2002e]]<br />
| standard=DVB-T<br />
| supported=?<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=????:0x025c<br />
| hw=<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=dib0700<br />
| fw=<br />
| comment=Should be supported soon (writing as of june 30 2013): http://www.mail-archive.com/linux-media@vger.kernel.org/msg63924.html<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== pctv-2002e SE ====<br />
{{DeviceDisplayMedium|pctv-2002eSE}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=pctv-2002eSE<br />
| vendor=<br />
| device=[[PCTV 2002eSE]]<br />
| standard=DVB-T<br />
| supported=?<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=????:0x025d<br />
| hw=<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=dib0700<br />
| fw=<br />
| comment=Should be supported soon (writing as of june 30 2013): http://www.mail-archive.com/linux-media@vger.kernel.org/msg63924.html<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== terratec-dt-xs-diversity ====<br />
{{DeviceDisplayMedium|terratec-dt-xs-diversity}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-dt-xs-diversity<br />
| vendor=[[TerraTec]]<br />
| device=[[TerraTec Cinergy DT USB XS Diversity|Cinergy DT XS Diversity]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.24}}<br />
| pic=<br />
| url=[http://www.terratec.net/en/products/Cinergy_DT_USB_XS_Diversity_1608.html]<br />
| hostinterface=USB2.0<br />
| usbid=0ccd:005a<br />
| hw=DiB7700P, Dib 7000P, 2 * MT2266<br />
| tuner=mt2266<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=Dual tuner device. The diversity feature is not supported yet.<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== hauppauge-nova-td-diversity ====<br />
{{DeviceDisplayMedium|hauppauge-nova-td-diversity}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=hauppauge-nova-td-diversity<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge WinTV-NOVA-TD-Stick|Nova-TD Stick]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.24}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2040:9580<br />
| hw=DiB7700P, Dib 7000P, 2 * MT2266<br />
| tuner=mt2266<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=Dual tuner device. The diversity feature is not supported yet. same as: Elgato Eye-TV Diversity<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== dibcom-stk7700d-ref ====<br />
{{DeviceDisplayMedium|dibcom-stk7700d-ref}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dibcom-stk7700d-ref<br />
| vendor=[[DiBcom]]<br />
| device=STK7700D reference design<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.24}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=10b8:1ef0<br />
| hw=<br />
| tuner=mt2266<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=dual tuner/diversity device <br />
}}<br />
<br />
<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== dibcom-dib7070p-ref ====<br />
{{DeviceDisplayMedium|dibcom-dib7070p-ref}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dibcom-dib7070p-ref<br />
| vendor=[[DiBcom]]<br />
| device=STK7070P reference design<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.24}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=10b8:1ebc<br />
| hw=<br />
| tuner=dib0070<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== pinnacle-pctv-flash-stick ====<br />
{{DeviceDisplayMedium|pinnacle-pctv-flash-stick}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=pinnacle-pctv-flash-stick<br />
| vendor=[[Pinnacle]]<br />
| device=PCTV DVB-T Flash Stick<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.24}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2304:0228<br />
| hw=<br />
| tuner=dib0070<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
<br />
<br />
</includeonly><noinclude><br />
==== dibcom-dib7070pd-ref ====<br />
{{DeviceDisplayMedium|dibcom-dib7070pd-ref}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dibcom-dib7070pd-ref<br />
| vendor=[[DiBcom]]<br />
| device=STK7070PD reference design<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.24}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=10b8:1ebe<br />
| hw=<br />
| tuner=dib0070<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=dual tuner device<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== avermedia-avertv-dvbt-t-express ====<br />
{{DeviceDisplayMedium|avermedia-avertv-dvbt-t-express}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=avermedia-avertv-dvbt-t-express<br />
| vendor=[[AVerMedia]]<br />
| device=AVerTV DVB-T Express<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.24}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=07ca:b568<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== gigabyte-u7000 ====<br />
{{DeviceDisplayMedium|gigabyte-u7000}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=gigabyte-u7000<br />
| vendor=Gigabyte<br />
| device=U7000<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.24}}<br />
| pic=<br />
| url=[http://www.gigabyte.com.tw/Products/TVCard/Products_Spec.aspx?ProductID=2440]<br />
| hostinterface=USB2.0<br />
| usbid=1044:7001<br />
| hw=Microtune 2060, Dibcom 7700 series<br />
| tuner=mt2060<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=[http://osdir.com/ml/linux-media/2009-06/msg01254.html Remote is not working yet.(7.2009)]<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== artec-t14br-dib7xxx-based ====<br />
{{DeviceDisplayMedium|artec-t14br-dib7xxx-based}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=artec-t14br-dib7xxx-based<br />
| vendor=[[Artec]]<br />
| device=T14BR DVB-T<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.25}}<br />
| pic=<br />
| url=[http://www.artec.com.tw/ehtm/products/t14.htm]<br />
| hostinterface=USB2.0<br />
| usbid=05d8:810f<br />
| hw=DiB7070P (DiB7000PC + DiB0070)<br />
| tuner=dib0070<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=[http://www.wi-bw.tfh-wildau.de/~pboettch/home/files/dvb-usb-dib0700-1.20.fw dvb-usb-dib0700-1.20.fw]<br />
| comment=Remote control untested.<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== asus-my-cinema-u3000-mini ====<br />
{{DeviceDisplayMedium|asus-my-cinema-u3000-mini}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=asus-my-cinema-u3000-mini<br />
| vendor=[[ASUS]]<br />
| device=[[ASUS_My_Cinema-U3000_Mini|My Cinema U3000 Mini DVBT Tuner]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.25}}<br />
| pic=[http://www.asus.com/products.aspx?l1=18&l2=84&l3=255&l4=0&model=1298&modelmenu=1]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0b05:171f<br />
| hw=DiB7700P<br />
| tuner=mt2266<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=ASUS also provides drivers for this device through their [http://support.asus.com/download/download.aspx?SLanguage=en-us&model=My%20Cinema-U3000Mini website]<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== asus-my-cinema-u3100-mini-dib ====<br />
{{DeviceDisplayMedium|asus-my-cinema-u3100-mini-dib}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=asus-my-cinema-u3100-mini-dib<br />
| vendor=[[ASUS]]<br />
| device=[[ASUS_My_Cinema-U3100_Mini|My Cinema U3100 Mini DVBT Tuner]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.25}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0b05:173f<br />
| hw=DiB7070P (DiB7000PC + DiB0070)<br />
| tuner=dib0070<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== hauppauge-nova-t-ce-stick ====<br />
{{DeviceDisplayMedium|hauppauge-nova-t-ce-stick}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=hauppauge-nova-t-ce-stick<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge WinTV-NOVA-T-Stick|Nova-T-CE Stick]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.25}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2040:7070<br />
| hw=<br />
| tuner=dib0070<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== hauppauge-nova-t-mytv-t-stick ====<br />
{{DeviceDisplayMedium|hauppauge-nova-t-mytv-t-stick}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=hauppauge-nova-t-mytv-t-stick<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge myTV.t|Nova-T MyTV.t Stick]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.25}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2040:7080<br />
| hw=<br />
| tuner=dib0070<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== terratec-cinergy-ht-usb-xe ====<br />
{{DeviceDisplayMedium|terratec-cinergy-ht-usb-xe}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-cinergy-ht-usb-xe<br />
| vendor=[[TerraTec]]<br />
| device=[[TerraTec Cinergy HT USB XE|Cinergy HT USB XE]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.26}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0ccd:0058<br />
| hw=DiB7700ci tuner:XC3028<br />
| tuner=xc3028<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== pinnacle-expresscard-320cx ====<br />
{{DeviceDisplayMedium|pinnacle-expresscard-320cx}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=pinnacle-expresscard-320cx<br />
| vendor=[[Pinnacle]]<br />
| device=Expresscard 320cx<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.26}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2304:022e<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== pinnacle-pctv-72e ====<br />
{{DeviceDisplayMedium|pinnacle-pctv-72e}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=pinnacle-pctv-72e<br />
| vendor=[[Pinnacle]]<br />
| device=[[Pinnacle PCTV 72e|PCTV 72e]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.26}}<br />
| pic=[http://neduz.be/dvb/pinnacle_pctv_dvb-t_stick_solo.jpg]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2304:0236<br />
| hw=DiB7000PC<br />
| tuner=dib0070<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== pinnacle-pctv-73e-plain ====<br />
{{DeviceDisplayMedium|pinnacle-pctv-73e-plain}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=pinnacle-pctv-73e-plain<br />
| vendor=[[Pinnacle]]<br />
| device=[[Pinnacle PCTV nano Stick (73e)|PCTV 73e]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.26}}<br />
| pic=[http://www.flickr.com/photos/nk-h/2630657143/] [http://www.flickr.com/photos/nk-h/2630658003/]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2304:0237<br />
| hw=DiB7000PC<br />
| tuner=dib0070<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== yuan-ec372s ====<br />
{{DeviceDisplayMedium|yuan-ec372s}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=yuan-ec372s<br />
| vendor=YUAN High-Tech<br />
| device=EC372S<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.26}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1164:1edc<br />
| hw=DiB7700P<br />
| tuner=mt2266<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== terratec-cinergy-ht-express ====<br />
{{DeviceDisplayMedium|terratec-cinergy-ht-express}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-cinergy-ht-express<br />
| vendor=[[TerraTec]]<br />
| device=[[TerraTec Cinergy HT Express|Cinergy HT Express]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.26}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0ccd:0060<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== terratec-cinergy-t-usb-xxs-t3 ====<br />
{{DeviceDisplayMedium|terratec-cinergy-t-usb-xxs-t3}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-cinergy-t-usb-xxs-t3<br />
| vendor=[[TerraTec]]<br />
| device=[[TerraTec Cinergy T USB XXS|Cinergy T USB XXS/ T3]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.26|file=drivers/media/dvb/dvb-usb/dib0700_devices.c}}<br />
| pic=[[image:Terratec Cinergy XXS 001.jpg|120px]] [[image:Terratec T3 001.jpg|120px]] <br />
| url=[http://www.terratec.net/en/products/Cinergy_T_USB_XXS_2068.html] [http://www.terratec.net/en/products/TerraTec_T3_83463.html]<br />
| hostinterface=USB2.0<br />
| usbid=0ccd:0078 0ccd:10a0<br />
| hw=DiB7070P (DiB7000PC + DiB0070)<br />
| tuner=dib0070<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=T3 (0ccd:10a0) added in 2.6.31<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== hauppauge-nova-td-stick-52009 ====<br />
{{DeviceDisplayMedium|hauppauge-nova-td-stick-52009}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=hauppauge-nova-td-stick-52009<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge WinTV-NOVA-TD-Stick|Nova-TD Stick (52009)]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.27}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2040:5200<br />
| hw=<br />
| tuner=dib0070<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== hauppauge-nova-td-500-84xxx ====<br />
{{DeviceDisplayMedium|hauppauge-nova-td-500-84xxx}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=hauppauge-nova-td-500-84xxx<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge WinTV-NOVA-T-500#WinTV-NOVA-TD-500 |Nova-TD-500 (84xxx)]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.27}}<br />
| pic=[[image:Nova-td-500.jpg|120px]]<br />
| url=[http://www.hauppauge.co.uk/pages/products/data_novat500.html]<br />
| hostinterface=PCI32<br />
| usbid=2040:8400<br />
| hw=2&times;DiB3000P, 2&times;MT2060, LNA<br />
| tuner=mt2060<br />
| demodulator=dib3000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=''Bristol'' device (PCI card with USB devices onboard). DiB3000P on DiB0700. The LNA may need manual activation.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== gigabyte-u8000-rh ====<br />
{{DeviceDisplayMedium|gigabyte-u8000-rh}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=gigabyte-u8000-rh<br />
| vendor=Gigabyte<br />
| device=U8000-RH<br />
| standard=DVB-T ANALOG-NTSC ANALOG-PAL ANALOG-SECAM<br />
| supported={{Supported in Kernel|since=2.6.28}}<br />
| pic=<br />
| url=[http://www.gigabyte.com.tw/Products/TVCard/Products_Spec.aspx?ProductID=2441]<br />
| hostinterface=USB2.0<br />
| usbid=1044:7002<br />
| hw=DIB7700C, XC3028ACQ, CX25843-24Z<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=hybrid dvb-t and analog device<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== yuan-high-tech-stk7700ph ====<br />
{{DeviceDisplayMedium|yuan-high-tech-stk7700ph}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=yuan-high-tech-stk7700ph<br />
| vendor=YUAN High-Tech<br />
| device=STK7700PH<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.28}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1164:1f08<br />
| hw=<br />
| tuner=xc3028<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=DVB-part of the Asus notebook M51Sn tv-tunner<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== yuan-high-tech-pd770a ====<br />
{{DeviceDisplayMedium|yuan-high-tech-pd770a}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=yuan-high-tech-pd770a<br />
| vendor=YUAN High-Tech<br />
| device=PD770A<br />
| standard=DVB-T, ANALOG-PAL, ANALOG-NTSC, ANALOG-SECAM, FM-RADIO<br />
| supported=<br />
Mixed:<br />
* DVB-T part: {{Clone of|src=USB_Device_Data|did=yuan-high-tech-stk7700ph}} but not working yet?<br />
* Analog TV: {{no}}<br />
* FM Radio: {{no}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1164:1f08<br />
| hw=<br />
| tuner=xc3028<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== crypto-diva-pd770a ====<br />
{{DeviceDisplayMedium|crypto-diva-pd770a}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=crypto-diva-pd770a<br />
| vendor=Crypto<br />
| device=[[Crypto Diva FM DVB-T Hybrid|Diva FM DVB-T Hybrid]]<br />
| standard=DVB-T, ANALOG-PAL, ANALOG-NTSC, ANALOG-SECAM, FM-RADIO<br />
| supported={{Clone of|src=USB_Device_Data|did=yuan-high-tech-pd770a}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1164:1f08<br />
| hw=<br />
| tuner=xc3028<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=Apparently a full clone of the YUAN High-Tech PD770A, only sold in Greece.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== asus-my-cinema-u3000hybrid ====<br />
{{DeviceDisplayMedium|asus-my-cinema-u3000hybrid}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=asus-my-cinema-u3000hybrid<br />
| vendor=[[ASUS]]<br />
| device=[[ASUS|My Cinema-U3000Hybrid]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.28}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0b05:1736<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== pinnacle-pctv-hd-pro-usb-stick ====<br />
{{DeviceDisplayMedium|pinnacle-pctv-hd-pro-usb-stick}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=pinnacle-pctv-hd-pro-usb-stick<br />
| vendor=Pinnacle<br />
| device=PCTV HD Pro USB Stick (801e) <br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.28}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2304:023a<br />
| hw=<br />
| tuner=xc5000<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== pinnacle-pctv-hd-usb-stick ====<br />
{{DeviceDisplayMedium|pinnacle-pctv-hd-usb-stick}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=pinnacle-pctv-hd-usb-stick<br />
| vendor=Pinnacle<br />
| device=PCTV HD USB Stick (801e SE)<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.28}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2304:023b<br />
| hw=<br />
| tuner=xc5000<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== terratec-cinergy-t-express ====<br />
{{DeviceDisplayMedium|terratec-cinergy-t-express}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-cinergy-t-express<br />
| vendor=TerraTec<br />
| device=Cinergy T Express<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.29}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0ccd:0062<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== terratec-cinergy-dt-usb-xs-diversity-t5 ====<br />
{{DeviceDisplayMedium|terratec-cinergy-dt-usb-xs-diversity-t5}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-cinergy-dt-usb-xs-diversity-t5<br />
| vendor=[[TerraTec]]<br />
| device=[[TerraTec Cinergy DT USB XS Diversity|Cinergy DT USB XS Diversity/ T5]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.29}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0ccd:0081 0ccd:10a1<br />
| hw=2 * DiB7070PB1, DiB 0700C<br />
| tuner=dib0070<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=0ccd:10a1 added in 2.6.31 . This device looks identical to [[TerraTec Cinergy DT USB XS Diversity|this one]] and is sold (in Germany) under the same name and in an almost identical box.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== sony-playtv ====<br />
{{DeviceDisplayMedium|sony-playtv}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=sony-playtv<br />
| vendor=Sony<br />
| device=[[Sony PlayTV dual tuner DVB-T|PlayTV]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.30}}<br />
| pic=<br />
| url=[http://uk.playstation.com/ps3/hardware/accessories/detail/item102429/PlayTV/]<br />
| hostinterface=USB2.0<br />
| usbid=1415:0003<br />
| hw=2*DiB7070P stk7070pd<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=Dual Tuner.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== yuan-pd378s ====<br />
{{DeviceDisplayMedium|yuan-pd378s}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=yuan-pd378s<br />
| vendor=YUAN High-Tech<br />
| device=PD378S<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.30}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1164:2edc<br />
| hw=<br />
| tuner=dib0070<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== hauppauge-atsc-minicard-b200- ====<br />
{{DeviceDisplayMedium|hauppauge-atsc-minicard-b200-}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=hauppauge-atsc-minicard-b200-<br />
| vendor=Hauppauge<br />
| device=ATSC MiniCard (B200)<br />
| standard=ATSC<br />
| supported={{Supported in Kernel|since=2.6.30}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2040:b200<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=ATCS device .. move to ATSC table later<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== hauppauge-atsc-minicard-b210- ====<br />
{{DeviceDisplayMedium|hauppauge-atsc-minicard-b210-}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=hauppauge-atsc-minicard-b210-<br />
| vendor=Hauppauge<br />
| device=ATSC MiniCard (B210)<br />
| standard=ATSC<br />
| supported={{Supported in Kernel|since=2.6.30}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2040:b210<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=ATCS device .. move to ATSC table later<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== yuan-high-tech-mc770 ====<br />
{{DeviceDisplayMedium|yuan-high-tech-mc770}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=yuan-high-tech-mc770<br />
| vendor=YUAN High-Tech<br />
| device=MC770<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.30}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1164:0871<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== elgato-eyetv-dtt-plain ====<br />
{{DeviceDisplayMedium|elgato-eyetv-dtt-plain}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=elgato-eyetv-dtt-plain<br />
| vendor=[[Elgato]]<br />
| device=[[Elgato EyeTV DTT|EyeTV DTT]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.31}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0fd9:0021<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=clone of Hauppauge WinTV-NOVA-T<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== elgato-eyetv-dtt-dlx-pd378s ====<br />
{{DeviceDisplayMedium|elgato-eyetv-dtt-dlx-pd378s}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=elgato-eyetv-dtt-dlx-pd378s<br />
| vendor=[[Elgato]]<br />
| device=[[Elgato EyeTV DTT deluxe|EyeTV DTT deluxe (PD378S)]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.31}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0fd9:0020<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== elgato-eyetv-dtt-dlx-v2 ====<br />
{{DeviceDisplayMedium|elgato-eyetv-dtt-dlx-v2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=elgato-eyetv-dtt-dlx-v2<br />
| vendor=[[Elgato]]<br />
| device=[[Elgato EyeTV DTT deluxe v2|EyeTV DTT deluxe v2]]<br />
| standard=DVB-T<br />
| supported=unknown<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0fd9:002c<br />
| hw=<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=<br />
| fw=<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== leadtek-winfast-dtv-dongle-h ====<br />
{{DeviceDisplayMedium|leadtek-winfast-dtv-dongle-h}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=leadtek-winfast-dtv-dongle-h<br />
| vendor=Leadtek<br />
| device=WinFast DTV Dongle H<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.31}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0413:60f6<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== yuan-high-tech-stk7700d ====<br />
{{DeviceDisplayMedium|yuan-high-tech-stk7700d}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=yuan-high-tech-stk7700d<br />
| vendor=YUAN High-Tech<br />
| device=STK7700D<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.32}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1164:1efc<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== yuan-high-tech-dibcom-stk7700d ====<br />
{{DeviceDisplayMedium|yuan-high-tech-dibcom-stk7700d}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=yuan-high-tech-dibcom-stk7700d<br />
| vendor=YUAN High-Tech<br />
| device=DiBcom STK7700D<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.32}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1164:1e8c<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== pinnacle-pctv-73a ====<br />
{{DeviceDisplayMedium|pinnacle-pctv-73a}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=pinnacle-pctv-73a<br />
| vendor=[[Pinnacle]]<br />
| device=PCTV 73A<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.26}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2304:0243<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== pinnacle-pctv-73e-se ====<br />
{{DeviceDisplayMedium|pinnacle-pctv-73e-se}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=pinnacle-pctv-73e-se<br />
| vendor=[[Pinnacle]] (now PCTV Systems)<br />
| device=[[Pinnacle PCTV nano Stick (73e)|PCTV NanoStick 73e SE (solo)]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.26}}(USBID 2304:0245)<br/>{{Supported in Kernel|since=2.6.33}}(USBID 2013:0245)<br />
| pic=<br />
| url=[http://www.pctvsystems.com/Products/ProductsEuropeAsia/Digitalproducts/PCTVnanoStickSolo/tabid/176/language/en-GB/Default.aspx]<br />
| hostinterface=USB2.0<br />
| usbid=2304:0245 and 2013:0245<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=Same as the plain 73e but without remote control, antenna adapter and USB extension cable.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== pinnacle-pctv-282e ====<br />
{{DeviceDisplayMedium|pinnacle-pctv-282e}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=pinnacle-pctv-282e<br />
| vendor=[[Pinnacle]]<br />
| device=PCTV 282e<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.26}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2304:0248<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== dibcom-stk7770p-reference-design ====<br />
{{DeviceDisplayMedium|dibcom-stk7770p-reference-design}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dibcom-stk7770p-reference-design<br />
| vendor=[[DiBcom]]<br />
| device=STK7770P reference design<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.32}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=10b8:1e80<br />
| hw=<br />
| tuner=<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== terratec-cinergy-t-usb-xxs-hd ====<br />
{{DeviceDisplayMedium|terratec-cinergy-t-usb-xxs-hd}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-cinergy-t-usb-xxs-hd<br />
| vendor=[[TerraTec]]<br />
| device=[[TerraTec Cinergy T USB XXS|Cinergy T USB XXS (HD)]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.32|file=drivers/media/dvb/dvb-usb/dib0700_devices.c}}<br />
| pic=[[image:Terratec Cinergy XXS 001.jpg|120px]]<br />
| url=[http://www.terratec.net/en/products/Cinergy_T_USB_XXS_2068.html]<br />
| hostinterface=USB2.0<br />
| usbid=0ccd:00ab<br />
| hw=dib7770<br />
| tuner=dib0070<br />
| demodulator=dib7000p<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== dibcom-stk807xpvr-reference-design ====<br />
{{DeviceDisplayMedium|dibcom-stk807xpvr-reference-design}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dibcom-stk807xpvr-reference-design<br />
| vendor=DiBcom<br />
| device=STK807xPVR reference design<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.32}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=10b8:1f98<br />
| hw=<br />
| tuner=<br />
| demodulator=dib8000<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== dibcom-stk807xp-reference-design ====<br />
{{DeviceDisplayMedium|dibcom-stk807xp-reference-design}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dibcom-stk807xp-reference-design<br />
| vendor=[[DiBcom]]<br />
| device=STK807xP reference design<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.32}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=10b8:1f90<br />
| hw=<br />
| tuner=<br />
| demodulator=dib8000<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== prolink-pixelview-sbtvd ====<br />
{{DeviceDisplayMedium|prolink-pixelview-sbtvd}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=prolink-pixelview-sbtvd<br />
| vendor=Prolink<br />
| device=Pixelview SBTVD<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.32}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1554:5010<br />
| hw=<br />
| tuner=<br />
| demodulator=dib8000<br />
| usbbridge=dib0700<br />
| fw=dvb-usb-dib0700-1.20.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== [[DiBcom DiB3000|DiB3000M-B]] USB1.1 DVB-T devices===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== avermedia-dib3000mb-based ====<br />
{{DeviceDisplayMedium|avermedia-dib3000mb-based}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=avermedia-dib3000mb-based<br />
| vendor=[[AVerMedia]]<br />
| device=AVerTV DVBT USB<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=[http://www.avermedia.com/cgi-bin/products_digitvtuner_dvbtusb.asp?show=2]<br />
| hostinterface=USB1.1<br />
| usbid=14aa:0001<br />
| hw=[[DiBcom DiB3000|DiBcom 3000M-B]]<br />
| tuner=<br />
| demodulator=dib3000mb<br />
| usbbridge=dib3000mb<br />
| fw=dvb-usb-dibusb-5.0.0.11.fw<br />
| comment=Whats the Axxx model number of this device? warm usbid 14aa:0002<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== compro-videomate-u2000 ====<br />
{{DeviceDisplayMedium|compro-videomate-u2000}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=compro-videomate-u2000<br />
| vendor=Compro<br />
| device=Videomate DVB-U2000 - DVB-T USB1.1<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=[http://www.comprousa.com/en/product/vmu2000.html]<br />
| hostinterface=USB1.1<br />
| usbid=185b:d000 145f:010c<br />
| hw=[[DiBcom DiB3000|DiBcom 3000M-B]]<br />
| tuner=<br />
| demodulator=dib3000mb<br />
| usbbridge=dib3000mb<br />
| fw=dvb-usb-dibusb-5.0.0.11.fw<br />
| comment=warm usbids: 185b:d001 145f:010c<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== dibcom-dib3000mb-mod3000 ====<br />
{{DeviceDisplayMedium|dibcom-dib3000mb-mod3000}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dibcom-dib3000mb-mod3000<br />
| vendor=[[DiBcom]]<br />
| device=USB1.1 DVB-T reference design (MOD3000)<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB1.1<br />
| usbid=10b8:0bb8<br />
| hw=[[DiBcom DiB3000|DiBcom 3000M-B]]<br />
| tuner=<br />
| demodulator=dib3000mb<br />
| usbbridge=dib3000mb<br />
| fw=dvb-usb-dibusb-5.0.0.11.fw<br />
| comment=warm usbid: 10b8:0bb9<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== kworld-xpert-dtv-dib3000mb ====<br />
{{DeviceDisplayMedium|kworld-xpert-dtv-dib3000mb}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=kworld-xpert-dtv-dib3000mb<br />
| vendor=[[KWorld]]<br />
| device=V-Stream XPERT DTV - DVB-T USB1.1<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB1.1<br />
| usbid=eb1a:17de<br />
| hw=[[DiBcom DiB3000|DiBcom 3000M-B]]<br />
| tuner=<br />
| demodulator=dib3000mb<br />
| usbbridge=dib3000mb<br />
| fw=dvb-usb-dibusb-5.0.0.11.fw<br />
| comment=warm usbid: eb1a:17df<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== grandtec-dib3000mb ====<br />
{{DeviceDisplayMedium|grandtec-dib3000mb}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=grandtec-dib3000mb<br />
| vendor=Grandtec<br />
| device=USB1.1 DVB-T<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB1.1<br />
| usbid=5032:0fa0 5032:0bb8<br />
| hw=[[DiBcom DiB3000|DiBcom 3000M-B]]<br />
| tuner=<br />
| demodulator=dib3000mb<br />
| usbbridge=dib3000mb<br />
| fw=dvb-usb-dibusb-5.0.0.11.fw<br />
| comment=warm usbid: 5032:0fa1 5032:0bb9<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== unknown-dib3000mb ====<br />
{{DeviceDisplayMedium|unknown-dib3000mb}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=unknown-dib3000mb<br />
| vendor=Unknown<br />
| device=Unkown USB1.1 DVB-T device ???? please report the name to the author<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB1.1<br />
| usbid=1025:005e<br />
| hw=[[DiBcom DiB3000|DiBcom 3000M-B]]<br />
| tuner=<br />
| demodulator=dib3000mb<br />
| usbbridge=dib3000mb<br />
| fw=dvb-usb-dibusb-5.0.0.11.fw<br />
| comment=warm usbid: 1025:005f<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== twinhan-magicbox-i-hama ====<br />
{{DeviceDisplayMedium|twinhan-magicbox-i-hama}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=twinhan-magicbox-i-hama<br />
| vendor=Twinhan<br />
| device=TwinhanDTV USB-Ter USB1.1 (VP7041)/ TwinhanDTV Magic Box I (VP7041e)/ HAMA USB1.1 DVB-T device<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=[http://www.hama.de/bilder/00049/abb/00049021abb.jpg]<br />
| url=[http://www.twinhan.com/product_terrestrial_3.asp] [http://www.twinhan.com/product_terrestrial_5.asp]<br />
| hostinterface=USB1.1<br />
| usbid=13d3:3201 1822:3201<br />
| hw=[[DiBcom DiB3000|DiBcom 3000M-B]]<br />
| tuner=<br />
| demodulator=dib3000mb<br />
| usbbridge=dib3000mb<br />
| fw=dvb-usb-dibusb-5.0.0.11.fw<br />
| comment=warm usbid: 13d3:3202 1822:3202<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== artec-t1-an2135 ====<br />
{{DeviceDisplayMedium|artec-t1-an2135}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=artec-t1-an2135<br />
| vendor=[[Artec]]<br />
| device=[[Artec T1 USB TV Box|T1 USB1.1 TVBOX with AN2135]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB1.1<br />
| usbid=05d8:8105<br />
| hw=[[DiBcom DiB3000|DiBcom 3000M-B]]<br />
| tuner=<br />
| demodulator=dib3000mb<br />
| usbbridge=dib3000mb<br />
| fw=dvb-usb-dibusb-5.0.0.11.fw<br />
| comment=warm usbid: 05d8:8106<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== videowalker-dib3000mb ====<br />
{{DeviceDisplayMedium|videowalker-dib3000mb}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=videowalker-dib3000mb<br />
| vendor=VideoWalker<br />
| device=DVB-T USB<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=[http://www.geniusnet.com.tw/product/product-1.asp?pdtno=541]<br />
| hostinterface=USB1.1<br />
| usbid=0458:701e<br />
| hw=[[DiBcom DiB3000|DiBcom 3000M-B]]<br />
| tuner=<br />
| demodulator=dib3000mb<br />
| usbbridge=dib3000mb<br />
| fw=dvb-usb-dibusb-5.0.0.11.fw<br />
| comment=warm usbid: 0458:701f<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== artec-t1-an2235 ====<br />
{{DeviceDisplayMedium|artec-t1-an2235}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=artec-t1-an2235<br />
| vendor=[[Artec]]<br />
| device=[[Artec T1 USB TV Box|T1 USB1.1 TVBOX with AN2235]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB1.1<br />
| usbid=05d8:8107<br />
| hw=[[DiBcom DiB3000|DiBcom 3000M-B]]<br />
| tuner=<br />
| demodulator=dib3000mb<br />
| usbbridge=dib3000mb<br />
| fw=dvb-usb-dibusb-an2235-01.fw<br />
| comment=warm usbid: 05d8:8108 <br />
Some "broken" devices where sold with cold id: 0547:2235 . You will need to enable CONFIG_DVB_USB_DIBUSB_MB_FAULTY in the kernel .config to catch those.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== kworld-300u ====<br />
{{DeviceDisplayMedium|kworld-300u}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=kworld-300u<br />
| vendor=[[KWorld]]<br />
| device=300U/Instant DVB-T USB2.0 PTV-333<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=[http://www.tv-cards.com/model.php?modelid=162]<br />
| hostinterface=USB2.0<br />
| usbid=06e1:a333<br />
| hw=[[DiBcom DiB3000|DiBcom 3000M-B]]<br />
| tuner=<br />
| demodulator=dib3000mb<br />
| usbbridge=dib3000mb<br />
| fw=dvb-usb-adstech-usb2-02.fw<br />
| comment=warm usbid: 06e1:a334<br />
}}<br />
<br />
</includeonly><noinclude><br />
===== adstech-ptv333 =====<br />
{{DeviceDisplayMedium|adstech-ptv333}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=adstech-ptv333<br />
| vendor=ADSTech<br />
| device=Instant DVB-T USB2.0 PTV-333<br />
| standard=DVB-T<br />
| supported={{Clone of|src=USB_Device_Data|did=kworld-300u}}<br />
| pic=<br />
| url=[http://www.adstech.com/products/PTV-333/intro/PTV-333_intro.asp?pid=PTV-333]<br />
| hostinterface=USB2.0<br />
| usbid=06e1:a333<br />
| hw=[[DiBcom DiB3000|DiBcom 3000M-B]]<br />
| tuner=<br />
| demodulator=dib3000mb<br />
| usbbridge=dib3000mb<br />
| fw=dvb-usb-adstech-usb2-02.fw<br />
| comment=warm usbid: 06e1:a334<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== kworld-xpert-usb2 ====<br />
{{DeviceDisplayMedium|kworld-xpert-usb2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=kworld-xpert-usb2<br />
| vendor=[[KWorld]]<br />
| device=Xpert DVB-T USB2.0<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.14}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=eb2a:17de<br />
| hw=[[DiBcom DiB3000|DiBcom 3000M-B]]<br />
| tuner=<br />
| demodulator=dib3000mb<br />
| usbbridge=dib3000mb<br />
| fw=dvb-usb-adstech-usb2-02.fw<br />
| comment=<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== artec-t1-dib3000mb-usb2 ====<br />
{{DeviceDisplayMedium|artec-t1-dib3000mb-usb2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=artec-t1-dib3000mb-usb2<br />
| vendor=[[Artec]]<br />
| device=T1 USB2.0<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.15}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=05d8:8109<br />
| hw=[[DiBcom DiB3000|DiBcom 3000M-B]]<br />
| tuner=<br />
| demodulator=dib3000mb<br />
| usbbridge=dib3000mb<br />
| fw=dvb-usb-dibusb-6.0.0.8.fw<br />
| comment=warm usbid: 05d8:810a<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
=== [[DiBcom DiB3000|DiB3000M-C/P]] USB2.0 DVB-T devices ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== dibcom-dib3000mc-mod3000p ====<br />
{{DeviceDisplayMedium|dibcom-dib3000mc-mod3000p}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dibcom-dib3000mc-mod3000p<br />
| vendor=[[DiBcom]]<br />
| device=USB2.0 DVB-T reference design (MOD3000P)<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=10b8:0bc6<br />
| hw=Panasonic tuner, [[DiBcom DiB3000|DiB3000M-C/P]]<br />
| tuner=<br />
| demodulator=dib3000mc<br />
| usbbridge=dib3000mc<br />
| fw=dvb-usb-dibusb-6.0.0.8.fw<br />
| comment=warm usbid: 10b8:0bc7<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== artec-t1-3000mc-usb2 ====<br />
{{DeviceDisplayMedium|artec-t1-3000mc-usb2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=artec-t1-3000mc-usb2<br />
| vendor=[[Artec]]<br />
| device=T1 USB2.0 TVBOX<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=05d8:8109<br />
| hw=Panasonic tuner, [[DiBcom DiB3000|DiB3000M-C/P]]<br />
| tuner=<br />
| demodulator=dib3000mc<br />
| usbbridge=dib3000mc<br />
| fw=dvb-usb-dibusb-6.0.0.8.fw<br />
| comment=Author says: Please check the warm ID.( is it 05d8:810a ?)<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== lite-on-dib3000mc ====<br />
{{DeviceDisplayMedium|lite-on-dib3000mc}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=lite-on-dib3000mc<br />
| vendor=LITE-ON<br />
| device=USB2.0 DVB-T Tuner<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.19}}<br />
| pic=[[image:Dvb-t-usb-toshiba-px1211e-1tvd-001.jpg|120px]]<br />
| url=<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=04ca:f000<br />
| hw=<br />
| tuner=mt2060<br />
| demodulator=dib3000mc<br />
| usbbridge=dib3000mc<br />
| fw=dvb-usb-dibusb-6.0.0.8.fw<br />
| comment=warm usbid 04ca:f001 Also rebranded as "Intuix Tv Tuner Tnt S800", "Toshiba USB DVB-T Tuner PX1211E-1TVD", and "Medion USB DVB-T TV Tuner"<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== msi-digivox-mini-sl ====<br />
{{DeviceDisplayMedium|msi-digivox-mini-sl}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=msi-digivox-mini-sl<br />
| vendor=[[MSI]]<br />
| device=Digivox Mini SL<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.19}}<br />
| pic=[http://www1.conrad.de/xl/9000_9999/9900/9940/9949/994904_BB_00_FB.EPS.jpg]<br />
| url=<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=eb1a:e360<br />
| hw=<br />
| tuner=mt2060<br />
| demodulator=dib3000mc<br />
| usbbridge=dib3000mc<br />
| fw=dvb-usb-dibusb-6.0.0.8.fw<br />
| comment=warm usbid eb1a:e361<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== grand-dib3000mc ====<br />
{{DeviceDisplayMedium|grand-dib3000mc}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=grand-dib3000mc<br />
| vendor=GRAND<br />
| device=USB2.0 DVB-T adapter<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.19}}<br />
| pic=[http://www.grand.com.tw/en/product_form.asp?lwk_series=54&lwk_product=h-005&lwk_page=1]<br />
| url=<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=5032:0bc6<br />
| hw=<br />
| tuner=mt2060<br />
| demodulator=dib3000mc<br />
| usbbridge=dib3000mc<br />
| fw=dvb-usb-dibusb-6.0.0.8.fw<br />
| comment=warm usbid 5032:0bc7<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== artec-t14-dib3000mc-based ====<br />
{{DeviceDisplayMedium|artec-t14-dib3000mc-based}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=artec-t14-dib3000mc-based<br />
| vendor=[[Artec]]<br />
| device=T14<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.19}}<br />
| pic=<br />
| url=[http://www.artec.com.tw/ehtm/be122.htm]<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=05d8:810b<br />
| hw=MT2060 silicon tuner, [[DiBcom DiB3000|DiB3000M-C/P]]<br />
| tuner=mt2060<br />
| demodulator=dib3000mc<br />
| usbbridge=dib3000mc<br />
| fw=dvb-usb-dibusb-6.0.0.8.fw<br />
| comment=warm usbid 05d8:810c Based on the DiBcom DVB-T USB 2.0 reference design. <br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== leadtek-dib3000mc-based ====<br />
{{DeviceDisplayMedium|leadtek-dib3000mc-based}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=leadtek-dib3000mc-based<br />
| vendor=[[Leadtek]]<br />
| device=USB2.0 Winfast DTV dongle (STK3000P based)<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.19}}<br />
| pic=<br />
| url=[http://www.leadtek.com.tw/eng/tv_tuner/overview.asp?lineid=6&pronameid=231]<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=0413:6025<br />
| hw=MT2060 silicon tuner, [[DiBcom DiB3000|DiB3000M-C/P]]<br />
| tuner=mt2060<br />
| demodulator=dib3000mc<br />
| usbbridge=dib3000mc<br />
| fw=dvb-usb-dibusb-6.0.0.8.fw<br />
| comment=warm usbid 0413:6026<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== yuan-pd300-dib3000mc ====<br />
{{DeviceDisplayMedium|yuan-pd300-dib3000mc}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=yuan-pd300-dib3000mc<br />
| vendor=YUAN High-Tech<br />
| device=PD300 DVB-T mobility<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.19}}<br />
| hostinterface=USB1.1 USB2.0<br />
| url=[http://www.linuxtv.org/pipermail/linux-dvb/2006-March/008936.html] [http://www.yuan.com.tw/en/products/vdo_pd300mini.htm]<br />
| usbid=10b8:0bc6<br />
| hw=MT2060 silicon tuner, [[DiBcom DiB3000|DiB3000M-C/P]]<br />
| tuner=mt2060<br />
| demodulator=dib3000mc<br />
| usbbridge=dib3000mc<br />
| fw=dvb-usb-dibusb-6.0.0.8.fw<br />
| comment=same usbid as ref design, but different tuner, yikes! warm usbid: 10b8:0bc7 <br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
===== clones =====<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
====== toshiba-px1211e-1tvd ======<br />
{{DeviceDisplayMedium|toshiba-px1211e-1tvd}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=toshiba-px1211e-1tvd<br />
| vendor=Toshiba<br />
| device=PX1211E-1TVD USB DVB-T Tuner<br />
| standard=DVB-T<br />
| supported={{Clone of|src=USB_Device_Data|did=lite-on-dib3000mc}}<br />
| hostinterface=USB1.1 USB2.0<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
====== intuix-tnt-s800 ======<br />
{{DeviceDisplayMedium|intuix-tnt-s800}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=intuix-tnt-s800<br />
| vendor=Intuix<br />
| device=Tv Tuner Tnt S800<br />
| standard=DVB-T<br />
| supported={{Clone of|src=USB_Device_Data|did=lite-on-dib3000mc}}<br />
| hostinterface=USB1.1 USB2.0<br />
}}<br />
<br />
</includeonly><noinclude><br />
====== medion-95733-95713 ======<br />
{{DeviceDisplayMedium|medion-95733-95713}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=medion-95733-95713<br />
| vendor=Medion<br />
| device=USB DVB-T TV Tuner (MD95733/MD95713)<br />
| standard=DVB-T<br />
| supported={{Clone of|src=USB_Device_Data|did=lite-on-dib3000mc}}<br />
| hostinterface=USB1.1 USB2.0<br />
}}<br />
<br />
</includeonly><noinclude><br />
====== typhoon-tv-movie-dib3000mc ======<br />
{{DeviceDisplayMedium|typhoon-tv-movie-dib3000mc}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=typhoon-tv-movie-dib3000mc<br />
| vendor=Typhoon<br />
| device=TV MOVIE STICK<br />
| url=[http://www.typhoon.de/en/art.php?p=826&c=]<br />
| standard=DVB-T<br />
| supported={{Clone of|src=USB_Device_Data|did=msi-digivox-mini-sl}}<br />
| hostinterface=USB1.1 USB2.0<br />
| comment="Art. 50506"<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== Nebula DigiTV USB version - DVB-T ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== nebula-micro-digitv-usb ====<br />
{{DeviceDisplayMedium|nebula-micro-digitv-usb}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=nebula-micro-digitv-usb<br />
| vendor=[[Nebula]]<br />
| device=micro-DigiTV USB<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=[http://www.nebula-electronics.com/information/info.asp?Code=0003]<br />
| hostinterface=USB2.0<br />
| usbid=<br />
| hw=[[Zarlink MT352]] or NxtWave(now ATI/AMD) Nxt6000<br />
| tuner=<br />
| demodulator=mt352, nxt6000<br />
| usbbridge=<br />
| fw=dvb-usb-digitv-01.fw<br />
| comment=The device is also called "µDigiTV" (using the micro symbol instead of spelling it out). There is an SDK for download on the Nebula WebSite, which was used to improve the driver's quality. Was the first USB2.0 box on the market (late 2003/early 2004).<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== dtt200u.c WideView/Yakumo/Hama/Typhoon/Club3D/Miglia DVB-T USB2.0 devices===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== wideview-wt200u ====<br />
{{DeviceDisplayMedium|wideview-wt200u}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=wideview-wt200u<br />
| vendor=WideView/YUAN/Yakumo/Hama/Typhoon<br />
| device=DVB-T USB2.0 (WT-200U)<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=14aa:0201<br />
| hw=<br />
| tuner=dtt200u<br />
| demodulator=dtt200u<br />
| usbbridge=<br />
| fw=dvb-usb-dtt200u-01.fw<br />
| comment=warm usbid 14aa:0301<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== wideview-wt220u ====<br />
{{DeviceDisplayMedium|wideview-wt220u}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=wideview-wt220u<br />
| vendor=WideView<br />
| device=WT-220U PenType Receiver (Typhoon/Freecom)<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=14aa:0222 14aa:0220<br />
| hw=<br />
| tuner=dtt200u<br />
| demodulator=dtt200u<br />
| usbbridge=<br />
| fw=dvb-usb-wt220u-02.fw<br />
| comment=warm usbid 14aa:0221. Support for Club3D Zap 250 (14aa:0220) added in 2.6.19 Hardware. PID filter table count 15 - limited to about 3 or 4 simultaneous TV channels.<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== wideview-zl353-wt220u ====<br />
{{DeviceDisplayMedium|wideview-zl353-wt220u}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=wideview-zl353-wt220u<br />
| vendor=WideView<br />
| device=WT-220U PenType Receiver (based on ZL353)<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=14aa:022a<br />
| hw=<br />
| tuner=dtt200u<br />
| demodulator=dtt200u<br />
| usbbridge=<br />
| fw=dvb-usb-wt220u-zl0353-01.fw<br />
| comment=warm usbid 14aa:022b<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== wideview-fc-wt220u ====<br />
{{DeviceDisplayMedium|wideview-fc-wt220u}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=wideview-fc-wt220u<br />
| vendor=Freecom<br />
| device=DVB-T (WT-220U PenType Receiver)<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.19}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=14aa:0225<br />
| hw=<br />
| tuner=dtt200u<br />
| demodulator=dtt200u<br />
| usbbridge=<br />
| fw=dvb-usb-wt220u-fc03.fw<br />
| comment=warm usbid 14aa:0226<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== miglia-wt220u ====<br />
{{DeviceDisplayMedium|miglia-wt220u}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=miglia-wt220u<br />
| vendor=Miglia<br />
| device=WT-220U PenType Receiver<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.24}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=18f3:0220<br />
| hw=<br />
| tuner=dtt200u<br />
| demodulator=dtt200u<br />
| usbbridge=<br />
| fw=dvb-usb-wt220u-miglia-01.fw<br />
| comment=warm usbid 14aa:022b(according to a comment in the code)<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
=== m920x devices ===<br />
<br />
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/media/dvb/dvb-usb/m920x.c<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== msi-mega-sky-580 ====<br />
{{DeviceDisplayMedium|msi-mega-sky-580}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=msi-mega-sky-580<br />
| vendor=[[MSI]]<br />
| device=Mega Sky 580<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.21}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB1.1 USB2.0<br />
| usbid=0db0:5580<br />
| hw=tuner: qt1010 demodulator: mt352 USB Bridge: ULi M9206<br />
| tuner=qt1010<br />
| demodulator=mt352<br />
| usbbridge=m920x<br />
| fw=dvb-usb-megasky-02.fw<br />
| comment=Apparently the [[MSI Mega Sky 55801]] is sold under the same name. At least they have a different usb id.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== lifeview-lr540 ====<br />
{{DeviceDisplayMedium|lifeview-lr540}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=lifeview-lr540<br />
| vendor=[[LifeView]]<br />
| device=[[LifeView TV Walker Twin DVB-T (LR540)|TV Walker Twin DVB-T (LR540)]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.22}}(one tuner)<br/>{{Supported_in_Kernel|since=2.6.23}}(both tuners)<br />
| pic=[[image:LifeView TV Walker Twin.jpg|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=10fd:0513<br />
| hw=tuner: 2x[[NXP/Philips_TDA827x|NXP/Philips 8275AC1]] demodulator: 2xNXP/Philips TDA10046A USB Bridge: ULi M9206<br />
| tuner=tda8275<br />
| demodulator=tda1004x<br />
| usbbridge=m920x<br />
| fw=dvb-usb-tvwalkert.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== zappa-lr523 ====<br />
{{DeviceDisplayMedium|zappa-lr523}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=zappa-lr523<br />
| vendor=Zappa<br />
| device=[[LifeView TV Walker Twin DVB-T (LR540)#Zappa_DVB-T_USB_LR523|DVB-T USB LR523]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.22}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=10fd:0513<br />
| hw=tuner: [[NXP/Philips_TDA827x|NXP/Philips 8275AC1]] demodulator: NXP/Philips TDA10046A USB Bridge: ULi M9206<br />
| tuner=tda8275<br />
| demodulator=tda1004x<br />
| usbbridge=m920x<br />
| fw=dvb-usb-tvwalkert.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== msi-digivox-mini-ii-v1 ====<br />
{{DeviceDisplayMedium|msi-digivox-mini-ii-v1}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=msi-digivox-mini-ii-v1<br />
| vendor=[[MSI]]<br />
| device=[[MSI DigiVox mini II|DIGI VOX mini II]]<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.22}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=10fd:1513<br />
| hw=tuner: [[NXP/Philips_TDA827x|NXP/Philips 8275AC1]] demodulator: NXP/Philips TDA10046A USB Bridge: ULi M9206<br />
| tuner=tda8275<br />
| demodulator=tda1004x<br />
| usbbridge=m920x<br />
| fw=dvb-usb-digivox-02.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== dposh-920x ====<br />
{{DeviceDisplayMedium|dposh-920x}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dposh-920x<br />
| vendor=Dposh<br />
| device=DVB-T USB2.0<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.22}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=1498:9206<br />
| hw=tuner: qt1010 demodulator: mt352 USB Bridge: ULi M9206<br />
| tuner=qt1010<br />
| demodulator=mt352<br />
| usbbridge=m920x<br />
| fw=dvb-usb-dposh-01.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
=== Hauppauge WinTV-NOVA-T usb2 ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== hauppauge-wintv-nova-t-usb2 ====<br />
{{DeviceDisplayMedium|hauppauge-wintv-nova-t-usb2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=hauppauge-wintv-nova-t-usb2<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge WinTV-NOVA-T-USB2|WinTV-NOVA-T USB2]]<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2040:9300<br />
| hw=dib3000mc<br />
| tuner=dib3000mc<br />
| demodulator=dib3000mc<br />
| usbbridge=<br />
| fw=dvb-usb-nova-t-usb2-02.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== HanfTek UMT-010 ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== hanftek-umt-010 ====<br />
{{DeviceDisplayMedium|hanftek-umt-010}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=hanftek-umt-010<br />
| vendor=Hanftek<br />
| device=UMT-010<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.13}}<br />
| pic=<br />
| url=[http://www.hanftek.com/] [http://www.linuxtv.org/pipermail/linux-dvb/2006-November/014259.html]<br />
| hostinterface=USB2.0<br />
| usbid=15f4:0001<br />
| hw=[[Zarlink MT352]]<br />
| tuner=<br />
| demodulator=mt352<br />
| usbbridge=dib3000mc<br />
| fw=dvb-usb-umt-010-02.fw<br />
| comment=Stick-sized. Different colours (blue, grey, red). USBID: 15f4:0001(cold) 15f4:0015(warm)<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== MSI Mega Sky 55801 DVB-T USB2.0 ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== msi-mega-sky-55801 ====<br />
{{DeviceDisplayMedium|msi-mega-sky-55801}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=msi-mega-sky-55801<br />
| vendor=[[MSI]]<br />
| device=[[MSI Mega Sky 55801|Mega Sky 55801]] DVB-T USB2.0<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.21}}<br />
| pic=[[image:MSIMegasky55801-exterior-small.jpg|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0db0:5581<br />
| hw=[[Zarlink ZL10353]]<br>Tuner: Quantek QT1010<br>USB bridge: Genesys Logic GL861<br />
| tuner=qt1010<br />
| demodulator=zl10353<br />
| usbbridge=gl861<br />
| fw=none needed<br />
| comment=The QT1010 in this device has it's problems. If you get no or poor signal on Linux, that's "normal". You can try lowering the signal strength from your antenna, remove signal boosters and/or buy an attenuator. Or buy a device with better support.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== a-link-dtu-dvb-t-no-postfix ====<br />
{{DeviceDisplayMedium|a-link-dtu-dvb-t-no-postfix}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=a-link-dtu-dvb-t-no-postfix<br />
| vendor=A-LINK<br />
| device=DTU DVB-T USB2.0<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.23}}<br />
| pic=[[image:A-LINK DTU-002.jpg|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=05e3:f170<br />
| hw=[[Zarlink ZL10353]]<br>Tuner: Quantek QT1010<br>USB bridge: Genesys Logic GL861<br />
| tuner=qt1010<br />
| demodulator=zl10353<br />
| usbbridge=gl861<br />
| fw=none needed<br />
| comment=This is neither the "A-LINK DTU(m)" (which is a AF9015 device) nor the "A-LINK DTU(h)" (which from the pictures I've seen, looks very much like a re-branded "GeniaTech T328B").<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== Twinhan DVB-T USB2.0 ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== digitalnow-tinyusb-2 ====<br />
{{DeviceDisplayMedium|digitalnow-tinyusb-2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=digitalnow-tinyusb-2<br />
| vendor=DigitalNow<br />
| device=TinyUSB 2 DVB-t<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.13}}<br />
| pic=[http://www.digitalnow.com.au/product_images/tinyusb2-device.jpg]<br />
| url=[http://www.digitalnow.com.au/product_pages/tinyusb2.html]<br />
| hostinterface=USB2.0<br />
| usbid=<br />
| hw=[[Zarlink MT352]]<br />
| tuner=<br />
| demodulator=mt352<br />
| usbbridge=vp7045<br />
| fw=dvb-usb-vp7045-01.fw <br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== digitalrise-ter-beetle ====<br />
{{DeviceDisplayMedium|digitalrise-ter-beetle}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=digitalrise-ter-beetle<br />
| vendor=DigitalRise<br />
| device=DVB-T USB 2.0 Ter Beetle<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.13}}<br />
| pic=[http://www.digitalrise.biz/images/products/dvb_tuner/ter/usb2/large.jpg]<br />
| url=[http://www.digitalrise.biz/products/dvb_tuner/ter/usb2/]<br />
| hostinterface=USB2.0<br />
| usbid=<br />
| hw=[[Zarlink MT352]]<br />
| tuner=<br />
| demodulator=mt352<br />
| usbbridge=vp7045<br />
| fw=dvb-usb-vp7045-01.fw<br />
| comment=Looks like a clone of the DigitalNow TinyUSB 2 DVB-t.<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== dnt-euromini-100 ====<br />
{{DeviceDisplayMedium|dnt-euromini-100}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=dnt-euromini-100<br />
| vendor=dnt<br />
| device=EuroMini 100<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.13}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=<br />
| hw=[[Zarlink MT352]]<br />
| tuner=<br />
| demodulator=mt352<br />
| usbbridge=vp7045<br />
| fw=dvb-usb-vp7045-01.fw<br />
| comment=Looks like clone of TwinhanDTV Alpha<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== fujitsu-siemens-dvbt-mobile-tv-tuner ====<br />
{{DeviceDisplayMedium|fujitsu-siemens-dvbt-mobile-tv-tuner}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=fujitsu-siemens-dvbt-mobile-tv-tuner<br />
| vendor=Fujitsu-Siemens<br />
| device=DVB-T Mobile TV Tuner<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.13}}<br />
| pic=[[Image:Fujitsu-Siemens-DVB-T-Mobile-001.jpg|120px]]<br />
| url=[http://www.fujitsu-siemens.de/home/products/accessories/others/dvb_t_mobile.html de] [http://www.fujitsu-siemens.com/home/products/others/dvb_t_mobile.html en]<br />
| hostinterface=USB2.0<br />
| usbid=13d3:3205<br />
| hw=[[Zarlink MT352]]<br />
| tuner=<br />
| demodulator=mt352<br />
| usbbridge=vp7045<br />
| fw=dvb-usb-vp7045-01.fw<br />
| comment=Looks like clone of TwinhanDTV Alpha<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
==== twinhandtv-alpha-rev7045 ====<br />
{{DeviceDisplayMedium|twinhandtv-alpha-rev7045}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=twinhandtv-alpha-rev7045<br />
| vendor=TwinhanDTV<br />
| device=Alpha<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.13}}<br />
| pic=[http://www.twinhan.com/Images/products/TwinHanDTV-alpha_B.jpg]<br />
| url=[http://www.twinhan.com/product_terrestrial_7.asp]<br />
| hostinterface=USB2.0<br />
| usbid=13d3:3205<br />
| hw=[[Zarlink MT352]]<br />
| tuner=<br />
| demodulator=mt352<br />
| usbbridge=vp7045<br />
| fw=dvb-usb-vp7045-01.fw<br />
| comment='''It seems that some TwinhanDTV Alphas(rev 7045A) need newer firmware. 7045A sticks have another frontend and need another firmware. The 7045A frontend is tda10046 based. ''' The symptoms are that they can not find any channels. Consequently, they are unusable at the moment. See these posts for more details: [http://www.linuxtv.org/pipermail/linux-dvb/2006-November/014202.html][http://www.linuxtv.org/pipermail/linux-dvb/2006-November/014226.html][http://www.linuxtv.org/pipermail/linux-dvb/2007-January/015145.html][http://www.linuxtv.org/pipermail/linux-dvb/2007-January/015222.html]<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
==== twinhandtv-magicboxii ====<br />
{{DeviceDisplayMedium|twinhandtv-magicboxii}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=twinhandtv-magicboxii<br />
| vendor=TwinhanDTV<br />
| device=MagicBox II<br />
| standard=DVB-T<br />
| supported={{Supported_in_Kernel|since=2.6.13}}<br />
| pic=[http://www.twinhan.com/Images/products/TwinhanDTV-MagicBox2_B.jpg]<br />
| url=[http://www.twinhan.com/product_terrestrial_6.asp]<br />
| hostinterface=USB2.0<br />
| usbid=<br />
| hw=[[Zarlink MT352]]<br />
| tuner=<br />
| demodulator=mt352<br />
| usbbridge=vp7045<br />
| fw=dvb-usb-vp7045-01.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== WideView/Yakumo/Hama/Typhoon/Yuan Boxes and Pens ===<br />
</noinclude><includeonly><br />
<br />
<br />
</includeonly><noinclude><br />
==== bestbuy-easy-tv-wt220u ====<br />
{{DeviceDisplayMedium|bestbuy-easy-tv-wt220u}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=bestbuy-easy-tv-wt220u<br />
| vendor=Bestbuy<br />
| device=Easy TV<br />
| standard=DVB-T<br />
| supported={{yes}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=<br />
| hw=<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=<br />
| fw=dvb-usb-wt220u-02.fw<br />
| comment=This is a WideView WT-220U PenType Receiver (Typhoon/Freecom).<br />
}}<br />
<br />
</includeonly><noinclude><br />
=== RealTek 2832U devices ===<br />
* Twintech-UT-30<br />
* Genius TVGo DVB-T03<br />
* Gigabyte U7300<br />
* ...<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== twintech-ut-30 ====<br />
{{DeviceDisplayMedium|twintech-ut-30}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=twintech-ut-30<br />
| vendor=TwinTech<br />
| device=Twintech-UT-30<br />
| standard=DVB-T, DAB, DAB+<br />
| supported={{Partial}} Only the DVB-T at the moment.<br />
| pic=<br />
| url=[http://www.twintech3d.com/products_features.asp?num=300]<br />
| hostinterface=USB2.0<br />
| usbid=1b80:d393<br />
| hw=[[RealTek RTL2832U]]<br />
| tuner=Fitipower FC0012<br />
| demodulator=RTL2832U<br />
| usbbridge=RTL2832U<br />
| fw=<br />
| comment=Using the [http://www.zazz.com.au/Manuals/DVBT-DAB_LinuxDriver.zip driver at Zazz] it is sufficient to unzip then within the directory sudo sh ./install.sh and the thing will work. I installed Kaffeine then "Me TV" worked as expected.<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== genius-tvgo-t03-rtl2832u ====<br />
{{DeviceDisplayMedium|genius-tvgo-t03-rtl2832u}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=genius-tvgo-t03-rtl2832u<br />
| vendor=Genius<br />
| device=[[Genius TVGo DVB-T03|TVGo DVB-T03]] (rtl2832 version)<br />
| standard=DVB-T<br />
| supported={{yes}}, by manufacturer. See device page for details.<br />
| pic=[[image:Dvb-t-usb-genius-tvgo-t03-rtl2830-001.jpg|120px]]<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0458:707f<br />
| hw=[[RealTek RTL2832U]]<br />
| tuner=fc0012<br />
| demodulator=<br />
| usbbridge=rtl2832u<br />
| fw=<br />
| comment=also sold with af9015 chipset<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== gigabyte-u7300 ====<br />
{{DeviceDisplayMedium|gigabyte-u7300}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=gigabyte-u7300<br />
| vendor=[[Gigabyte]]<br />
| device=[[Gigabyte U7300|U7300]]<br />
| standard=DVB-T<br />
| supported={{Supported by Vendor|text=[[https://github.com/ambrosa/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0]] driver from external repo, made by vendor, GPL}}<br />
| pic=[http://www.gigabyte.com/fileupload/product/69/3493/3132.jpg]<br />
| url=[http://www.gigabyte.com/products/product-page.aspx?pid=3493]<br />
| hostinterface=USB2.0<br />
| usbid=1b80:d393<br />
| hw=[[RealTek RTL2832U]]<br />
| tuner=Fitipower FC0012<br />
| demodulator=RTL2832U<br />
| usbbridge=RTL2832U<br />
| fw=<br />
| comment=driver compiles without problem on 3.2 kernel, says that works also on 2.6, 3.0 and 3.2 (I haven't tried other than 3.2)<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== gotview-masterhd3 ====<br />
{{DeviceDisplayMedium|gotview-masterhd3}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=gotview-masterhd3<br />
| vendor=[[GoTView]]<br />
| device=[[GoTView MasterHD 3|MasterHD 3]]<br />
| standard=DVB-T2<br />
| supported={{Yes}}<br />
| pic=[http://www.gotview.ru/v2/images/stories/masterhd3_logo.jpg]<br />
| url=[http://www.gotview.ru/v2/opisanie-gotview-usb-masterhd3.html]<br />
| hostinterface=USB2.0<br />
| usbid=5654:ca42<br />
| hw=[[RealTek RTL2832U]]<br />
| tuner=[[Silicon Labs Si2157]]<br />
| demodulator=[[Silicon Labs Si2168]]<br />
| usbbridge=RTL2832U<br />
| fw=<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== Supported Em2880/Em2870 Based USB DVB-T devices ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== bestbuy-easy-tv-hybrid ====<br />
{{DeviceDisplayMedium|bestbuy-easy-tv-hybrid}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=bestbuy-easy-tv-hybrid<br />
| vendor=BestBuy<br />
| device=Easy TV USB hybrid<br />
| standard=DVB-T<br />
| supported={{Supported_in_External|since=?|url=http://mcentral.de/wiki/index.php5/Em2880}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=eb1a:2881<br />
| hw=<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=<br />
| fw=<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
=== AME DTV-5100 / TechGear DigitalTV Stick (TGTV-490) ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== ame-dtv-5100 ====<br />
{{DeviceDisplayMedium|ame-dtv-5100}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=ame-dtv-5100<br />
| vendor=AME<br />
| device=DTV-5100<br />
| standard=DVB-T<br />
| supported={{Supported in Kernel|since=2.6.28}}<br />
| pic=[[image:AME-dtv-5100-001.jpg|120px]]<br />
| url=[http://www.ame-group.com/dtv_5100.htm] [http://royale.zerezo.com/dtv5100/] [http://www.tatatou.org/dotclear/index.php?2008/08/26/162-tuto-premier-jet]<br />
| hostinterface=USB2.0<br />
| usbid=06be:a232<br />
| hw=qt1010, zl10353 (WJCE6353), CY7C68013A<br />
| tuner=qt1010<br />
| demodulator=zl10353<br />
| usbbridge=<br />
| fw=none needed<br />
| comment=Also sold as "TechGear DigitalTV Stick (TGTV-490)"<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== AVerMedia AverTV Hybrid Volar HX (A827) ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== avermedia-a827 ====<br />
{{DeviceDisplayMedium|avermedia-a827}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=avermedia-a827<br />
| vendor=[[AVerMedia]]<br />
| device=[[AVerMedia AverTV Hybrid Volar HX (A827)|AverTV Hybrid Volar HX (A827)]]<br />
| standard=DVB-T, ANALOG, FM<br />
| supported={{Supported by Vendor|text=[[http://www.avermedia.com/avertv/Product/ProductDetail.aspx?Id=293&tab=APDriver]]}}<br />
| pic=[http://www.avermedia.com/avertv/Upload/ProductImages/A827%20Renew%20300.jpg]<br />
| url=[http://www.avermedia.com/avertv/Product/ProductDetail.aspx?Id=293]<br />
| hostinterface=USB2.0<br />
| usbid=07ca:a827<br />
| hw=<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=<br />
| fw=none needed<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
=== Supported TM5600/6000/6010 Based USB DVB-T devices ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== terratec-cinergy-hybrid-xe ====<br />
{{DeviceDisplayMedium|terratec-cinergy-hybrid-xe}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-cinergy-hybrid-xe<br />
| vendor=Terratec<br />
| device=Cinergy Hybrid XE<br />
| standard=DVB-T, ANALOG<br />
| supported={{Supported in Kernel|since=2.6.35}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=0ccd:0086<br />
| hw=<br />
| tuner=xc3028L<br />
| demodulator=ZL10353<br />
| usbbridge=tm6010<br />
| fw=xc3028L-v36.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== terratec-cinergy-hybrid-stick ====<br />
{{DeviceDisplayMedium|terratec-cinergy-hybrid-stick}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-cinergy-hybrid-stick<br />
| vendor=Terratec<br />
| device=Cinergy Hybrid Stick<br />
| standard=DVB-T, ANALOG<br />
| supported={{Supported in Kernel|since=2.6.35}}<br />
| pic=[http://www.terratec.net/en/products/pictures/img/2418555_24d41902b7.png]<br />
| url=[http://www.terratec.net/en/products/Cinergy_Hybrid_Stick_82268.html]<br />
| hostinterface=USB2.0<br />
| usbid=0ccd:00a5<br />
| hw=<br />
| tuner=xc3028L<br />
| demodulator=ZL10353<br />
| usbbridge=TM6010<br />
| fw=xc3028L-v36.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== hauppauge-wintv-hvr900h ====<br />
{{DeviceDisplayMedium|hauppauge-wintv-hvr900h}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=hauppauge-wintv-hvr900h<br />
| vendor=Hauppauge<br />
| device=WinTv HVR-900H<br />
| standard=DVB-T, ANALOG<br />
| supported={{Supported in Kernel|since=2.6.35}}<br />
| pic=<br />
| url=<br />
| hostinterface=USB2.0<br />
| usbid=2040:6600<br />
| hw=<br />
| tuner=xc3028L<br />
| demodulator=zl10353<br />
| usbbridge=TM6010<br />
| fw=xc3028L-v36.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
=== TechnoTrend USB2.0 DVB-T devices ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== tt-ct-3650-ci ====<br />
{{DeviceDisplayMedium|tt-ct-3650-ci}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=tt-ct-3650-ci<br />
| vendor=TechnoTrend<br />
| device=[[TechnoTrend TT-connect CT-3650 CI|TT-connect CT-3650 CI]]<br />
| standard=DVB-T, DVB-C<br />
| supported={{Supported in Kernel|since=3.2}} <br />
| pic=[[Image:TT-connect_CT-3650_CI.jpg|120px]]<br />
| url=[http://www.tt-pc.com/2916/TT-connect__CT-3650_CI.html]<br />
| hostinterface=USB2.0<br />
| usbid=0b48:300d<br />
| hw=Philips TDA10023 DVB-C, NXP TDA10048HN DVB-T<br />
| tuner=<br />
| demodulator=<br />
| usbbridge=<br />
| fw=N/A<br />
| comment=Combined DVB-T/DVB-C with integrated CI, which is fully supported from kernel 3.2.<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
=== Sony CXD2820 DVB-T2 Devices ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== geniatech-t220 ====<br />
{{DeviceDisplayMedium|geniatech-t220}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=geniatech-t220<br />
| vendor=[[Geniatech]]<br />
| device=[[Geniatech_T220|T220]]<br />
| standard=DVB-T, DVB-T2, DVB-C<br />
| supported={{Supported in Kernel|since=3.14}}, [https://tvheadend.org/boards/5/topics/10864?r=11372#message-11372 Users reporting errors with DVB-T2] <br />
| pic=<br />
| url=[http://www.geniatech.com/pa/t220.asp]<br />
| hostinterface=USB2.0<br />
| usbid=1f4d:d220<br />
| hw= Sony CXD2820R / NXP TDA18271HD/C2 / Cypress CY7C68013A<br />
| tuner=tda18271<br />
| demodulator=cxd2820r<br />
| usbbridge=cy7C68013a<br />
| fw=N/A<br />
| comment=Looks like [https://github.com/raspberrypi/linux/issues/82#issuecomment-27704840 August DVB-T210 is a rebranded device with the same usbids].<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== pctv-nanostick-t2-290e ====<br />
{{DeviceDisplayMedium|pctv-nanostick-t2-290e}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=pctv-nanostick-t2-290e<br />
| vendor=[[PCTV Systems]]<br />
| device=[[PCTV Systems nanoStick T2 290e|nanoStick T2 290e]]<br />
| standard=DVB-T, DVB-T2, DVB-C<br />
| supported={{Supported in Kernel|since=3.0}} <br />
| pic=[[Image:PCTV_nanoStick_T2_290e_PCB_em28xx_demod.jpg|120px]]<br />
| url=[http://www.pctvsystems.com/Products/ProductsEuropeAsia/Digitalproducts/PCTVnanoStickT2/tabid/248/language/en-GB/Default.aspx]<br />
| hostinterface=USB2.0<br />
| usbid=2013:024f<br />
| hw=[[Em28xx_devices|eMPIA em28xx]], [[Sony_CXD2820|Sony CXD2820R]], [[NXP/Philips_TDA182xx|NXP TDA18271HD/C2]]<br />
| tuner=[[NXP/Philips_TDA182xx|NXP TDA18271HD/C2]]<br />
| demodulator=c[[Sony_CXD2820|Sony CXD2820R]]<br />
| usbbridge=[[Em28xx_devices|eMPIA em28xx]]<br />
| fw=N/A<br />
| comment=First DVB-T2 capable receiver with Linux support. Kernel 3.2+ or latest media-build may be needed for multiple Empia-based devices to work together. Details on [http://www.stevekerrison.com/290e/index.html development history].<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
=== realtek rtl2832p devices ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
<br />
==== astrometa-dvb-t2 ====<br />
{{DeviceDisplayMedium|astrometa-dvb-t2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=astrometa-dvb-t2<br />
| vendor=[[Astrometa]]<br />
| device=[[Astrometa DVB-T2|DVB-T2]]<br />
| standard=DVB-T, DVB-T2, DVB-C<br />
| supported=DVB-T {{Supported in Kernel|since=3.13}}, DVB-T2 {{Supported in Kernel|since=4.6}} <br />
| pic=[[Image:Astrometa-dvb-t2.png|240px|Astometa HD-901T2]]<br />
| url=[http://www.astrometa.com.tw/integrated_en.html]<br />
| hostinterface=USB2.0<br />
| usbid=15f4:0131<br />
| hw=[[RealTek RTL2832P]], Panasonic MN88472 or MN88473, Rafael Micro R828D<br />
| tuner=Rafael Micro R828D<br />
| demodulator=[[RealTek RTL2832P]], Panasonic MN88472 or MN88473<br />
| usbbridge=[[RealTek RTL2832P]]<br />
| fw=<br />
| comment=Popular generic DVB-T2 USB tuner from different Chinese suppliers<br />
}}<br />
<br />
<br />
</includeonly><noinclude><br />
<br />
=== Silicon Labs si2168 devices ===<br />
</noinclude><includeonly><br />
<br />
</includeonly><noinclude><br />
==== geniatech-t230 ====<br />
{{DeviceDisplayMedium|geniatech-t230}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=geniatech-t230<br />
| vendor=[[Geniatech]]<br />
| device=[[Geniatech_T230|T230]]<br /><small>MyGica T230<br />August T210v2<br />Geniatech PT360 (USB-OTG)<br />MyGica PT360 (USB-OTG)<br />D202 (USB-OTG, OEM)</small><br />
| standard=DVB-T, DVB-T2, DVB-C<br />
| supported={{yes}}<br />
| pic=[[Image:Geniatech-t230.jpg|120px]]<br />
| url=[http://www.geniatech.com/pa/t230.asp]<br />
| hostinterface=USB2.0<br />
| usbid=0572:c688<br />
| hw=[[Silicon Labs Si2157|Silicon Labs Si2148]]-A20 or [[Silicon Labs Si2157|Si2158]]-A20, [[Silicon Labs Si2168]]-B40, [[Cypress EZ-USB FX2|Cypress EZ-USB FX2 CY7C68013A]]<br />
| tuner=[[Silicon Labs Si2157|Silicon Labs Si2148]]-A20/[[Silicon Labs Si2157|Silicon Labs Si2158]]-A20<br />
| demodulator=[[Silicon Labs Si2168]]-B40<br />
| usbbridge=[[Cypress EZ-USB FX2|Cypress EZ-USB FX2 CY7C68013A]]<br />
| fw=[https://github.com/OpenELEC/dvb-firmware dvb-demod-si2168-b40-01.fw, dvb-tuner-si2158-a20-01.fw]<br />
| comment= kernel >= 3.19, remote control supported.<br />
}}<br />
<br />
</includeonly><noinclude><br />
==== geniatech-t230c ====<br />
{{DeviceDisplayMedium|geniatech-t230c}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=geniatech-t230c<br />
| vendor=[[Geniatech]]<br />
| device=[[Geniatech T230C|T230C]]<br /><small>MyGica T230C<br />eyeTV T2<br />eyeTV T2 Hybrid<br />eyeTV T2 Lite</small><br />
| standard=DVB-T, DVB-T2, DVB-C<br />
| supported={{Partial}} You may have to build the drivers yourself<br />
| pic=[[Image:Geniatech-t230.jpg|120px]]<br />
| url=<br />
| hostinterface=USB 2.0<br />
| usbid=0572:c689<br />
| hw=[[Silicon Labs Si2141]]-A10, [[Silicon Labs Si2168]]-D60, [[Cypress EZ-USB FX2|Cypress EZ-USB FX2 CY7C68013A]]<br />
| tuner=[[Silicon Labs Si2141]]-A10<br />
| demodulator=[[Silicon Labs Si2168]]-D60<br />
| usbbridge=[[Cypress EZ-USB FX2|Cypress EZ-USB FX2 CY7C68013A]]<br />
| fw=dvb-demod-si2168-d60-01.fw dvb-tuner-si2141-a10-01.fw <br />
| comment=Fully works if the correct drivers are used<br />
}}<br />
</includeonly><noinclude><br />
<br />
==== geniatech-t230c2 ====<br />
{{DeviceDisplayMedium|geniatech-t230c2}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=geniatech-t230c2<br />
| vendor=[[Geniatech]]<br />
| device=[[Geniatech_T230C2|T230C2]]<br /><small>MyGica T230C2<br />August DVB-T210 v2.0</small><br />
| standard=DVB-T, DVB-T2, DVB-C<br />
| supported={{Supported in Kernel|since=5.4}} <br />
| pic=[[Image:Geniatech-t230.jpg|120px]] [[File:Evolveo_Sigma_T2.jpeg|120px]] [[File:August.jpg|120px]]<br />
| url=[https://www.geniatech.com/product/t230/]<br />
| hostinterface=USB2.0<br />
| usbid=0572:c68a<br />
| hw=[[Silicon Labs Si2141]]-A10, [[Silicon Labs Si2168]]-D60, [[Cypress EZ-USB FX2|Cypress EZ-USB FX2 CY7C68013A]], [[Evolveo Sigma T2]]<br />
| tuner=[[Silicon Labs Si2141]]-A10<br />
| demodulator=[[Silicon Labs Si2168]]-D60<br />
| usbbridge=[[Cypress EZ-USB FX2|Cypress EZ-USB FX2 CY7C68013A]]<br />
| fw=[dvb-demod-si2168-d60-01.fw, dvb-tuner-si2141-a10-01.fw]<br />
| comment=Drivers can be built with [[How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers#Retrieving_and_Building.2FCompiling_the_Latest_V4L-DVB_Source_Code|media_build]] for older kernels. Evidence of August DVB-T210 v2.0 using [[Geniatech T230]] in the past, ones bought today are likely to be T230C2 instead.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== terratec-cinergy-t2-stick-hd ====<br />
{{DeviceDisplayMedium|terratec-cinergy-t2-stick-hd}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=terratec-cinergy-t2-stick-hd<br />
| vendor=[[TerraTec]]<br />
| device=[[TerraTec_Cinergy_T2_Stick_HD|Cinergy T2 Stick HD]]<br />
| standard=DVB-T, DVB-T2, DVB-C<br />
| supported={{yes}}<br />
| pic=[[Image:TerraTec_Cinergy_T2_Stick_HD.jpg|120px]]<br />
| url=[http://www.terratec.net/details.php?artnr=130638#.VK45hHvll2j]<br />
| hostinterface=USB2.0<br />
| usbid=eb1a:8179<br />
| hw=[[Silicon Labs Si2157|Silicon Labs Si2146]], [[Silicon Labs si2168]], [[Em28xx_devices|Empia EM28178]]<br />
| tuner=[[Silicon Labs Si2157|Silicon Labs Si2148]]<br />
| demodulator=[[Silicon Labs Si2168]]<br />
| usbbridge=[[Em28xx_devices|Empia EM28178]]<br />
| fw=[https://github.com/OpenELEC/dvb-firmware dvb-demod-si2168-a30-01.fw]<br />
| comment= kernel >= 3.19, remote control supported.<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
<br />
==== pctv-triplestick-292e ====<br />
{{DeviceDisplayMedium|pctv-triplestick-292e}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=pctv-triplestick-292e<br />
| vendor=[[PCTV Systems]]<br />
| device=[[PCTV Systems tripleStick T2 (292e)|tripleStick 292e]]<br />
| standard=DVB-T, DVB-T2, DVB-C<br />
| supported={{yes}}<br />
| pic=<br />
| url=[http://www.pctvsystems.com/Products/ProductsEuropeAsia/Hybridproducts/PCTVtripleStick/tabid/308/language/en-GB/Default.aspx]<br />
| hostinterface=USB2.0<br />
| usbid=2013:025f<br />
| hw=[[Silicon Labs Si2157]], [[Silicon Labs Si2168]], [[Em28xx_devices|eMPIA em28174]]<br />
| tuner=[[Silicon Labs Si2157]]<br />
| demodulator=[[Silicon Labs si2168]]<br />
| usbbridge=[[eMPIA em28174]]<br />
| fw=dvb-demod-si2168-b40-01.fw<br />
| comment=First version of the driver has been released, look [http://blog.palosaari.fi/2014/04/naked-hardware-15-pctv-triplestick-292e.html here]<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== technotrend-ct2-4400 ====<br />
{{DeviceDisplayMedium|technotrend-ct2-4400}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=technotrend-ct2-4400<br />
| vendor=[[TechnoTrend]]<br />
| device=[[TechnoTrend_TT-TVStick_CT2-4400|TVStick CT2-4400]]<br />
| standard=DVB-T, DVB-T2, DVB-C<br />
| supported={{yes}}<br />
| pic=<br />
| url=[http://engl.technotrend.eu/2990/TT-TVStick__CT2-4400.html]<br />
| hostinterface=USB2.0<br />
| usbid=0b48:3014<br />
| hw=[[Silicon Labs Si2157|Silicon Labs Si2158]], [[Silicon Labs Si2168]], [[Cypress EZ-USB FX2|Cypress CY7C68013A]]<br />
| tuner=[[Silicon Labs Si2157|Silicon Labs Si2158]]<br />
| demodulator=[[Silicon Labs Si2168]]<br />
| usbbridge=[[Cypress EZ-USB FX2]]<br />
| fw=dvb-demod-si2168-a30-01.fw<br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== technotrend-ct2-4650 ====<br />
{{DeviceDisplayMedium|technotrend-ct2-4650}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=technotrend-ct2-4650<br />
| vendor=[[TechnoTrend]]<br />
| device=[[TechnoTrend_TT-connect_CT2-4650_CI|TT-connect CT2-4650 CI]]<br />
| standard=DVB-T, DVB-T2, DVB-C<br />
| supported={{yes}}<br />
| pic=<br />
| url=[http://engl.technotrend.eu/2987/TT-connect_CT2-4650_CI.html]<br />
| hostinterface=USB2.0<br />
| usbid=0b48:3012<br />
| hw=[[Silicon Labs Si2157|Silicon Labs Si2158]], [[Silicon Labs Si2168]], [[Cypress EZ-USB FX2|Cypress CY7C68013A]]<br />
| tuner=[[Silicon Labs Si2157|Silicon Labs Si2158]]<br />
| demodulator=[[Silicon Labs Si2168]]<br />
| usbbridge=[[Cypress EZ-USB FX2]]<br />
| fw=dvb-demod-si2168-a20-01.fw, dvb-tuner-si2158-a20-01.fw <br />
| comment=<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== technotrend-ct2-4650-v1_1 ====<br />
{{DeviceDisplayMedium|technotrend-ct2-4650-v1_1}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=technotrend-ct2-4650-v1_1<br />
| vendor=[[TechnoTrend]]<br />
| device=[[TechnoTrend_TT-connect_CT2-4650_CI|TT-connect CT2-4650 CI v1.1]]<br />
| standard=DVB-T, DVB-T2, DVB-C<br />
| supported={{yes}}<br />
| pic=<br />
| url=[http://engl.technotrend.eu/2987/TT-connect_CT2-4650_CI.html]<br />
| hostinterface=USB2.0<br />
| usbid=0b48:3015<br />
| hw=[[Silicon Labs Si2157|Silicon Labs Si2157]], [[Silicon Labs Si2168]], [[Cypress EZ-USB FX2|Cypress CY7C68013A]]<br />
| tuner=[[Silicon Labs Si2157|Silicon Labs Si2157]]<br />
| demodulator=[[Silicon Labs Si2168]]<br />
| usbbridge=[[Cypress EZ-USB FX2]]<br />
| fw=dvb-demod-si2168-b40-01.fw, dvb-demod-si2168-02.fw, dvb-tuner-si2158-a20-01.fw <br />
| comment=[https://www.mail-archive.com/linux-media@vger.kernel.org/msg94927.html Patch for v1.1 (2016)]<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
==== hauppauge_wintv-solohd ====<br />
{{DeviceDisplayMedium|hauppauge_wintv-solohd}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=hauppauge_wintv-solohd<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge_WinTV-soloHD]] <br />
| standard=DVB-T, DVB-T2, DVB-C<br />
| supported={{yes}}<br />
| pic=<br />
| url=[http://www.hauppauge.de/site/products/data_solohd.html]<br />
| hostinterface=USB2.0<br />
| usbid=2040:0264<br />
| hw=[[Silicon Labs Si2157]], [[Silicon Labs Si2168]], [[Em28xx_devices|eMPIA em28174]]<br />
| tuner=[[Silicon Labs Si2157]]<br />
| demodulator=[[Silicon Labs si2168]]<br />
| usbbridge=[[eMPIA em28174]]<br />
| fw=dvb-demod-si2168-b40-01.fw<br />
| comment=First version of the driver has been released, look [http://blog.palosaari.fi/2014/04/naked-hardware-15-pctv-triplestick-292e.html here]<br />
}}<br />
<br />
</includeonly><noinclude><br />
<br />
<br />
==== hauppauge_wintv-dualhd ====<br />
{{DeviceDisplayMedium|hauppauge_wintv-dualhd}}<br />
</noinclude><includeonly><br />
{{{{{renderwith}}}|src=USB_Device_Data|selatt1={{{selatt1|}}}|selval1={{{selval1|}}}|selatt2={{{selatt2|}}}|selval2={{{selval2|}}}|selatt3={{{selatt3|}}}|selval3={{{selval3|}}}|selatt4={{{selatt4|}}}|selval4={{{selval4|}}}<br />
| did=hauppauge_wintv-dualhd<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge_WinTV-dualHD]] Model 01590<br />
| standard=DVB-T, DVB-T2, DVB-C<br />
| supported={{Supported in Kernel|since=4.17}}<br />
| pic=<br />
| url=[http://www.hauppauge.co.uk/site/products/data_dualhd.html]<br />
| hostinterface=USB2.0<br />
| usbid=2040:0265<br />
| hw=[[Silicon Labs Si2157]], [[Silicon Labs Si2168]],[[Em28xx_devices|Empia EM28274]]<br />
| tuner=2*[[Silicon Labs Si2157]]-A30<br />
| demodulator=2*[[Silicon Labs Si2168]]-B40<br />
| usbbridge=[[Em28xx_devices|Empia EM28274]]<br />
| fw=dvb-demod-si2168-b40-01.fw<br />
| comment=Kernel >=4.7 first tuner only, kernel patch for both tuners. Kernel >=4.17 both tuners suported.<br />
}}<br />
<br />
</includeonly><noinclude></div>Jshttps://www.linuxtv.org/wiki/index.php?title=USB_Devices_ListData/Helper&diff=36511USB Devices ListData/Helper2020-08-29T18:04:32Z<p>Js: revert to the last version by Hlangos which fulfills the intended purpose</p>
<hr />
<div>== Full Detail Table ==<br />
<br />
The table below is rendered using those two templates: [[Template:Device List Full Detail/Header]] and<br />
[[Template:Device List Full Detail/Row]].<br />
<br />
{{Device_List_Full_Detail/Header<br />
| content = {{USB_Device_Data|renderwith=Device_List_Full_Detail/Row}}<br />
}}<br />
<br />
== did table ==<br />
<br />
Please make sure that ''did''s are unique and not prefix of any other did. Here's a short helper table that only lists those did's:<br />
<br />
The table below is rendered using those two templates: [[Template:Device List did-only/Header]] and<br />
[[Template:Device List did-only/Row]].<br />
<br />
{{Device_List_did-only/Header<br />
| content = {{USB_Device_Data|renderwith=Device_List_did-only/Row}}<br />
}}</div>Jshttps://www.linuxtv.org/wiki/index.php?title=User_talk:Johnywhy&diff=36417User talk:Johnywhy2019-11-24T21:40:44Z<p>Js: Welcome!</p>
<hr />
<div>'''Welcome to ''LinuxTVWiki''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:Js|js]] ([[User talk:Js|talk]]) 21:40, 24 November 2019 (UTC)</div>Jshttps://www.linuxtv.org/wiki/index.php?title=User:Johnywhy&diff=36416User:Johnywhy2019-11-24T21:40:43Z<p>Js: Creating user page for new user.</p>
<hr />
<div>Experienced programmer, learning Linux, recently wrote a motion detector based on qvidcap and GraphicsMagick.</div>Jshttps://www.linuxtv.org/wiki/index.php?title=On-Screen_Display&diff=35538On-Screen Display2017-01-01T16:12:13Z<p>Js: fix DirectFB link (directfb.net)</p>
<hr />
<div>An '''On-Screen Display''' (short '''OSD''') is usually used on [[SetTopBox]]es to display a menu on the TV screen. Sometimes programmed using a proprietary API. Linux-based STBs sometimes use [[DirectFB]] as more portable [[API]] to render their [[GUI]] and set up the video layers.<br />
<br />
== Links ==<br />
<br />
* [http://www.directfb.net/ DirectFB Website]<br />
<br />
[[Category:Technology]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=User_talk:Js&diff=33402User talk:Js2014-06-04T18:06:02Z<p>Js: re</p>
<hr />
<div>Hi,<br />
<br />
thank you creating account, could I ask how to add image?<br />
In the menu Tools missing upload option. Maybe, I am blind and it is easy.<br />
<br />
Milos<br />
<br />
<br />
You're not blind, just impatient. Wait 24 hours after account creation.<br />
<br />
js</div>Jshttps://www.linuxtv.org/wiki/index.php?title=User:Tv-user&diff=33340User:Tv-user2014-04-21T17:03:30Z<p>Js: Creating user page for new user.</p>
<hr />
<div></div>Jshttps://www.linuxtv.org/wiki/index.php?title=MediaWiki:Requestaccount-ext-text&diff=33339MediaWiki:Requestaccount-ext-text2014-04-19T20:47:31Z<p>Js: Created page with "The following information is kept private and will only be used for this request. Please write a few words to convince us you're not a spammer. "I want to fix a typo" is not e..."</p>
<hr />
<div>The following information is kept private and will only be used for this request.<br />
Please write a few words to convince us you're not a spammer.<br />
"I want to fix a typo" is not enough.</div>Jshttps://www.linuxtv.org/wiki/index.php?title=LinuxTVWiki:Terms_of_Service&diff=33338LinuxTVWiki:Terms of Service2014-04-19T20:46:48Z<p>Js: Created page with "No spam, please."</p>
<hr />
<div>No spam, please.</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Talk:Main_Page&diff=32293Talk:Main Page2013-09-30T06:44:55Z<p>Js: Reverted edits by Msy619919 (talk) to last revision by Wirbel</p>
<hr />
<div>== main page hacked ==<br />
<br />
Main Page was "hacked" by a stupid guy: http://www.linuxtv.org/wiki/index.php?title=Main_Page&oldid=11512 <br />
someone should consider taking some actions towards his account. <br />
<br />
I would like to say something to that guy: <br />
do you really think you are an hacker just because you changed the main page of a wiki that can be edited by whoever wants?<br />
<br />
If you just sit down and think you will realize the real hackers here are all those coders here behind who hack inside closed devices and manage to free them through a gpl driver written from scratch.<br />
<br />
Instead of abusing open source communities where nobody has got the power because everybody does have the power (for istance I registered just in order to change back the homepage, exactly as you did to destroy it), focus your efforts on big evil corporations websites: there you can fight against a webadmin and maybe eventually win, but never would you win over a linux community, it's simply too big (and does not code for money)!<br />
<br />
== Categories articles organization ==<br />
<br />
I just added some trivial categories to the ISDB-T devices pages, but, I have a little trouble. Watching the existing scheme in another standard, for example DVB-T, we can find categories like "DVB-T PCI Cards" in the same name page, but in the "DVB-T PCie Cards" we have the "PCIe" category. There are anything "official" about the procedures of Categories? --[[User:Howl|howl]] 01:15, 1 October 2009 (UTC)</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Development:_How_to_submit_patches&diff=32288Development: How to submit patches2013-09-28T16:12:17Z<p>Js: Reverted edits by Ritawi (talk) to last revision by Olliv3r</p>
<hr />
<div>This article provides an overview for submitting patches against the [[What is V4L or DVB?|V4L-DVB source code]] (for either new or existing kernel driver modules and/or documentation), and as well as for the [[LinuxTV dvb-apps|dvb-apps]] source. For general references in regards as to how to develop support for a particular device or in writing a new device driver, see [[Development: How to add support for a device|here]].<br />
<br />
<br />
Initial dvb scan tables/files can also be [[Scantables|submitted]].<br />
<br />
<br />
== Patch Preparation ==<br />
For V4L-DVB driver modules and/or documentation, patches should be created against the [http://git.linuxtv.org/media_tree.git master linux-media git tree]; for instructions on obtaining and building these sources, see the "[[How to Obtain, Build and Install V4L-DVB Device Drivers]]" article. Similarly, for submissions related to the dvb-apps, one should patch against the [http://linuxtv.org/hg/dvb-apps dvb-apps ''mercurial'' tree]. <br />
<br />
<br />
The patch should contain an unified diff between the latest code at the tree and the code you modified. The best way to do it is by running the command ''git diff'' or ''hg diff''. Before submitting your patch, please run ''make checkpatch''. This will tell the build system to run a script that checks for coding style violations.<br />
<br />
Post your patches to the [mailto:majordomo@vger.kernel.org?body=subscribe%20linux-media Linux-Media Mailing List] for review and testing. [http://vger.kernel.org/vger-lists.html#linux-media Subscription to the mailing list] is recommended, though it is not required.<br />
<br />
Follow the guidelines in [[Development: Submitting Patches|Submitting Patches]] (cf. [http://linux.yyz.us/patch-format.html jgarzik's version]), including:<br />
:* Verify best-practice [[Development: Coding Style|kernel coding style]]<br />
:* Use [PATCH] in the subject line to get attention ... '''Note''': the patchwork tool (discussed below) actually does NOT rely upon this label for detection of patches; rather, patchwork utilizes logic algorithms to detect for the presence of a patch within an email message. That being the case, the "[PATCH]" flag serves only to alert your human counterparts/peers on the mailing list of your submission<br />
:* Explain what the patch does and to what hardware it applies. Note: All comments you add on your patch will be part of the commit message (except for the meta-tags)<br />
:* Document your work where appropriate (i.e. in the form of patches to the Documentation/video4linux or Documentation/dvb files) <br />
:* Add a '''Signed-off-by: Your name <name@yoursite.com>''' as a [[Development: Submitting Patches#Developer.27s_Certificate_of_Origin_1.1|Developer's Certificate of Origin 1.1 ]]<br />
:* Send the patch inline, not as an attachment (unless otherwise asked to do so) ... patches presented in the form of inline text in the body of an email are easier to deal with from the perspective of a peer review process (for more information, see the <code>/usr/src/linux/Documentation/email-clients.txt</code> file; a current copy of which can also be found online [http://lxr.linux.no/linux+v2.6.28.5/Documentation/email-clients.txt here]).<br />
:* '''Note''': various web mail interfaces seem to be problematic for patch submission, in that:<br />
:** they may break the patch (e.g. line wrapping it) or<br />
:** in the case where you have sent the patch as an attachment, the emailer may use the wrong mime encoding type ... (web mailers often wrongly use "application/octet-stream" for diffs, whereas the proper type is "text/x-patch" ... Note: the patchwork tool (discussed below) is robust in that it supports both mime types "text/x-patch" and "text/plain", but if the emailer has sent it with a different type, the attachment will be disregarded/discarded.<br />
<br />
Hint: There is also a [[Development: Linux Kernel patch submittal checklist|checklist for patch submission]]<br />
<br />
== Example of a good patch submission email ==<br />
<br />
The following example (based on a real patch submission) shows, in practice, how<br />
a good patch should look like:<br />
<br />
From: Patch Developer<br />
Date: Thu, 27 Sep 2012 05:32:52 -0300<br />
Subject: [PATCH] davinci: vpif: capture/display: fix race condition<br />
<br />
channel_first_int[][] variable is used as a flag for the ISR,<br />
This flag was being set after enabling the interrupts, There<br />
where situations when the isr occurred even before the flag was set<br />
due to which it was causing the application hang.<br />
This patch sets channel_first_int[][] flag just before enabling the<br />
interrupt.<br />
<br />
Reported-by: Some User<br />
Signed-off-by: Patch Developer<br />
Reviewed-by: Patch Reviewer<br />
<br />
---<br />
<br />
v2: Coding Style fixed, as per-review.<br />
<br />
drivers/media/platform/davinci/vpif_capture.c | 1 +<br />
1 file changed, 1 insertion(+)<br />
<br />
diff --git a/drivers/media/platform/davinci/vpif_capture.c b/drivers/media/platform/davinci/vpif_capture.c<br />
index 13aa46d..0bafeca 100644<br />
--- a/drivers/media/platform/davinci/vpif_capture.c<br />
+++ b/drivers/media/platform/davinci/vpif_capture.c<br />
@@ -339,6 +339,7 @@ static int vpif_start_streaming(struct vb2_queue *vq, unsigned int count)<br />
* Set interrupt for both the fields in VPIF Register enable channel in<br />
* VPIF register<br />
*/<br />
+ channel_first_int[VPIF_VIDEO_INDEX][ch->channel_id] = 1;<br />
if ((VPIF_CHANNEL0_VIDEO == ch->channel_id)) {<br />
channel0_intr_assert();<br />
channel0_intr_enable(1);<br />
<br />
*The fist part contains the email header and the first part of the email body, with the patch description, followed by Signed-off/Reviewed-by/Acked-By tags.<br />
<br />
Note: For patches submitted by one person, but authored by another one, the '''first line''' of the email body should contain a ''From:'' tag with the name and email of the original author. For example, if the above e-mail was sent by ''Patch Reviewer'', it would contain, instead:<br />
<br />
From: Patch Reviewer<br />
Date: Thu, 27 Sep 2012 05:32:52 -0300<br />
Subject: [PATCH] davinci: vpif: capture/display: fix race condition<br />
<br />
From: Patch Developer<br />
<br />
channel_first_int[][] variable is used as a flag for the ISR,<br />
This flag was being set after enabling the interrupts, There<br />
where situations when the isr occurred even before the flag was set<br />
due to which it was causing the application hang.<br />
This patch sets channel_first_int[][] flag just before enabling the<br />
interrupt.<br />
<br />
Reported-by: Some User<br />
Signed-off-by: Patch Developer<br />
Signed-off-by: Patch Reviewer<br />
<br />
*The second part is optional, separated by "---", contains the patch diffstat. It can also contain any notice for the patch reviewers to read. The second part won't be merged at the patch commit.<br />
<br />
*The third part is the diff, using unified diff, -p1 format. It is typically generated by a "git diff" command.<br />
<br />
Note: on the above, ''Some User'', ''Patch Developer'' and ''Patch Reviewer'' should be the full email of real persons, in the form: ''some name <some email>''.<br />
<br />
== Firmware submission ==<br />
<br />
Some devices may require [[Firmware|firmware(s)]] in order for the device drivers to work properly. In such cases, if the firmware is not already available, some sort of procedure is needed so that end users may make use of the driver.<br />
<br />
In the spirit of Open Source Software (OSS) development and distribution, it is most preferable if the firmware can be provided by submitting it as open source code, licenced under the GPL. Making the firmware open source facilitates tremendous advantages when it comes to debugging problems (i.e. the concept of many eyes to spot the trouble spots). Unfortunately, very few firmwares are submitted with sources, and, to be sure, this is certainly not a mandatory requirement. Indeed, as it currently stands, most firmware are instead provided in a binary format. However, there is an associated problem with distributing firmware as a closed source "binary blob" -- namely, for it to be made available within Linux distributions, it is required that each firmware should be provided with the distribution and redistribution rights, given specifically by the device or chipset manufacturer.<br />
<br />
Therefore, if you are a device vendor or original chipset manufacturer and wish to submit the requisite firmware for inclusion within Linux distributions, in order to do so, please email the [mailto://linux-media@vger.kernel.org Linux Media Mailing List (LMML)], and/or to [mailto:mchehab@infradead.org Mauro (the V4L/DVB Maintainer)], sending copies of the firmware files and the appropriate license terms. <br />
<br />
If the licensing terms are deemed acceptable for legally permitting wide redistribution of the firmware software, then the firmware files will be added at the [http://git.kernel.org/?p=linux/kernel/git/mchehab/linux-firmware.git V4L/DVB Linux-firmware git tree] and submitted to the upstream Linux-firmware tree.<br />
<br />
Note that there is no unique model for firmware licensing, but there are some examples provided within the [http://git.kernel.org/?p=linux/kernel/git/mchehab/linux-firmware.git;a=blob_plain;f=WHENCE;hb=HEAD WHENCE] file and within the several LICENCE files avaiable at the tree. The most common models for non GPL'd firmwares are: <br />
:* [[firmware model1]]<br />
:* [[firmware model2]]<br />
There are also some existing examples of firmwares released as Open Source Software:<br />
:* [[GPL model]]<br />
:* [[Cinergy T2 license]]<br />
<br />
== After you've Submitted: What happens Next? ==<br />
In conjunction with the move to the new Linux-media mailing list, V4L-DVB is now using the [http://patchwork.linuxtv.org/project/linux-media/list/ Patchwork tool] for aggregating patches sent into the list (you can read more about it [http://www.linuxtv.org/news.php?entry=2009-01-06.mchehab here] and [http://www.linuxtv.org/news.php?entry=2011-09-18.mchehab here]). In the past, it was, unfortunately, not uncommon for patches to be overlooked and become lost on the V4L-DVB mailing lists; thus making the adoption of the patchwork tool a very welcome addition. So, provided you have correctly submitted your patch (as discussed above), the steps towards having your code adopted will have automatically been put into motion. You can, of course, check to see the status of your submission from the [http://patchwork.kernel.org/project/linux-media/list/ Patchwork webpage]. If patchwork has not picked up your patch (after a reasonable period of time has elapsed), it is quite probable that your submission was incorrect for some reason; please review the information contained in the above section and try again.<br />
<br />
<div style="border: solid 1px; border-color: blue; margin: 1em; padding: 0.5em; background-color: Lavender;">"The most difficult problem isn't fixing bugs, but fixing bugs without breaking other configurations. There are many: different cards, different TV norms, whereas most of the developers can test only one TV norm." - Gerd Knorr</div><br />
<br />
After being picked up by patchwork, the first thing you should expect next is that a [[Development: Code Review|code review]] will be performed, and often this is by various parties. This may lead to a series of requests for you to fix any observed problems and require you to then resubmit your work, by repeating the same steps outlined above, until everyone is happy with the submission. In other words: wash, rinse, repeat ;)<br />
<br />
Then, when your patch is accepted, it will initially be applied to the main linux-media git tree. Once tested and integrated, such patches are later merged into a git tree by the V4L-DVB maintainer and, upon request, periodically pulled by Linus into one of his own git trees in an intermediate step towards final inclusion into the Linux kernel.<br />
<br />
[[Category:Development]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Supported_Hardware&diff=32250Supported Hardware2013-09-10T06:26:52Z<p>Js: Reverted edits by Domtheo (talk) to last revision by CityK</p>
<hr />
<div>This page is intended to help the "end user" determine whether or not the V4L-DVB device they own, or one that they are considering acquiring, is supported under Linux.<br />
{{Note|Just because your device happens to have a chip on it that corresponds to some existing driver does NOT mean your product is supported. The driver has to be aware that it's related to some hardware (typically through the [[Supported_Hardware#Determining_the_Device's_Identity|subsystem ID from the USB ID or PCI ID]]). If the driver doesn't recognize/bind to your particular hardware, then the module will probably load but then proceed to not do anything. In other words, support for your device would have to be added to the driver.}}<br />
<br />
<br />
== Determining the Device's Identity==<br />
Normally the device name and model are written somewhere on either the device itself, its box/packaging or, at the very least, listed in its manual. That may seem obvious enough, but a surprising number of devices are available with no, or next to little in the way of, model identification. Ordinarily, that would make for a rather problematic exercise of trying to find support information, however, there are a couple of steps you can do to help give you a starting point for your search (and these steps are just as relevant in the case where you know the device's identity, and you know that it is unsupported, but are seeking to see if it is possible to add support for it):<br />
<br />
'''A. With the device NOT installed within or attached to the system:'''<br><br />
Take note of any visual clues that will help identify the device. For PCI/PCIe based devices, see if there are any written text/numerical markings printed directly on the board or on IC components. With USB based devices, as they tend to be completely encased, it is difficult, if not impossible, to make any visual identifications of components used in the device's design without resorting to physically prying it open. The degree of difficulty of undertaking such a task can vary greatly, but in most cases the user can, with patience and care, find a way to non-destructively disassemble the device. (Nonetheless, anyone attempting such a venture should be prepared to fully accept the consequences of their own actions in the event of an unsuccessful attempt). If you are not willing to do so, proceed to step "B".<br />
<br />
Also note that, for older devices, the former bttv-gallery was a good resource for helping to identify a device; see [[Development:_How_to_add_support_for_a_device#bttv-gallery|here for more details]].<br />
<br />
'''B. With the device installed within or attached to the system:'''<br><br />
For PCI/PCIe based devices, the output of the following command may be able to aide you in making a determination <br />
:<code>$ /sbin/lspci -vnn</code><br />
In the output from those commands, look for lines with "Multimedia video controller", "Multimedia controller", "Multimedia adapters" or something similar. The item of particular interest is the '''Subsystem ID''' for that entry.<br />
<br />
Similarily, for USB devices, look at the output generated from the command<br />
:<code>$ /sbin/lsusb -v</code><br />
<br />
'''Note:''' Subsystem ID's are usually unique, but in some cases they are not. Meaning that sometimes two different devices have, unfortunately, been given the same ID. This in turn makes obtaining as many as possible identifiable aspects about a device (such as described in point "A" above) an important factor in making a precise device identification.<br />
<br />
== Support Information Resources==<br />
Armed with the information you obtained above (such as model name, subsystem ID, etc) try searching:<br />
<br />
===The V4L-DVB Wiki===<br />
A good first step is to check whether the device is listed as supported within the appropriate section of the wiki (see the "[[Hardware Device Information]]" section, as also linked to from the Main Pag,e for a starting point for your search. Though, it might be a good idea to also search this wiki using the device's name or the manufacturer name). If the device is not cited anywhere as being supported, then there is a good chance that it will not work under Linux. However, as the information in the wiki is not always current, and far from exhaustive, there are also other sources from which you can check.<br />
<br />
{{Note|'''Please be nice to the community and add your insights about your device to the appropriate area in this wiki if there currently is none !!! '''}}<br />
<br />
===The V4L-DVB source code===<br />
Navigate through the Linux media driver files (e.g. on your system try /usr/src/linux/drivers/media/, or check the corresponding directories on the git or hg repos you are interested in) and search for the relevant "xxxx-cards.c" file, as it will list devices supported by the "xxxx" driver. Example, within the file [http://git.linuxtv.org/media_tree.git/blob/HEAD:/drivers/media/video/saa7134/saa7134-cards.c saa7134-cards.c] is a listing of all the saa713x media controller IC based devices supported by the saa7134 driver. Similarly for exm28xx-cards.c, cx88-cards.c, etc. etc. ...<br />
<br />
===The Mailing Lists===<br />
You should also consider consulting the mailing list archives to see if there is any mention of the device. <br />
* The [mailto:majordomo@vger.kernel.org?body=subscribe%20linux-media Linux-Media Mailing List]. [http://vger.kernel.org/vger-lists.html#linux-media Subscription to the mailing list] is recommended, though it is not required.<br />
<br />
Older mailing list archives: Make sure you check both the V4L and DVB mailing lists, as topical misplacement/mis-posting often occurs (as many users are unaware of the distinction between the two different, but in many ways intertwined, subsystems). <br />
* MARC provides a comprehensive [http://marc.info/?l=linux-video searchable V4L archive] ... the actual m/l is archived [https://www.redhat.com/mailman/private/video4linux-list/ here] but requires authentication to access, nor is it as easily searched through<br />
* MARC also provides a [http://marc.info/?l=linux-dvb&r=1&w=2 searchable DVB archive], but its records are not comprehensive (and, as well as, contain a large gap). Therefore, for inquiries relevant to older equipment you will have to sift through either the [http://www.linuxtv.org/pipermail/linux-dvb/ new DVB mailing list] (which began Feb 2005) or use the likes of either a [http://www.google.ca/search?hs=NtR&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=site%3Alinuxtv.org&btnG=Search&meta= google site search] or [http://www.spinics.net/lists/linux-dvb/ spinics] to find even older (as well as present) DVB m/l postings...some further resources are also [http://www.linuxtv.org/lists.php mentioned here]. <br />
<br />
If that search step also proves unsuccessful, then you may wish to consider directly inquiring about the device's status on the relevant mailing list (but please search the archives first!) or #irc channel. Send the information obtained from steps "A" and "B" to the mailing list, along with other important information (such as what type of device it is, a link to a product page if you can find one etc etc). '''''But please first do a search through the archives<sup>*</sup> to make sure that this hasn't been submitted previously''''' --- a simple way to check if this has been the case is to search the archives for your device's subsystem ID (as determined in step "B").<br><br />
<br />
===Elsewhere on the Internet ===<br />
It is worth mentioning that there may be support for your device under Linux offered outside of that provided by LinuxTV, so a google search, using the appropriate combinations of terms, is also recommended. In addition, there are likely a number of websites (outside of the V4L-DVB wiki) that track hardware support -- For example, you can take a look at http://hardware4linux.info/type/87/ to see the note for the different devices.<br />
[[Category:Hardware]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=TerraTec_Cinergy_DT_USB_XS_Diversity&diff=32249TerraTec Cinergy DT USB XS Diversity2013-09-10T06:26:41Z<p>Js: Reverted edits by Domtheo (talk) to last revision by PaulePanter</p>
<hr />
<div>[[Image:TerraTec_Cinergy_DT_USB_XS_Diversity-1.jpg|thumb|200px|TerraTec-DT-USB-XS-Diversity-Stick]]<br />
A [[DVB-T]] [[DVB-T USB Devices|USB device]] from [[TerraTec]].<br />
<br />
It is supported under Linux.<br />
<br />
==Overview/Features==<br />
Features two tuners, and have two antennas. You’ll have adapter0 and adapter1 in /dev/dvb, which you can use separately. <br />
<br />
The ''Diversity'' option is a hardware based feature that allows for the device’s two receivers to be configured in a combined use mode to achieve better reception on a single channel. The diversity feature of the [[DiBcom]] demodulators is currently not implemented in the Linux-DVB drivers, so only the dual tuner configuration is presently supported on such devices [http://www.linuxtv.org/pipermail/linux-dvb/2007-July/019419.html].<br />
<br />
It seems that either this tuner stick does not have a very sensitive tuner, or the small antennas that come with it are simply insufficient for real-life use, unless one lives next door to a broadcast tower and has a direct line-of-sight to it. It is thus likely that an external antenna with a builtin amplifier is needed when this tuner is used.<br />
<br />
===Components Used===<br />
<br />
<br />
===Identification===<br />
Two identical looking devices are known. They can be distinguished by their USB ID:<br />
* The first device has USB ID 0ccd:005a. It is supported by the official sources (see below).<br />
* The second device has USB ID 0ccd:0081. It is supported by the official sources since 14.01.2009 – make sure your sources are up to date.<br />
<br />
Note: 0ccd is the Vendor USB ID (VID) of TerraTec, while 005a and 0081 are the Product USB ID (PID) of the sticks.<br />
<br />
===Other Images===<br />
<gallery perrow=5><br />
Image:TerraTec_Cinergy_DT_USB_XS_Diversity-front.jpg|front<br />
Image:TerraTec_Cinergy_DT_USB_XS_Diversity-back.jpg|back<br />
Image:TerraTec_Cinergy_DT_USB_XS_Diversity-front2.jpg|Input plugs<br />
</gallery><br />
<br />
<br />
{{Making-it-work:dvb-usb-dib0700}}<br />
<br />
<br />
=== Specific to the Model ===<br />
<br />
==== Specific Remote control support ====<br />
<br />
The remote is supported at least in the Mercurial repository (see '''Drivers''' section above).<br />
<br />
{{RemoteControlSupport:TerraTecGrayOrange}}<br />
<br />
=== Sample Kernel Output ===<br />
From 2.6.23-tuxonice-r6 (gentoo) with drivers compiled from repository 11th Feb 08:<br />
<br />
$ dmesg | grep -i dvb<br />
dvb-usb: found a 'Terratec Cinergy DT XS Diversity' in cold state, will try to load a firmware<br />
dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw'<br />
dvb-usb: found a 'Terratec Cinergy DT XS Diversity' in warm state.<br />
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.<br />
DVB: registering new adapter (Terratec Cinergy DT XS Diversity)<br />
DVB: registering frontend 0 (DiBcom 7000PC)...<br />
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.<br />
DVB: registering new adapter (Terratec Cinergy DT XS Diversity)<br />
DVB: registering frontend 1 (DiBcom 7000PC)...<br />
input: IR-receiver inside an USB DVB receiver as /class/input/input6<br />
dvb-usb: schedule remote query interval to 150 msecs.<br />
dvb-usb: Terratec Cinergy DT XS Diversity successfully initialized and connected.<br />
usbcore: registered new interface driver dvb_usb_dib0700<br />
<br />
===User Experiences===<br />
See the [[Talk:TerraTec Cinergy DT USB XS Diversity|talk page]].<br />
<br />
== External Links ==<br />
* [http://tven.terratec.net/modules.php?op=modload&name=News&file=article&sid=251 TerraTec product page]<br />
* [http://linux.terratec.de/ TerraTec Linux “support” page]<br />
[[Category:DVB-T USB Devices]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=SIGMACOM_SIGMA_HDTV5_X1&diff=31653SIGMACOM SIGMA HDTV5 X12013-02-01T14:24:27Z<p>Js: Reverted edits by JoshuaBrooks (talk) to last revision by Jimbley</p>
<hr />
<div>The [[SIGMACOM]] SIGMA HDTV5 X1 is an [[ATSC]] [[ATSC PCI Cards|PCI card]], and although there is presently no offical kernel support for the card, a [http://mandrake.joayo.net/mediawiki/index.php/8._%EC%97%91%EC%8A%A4_%EB%A9%80%ED%8B%B0%EB%AF%B8%EB%94%94%EC%96%B4_%EC%9D%91%EC%9A%A9_%ED%94%84%EB%A1%9C%EA%B7%B8%EB%9E%A8#HDTV_On_Mandriva Mandrake JoayoNET] (Korean wiki) article outlines how to get it working under Linux.<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" bgcolor="yellow" style="background:white;"<br />
|- style="background:#efefef;" |- align="center"<br />
! - align="left"|'''Vendor <BR> Model''' !! Added to<BR>Kernel !! align="left"|'''Frontend'''|!! '''Bridge Interface''' !! '''8VSB''' !! '''QAM''' !! '''NTSC''' !! '''Other Features'''<br />
|- align="center"<br />
| - align="left" valign="top"|'''[[SIGMACOM]] <BR> [[SIGMACOM SIGMA HDTV5 X1|SIGMA HDTV5 X1]]'''|| n.a. || - align="left"|LG TDVS-H064P <BR>''* Infineon TUA6034 tuner''<BR>''* Philips TDA9887 demodulator (A)'' <BR>''* LG DT3303 demodulator (D)'' || [[Conexant CX2388x|Conexant CX23881]] || yes || yes || yes || - align="left"| * S-Video & Composite inputs<br />
|}<br />
<br />
<br />
There are actually several near identical cards in the SIGMA HDTV5 X1 family. From the promotional photos on SIGMACOM's websites, one can see that:<br />
* there is scant difference in the appearance between the older SIGMA Cyber HDTV II, the SIGMA HDTV5 Penta and the SIGMA HDTV5 X1 <br />
** the Penta model even has 'Cyber HDTV II' silk screened on the PCB, whereas the X1 has "SMT-30" <br />
* the layout of the X1 Star and X1 365 are clearly identical to the above boards except both share a slightly longer PCB (both cards are silk screened "SMT-31")<br />
** although the extended portion of the X1 Star's PCB contains traces and spots for circuitry, it is essentially barren. The X1 365, on the otherhand, contains the additional circuitry and has several headers in the extended portion of the card's PCB.<br />
** the X1 365 also has what appears to be a 2nd S-Video port<br />
<br />
Whether or not the Mandrake JoayoNET instructions will work for all the cards in the X1 family is unclear, but given their high degree of similarity, it is quite reasonalbe to assume that they should.<br />
<br />
The X1 cards are highly similar to the [[DViCO FusionHDTV5 Gold]].<br />
<br />
<br />
[[image:sigmax1.jpg]]<br />
<br />
<br />
==External Links==<br />
* [http://www.sigmacom.co.kr/m1/m1_view.htm?p=&no=132 SIGMA HDTV5 X1]<br />
* [http://www.sigmacom.co.kr/m1/m1_view.htm?no=166 SIGMA HDTV5 X1 Star]<br />
* [http://www.sigmacom.co.kr/m1/m1_view.htm?p=&no=150 SIGMA HDTV5 X1 365]<br />
* [http://www.sigmacom.co.kr/eng/m1/m1_view.htm?p=1&no=6 SIGMA HDTV5 Penta]<br />
* [http://www.sigmacom.co.kr/m1/m1_view.htm?p=&no=22 SIGMA Cyber HDTV II]<br />
[[Category:ATSC PCI Cards]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Decoder&diff=31619Decoder2013-01-16T16:27:00Z<p>Js: Reverted edits by Badrieastham (talk) to last revision by Alec v</p>
<hr />
<div>Taken from the Linux kernel Documentation/video4linux/[http://trac.mcs.anl.gov/projects/ZeptoOS/browser/tests/linux-2.6.19.2svn/Documentation/video4linux/Zoran?rev=3131 Zoran]<br />
<br />
<br />
<br />
The best know TV standards are NTSC/PAL/SECAM. but for decoding a frame that<br />
information is not enough. There are several formats of the TV standards.<br />
And not every TV decoder is able to handle every format. Also the every<br />
combination is supported by the driver. There are currently 11 different<br />
tv broadcast formats all aver the world.<br />
<br />
The CCIR defines parameters needed for broadcasting the signal.<br />
The CCIR has defined different standards: A,B,D,E,F,G,D,H,I,K,K1,L,M,N,...<br />
The CCIR says not much about the colorsystem used !!!<br />
And talking about a colorsystem says not to much about how it is broadcast.<br />
<br />
The CCIR standards A,E,F are not used any more.<br />
<br />
When you speak about NTSC, you usually mean the standard: CCIR - M using<br />
the NTSC colorsystem which is used in the USA, Japan, Mexico, Canada<br />
and a few others.<br />
<br />
When you talk about PAL, you usually mean: CCIR - B/G using the PAL<br />
colorsystem which is used in many Countries.<br />
<br />
When you talk about SECAM, you mean: CCIR - L using the SECAM Colorsystem<br />
which is used in France, and a few others.<br />
<br />
There the other version of SECAM, CCIR - D/K is used in Bulgaria, China,<br />
Slovakai, Hungary, Korea (Rep.), Poland, Rumania and a others.<br />
<br />
The CCIR - H uses the PAL colorsystem (sometimes SECAM) and is used in<br />
Egypt, Libya, Sri Lanka, Syrain Arab. Rep.<br />
<br />
The CCIR - I uses the PAL colorsystem, and is used in Great Britain, Hong Kong,<br />
Ireland, Nigeria, South Africa.<br />
<br />
The CCIR - N uses the PAL colorsystem and PAL frame size but the NTSC framerate,<br />
and is used in Argentinia, Uruguay, an a few others<br />
<br />
We do not talk about how the audio is broadcast !<br />
<br />
A rather good sites about the TV standards are:<br />
http://www.sony.jp/ServiceArea/Voltage_map/<br />
http://info.electronicwerkstatt.de/bereiche/fernsehtechnik/frequenzen_und_normen/Fernsehnormen/<br />
and http://www.cabl.com/restaurant/channel.html<br />
<br />
Other weird things around: NTSC 4.43 is a modificated NTSC, which is mainly<br />
used in PAL VCR's that are able to play back NTSC. PAL 60 seems to be the same<br />
as NTSC 4.43 . The Datasheets also talk about NTSC 44, It seems as if it would<br />
be the same as NTSC 4.43.<br />
NTSC Combs seems to be a decoder mode where the decoder uses a comb filter<br />
to split coma and luma instead of a Delay line.<br />
<br />
But I did not defiantly find out what NTSC Comb is.<br />
<br />
Philips saa7111 TV decoder<br />
:was introduced in 1997, is used in the BUZ and can handle: PAL B/G/H/I, PAL N, PAL M, NTSC M, NTSC N, NTSC 4.43 and SECAM<br />
<br />
Philips saa7110a TV decoder<br />
:was introduced in 1995, is used in the Pinnacle/Miro DC10(new), DC10+ and can handle: PAL B/G, NTSC M and SECAM<br />
<br />
Philips saa7114 TV decoder<br />
:was introduced in 2000, is used in the LML33R10 and can handle: PAL B/G/D/H/I/N, PAL N, PAL M, NTSC M, NTSC 4.43 and SECAM<br />
<br />
Brooktree bt819 TV decoder<br />
:was introduced in 1996, and is used in the LML33 and can handle: PAL B/D/G/H/I, NTSC M<br />
<br />
Micronas vpx3220a TV decoder<br />
:was introduced in 1996, is used in the DC30 and DC30+ and can handle: PAL B/G/H/I, PAL N, PAL M, NTSC M, NTSC 44, PAL 60, SECAM,NTSC Comb<br />
<br />
Samsung ks0127 TV decoder<br />
:is used in the AVS6EYES card and can handle: NTSC-M/N/44, PAL-M/N/B/G/H/I/D/K/L and SECAM</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Radio_Listening_Software&diff=31340Radio Listening Software2012-10-26T17:11:46Z<p>Js: Reverted edits by Ipodsoft (talk) to last revision by CityK</p>
<hr />
<div>__NOTOC__<br />
__NOEDITSECTION__<br />
<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;"><br />
{| style="background-color:#F7F9FB;" cellspacing=0 cellpadding=5 border=0 <br />
| valign=top | [[Image:Radio_icon.png|50px]]<br />
|<br />
== '''Radio Listening Software:'''==<br />
|}<br />
There are a number of [[Radio devices]], in particular those TV tuner devices which also contain a radio receiver/tuner, for which V4L directly supports. The following list of software applications allow one to control a radio tuner.<br />
<br />
== Radio Applications ==<br />
Gnomeradio and kradio, the most fully featured applications, are not yet available in all distributions and need to be compiled first. Some of the older applications are mature and readily available, but no longer actively developed.<br />
<br />
* [[fftv]] [http://fftv.sourceforge.net/]<br />
* [[fmtools]]<br />
* [http://gkrellm.luon.net/gkrellm-radio.phtml gkrellm-radio] -- minimalistic [http://gkrellm.net gkrellm] plugin to control radio tuners<br />
* [http://www.wh-hms.uni-ulm.de/~mfcn/gnomeradio gnomeradio] -- for Gnome, capable of recording<br />
* [http://www.gnu.org/software/gnuradio/ GNU Radio] -- the GNU software radio, testing phase; cf. [http://comsec.com/wiki?GnuRadio2.X wiki]<br />
* [http://foobazco.org/projects/gradio/ gradio] -- in Debian, but not currently active<br />
* [[ivtv-radio]] [http://ivtvdriver.org/index.php/Howto:Radio_tuner] -- part of the ivtv-utils package<br />
* [http://kradio.sourceforge.net/ KRadio] for KDE<br />
* [[MPlayer#Using_MPlayer_for_Radio_Listening|MPlayer]] -- media player for Linux. See link for radio usage information <br />
* [[radio]] -- a n-curses-based radio application (part of the [[Xawtv#Associated_Utilities|xawtv package]]) <br />
* [http://whats.all.this.brouhaha.com/?p=199 radioshark] -- application to control the griffin radioshark<br />
* [https://sourceforge.net/projects/xdradio/ XDRadio] --- XDialog wrapper for radio listening<br />
* [http://goodies.xfce.org/projects/panel-plugins/xfce4-radio-plugin/ xfce4-radio-plugin] -- plugin for the [http://www.xfce.org/ Xfce] panel<br />
* [http://silicone.free.fr/xmms-FMRadio/ xmms-fmradio] -- plugin for [http://www.xmms.org/ XMMS], last version autumn 2004, Debian and Red Hat packages<br />
<br />
==Also See==<br />
* For [[Radio Data System (RDS)#What devices can receive RDS information|devices capable of receiving RDS information]], see the associated [[Radio Data System (RDS)#User applications|userspace applications]].<br />
* [[dvbradio]] (part of the [[xawtv#Associated_Utilities_2|v4 xawtv package]]) as an example of a specific application for listening to radio streams embedded within dvb transport streams<br />
<br />
</div><br />
<br />
== User experiences ==<br />
<br />
If you're a user, post your installation and user experiences here!<br />
<br />
=== gnomeradio ===<br />
Clearly a more sophisticated application. There's only a debian package for i386, so I'll need to build from the tarball. Since I'm mainly interested in remote recording, I'll try fmtools and radio first.<br />
<br />
=== gradio ===<br />
I tried gradio on Debian amd64, as it's available; it's very basic. If you don't have the card on /dev/radio, start with <br />
<br />
gradio -d /dev/radio2<br />
<br />
No recording capability, stable gui, minimal functionality -- tuner and volume. I had to hand-edit the .gradiorc configuration file to get station presets; I may have missed some way of doing this through the gui.<br />
<br />
[[Category:Radio]]<br />
[[Category:Software]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Main_Page&diff=31297Main Page2012-09-28T06:32:20Z<p>Js: Reverted edits by Jasonsi (talk) to last revision by CityK</p>
<hr />
<div>__NOTOC__<br />
__NOEDITSECTION__<br />
<br />
<div style="background-color:#6289AB; padding:0.3em; color:#ffffff; font-weight:bold; font-size:150%; text-align:center"><br />
Welcome to the linuxtv.org V4L-DVB Wiki !<br />
</div><br />
{|valign=top background=none<br />
|valign=top|<br />
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff"><br />
<br />
{|valign=top cellpadding=0 cellspacing=0 width=100%<br />
<br />
|valign=top bgcolor=#F7F9FB width=49%|<br />
==What is this wiki about?==<br />
This wiki is intended to become an authoritative source of information regarding the use of analog video and digital TV sources under Linux -- i.e. [[What is V4L or DVB?|the subject matters covered under the V4L & DVB frameworks]]. The basic plan is to aggregate information about available hardware, how V4L or DVB work, software used with the hardware and so forth. Like all other wikis, the V4L-DVB wiki relies upon the contributions of its users. Hence, it will only be as useful as we make it! <br> <br />
<br><br />
<div style="text-align:right">-- [[LinuxTVWiki:People|The LinuxTV V4L-DVB wiki team]] / [[People behind V4L-DVB]] </div><br />
<br />
|valign=top bgcolor=#F7F9FB width=2%|<br />
|valign=top bgcolor=#F7F9FB width=49%|<br />
<br />
==How can I help with the wiki?==<br />
We encourage you to share your knowledge and help with the task of turning this site into a grand repository of knowledge. Your input, whether it be for providing a set of instructions as to how to get a certain device working, or an explanation for some complex concept, or improving an existing article by correcting something even as simple as a spelling mistake, will be highly appreciated. Here are a few basic links that can help you get started:<br />
* [[Help:Contents|Everything you need to know about editing wiki pages but were afraid to ask]]<br />
* [[Wiki - Help Wanted List|A list of things that need to be tackled]] <br />
* [[Wiki - New Device Copy & Paste Template|New Device Copy & Paste Template]]<br />
|}<br />
|}<br />
</div><br />
<br />
{| style="border: solid 1px; border-color:#6289AB; margin: oem; background-color: #6289AB;" cellspacing=5 cellpadding=1 width="100%"<br />
| valign=top |<br />
<br />
{| cellspacing=0 cellpadding=5 border=0 width="100%"<br />
<br />
<br />
| valign=top | [[Image:index.png|50px]]<br />
| valign=top | '''[[Special:Allpages|The Wiki's Indexes]]'''<br><small>Article, category, image, .... <br />
| valign=top ; style="background-color:#FFFFCC;" | [[Image:User_Info_icon.png|50px]]<br />
| valign=top ; style="background-color:#FFFFCC;" | '''[[User Information]]'''<br><small>How to install drivers for your hardware, and software to use with your device, ... <br />
| valign=top ; style="background-color:#F5DEB3;" | [[Image:Technical_background_icon.png|50px]]<br />
| valign=top ; style="background-color:#F5DEB3;" | '''[[Technical Background]]'''<br><small>Technical details on standards and hardware components/chipsets, etc<br />
|-<br />
|-<br />
|-<br />
<br />
| valign=top | [[Image:More_info.png|50px|]]<br />
| valign=top | '''[[Other Sources of Info]]'''<br><small>Mailing lists, #irc channels....<br />
| valign=top ; style="background-color:#FFFFCC;" | [[Image:Hardware_icon.png|50px]]<br />
| valign=top ; style="background-color:#FFFFCC;" | '''[[Hardware Device Information]]'''<br><small>Information on hardware devices <br />
| valign=top ; style="background-color:#F5DEB3;" | [[Image:Developer_icon.png|50px]]<br />
| valign=top ; style="background-color:#F5DEB3;" | '''[[Developer Section]]'''<br><small>Information to help device driver development<br />
|-<br />
|-<br />
|-<br />
<br />
|}<br />
|}<br />
<br />
<br />
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff"><br />
{|valign=top cellpadding=0 cellspacing=5 width=100%<br />
| [[Image:News_icon2.png|50px]] '''GENERAL NEWS:''' <br><br />
'''Announcement: 2012 Media Subsystem Summit'''<br><br />
Once again, the Linux Media Subsystem looks to hold its own workshop, running along side and during the 2012 Linux Kernel Summit (KS/2012), being held, between August 26-28th, in San Diego, CA., U.S.A. Preliminary discussions about the range of topics and details for the forthcoming event can be found in a pair of threads on the mailing list (unfortunately, the discussion got fractured into two for some unimportant reason):<br />
* http://www.mail-archive.com/linux-media@vger.kernel.org/msg49006.html<br />
* http://www.mail-archive.com/linux-media@vger.kernel.org/msg49169.html<br />
If you wish to see particular subject matters addressed during the summit or are interested in participating in the series talks, now is the time to figure that all out! --19:32, 21 July 2012 (CEST)<br />
<br><br />
<br><br />
<br />
'''Look Out GSoC, Here Comes CSoC (Crope's Summer of Code) !'''<br><br />
A (very) belated congratulations goes out to Antti Palosaari (aka "Crope" on IRC) for his project's acceptance into this year's [http://code.google.com/soc/ GSoC]. Antti will be focusing on bringing improvements to the DVB USB framework and, as well, to the DVB-core itself. More information can be found in the following links:<br />
* http://www.mail-archive.com/linux-media@vger.kernel.org/msg46062.html<br />
* http://www.google-melange.com/gsoc/project/google/gsoc2012/crope/10001<br />
* http://blog.palosaari.fi/<br />
And, if your curiosity has really been piqued by this, but the above links prove insufficient, you can find even further details related to this work in a number of the discussions that have occurred on the Linux-media mailing list over the past eight weeks or so. <br />
<br />
Hopefully in the future we shall see further interest and participation in the GSoC program; it really is an excellent opportunity afforded to students and there are just sooooo many areas in the realm of V4L-DVB code that could use improvement/refinement and, hence, could make for interesting summer projects. --06:47, 2 July 2012 (CEST) <br />
|-<br />
| align=right| <span style="font-size: 50%;">''For older news items see [[News Archive|here]]</span><br />
|}<br />
</div><br />
<br />
<br />
<br />
[[Category:LinuxTV]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers&diff=31170How to Obtain, Build and Install V4L-DVB Device Drivers2012-08-20T06:04:33Z<p>Js: Reverted edits by Llnbig (talk) to last revision by Kjoekjoe</p>
<hr />
<div>The LinuxTV project hosts the latest set of Linux kernel driver modules for [[What is V4L or DVB?|V4L-DVB devices]]. This page contains information to help an "end user" install these device drivers in a GNU/Linux system. <br />
<br />
{{Note|This article assumes that:<br />
* your device is actually supported by the drivers -- Just because your board happens to have a chip on it that corresponds to some existing driver does NOT mean your product is supported. The driver has to be aware that it's related to some hardware (typically through the [[Supported_Hardware#Determining_the_Device's_Identity|subsystem ID from the USB ID or PCI ID]]). If the driver doesn't recognize/bind to your particular hardware, then the module will probably load but then proceed to not do anything. In other words, support for your device would have to be added to the driver.<br />
* you have already physically installed the hardware device into, or connected it to, your system. (Refer to the manufacturer's instructions for such details)}}.<br />
<br />
== Software Requirements ==<br />
===Kernel Support===<br />
The LinuxTV V4L-DVB drivers will work only in conjunction with relatively modern 2.6 kernels; specifically, <br />
<br />
{{Note|CityK here: I have no clue as to where the current backwards compatibility status stands. Suffice to say, more modern kernels (which I'd define as ~2.6.32 and newer) are much more likely to work with the new media_build snapshots of the git tree. When the situation is more clear, please update this section accordingly.}}<br />
<br />
===Additional Software Requrirements===<br />
In order to be able to build the V4L-DVB kernel driver modules, you will need: <br />
* kernel-source or kernel-headers<br />
* (OpenSuSE and fedora only) kernel-devel<br />
* (Debian) libdigest-sha1-perl<br />
* make <br />
* gcc<br />
* git<br />
* patch<br />
* patchutils<br />
* libproc-processtable-perl ("perl-Proc-ProcessTable")<br />
If these packages are not currently installed on your system, you should do so now.<br />
<br />
==Retrieving and Building/Compiling the Latest V4L-DVB Source Code==<br />
There are a couple of different methods by which you can obtain and build the latest source code. Regardless of which route you take, all are performed from the command line within a console. The "basic" method is likely appropriate for most end users, though, in some cases, some users will have to use the slightly more "manually intensive" approach. This second approach is effectively, for all intents and purposes, really just the same as the "basic" method, but performing the steps in a piecemeal fashion affords you the opportunity to tailor the source code or the "make"/build process as might be required in your particular situation. Again, before proceeding with either approach, make sure you have installed all the prerequisite software listed above.<br />
<br />
{{Note|If you are using Ubuntu, you were previously very likely to run into a fatal compilation error within the v4l-dvb build process when it reaches the firedtv module. The reason for this is because Ubuntu had a bug in their packaging of the kernel headers. <b>This seems to be fixed</b> on a fully updated systtem (5 July 2011) This was a long standing issue, and one of the most frequently reported on the mailing list. <br><br />
If you still have the problem, you should be able to correct this compilation problem by following the more manual procedure listed below. In particular, before proceeding to build the modules, you will have to edit the file ''v4l/.config'' and change the line for the firedtv driver from <nowiki>"firedtv=m" to "firedtv=n"</nowiki>.}}<br />
<br />
{{Note|If you are having build failures like "implicit declaration of function 'mfd_get_data'" try editing v4l/Makefile.media, and just comment out anything related to CONFIG_*_TIMBERALE. [[http://sourceforge.net/mailarchive/message.php?msg_id=27353778 Source]] }}<br />
<br />
<br />
<br />
{| class="wikitable" <br />
|+'''Retrieving the Source Code & Building/Compiling the Modules'''<br />
|-<br />
! "Basic" Approach !! Developer's Approach !! More "Manually Intensive" Approach<br />
<br />
|-<br />
| valign=top |<br />
git clone git://linuxtv.org/media_build.git<br />
cd media_build <br />
./build<br />
<br />
These commands will download the newest tarball of the source code from linuxtv.org, apply the backport patches to it and then build/compile the source via the included script build.sh. <br />
<br />
NB: to add a patch copy the .patch file to the backports directory, and add the patch file as a line to the {kernel-version}_series file in the packports dir.<br />
| valign=top |<br />
~ $ git clone git://linuxtv.org/media_build.git<br />
~ $ cd media_build <br />
~/media_build $./build --main-git<br />
{{Note|'''The build script will clone the entire media-tree.git, with will take some time'''}}<br />
<br />
In order to modify a driver foo.c:<br />
<br />
~/media_build $ cd media<br />
~/media $ gedit drivers/media/video/foo.c<br />
~/media $ make -C ../v4l<br />
~/media $ make -C ../ install<br />
~/media $ make -C .. rmmod<br />
~/media $ modprobe foo<br />
<br />
(some procedure to test the "foo" driver)<br />
<br />
To generate a patch, use:<br />
<br />
~/media $ git commit -as<br />
<br />
Then submit the patch upstream. If your sendmail is properly configured, you can easily send the patch upstream with:<br />
<br />
~/media $ git send-email HEAD^1<br />
<br />
or, to send a patch series:<br />
<br />
~/media $ git send-email ''initial_branch''<br />
<br />
Where ''initial_branch'' is the name of a branch of a changeset number for the last patch before your changes.<br />
<br />
|<br />
git clone git://linuxtv.org/media_build.git<br />
cd media_build/linux<br />
make tar DIR=<some dir with media -git tree><br />
make untar<br />
cd ..<br />
<br />
If you need to make any sort of change or modification to the source code, now is the time. <br />
<br />
<div style="border: solid 1px; border-color: blue; margin: 1em; padding: 1em; background-color: Lavender;"><br />
'''Optional Pre-Compilation Steps'''<br><br />
These optional command steps are applicable only in certain situations approaching a new build of the driver set, or for experienced users wishing to streamline the build process to consist of only those components they want to install.<br />
* <code>make rminstall</code> ... you would use this to remove the currently installed driver set (located within the relevant ''/lib/modules/["kernel version"]/kernel/drivers/media'' directory to which they were installed)<br />
* <code>make distclean</code> ... cleans up the build configuration environment ... noteworthy is that it will set things up such that a following "make" build process will be against "''/usr/src/[uname -r]''” kernel source<br />
* <code>make menuconfig</code> ... this will open up the ncurses based menu that allows you to select only those components you wish to build and install<br />
<br />
The building system offers some other make targets that may be useful for advanced users or developers. For listing the supported targets, please use <code>make help</code>.</div><br />
<br />
Next, build/compile the modules from the source code with the command:<br />
make<br />
{{Note|For multi-core processor systems, the ''make'' command has available options that can be beneficial in terms of the reducing the amount of time required for the process' completion. Specifically, you can run "''make -jN''" (where "''N''" <nowiki>=</nowiki> 1 + the number of cores your cpu has ... i.e. if you have a dual core cpu use: ''make -j3'' )}}<br />
<br />
|}<br />
===Information Regarding the Build Process===<br />
Generally, this step will tend to take a while to complete; being dependent upon both the number of modules being built and your system's processing power.<br />
<br />
You can monitor the build progress via the console output. You will notice that a ''/v4l'' directory will have been created and within which the completed *.ko module files are written. Some drivers included within the snapshot may have their own requirements in regards to the kernel that you must be running in order for the module to be built; such cases can be found listed at the beginning of the build process' console output.<br />
<br />
The entire build process should complete without error. If any errors are encountered, the compilation will be halted and, at this point, you should not attempt to proceed any further (unless you really, really enjoy experiencing the outcome of a preordained failure). Errors that prevent building a particular V4L-DVB snapshot do indeed surface from time to time, but these are usually corrected quickly upon notification from an end user submitted [[Bug Report|bug report]], or upon detection from the daily automated build tests (see note below). If you have run into a build error via the "basic" approach outlined above, you may wish to see if you can remedy the error and attempt a module build via the more "manually intensive" approach also outlined above.<br />
<br />
{{Note|'''The Daily Automated Build Tests'''<br><br />
Hans Verkuil has set up an automated daily build of the V4L-DVB source code upon all supported kernels, as well as testing that very same upon several CPU architectures. A brief synopsis of the results from those tests is published each day on the Linux-Media Mailing List (LMML) under a message subject heading prefix of "''[cron job] v4l-dvb daily build ...''". A link to more detailed results of these tests is also provided within that message or can be found directly from [http://www.xs4all.nl/~hverkuil/logs/ here].}} <br />
<br />
If you do run into any problems during the build step, you should:<br />
* first, see whether the issue is already known or not -- consult the results of the daily automated build tests (see note above)<br />
* if it appears that this is a new issue, please [[Bug Report|inform the developers of the bug via the LMML]] (preferred) or thorough one of the irc.freenode.net irc channels (#v4l or #linuxtv or #dvb).<br />
* you may also wish to consult any errata that might be found on this article's talk page<br />
<br />
In general, if the source builds correctly, it is likely that the drivers will work, though this is not a guarantee.<br />
<br />
== Installing the Compiled Driver Modules ==<br />
The next step is to install the kernel driver modules by executing:<br />
sudo make install<br />
The command above will prompt you for your root password, and will then copy the *.ko module files you built in the above step into the ''/lib/modules/[kernel version]/kernel/drivers/media'' directories. <br />
<br />
{{Note|If your distribution doesn't support the sudo command (i.e the command line returns ''"bash: sudo: command not found"''), use the "su" command instead. "su" will prompt you for the root password, and after which entering, you can then proceed with the command. Ex.:<br />
su<br />
make install<br />
}}<br />
<br><br />
{{Note|In the case where you have more then one kernel installed but have used the pre-compilation option of "make distclean", the new modules will be installed only into the ''/lib/modules/[uname -r]/kernel/drivers/media'' directory}} <br><br />
<br />
== First Use: Out with the Old, In with the New==<br />
{| <br />
| valign=top |<br />
Before trying to use the device with your newly installed driver set, you should remove from system memory any older versions of related modules that may have been loaded by the running kernel; otherwise, you will likely run into various fatal mismatch errors -- typified by an "unknown symbol" or "unknown parameter" -- as a result of your system trying to work from a mixture of old and new modules. <br />
<br />
To achieve a [[Wikipedia:Tabula rasa |clean slate]] state, you could either: <br><br />
<br />
'''1. Reboot:''' Perhaps the most straightforward thing to do at this point, particularly for Linux newbies, is to just restart your system; the reboot will, obviously, clear out the old modules loaded into memory and, as an added bonus, create a fresh running environment under which the new modules should have been automagically loaded into system memory. <br />
<br />
Or, on the other hand,<br />
<br />
'''2. Take care of business yourself:''' More experienced users might prefer to use more eloquent approaches. For example, using <br />
sudo make unload<br />
will essentially (and similar as to manually using "rmmod" commands) remove all older modules for the device that might be currently loaded in memory by the running kernel. After which, one can then load, from the newly installed device driver set, the appropriate modules for the device using relevant<br />
modprobe ''driver_name'' <br />
commands.<br />
<br />
| valign=top halign=right width=30% |<br />
<div style="border: solid 1px; border-color: blue; margin: 1em; padding: 1em; background-color: Lavender;"><br />
'''For Advanced Users'''<br><br />
The following information is likely useful only for developers. After building the modules as per usual ("make"), and without needing to install them, you can:<br />
* remove all older modules from memory at once using "make unload" and <br />
* then insert all the newly built modules into memory for the running kernel with "make load"<br />
Alternatively, to perform the previous two commands ("make unload" and "make load") in a single step, you can use "make reload"<br />
<br />
Note, however, that it is highly recommended that you avoid using either the make load or make reload options, as they will end up inserting <u>all</u> V4L-DVB device drivers into memory, and that may introduce instability, or complicate testing.<br />
</div><br />
|}<br />
Regardless of which approach you take to remove the old modules and to insert the new ones, the end result should be the same. In addition, upon future starts of your system, your device should "automagically" be detected and will have the appropriate driver modules loaded into memory. <br />
<br />
===If the Modules load correctly:===<br />
Provided that the modules were loaded correctly into system memory:<br />
<br />
'''1. They should be listed in ''/proc/modules''''': you can use either <code>cat /proc/modules</code> or, even better, <code>lsmod</code> to see this content.<br />
<br />
Which modules should you be looking for? Well, the answer to that question depends entirely upon the chipsets used by your device -- see the relevant wiki article for your device for a listing of such components and required drivers (or search the web if such information does not exist. '''Note''': Please add any information missing from the wiki!)<br />
<br />
'''2. They should provide some indication within your system log''': you can consult the output from the "<code>dmesg</code>" command or directly review your system log file (typically housed within the ''/var/log'' directory) for indication that they have been successfully loaded and that the device is now correctly configured for operation. Examples of successful module loads are provided by users under the "Sample kernel output" section in many device articles witin the wiki.<br />
<br />
'''3. The device manager [[Wikipedia:udev|udev]] will "automagically" create appropriate [[Device nodes and character devices|device nodes]] on ''/dev''''': <br><br />
'''(a) For a DVB device''', you should now have a non-empty ''/dev/dvb'' directory. You can check on whether this is true for you with the following command:<br />
: <code>ls -l /dev/dvb/</code><br />
(alternatively, you can browse your directory structure with the graphical file manager of your choice). If you have a single DVB device installed in your system, then the output of the above command should reveal that /dev/dvb/ is populated by adapter0. Digging further, <br />
: <code>ls -l /dev/dvb/adapter0 </code><br />
reveals the [[Device_nodes_and_character_devices#DVB_character_devices|character devices]] associated with adapter0 for which the drivers have control. If you have more then one DVB device, you can see the same for all with <br />
: <code>ls -l /dev/dvb/adapter* </code><br />
<br />
'''(b) For a V4L device''', you should now have a non-empty ''/dev/v4l'' directory. You can check on whether this is true for you with the following command:<br />
: <code>ls -l /dev/v4l</code><br />
Digging further, <br />
: <code>ls -l /dev/v4l/by-path </code><br />
reveals the symbolic links to the [[Device_nodes_and_character_devices#V4L_character_devices|character devices]] associated with your V4L adapter for which the drivers have control. The most typical of which is ''/dev/video0''. If you have more then one V4L device, you can see the same for all with <br />
: <code>ls -l /dev/video* </code><br />
<br />
===If the Modules did not load correctly or the device is still not configured correctly for use:===<br />
There could be several reasons why you may have encountered a module loading error or, absent such an error, why the device is still not configured correctly for use, even after having correctly followed the steps from the above procedure. If either of these cases applies, the very first thing you should do is [[Supported Hardware|check whether your device is actually supported]] by the driver (see the very first note at the top of this page). Next, provided your device is supposed to be supported, check within your system log/dmesg for any messages that may give indication as to the problem. The following points address a few common trouble spots:<br />
<br />
'''Module Load Order Can Matter'''<br />
* in cases where loading more then one module is necessary, the order in which you load the modules can matter! <br />
<br />
'''Sometimes Automagic just isn't Automagic'''<br />
* If a module was, for whatever reason, not loaded, you can try manually loading it with the appropriate ''modprobe'' command.<br />
<br />
'''Unresolved Symbols'''<br />
* if you tried the second method ("make unload" followed by an appropriate modprobe command) but encountered errors in relation to unresolved symbols, e.g. using the saa7134 module as an example:<br />
sudo modprobe saa7134<br />
FATAL: Error inserting saa7134 (/lib/modules/''[your kernel version]''/kernel/drivers/media/video/saa7134/saa7134.ko):\ <br />
Unknown symbol in module, or unknown parameter (see dmesg) <br />
please try a system reboot before filing an [[Bug Report|error report]]. Irregardless of what caused the unresolved symbols errors, usually, after performing the reboot, you will find that the install was actually successful and the drivers will work as intended.<br />
<br />
* Special case: If your system uses compressed kernel modules, after running the "make install" command of the V4L-DVB installation process, you could end up with a mixture of new modules (*.ko) and their older compressed version (*.ko.gz) installed. If the system attempts to concurrently load both sets into memory, you are bound to run into modprobe insertion errors (eg. unknown symbol or unknown parameter). All conflicting *.ko.gz files must be removed. The following command line can help you locate these conflicting files in all your installed kernels:<br />
for file in `find /lib/modules -name "*.ko"`; do if <nowiki>[[</nowiki> -e $file.gz <nowiki>]]</nowiki>; then echo "$file.gz should be removed"; fi; done<br />
Usually all conflicting module files resulting of v4l-dvb installation will be located in:<br />
/lib/modules/''[your kernel version]''/kernel/drivers/media<br />
Once the conflicting *.ko.gz have been moved elsewhere or renamed (to *.ko.gz.disabled for example), use the v4l-dvb reload command and, to be safe, also add a "depmod" step in order to rebuild modules dependencies):<br />
make reload<br />
depmod -a<br />
Your new modules should now be loaded correctly.<br />
<br />
'''A Note on Firmware'''<br />
* You have all the modules active (listed in lsmod) but device nodes are nowhere to be found: The problem may be as simple as the [[Firmware|firmware]] for the device not being loaded; some devices also require a [[Firmware|firmware]], which is uploaded from the host PC to the device, in order to operate. <br />
<br />
In some cases, when the device is correctly recognized, the associated drivers provide information as to which firmware file is required -- look in the system log output. For example, for many [[TechnoTrend]] & [[Hauppauge]] (and other similar "premium" cards), if the dvb-ttpci firmware is not available you will observe an error such as:<br />
<pre> dvb-ttpci: could not load firmware, file not found: dvb-ttpci-01.fw<br />
dvb-ttpci: usually this should be in /usr/lib/hotplug/firmware or /lib/firmware<br />
dvb-ttpci: and can be downloaded from http://www.linuxtv.org/download/dvb/firmware/</pre><br />
Resolving that missing firmware issue should then result in proper detection and configuration of your device.<br />
In other cases, obtaining the correct firmware is not so straightforward a task. The very first thing you need to know is what device you're using; see "[[Supported_Hardware#Determining_the_Device's_Identity|Determining the Device's Identity]]". Once you have established which particular device you are in possession of, you can then move on to [[Firmware#Acquiring the Firmware|obtaining the correct firmware]]. In addition, information in wiki articles (eg. such as [[DVB-T USB Devices]]) will cite the appropriate firmware required. If you're still at a loss, a Google search may shed light on what file you need. Note, however, that not all supported devices have easily available firmware (eg. Hauppauge HVR 1100 & 1300). Firmware for such cards could be loaded via temporary installation in a Mirosoft Windows System with the manufacturer-supplied drivers.<br />
<br />
In any regard, once you find and obtain the necessary firmware for your device, copy it into the appropriate directory; the directory location depends upon that used by your distro, but typically it is: <br />
*/lib/firmware<br />
Consult resources for your distro if its preferred location is somewhere otherwise.<br />
<br />
==Some Further Documentation==<br />
* See [[Testing your DVB device]] for instructions on testing your newly installed DVB device<br />
<br />
<br />
[[Category:Software]]<br />
[[Category:Drivers]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=DVB-T_USB_Devices&diff=31169DVB-T USB Devices2012-08-20T06:03:58Z<p>Js: Reverted edits by Llnbig (talk) to last revision by Devin.heitmueller</p>
<hr />
<div>On this page you will find information regarding [[DVB-T]] [[USB]] devices. <br />
<br />
{{non-exhaustive list}}<br />
<br><br />
__TOC__<br />
<br><br />
<br />
==Firmwares==<br />
Many of the devices on this page need a firmware. If I'm not mistaken, I've collected all of them (july 2009) in this file: 7-zip file: [http://rapidshare.com/files/250533445/linux_dvb_firmware_v2.7z 728KiB download].<br />
<br />
==DVB-T USB Devices==<br />
The following tables list the known DVB-T USB devices and provides a brief summary of their features and components. (or at least it should)<br />
<br />
If you need more technical information on a device, have a look at its device specific wiki article if there is one.<br />
<br />
The device specific article is linked via the device's name but not all are linked yet. <br />
If you find an article (e.g. via the search feature on the left) then please edit the device entry here add that link. <br />
Just click on the edit icon in the last column of the device's row. <br />
<br />
If you are unsure about how to do it, click on the edit icon for a device that already has a link to see how it is done.<br />
Please feel free to create a device specific page if there is enough worthwhile information that doesn't fit in the comments field.<br />
<br />
There is also a [[DVB-T USB Devices/Full|full detail table]].<br />
<br />
If you'd like to add a new device (supported or unsupported), please go to [[Template:USB_Device_Data]] and follow the instruction there.<br />
If a device is unsupported, please add with which OS/kernel version you tested last.<br />
<br />
If you are experiencing problems with USB devices, it may not be the fault of the tuner. For example AMD 700 series chipsets (e.g. 780G) have a problem with USB ports which results in tuners working or partially working or not working at all. This can be solved by using a separate USB adapter with a reliable chipset (e.g. VIA 6212L, NEC).<br />
<br />
{{Device_List_Medium_Detail/Header<br />
| content =<br />
{{USB_Device_Data|renderwith=Device_List_Medium_Detail/Row<br />
| selatt1=hostinterface<br />
| selval1=USB<br />
| selatt2=standard<br />
| selval2=DVB-T<br />
}}<br />
}}<br />
<br />
==Supported DVB-T USB Devices (old data)==<br />
<br />
{{DvbDeviceList<br />
|content=<br />
{{DvbDeviceCommented<br />
| device=Easylite<br/>[[Easylite DVB-T stick|Easylite DVB-T Stick USB 2.0]]<br />
| type=USB2.0<br />
| comment=Supported in ?? since ??<br />
}}<br />
{{DvbDeviceCommented<br />
| vendor=ForwardVideo<br />
| device=ForwardVideo (If you own such a device please add the model. 616/618?)<br/>EzTV USB Hybrid TV Receiver<br />
| type=USB2.0<br />
| comment=Supported in ?? since ??<br />
| pic=[http://www.szforwardvideo.com/product/product_List_13.html]<br />
}}<br />
{{DvbDeviceCommented<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge]]<br/>[[Hauppauge WinTV-HVR-900]]<br />
| type=USB2.0<br />
| comment=Supported in kernel since 2.6.26 [http://www.hauppauge.com/site/support/linux.html]<br />
| supported=kernel >= 2.6.26<br />
}}<br />
{{DvbDeviceCommented<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge]]<br/>Hauppauge WinTV-HVR-930<br />
| type=USB2.0<br />
| comment=Supported in ?? since ??<br />
}}<br />
{{DvbDeviceCommented<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge]]<br/>[[Hauppauge WinTV-HVR-1900]]<br />
| type=USB2.0<br />
| comment=Supported in kernel since 2.6.26 [http://www.hauppauge.com/site/support/linux.html]<br />
| supported=kernel >= 2.6.26<br />
}}<br />
{{DvbDeviceCommented<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge]]<br/>[[Hauppauge WinTV-NOVA-T USB]]<br />
| type=USB1.1<br />
| comment=Supported in kernel since 2.6.??<br />
| supported=kernel >= ??<br />
}}<br />
{{DvbDeviceCommented<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge]]<br/>[[Hauppauge DEC2000-T USB]]<br />
| type=USB1.1<br />
| comment=Supported in kernel since 2.6.??<br />
| supported=kernel >= ??<br />
}}<br />
{{DvbDeviceCommented<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge]]<br/>[[Hauppauge DEC2540-T USB]]<br />
| type=USB1.1<br />
| comment=Supported in kernel since 2.6.??<br />
| supported=kernel >= ??<br />
}}<br />
}}<br />
<br />
<!-- ************************************************************************************ --><br />
<!-- ************* If you edit this page please help to clean it up ********************* --><br />
<!-- ************************************************************************************ --><br />
The following list of devices will have to be organized into a table. Please don't add your device here but try to add it to the table above.<br />
<br />
* [[Medion MD95700 (DVB-T)]] (''note, this thing is hybrid and offers also an FM radio tuner'')<br />
<br />
* [[TechniSat AirStar USB / Air2PC DVB USB]]<br />
<br />
<br />
<br />
Hybrid devices have a DVB-demodulator and a analogue capturing chip. Normally they share a tuner.<br />
<br />
------------<br />
<br />
<br />
{{Note|The following information is from the old deprecated DVB USB page. Eventually this page will become organized, but for now, you'll have to bear the mess....or, better yet, help with the reorganization}}<br />
[[Category:Clean_up]]<br />
<br />
<br />
<br />
=== WideView/Yakumo/Hama/Typhoon/Yuan Boxes and Pens ===<br />
<br />
All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:<br />
- dvb-usb.ko<br />
- dvb-usb-dtt200u.ko<br />
<br />
These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:<br />
- [[Zarlink MT352]]<br />
- The new units use the Zarlink ZL10353 instead of MT352<br />
- for pentype design it is unknown (but it doesn't matter at all)<br />
<br />
The programming of the MT352 is hidden behind the USB protocol defined within the firmware. These boxes can only deliver part of the [[TS|Transport Stream]] (using a hardware PID filter); it is not known how to deactivate this. (The driver was completely [[reverse-engineering|reverse-engineered]] without the help of its real vendor (assuming WideView is the manufacturer). '''UPDATE:''' the vendor was so kind to provide information about unknown commands, hence the driver is complete.<br />
<br />
There is apparently another Yakumo model not covered:<br />
<br />
<blockquote>Hi, I've purchased a "Yakumo Quickstick TV easy" and it doesn't work after compiling and installing the modules. Its vendor and product id ara 0x14aa and 0x620, and it does not appear in modules.usbmap. So I think it's not defined... ßingen.</blockquote><br />
<br />
'''Firmware:''' The firmware for the rev 3 Freecom sticks (dvb-usb-wt220u-fc03.fw) can be obtained from here [http://home.arcor.de/efocht/dvb-usb-wt220u-fc03.fw]. Rev 4 doesn't work yet, see below.<br />
<br />
'''Warning:''' When checking the table below, check the USB ID to see if you have an old or new revision of the firmware.<br />
<br />
{{DvbDeviceList<br />
| content=<br />
{{DvbDeviceCommented<br />
| device=Bestbuy Easy TV<br />
| type=USB2.0<br />
| fw=dvb-usb-wt220u-02.fw<br />
| comment=This is a WideView WT-220U PenType Receiver (Typhoon/Freecom). It works with newest linuxtv driver version.<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Club 3D ZAP-TV250mini<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-02.fw (dvb-usb-wt220u-01.fw untested)<br />
| hw=MT2060 silicon tuner<br />
| comment=USB ID (before firmware): 14aa:0220<br />
| pic=[http://www.club-3d.nl/productshow_zaptv.php?ordercode=ZAP-TV250M&show=&p=&l=en]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=dnt EuroStick USB-Stick DVB-T Receiver<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-01.fw<br />
| comment=Pen-sized.<br />
| pic=[http://www.dnt.de/index.php?dir=details&pid=20201&cat=dvbt&m_id=dvbt&h_curr=]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Freecom DVB-T USB Stick<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-01.fw<br />
| comment=Pen-sized.<br />
| pic=[http://www.freecom.com/ecProduct_detail.asp?ID=2234]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Freecom DVB-T USB Stick (25451 rev3)<br />
| type=USB2.0<br />
| fw=dvb-usb-wt220u-fc03.fw<br />
| comment=Pen-sized.<br />USB ID (before firmware): 14aa:0225<br />
| pic=[http://www.freecom.com/ecProduct_detail.asp?ID=2234]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Freecom DVB-T USB Stick. New revision of those devices with ZL0353 inside<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-zl0353-01.fw<br />
| comment=Pen-sized.<br />USB ID (before firmware): 14aa:022a.<br />
[mailto:david@myforest.com Someone] has three of these running just fine in parallel; USB IDs 14aa:0221 and 14aa:022b.<br />
| pic=[http://www.amazon.co.uk/gp/product/B000ALAWQ6/026-5347660-4657208?v=glance&n=560798]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Gainward DVB2go<br />
| type=USB2.0<br />
| fw=dvb-usb-wt220u-01.fw or dvb-usb-wt220u-02.fw<br />
| comment=Clone of YUAN PD300.<br />
}}<br />
{{DvbDevice<br />
| device=Hama DVB-T Box<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-02.fw<br />
| pic=[http://www.hama.de/portal/articleId*114663/action*2563]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Miglia TVMini Express<br />
| type=USB2.0<br />
| fw=dvb-usb-wt220u-02.fw<br />
| comment=Pen-sized. Sold as Mac exclusive, but exterior seems to be the same as dnt EuroStick.<br />
| pic=[http://www.miglia.com/tvminiexpress/]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Redbell DVB-T USB Stick (TDT-2GO)<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-01.fw or dvb-usb-wt220u-fc03.fw or dvb-usb-wt220u-zl0353-01.fw<br />
| comment=Pen-sized. Valid for PCMCIA version.<br />
| pic=[http://www.redbell.es/products/show_item/RB-TDTUSB2] [http://www.redbell.es/products/show_item/RB-TDTCBUS] [http://www.umdonline.com/guest/showitem?no_=RB-TDTUSB2]<br />
}}<br />
{{DvbDevice<br />
| device=Typhoon USB2.0 DVB-T Box<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-dtt200u-01.fw<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Typhoon DVB-T USB Drive<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-01.fw<br />
| comment=Pen-sized.<br />
| pic=[http://www.typhoon.de/de/art.php?p=826&c=]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=V-Gear PocketDTV USB2.0 DVB-T TVBox<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-dtt200u-01.fw<br />
| comment=Small container.<br />
| pic=[http://www.vgear.com/products/list1.asp?ProdID=AMVG1-016-001&SUB_NUM=1998/]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=V-Gear MobiDTV<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-01.fw or dvb-usb-wt220u-02.fw<br />
| comment=Pen-sized.<br />
| pic=[http://www.vgear.com/products/list.asp?ProdID=AMVG1-016-002]<br />
}}<br />
{{DvbDevice<br />
| device=WideView USB2.0 DVB-T Receiver<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-dtt200u-01.fw<br />
| pic=[http://www.wv.com.tw/]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=WideView Pentype DVB-T-Receiver (WT-220U)<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-01.fw<br />
| comment=Pen-sized.<br />
| pic=[http://www.wv.com.tw/]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Yakumo DVB-T mobile USB<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-dtt200u-01.fw<br />
| comment=A.K.A DTT200U<br />
| pic=[http://www.yakumo.de/produkte/index.php?pid=1&ag=DVB-T]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Yakumo QuickStick DVB-T USB<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-01.fw<br />
| comment=Pen-sized<br />
| pic=[http://www.yakumo.de/produkte/index.php?pid=1&ag=DVB-T]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Yakumo QuickStick Basic DVB-T USB<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-zl0353-01.fw<br />
| comment=Pen-sized<br />
| pic=[http://www.yakumo.de/produkte/index.php?pid=1&ag=DVB-T]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Yakumo QuickStick Basic DVB-T USB<br />
| type=USB2.0<br />
| fw=dvb-usb-wt220u-fc03.fw<br />
| comment=Pen-sized.<br />USB ID 14aa:0225 (cold state, before firmware).<br />USB ID 14aa:0226 (warm state, after firmware).<br />
| pic=[http://www.yakumo.de/produkte/index.php?pid=1&ag=DVB-T]<br />
}}<br />
{{DvbDevice<br />
| device=Yuan DVB2GO UB300<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-dtt200u-01.fw<br />
| pic=[http://www.yuan.com.tw/en/products/vdo_ub300.html]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=ELTA 8652 DVB-T<br />
| type=USB2.0<br />
| fw=dvb-usb-dtt200u-01.fw<br />
| comment=External box.<br />USB ID 14aa:0201 (cold, before firmware).<br />USB ID 14aa:0301 (warm, firmware installed).<br />
}}<br />
{{DvbDevice<br />
| device=Yuan PD300 DVB-T mini<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-01.fw<br />
| hw=MT2060 silicon tuner?<br />
| pic=[http://www.yuan.com.tw/en/products/vdo_pd300.html]<br />
}}<br />
}}<br />
<br />
=== Supported Em2880/Em2870 Based USB DVB-T devices ===<br />
<br />
Official project site: [http://www.mcentral.de/wiki/index.php5/Em2880 Em2880]<br />
<br />
{{DvbDeviceList<br />
| content=<br />
{{DvbDeviceCommented<br />
| device=BestBuy Easy TV USB hybrid<br />
| type=USB<br />
| comment=USB ID EB1A:2881<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Dazzle TV Hybrid Stick<br />
| type=USB<br />
| comment=USB ID EB1A:2881<br />
| pic=[http://doc.ubuntu-fr.org/pctv_hybrid_pro_stick?s=tnt]<br />
}}<br />
{{DvbDevice<br />
| device=DNT DA2 Hybrid<br />
| type=USB<br />
| pic=[http://www.dnt.de/index.php?dir=produkte/detail&id=20205]<br />
}}<br />
{{DvbDevice<br />
| device=Empire USB 2.0 Pen Dual TV<br />
| type=USB<br />
| pic=[http://www.empiremedia.it/site/prodotto.asp?idprodotto=231]<br />
}}<br />
{{DvbDevice<br />
| device=Hauppauge WinTV HVR 900 (rev. 1.0)<br />
| type=USB<br />
| pic=[http://www.hauppauge.co.uk/pages/products/data_hvr900.html]<br />
}}<br />
{{DvbDevice<br />
| device=Kworld 350 U DVB-T<br />
| type=USB<br />
}}<br />
{{DvbDevice<br />
| device=MSI DigiVox A/D<br />
| type=USB2.0<br />
| pic=[http://www.msi.com.tw/program/products/multimedia/mut/pro_mut_detail.php?UID=612]<br />
}}<br />
{{DvbDevice<br />
| device=[[MSI DigiVox A/D II]]<br />
| type=USB2.0<br />
| pic=<br />
}}<br />
{{DvbDevice<br />
| device=Pinnacle PCTV USB Stick<br />
| type=USB<br />
| pic=[http://linuxtv.org/v4lwiki/index.php/Em2880/PinnaclePCTV Device notes] [http://www.pinnaclesys.com/PublicSite/uk/Products/Consumer+Products/PCTV+Tuners/PCTV+Digital+PVR+(DVB-S_DVB-T)/PCTV+USB+Stick.htm]<br />
}}<br />
{{DvbDevice<br />
| device=Pinnacle PCTV Hybrid Pro Stick 330e<br />
| type=USB<br />
}}<br />
{{DvbDevice<br />
| device=Pinnacle PCTV Hybrid Pro Stick<br />
| type=USB<br />
| pic=[http://www.pinnaclesys.com/PublicSite/de/Products/Consumer+Products/PCTV+Tuners/PCTV+Analog_Digital+PVR/PCTV+Hybrid+Pro+Stick+(320e)]<br />
}}<br />
{{DvbDevice<br />
| device=[[TerraTec Cinergy Hybrid T USB XS]]<br />
| type=USB<br />
| hw=ZL10353<br />
| pic=[http://tvde.terratec.net/modules.php?op=modload&name=News&file=article&sid=249]<br />
}}<br />
{{DvbDevice<br />
| device=[[TerraTec Cinergy Hybrid T USB XS]]<br />
| type=USB<br />
| hw=MT352<br />
| pic=[http://tvde.terratec.net/modules.php?op=modload&name=News&file=article&sid=249]<br />
}}<br />
{{DvbDevice<br />
| device=[[TerraTec Cinergy T USB XS|TerraTec Cinergy T XS]]<br />
| type=USB<br />
| hw=XC3028<br />
| pic=[http://tvde.terratec.net/modules.php?op=modload&name=News&file=article&sid=253]<br />
}}<br />
{{DvbDevice<br />
| device=[[TerraTec Cinergy T USB XS|TerraTec Cinergy T XS]]<br />
| type=USB<br />
| hw=MT2060<br />
}}<br />
{{DvbDevice<br />
| device=[[TerraTec Prodigy Hybrid T XS]]<br />
| type=USB<br />
| hw=usbbridge:em2880 tuner:xc3028<br />
}}<br />
}}<br />
<br />
<br />
{{DvbDeviceList<br />
| content=<br />
{{DvbDeviceCommented<br />
| device=Sundtek MediaTV Pro<br />
| type=USB<br />
| comment=DVB-C, DVB-T, AnalogTV, Composite, S-Video, FM-Radio. Features fully supported by manufacturer's closed source driver but no open source driver available.<br />
| pic=[http://sundtek.de/shop/Digital-TV-Sticks/Sundtek-MediaTV-Pro.html]<br />
}}<br />
}}<br />
<br />
=== Supported TM5600/6000/6010 Based USB DVB-T devices ===<br />
<br />
Official project site: [[Trident_TM6000|TM6000]]<br />
<br />
{{DvbDeviceList<br />
| content=<br />
{{DvbDeviceCommented<br />
| device=TerraTec Cinergy Hybrid XE<br />
| type=USB2.0<br />
| hw=xc3028L, zl10353, IR<br />
| comment=USB ID 0CCD:0086<br />
| fw=xc3028L-v36.fw<br />
}}<br />
{{DvbDeviceCommented<br />
| device=TerraTec Cinergy Hybrid-Stick<br />
| type=USB2.0<br />
| hw=xc3028L, zl10353, IR<br />
| comment=USB ID 0CCD:00a5<br />
| fw=xc3028L-v36.fw<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Hauppauge WinTV HVR-900H<br />
| type=USB2.0<br />
| hw=xc3028L, zl10353, IR<br />
| comment=USB ID 2040:6600<br />
| fw=xc3028L-v36.fw<br />
}}<br />
}}<br />
<br />
==Currently Unsupported DVB-T USB Devices==<br />
{{help to support}}<br />
* [[ASUS My Cinema-U3000]]<br />
* [[DViCO FusionHDTV DVB-T NANO+]] usb id : 0fe9:db74<br />
* [[Emtec]] [[Emtec S830|S830]]<br />
* [[Lumanate Wave PAL SECAM DVBT Device]] [http://www.lumanate.com/aspx/sptwavedvbt.aspx] usb id : 1009:0015 (Emuzed, In).<br />
* [[Pinnacle PCTV 200e]]<br />
* Sweex MM002V<br />
* [[TerraTec Cinergy Piranha]]: work-in-progress, see [http://www.linuxtv.org/pipermail/linux-dvb/2008-June/026384.html mailing list] (June 2008)<br />
* [[Tongshi DVB-T USB]] [http://www.tongshi.com/cp_dvb_e.htm] ... Is this just a reference design? <br />
* [[WideView DVB-T/CATV USB2.0 Hybrid]] [http://www.wv.com.tw/]<br />
* [[WithView DMB Receiver]] [http://www.withview.co.kr]<br />
=== ASUS My Cinema-U3000 ===<br />
<br />
The U3000 (!= U3000 Mini) device is currently unrecognized by the Linux kernel. It is supposedly based on the dib3000p chipset. Picture and USB-info can be found [http://www.bttv-gallery.de/ here]<br />
<br />
=== DViCO FusionHDTV DVB-T NANO+ ===<br />
Not to be confused with the DViCO FusionHDTV DVB-T NANO which is supported. The Nano+ does not appear to have any drivers available for Linux.<br />
<br />
=== Freecom rev 4 DVB-T USB 2.0 tuner ===<br />
The latest Freecom/Yacumo usb stick has a Realtek 2831U chipset and any of the following usb id's: 14aa:0160, 0bda:2831, 2304:022b, 185b:0100, 13d3:3216, 13d3:3220, 13d3:3236, 13d3:3244, 08dd:2103. Latest Windows drivers dates january 2007 and can be downloaded at freecom.com<br />
<br />
More info is in the wiki's [[Realtek RTL2831U]] article.<br />
<br />
Chipset info at http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=35&Level=4&Conn=3&ProdID=147<br />
<br />
UPDATE: Realtek submitted a v0.0.2 of their driver feb 20th 2008. This has been confirmed to function for this Freecom (or Conceptronic) stick with usb id: 14aa:0160 on a 2.6.22.17 kernel. This stick has a MT2061F tuner chip, but this driver also supports the MLX5005 tuner chip. No additional firmware file is needed.<br />
<br />
The driver source can be downloaded from [http://www.megaupload.com/?d=DPE2C8I5], but be aware it has only be confirmed to work on devices with usb id 14aa:0160, and is not compatible with the current code base.<br />
<br />
===Geniatech T328 DVB-T ===<br />
[http://www.geniatech.com/pa/t682.htm]<br />
*chip: MT2060F, CY7C68013A and ZL10353. usb id: 04b4:8613. <br />
* It seems that this usb stick uses the same chips as FREEcom DVB-T usb stick and Yakumo Quickstick basic, but they have different usb id.<br />
<br />
=== LifeView TV Walker DVB-T (P/Q/Hybrid) ===<br />
<br />
P Stick<br />
<br />
* Now it doesn't exist in the Lifeview's page, not in discontinued products and not in External TV solutions, only a P Plus but I suppose that is different like the Q (now unsupported) and the Q PLus in External TV solutions. ¿Somebody can confirm this and also put info about the new product of lifeview if they're different?<br />
<br />
Q Stick [http://www.lifeview.com.tw/html/products/discontinued_products/q_dvbt.htm]<br />
<br />
* USB 2.0 stick. idProduct: 1506 ID: idVendor 0x10fd Anubis Electronics, Ltd<br />
<br />
* Chips visible on card:<br />
** Frontend: TDA10046A OFDM channel demodulator<br />
** Tuner: [http://www.semiconductors.philips.com/acrobat_download/literature/9397/75014128.pdf TDA8275A]Silicon Tuner<br />
<br />
There is a DVB-T-only box: [http://www.lifeview.com.tw/html/products/external_tv/tv_walker_dvbt.htm] I'm not able to find it in the discontinued products and correct the url to a new working one.<br />
<br />
There is a DVB-T/Analogue box (with external power): [http://www.lifeview.com.tw/html/products/discontinued_products/tv_walker_studio_hybrid.htm]<br />
<br />
=== Sweex MM002V2 === <br />
[http://www.sweex.com/producten.php?sectie=2&subsectie=2&item=127&artikel=879]<br />
* Just bought this to find out it doesn't work. Unfortunately I have no experience creating drivers :-(<br />
<br />
This is as much as I know, according to their site ...<br />
<br />
Specification<br />
# Interface: USB 2.0<br />
# [[Microtune MT2060]] silicon tuner<br />
# Chipsets: [[E3C_EC168|E3C, EC168]]<br />
<br />
Looking at dmesg in ubuntu 8.10 running kernel 2.6.27 I can see its being detected as a keyboard<br />
<br />
* [ 2893.200071] usb 5-5: new high speed USB device using ehci_hcd and address 6<br />
* [ 2893.342542] usb 5-5: configuration #1 chosen from 1 choice<br />
* [ 2893.344136] input: HID 18b4:1689 as /devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5:1.0/input/input10<br />
* [ 2893.387617] input,hidraw0: USB HID v1.11 Keyboard [HID 18b4:1689] on usb-0000:00:1d.7-5<br />
<br />
Hopefully someone can help with driver development.<br />
<br />
/Steve<br />
<br />
UPDATE: "Anttip" linuxtv HG [http://linuxtv.org/hg/~anttip/] repository has EC168 development drivers (not yet part of 2.6.31.1 Kernel v4l drivers), which work with EC168 based dvb-t sticks (18b4:1689 device id). Numerous other re-branded sticks use the same chipset.<br />
<br />
=== TVISTO DVB-T USB === <br />
There are different TVISTO usb dongles and some are supported, see [[TVISTO DVB-T USB]] for more information.<br />
<br />
=== [http://www.twinhan.com/product_AD-TU200.asp TwinHan/AzureWave AD-TU200 (7047) DVB-T] ===<br />
Uses a [[Realtek RTL2831U]] decoder chip and [[Maxlinear]] [[MXL5003S]] tuner. USB ID is 13d3:3216. It seems to work with the realtek experimental driver (see freecom v4 above):<br />
<br />
[ 3841.997121] DVB: registering new adapter (DTV-DVB UDTT 7047-USB 2.0 DVB-T Driver)<br />
[ 3841.998753] DVB: registering frontend 0 (Realtek RTL2831 DVB-T)...<br />
<br />
=== [http://www.twinhan.com/product_terrestrial_7049.asp TwinhanDTV Twister (7049) DVB-T] ===<br />
In germany a similar device seems to be sold as dnt EuroMini200 [http://www.dnt.de/index.php?dir=produkte/detail&id=20206].<br />
<br />
We tried to get information about the usb interface at Twinhan, but there was none avaiable. The chip vendor Uli [http://www.uli.com.tw/] refuses to open all relevant information.<br />
<br />
Maybe the same applies for the TwinhanDTV Hurricne (704D) [http://www.twinhan.com/product_704D.asp].<br />
<br />
=== [http://www.twinhan.com/product_D%2BA_3.asp TwinhanDTV MagicBox Pro (DVB-T/Analogue)] ===<br />
A [[hybrid]] USB2.0 box based on the [http://www.uli.com.tw/product_dm/m9207dm_web.pdf ULI M9207] chipset. Also based on this chipset is the Pinnacle [http://www.pinnaclesys.com/PublicSite/uk/Products/Consumer+Products/PCTV+Tuners/PCTV+Analog_Digital+PVR/PCTV+310e PCTV 310e], [http://www.lifeview.com/usa/html/products/multimedia/tvwalker_hybrid.htm LifeView TV Walker Hybrid] and [http://www.nurido.at/news/computer/testgericomtvtunerusb20beihofer.html Gericom USB 2.0 Hybrid Box] sold by Aldi (Germany) and Hofer (Austria).<br />
<br />
<br />
=== YUAN UB701 (DVB-T/Analogue) ===<br />
A [[hybrid]] USB2.0-only box. Maybe it is a clone of the Conexant Hybrid Reference design?<br />
It has an em2880 and a xc3028 tuner. USB id eb1a:2881<br />
[http://www.yuan.com.tw/en/products/vdo_ub701.html]<br />
<br />
<br />
=== WithView DMB Receiver ===<br />
* Model No : HDMB-T100A<br />
* lsusb : ID 10c4:0010 Cygnal Integrated Products, Inc.<br />
[http://www.withview.co.kr/eshop/contents.html?layout=t100a]<br />
<br />
<br />
=== WandTV ===<br />
AF9035 based. Check out the [[Afatech AF9035]] page for information on support. And please add details so that the device can be added to the big table above.<br />
<br />
There is also IT9135 based WandTV, id is: 048d:9006. You can try the way described for Kworld_UB499-2T. It "kind of works" for me with the older driver http://wasietsmet.nl/wp-content/uploads/2010/07/IT9135_SRC_i686_patch.tar.gz (scans the channels). The newer driver http://wasietsmet.nl/wp-content/uploads/2010/07/V10.12.30.1.zip compiles with unknown symbol errors: “__stack_chk_fail” and “mcount”.<br />
<br />
==Also See==<br />
* [[DVB via USB|General Information Regarding DVB via USB]]<br />
<br />
[[Category:DVB-T| ]]<br />
[[Category:Hardware| ]]<br />
[[Category:DVB-T USB Devices| ]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers&diff=30641How to Obtain, Build and Install V4L-DVB Device Drivers2012-04-04T14:38:17Z<p>Js: Reverted edits by Promenado645 (talk) to last revision by Bobatlcpmbdx</p>
<hr />
<div>The LinuxTV project hosts the latest set of Linux kernel driver modules for [[What is V4L or DVB?|V4L-DVB devices]]. This page contains information to help an "end user" install these device drivers in a GNU/Linux system. <br />
<br />
{{Note|This article assumes that:<br />
* your device is actually supported by the drivers -- Just because your board happens to have a chip on it that corresponds to some existing driver does NOT mean your product is supported. The driver has to be aware that it's related to some hardware (typically through the [[Supported_Hardware#Determining_the_Device's_Identity|subsystem ID from the USB ID or PCI ID]]). If the driver doesn't recognize/bind to your particular hardware, then the module will probably load but then proceed to not do anything. In other words, support for your device would have to be added to the driver.<br />
* you have already physically installed the hardware device into, or connected it to, your system. (Refer to the manufacturer's instructions for such details)}}.<br />
<br />
== Software Requirements ==<br />
===Kernel Support===<br />
The LinuxTV V4L-DVB drivers will work only in conjunction with relatively modern 2.6 kernels; specifically, <br />
<br />
{{Note|CityK here: I have no clue as to where the current backwards compatibility status stands. Suffice to say, more modern kernels (which I'd define as ~2.6.32 and newer) are much more likely to work with the new media_build snapshots of the git tree. When the situation is more clear, please update this section accordingly.}}<br />
<br />
===Additional Software Requrirements===<br />
In order to be able to build the V4L-DVB kernel driver modules, you will need: <br />
* kernel-source or kernel-headers<br />
* (OpenSuSE and fedora only) kernel-devel<br />
* (Debian) libdigest-sha1-perl<br />
* make <br />
* gcc<br />
* git<br />
* patch<br />
* patchutils<br />
* libproc-processtable-perl ("perl-Proc-ProcessTable")<br />
If these packages are not currently installed on your system, you should do so now.<br />
<br />
==Retrieving and Building/Compiling the Latest V4L-DVB Source Code==<br />
There are a couple of different methods by which you can obtain and build the latest source code. Regardless of which route you take, all are performed from the command line within a console. The "basic" method is likely appropriate for most end users, though, in some cases, some users will have to use the slightly more "manually intensive" approach. This second approach is effectively, for all intents and purposes, really just the same as the "basic" method, but performing the steps in a piecemeal fashion affords you the opportunity to tailor the source code or the "make"/build process as might be required in your particular situation. Again, before proceeding with either approach, make sure you have installed all the prerequisite software listed above.<br />
<br />
{{Note|If you are using Ubuntu, you were previously very likely to run into a fatal compilation error within the v4l-dvb build process when it reaches the firedtv module. The reason for this is because Ubuntu had a bug in their packaging of the kernel headers. <b>This seems to be fixed</b> on a fully updated systtem (5 July 2011) This was a long standing issue, and one of the most frequently reported on the mailing list. <br><br />
If you still have the problem, you should be able to correct this compilation problem by following the more manual procedure listed below. In particular, before proceeding to build the modules, you will have to edit the file ''v4l/.config'' and change the line for the firedtv driver from <nowiki>"firedtv=m" to "firedtv=n"</nowiki>.}}<br />
<br />
{{Note|If you are having build failures like "implicit declaration of function 'mfd_get_data'" try editing v4l/Makefile.media, and just comment out anything related to CONFIG_*_TIMBERALE. [[http://sourceforge.net/mailarchive/message.php?msg_id=27353778 Source]] }}<br />
<br />
<br />
<br />
{| class="wikitable" <br />
|+'''Retreiving the Source Code & Building/Compiling the Modules'''<br />
|-<br />
! "Basic" Approach !! More "Manually Intensive" Approach<br />
<br />
|-<br />
| valign=top |<br />
git clone git://linuxtv.org/media_build.git<br />
cd media_build <br />
./build<br />
<br />
These commands will download the newest tarball of the source code from linuxtv.org, apply the backport patches to it and then build/compile the source via the included script build.sh. <br />
<br />
NB: to add a patch copy the .patch file to the backports directory, and add the patch file as a line to the {kernel-version}_series file in the packports dir.<br />
|<br />
git clone git://linuxtv.org/media_build.git<br />
cd media_build/linux<br />
make tar DIR=<some dir with media -git tree><br />
make untar<br />
cd ..<br />
<br />
If you need to make any sort of change or modification to the source code, now is the time. <br />
<br />
<div style="border: solid 1px; border-color: blue; margin: 1em; padding: 1em; background-color: Lavender;"><br />
'''Optional Pre-Compilation Steps'''<br><br />
These optional command steps are applicable only in certain situations approaching a new build of the driver set, or for experienced users wishing to streamline the build process to consist of only those components they want to install.<br />
* <code>make rminstall</code> ... you would use this to remove the currently installed driver set (located within the relevant ''/lib/modules/["kernel version"]/kernel/drivers/media'' directory to which they were installed)<br />
* <code>make distclean</code> ... cleans up the build configuration environment ... noteworthy is that it will set things up such that a following "make" build process will be against "''/usr/src/[uname -r]''” kernel source<br />
* <code>make menuconfig</code> ... this will open up the ncurses based menu that allows you to select only those components you wish to build and install<br />
<br />
The building system offers some other make targets that may be useful for advanced users or developers. For listing the supported targets, please use <code>make help</code>.</div><br />
<br />
Next, build/compile the modules from the source code with the command:<br />
make<br />
{{Note|For multi-core processor systems, the ''make'' command has available options that can be beneficial in terms of the reducing the amount of time required for the process' completion. Specifically, you can run "''make -jN''" (where "''N''" <nowiki>=</nowiki> 1 + the number of cores your cpu has ... i.e. if you have a dual core cpu use: ''make -j3'' )}}<br />
<br />
|}<br />
===Information Regarding the Build Process===<br />
Generally, this step will tend to take a while to complete; being dependent upon both the number of modules being built and your system's processing power.<br />
<br />
You can monitor the build progress via the console output. You will notice that a ''/v4l'' directory will have been created and within which the completed *.ko module files are written. Some drivers included within the snapshot may have their own requirements in regards to the kernel that you must be running in order for the module to be built; such cases can be found listed at the beginning of the build process' console output.<br />
<br />
The entire build process should complete without error. If any errors are encountered, the compilation will be halted and, at this point, you should not attempt to proceed any further (unless you really, really enjoy experiencing the outcome of a preordained failure). Errors that prevent building a particular V4L-DVB snapshot do indeed surface from time to time, but these are usually corrected quickly upon notification from an end user submitted [[Bug Report|bug report]], or upon detection from the daily automated build tests (see note below). If you have run into a build error via the "basic" approach outlined above, you may wish to see if you can remedy the error and attempt a module build via the more "manually intensive" approach also outlined above.<br />
<br />
{{Note|'''The Daily Automated Build Tests'''<br><br />
Hans Verkuil has set up an automated daily build of the V4L-DVB source code upon all supported kernels, as well as testing that very same upon several CPU architectures. A brief synopsis of the results from those tests is published each day on the Linux-Media Mailing List (LMML) under a message subject heading prefix of "''[cron job] v4l-dvb daily build ...''". A link to more detailed results of these tests is also provided within that message or can be found directly from [http://www.xs4all.nl/~hverkuil/logs/ here].}} <br />
<br />
If you do run into any problems during the build step, you should:<br />
* first, see whether the issue is already known or not -- consult the results of the daily automated build tests (see note above)<br />
* if it appears that this is a new issue, please [[Bug Report|inform the developers of the bug via the LMML]] (preferred) or thorough one of the irc.freenode.net irc channels (#v4l or #linuxtv or #dvb).<br />
* you may also wish to consult any errata that might be found on this article's talk page<br />
<br />
In general, if the source builds correctly, it is likely that the drivers will work, though this is not a guarantee.<br />
<br />
== Installing the Compiled Driver Modules ==<br />
The next step is to install the kernel driver modules by executing:<br />
sudo make install<br />
The command above will prompt you for your root password, and will then copy the *.ko module files you built in the above step into the ''/lib/modules/[kernel version]/kernel/drivers/media'' directories. <br />
<br />
{{Note|If your distribution doesn't support the sudo command (i.e the command line returns ''"bash: sudo: command not found"''), use the "su" command instead. "su" will prompt you for the root password, and after which entering, you can then proceed with the command. Ex.:<br />
su<br />
make install<br />
}}<br />
<br><br />
{{Note|In the case where you have more then one kernel installed but have used the pre-compilation option of "make distclean", the new modules will be installed only into the ''/lib/modules/[uname -r]/kernel/drivers/media'' directory}} <br><br />
<br />
== First Use: Out with the Old, In with the New==<br />
{| <br />
| valign=top |<br />
Before trying to use the device with your newly installed driver set, you should remove from system memory any older versions of related modules that may have been loaded by the running kernel; otherwise, you will likely run into various fatal mismatch errors -- typified by an "unknown symbol" or "unknown parameter" -- as a result of your system trying to work from a mixture of old and new modules. <br />
<br />
To achieve a [[Wikipedia:Tabula rasa |clean slate]] state, you could either: <br><br />
<br />
'''1. Reboot:''' Perhaps the most straightforward thing to do at this point, particularly for Linux newbies, is to just restart your system; the reboot will, obviously, clear out the old modules loaded into memory and, as an added bonus, create a fresh running environment under which the new modules should have been automagically loaded into system memory. <br />
<br />
Or, on the other hand,<br />
<br />
'''2. Take care of business yourself:''' More experienced users might prefer to use more eloquent approaches. For example, using <br />
sudo make unload<br />
will essentially (and similar as to manually using "rmmod" commands) remove all older modules for the device that might be currently loaded in memory by the running kernel. After which, one can then load, from the newly installed device driver set, the appropriate modules for the device using relevant<br />
modprobe ''driver_name'' <br />
commands.<br />
<br />
| valign=top halign=right width=30% |<br />
<div style="border: solid 1px; border-color: blue; margin: 1em; padding: 1em; background-color: Lavender;"><br />
'''For Advanced Users'''<br><br />
The following information is likely useful only for developers. After building the modules as per usual ("make"), and without needing to install them, you can:<br />
* remove all older modules from memory at once using "make unload" and <br />
* then insert all the newly built modules into memory for the running kernel with "make load"<br />
Alternatively, to perform the previous two commands ("make unload" and "make load") in a single step, you can use "make reload"<br />
<br />
Note, however, that it is highly recommended that you avoid using either the make load or make reload options, as they will end up inserting <u>all</u> V4L-DVB device drivers into memory, and that may introduce instability, or complicate testing.<br />
</div><br />
|}<br />
Regardless of which approach you take to remove the old modules and to insert the new ones, the end result should be the same. In addition, upon future starts of your system, your device should "automagically" be detected and will have the appropriate driver modules loaded into memory. <br />
<br />
===If the Modules load correctly:===<br />
Provided that the modules were loaded correctly into system memory:<br />
<br />
'''1. They should be listed in ''/proc/modules''''': you can use either <code>cat /proc/modules</code> or, even better, <code>lsmod</code> to see this content.<br />
<br />
Which modules should you be looking for? Well, the answer to that question depends entirely upon the chipsets used by your device -- see the relevant wiki article for your device for a listing of such components and required drivers (or search the web if such information does not exist. '''Note''': Please add any information missing from the wiki!)<br />
<br />
'''2. They should provide some indication within your system log''': you can consult the output from the "<code>dmesg</code>" command or directly review your system log file (typically housed within the ''/var/log'' directory) for indication that they have been successfully loaded and that the device is now correctly configured for operation. Examples of successful module loads are provided by users under the "Sample kernel output" section in many device articles witin the wiki.<br />
<br />
'''3. The device manager [[Wikipedia:udev|udev]] will "automagically" create appropriate [[Device nodes and character devices|device nodes]] on ''/dev''''': <br><br />
'''(a) For a DVB device''', you should now have a non-empty ''/dev/dvb'' directory. You can check on whether this is true for you with the following command:<br />
: <code>ls -l /dev/dvb/</code><br />
(alternatively, you can browse your directory structure with the graphical file manager of your choice). If you have a single DVB device installed in your system, then the output of the above command should reveal that /dev/dvb/ is populated by adapter0. Digging further, <br />
: <code>ls -l /dev/dvb/adapter0 </code><br />
reveals the [[Device_nodes_and_character_devices#DVB_character_devices|character devices]] associated with adapter0 for which the drivers have control. If you have more then one DVB device, you can see the same for all with <br />
: <code>ls -l /dev/dvb/adapter* </code><br />
<br />
'''(b) For a V4L device''', you should now have a non-empty ''/dev/v4l'' directory. You can check on whether this is true for you with the following command:<br />
: <code>ls -l /dev/v4l</code><br />
Digging further, <br />
: <code>ls -l /dev/v4l/by-path </code><br />
reveals the symbolic links to the [[Device_nodes_and_character_devices#V4L_character_devices|character devices]] associated with your V4L adapter for which the drivers have control. The most typical of which is ''/dev/video0''. If you have more then one V4L device, you can see the same for all with <br />
: <code>ls -l /dev/video* </code><br />
<br />
===If the Modules did not load correctly or the device is still not configured correctly for use:===<br />
There could be several reasons why you may have encountered a module loading error or, absent such an error, why the device is still not configured correctly for use, even after having correctly followed the steps from the above procedure. If either of these cases applies, the very first thing you should do is [[Supported Hardware|check whether your device is actually supported]] by the driver (see the very first note at the top of this page). Next, provided your device is supposed to be supported, check within your system log/dmesg for any messages that may give indication as to the problem. The following points address a few common trouble spots:<br />
<br />
'''Module Load Order Can Matter'''<br />
* in cases where loading more then one module is necessary, the order in which you load the modules can matter! <br />
<br />
'''Sometimes Automagic just isn't Automagic'''<br />
* If a module was, for whatever reason, not loaded, you can try manually loading it with the appropriate ''modprobe'' command.<br />
<br />
'''Unresolved Symbols'''<br />
* if you tried the second method ("make unload" followed by an appropriate modprobe command) but encountered errors in relation to unresolved symbols, e.g. using the saa7134 module as an example:<br />
sudo modprobe saa7134<br />
FATAL: Error inserting saa7134 (/lib/modules/''[your kernel version]''/kernel/drivers/media/video/saa7134/saa7134.ko):\ <br />
Unknown symbol in module, or unknown parameter (see dmesg) <br />
please try a system reboot before filing an [[Bug Report|error report]]. Irregardless of what caused the unresolved symbols errors, usually, after performing the reboot, you will find that the install was actually successful and the drivers will work as intended.<br />
<br />
* Special case: If your system uses compressed kernel modules, after running the "make install" command of the V4L-DVB installation process, you could end up with a mixture of new modules (*.ko) and their older compressed version (*.ko.gz) installed. If the system attempts to concurrently load both sets into memory, you are bound to run into modprobe insertion errors (eg. unknown symbol or unknown parameter). All conflicting *.ko.gz files must be removed. The following command line can help you locate these conflicting files in all your installed kernels:<br />
for file in `find /lib/modules -name "*.ko"`; do if <nowiki>[[</nowiki> -e $file.gz <nowiki>]]</nowiki>; then echo "$file.gz should be removed"; fi; done<br />
Usually all conflicting module files resulting of v4l-dvb installation will be located in:<br />
/lib/modules/''[your kernel version]''/kernel/drivers/media<br />
Once the conflicting *.ko.gz have been moved elsewhere or renamed (to *.ko.gz.disabled for example), use the v4l-dvb reload command and, to be safe, also add a "depmod" step in order to rebuild modules dependencies):<br />
make reload<br />
depmod -a<br />
Your new modules should now be loaded correctly.<br />
<br />
'''A Note on Firmware'''<br />
* You have all the modules active (listed in lsmod) but device nodes are nowhere to be found: The problem may be as simple as the [[Firmware|firmware]] for the device not being loaded; some devices also require a [[Firmware|firmware]], which is uploaded from the host PC to the device, in order to operate. <br />
<br />
In some cases, when the device is correctly recognized, the associated drivers provide information as to which firmware file is required -- look in the system log output. For example, for many [[TechnoTrend]] & [[Hauppauge]] (and other similar "premium" cards), if the dvb-ttpci firmware is not available you will observe an error such as:<br />
<pre> dvb-ttpci: could not load firmware, file not found: dvb-ttpci-01.fw<br />
dvb-ttpci: usually this should be in /usr/lib/hotplug/firmware or /lib/firmware<br />
dvb-ttpci: and can be downloaded from http://www.linuxtv.org/download/dvb/firmware/</pre><br />
Resolving that missing firmware issue should then result in proper detection and configuration of your device.<br />
In other cases, obtaining the correct firmware is not so straightforward a task. The very first thing you need to know is what device you're using; see "[[Supported_Hardware#Determining_the_Device's_Identity|Determining the Device's Identity]]". Once you have established which particular device you are in possession of, you can then move on to [[Firmware#Acquiring the Firmware|obtaining the correct firmware]]. In addition, information in wiki articles (eg. such as [[DVB-T USB Devices]]) will cite the appropriate firmware required. If you're still at a loss, a Google search may shed light on what file you need. Note, however, that not all supported devices have easily available firmware (eg. Hauppauge HVR 1100 & 1300). Firmware for such cards could be loaded via temporary installation in a Mirosoft Windows System with the manufacturer-supplied drivers.<br />
<br />
In any regard, once you find and obtain the necessary firmware for your device, copy it into the appropriate directory; the directory location depends upon that used by your distro, but typically it is: <br />
*/lib/firmware<br />
Consult resources for your distro if its preferred location is somewhere otherwise.<br />
<br />
==Some Further Documentation==<br />
* See [[Testing your DVB device]] for instructions on testing your newly installed DVB device<br />
<br />
<br />
[[Category:Software]]<br />
[[Category:Drivers]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=DVB-T_USB_Devices&diff=30607DVB-T USB Devices2012-03-11T17:25:22Z<p>Js: Reverted edits by Sucipto82 (talk) to last revision by Jmiezitis</p>
<hr />
<div>On this page you will find information regarding [[DVB-T]] [[USB]] devices. <br />
<br />
{{non-exhaustive list}}<br />
<br><br />
__TOC__<br />
<br><br />
<br />
==Firmwares==<br />
Many of the devices on this page need a firmware. If I'm not mistaken, I've collected all of them (july 2009) in this file: 7-zip file: [http://rapidshare.com/files/250533445/linux_dvb_firmware_v2.7z 728KiB download].<br />
<br />
==DVB-T USB Devices==<br />
The following tables list the known DVB-T USB devices and provides a brief summary of their features and components. (or at least it should)<br />
<br />
If you need more technical information on a device, have a look at its device specific wiki article if there is one.<br />
<br />
The device specific article is linked via the device's name but not all are linked yet. <br />
If you find an article (e.g. via the search feature on the left) then please edit the device entry here add that link. <br />
Just click on the edit icon in the last column of the device's row. <br />
<br />
If you are unsure about how to do it, click on the edit icon for a device that already has a link to see how it is done.<br />
Please feel free to create a device specific page if there is enough worthwhile information that doesn't fit in the comments field.<br />
<br />
There is also a [[DVB-T USB Devices/Full|full detail table]].<br />
<br />
If you'd like to add a new device (supported or unsupported), please go to [[Template:USB_Device_Data]] and follow the instruction there.<br />
If a device is unsupported, please add with which OS/kernel version you tested last.<br />
<br />
If you are experiencing problems with USB devices, it may not be the fault of the tuner. For example AMD 700 series chipsets (e.g. 780G) have a problem with USB ports which results in tuners working or partially working or not working at all. This can be solved by using a separate USB adapter with a reliable chipset (e.g. VIA 6212L, NEC).<br />
<br />
{{Device_List_Medium_Detail/Header<br />
| content =<br />
{{USB_Device_Data|renderwith=Device_List_Medium_Detail/Row<br />
| selatt1=hostinterface<br />
| selval1=USB<br />
| selatt2=standard<br />
| selval2=DVB-T<br />
}}<br />
}}<br />
<br />
==Supported DVB-T USB Devices (old data)==<br />
<br />
{{DvbDeviceList<br />
|content=<br />
{{DvbDeviceCommented<br />
| device=Easylite<br/>[[Easylite DVB-T stick|Easylite DVB-T Stick USB 2.0]]<br />
| type=USB2.0<br />
| comment=Supported in ?? since ??<br />
}}<br />
{{DvbDeviceCommented<br />
| vendor=ForwardVideo<br />
| device=ForwardVideo (If you own such a device please add the model. 616/618?)<br/>EzTV USB Hybrid TV Receiver<br />
| type=USB2.0<br />
| comment=Supported in ?? since ??<br />
| pic=[http://www.szforwardvideo.com/product/product_List_13.html]<br />
}}<br />
{{DvbDeviceCommented<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge]]<br/>[[Hauppauge WinTV-HVR-900]]<br />
| type=USB2.0<br />
| comment=Supported in kernel since 2.6.26 [http://www.hauppauge.com/site/support/linux.html]<br />
| supported=kernel >= 2.6.26<br />
}}<br />
{{DvbDeviceCommented<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge]]<br/>Hauppauge WinTV-HVR-930<br />
| type=USB2.0<br />
| comment=Supported in ?? since ??<br />
}}<br />
{{DvbDeviceCommented<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge]]<br/>[[Hauppauge WinTV-HVR-1900]]<br />
| type=USB2.0<br />
| comment=Supported in kernel since 2.6.26 [http://www.hauppauge.com/site/support/linux.html]<br />
| supported=kernel >= 2.6.26<br />
}}<br />
{{DvbDeviceCommented<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge]]<br/>[[Hauppauge WinTV-NOVA-T USB]]<br />
| type=USB1.1<br />
| comment=Supported in kernel since 2.6.??<br />
| supported=kernel >= ??<br />
}}<br />
{{DvbDeviceCommented<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge]]<br/>[[Hauppauge DEC2000-T USB]]<br />
| type=USB1.1<br />
| comment=Supported in kernel since 2.6.??<br />
| supported=kernel >= ??<br />
}}<br />
{{DvbDeviceCommented<br />
| vendor=[[Hauppauge]]<br />
| device=[[Hauppauge]]<br/>[[Hauppauge DEC2540-T USB]]<br />
| type=USB1.1<br />
| comment=Supported in kernel since 2.6.??<br />
| supported=kernel >= ??<br />
}}<br />
}}<br />
<br />
<!-- ************************************************************************************ --><br />
<!-- ************* If you edit this page please help to clean it up ********************* --><br />
<!-- ************************************************************************************ --><br />
The following list of devices will have to be organized into a table. Please don't add your device here but try to add it to the table above.<br />
<br />
* [[Medion MD95700 (DVB-T)]] (''note, this thing is hybrid and offers also an FM radio tuner'')<br />
<br />
* [[TechniSat AirStar USB / Air2PC DVB USB]]<br />
<br />
<br />
<br />
Hybrid devices have a DVB-demodulator and a analogue capturing chip. Normally they share a tuner.<br />
<br />
------------<br />
<br />
<br />
{{Note|The following information is from the old deprecated DVB USB page. Eventually this page will become organized, but for now, you'll have to bear the mess....or, better yet, help with the reorganization}}<br />
[[Category:Clean_up]]<br />
<br />
<br />
<br />
=== WideView/Yakumo/Hama/Typhoon/Yuan Boxes and Pens ===<br />
<br />
All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:<br />
- dvb-usb.ko<br />
- dvb-usb-dtt200u.ko<br />
<br />
These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:<br />
- [[Zarlink MT352]]<br />
- The new units use the Zarlink ZL10353 instead of MT352<br />
- for pentype design it is unknown (but it doesn't matter at all)<br />
<br />
The programming of the MT352 is hidden behind the USB protocol defined within the firmware. These boxes can only deliver part of the [[TS|Transport Stream]] (using a hardware PID filter); it is not known how to deactivate this. (The driver was completely [[reverse-engineering|reverse-engineered]] without the help of its real vendor (assuming WideView is the manufacturer). '''UPDATE:''' the vendor was so kind to provide information about unknown commands, hence the driver is complete.<br />
<br />
There is apparently another Yakumo model not covered:<br />
<br />
<blockquote>Hi, I've purchased a "Yakumo Quickstick TV easy" and it doesn't work after compiling and installing the modules. Its vendor and product id ara 0x14aa and 0x620, and it does not appear in modules.usbmap. So I think it's not defined... ßingen.</blockquote><br />
<br />
'''Firmware:''' The firmware for the rev 3 Freecom sticks (dvb-usb-wt220u-fc03.fw) can be obtained from here [http://home.arcor.de/efocht/dvb-usb-wt220u-fc03.fw]. Rev 4 doesn't work yet, see below.<br />
<br />
'''Warning:''' When checking the table below, check the USB ID to see if you have an old or new revision of the firmware.<br />
<br />
{{DvbDeviceList<br />
| content=<br />
{{DvbDeviceCommented<br />
| device=Bestbuy Easy TV<br />
| type=USB2.0<br />
| fw=dvb-usb-wt220u-02.fw<br />
| comment=This is a WideView WT-220U PenType Receiver (Typhoon/Freecom). It works with newest linuxtv driver version.<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Club 3D ZAP-TV250mini<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-02.fw (dvb-usb-wt220u-01.fw untested)<br />
| hw=MT2060 silicon tuner<br />
| comment=USB ID (before firmware): 14aa:0220<br />
| pic=[http://www.club-3d.nl/productshow_zaptv.php?ordercode=ZAP-TV250M&show=&p=&l=en]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=dnt EuroStick USB-Stick DVB-T Receiver<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-01.fw<br />
| comment=Pen-sized.<br />
| pic=[http://www.dnt.de/index.php?dir=details&pid=20201&cat=dvbt&m_id=dvbt&h_curr=]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Freecom DVB-T USB Stick<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-01.fw<br />
| comment=Pen-sized.<br />
| pic=[http://www.freecom.com/ecProduct_detail.asp?ID=2234]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Freecom DVB-T USB Stick (25451 rev3)<br />
| type=USB2.0<br />
| fw=dvb-usb-wt220u-fc03.fw<br />
| comment=Pen-sized.<br />USB ID (before firmware): 14aa:0225<br />
| pic=[http://www.freecom.com/ecProduct_detail.asp?ID=2234]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Freecom DVB-T USB Stick. New revision of those devices with ZL0353 inside<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-zl0353-01.fw<br />
| comment=Pen-sized.<br />USB ID (before firmware): 14aa:022a.<br />
[mailto:david@myforest.com Someone] has three of these running just fine in parallel; USB IDs 14aa:0221 and 14aa:022b.<br />
| pic=[http://www.amazon.co.uk/gp/product/B000ALAWQ6/026-5347660-4657208?v=glance&n=560798]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Gainward DVB2go<br />
| type=USB2.0<br />
| fw=dvb-usb-wt220u-01.fw or dvb-usb-wt220u-02.fw<br />
| comment=Clone of YUAN PD300.<br />
}}<br />
{{DvbDevice<br />
| device=Hama DVB-T Box<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-02.fw<br />
| pic=[http://www.hama.de/portal/articleId*114663/action*2563]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Miglia TVMini Express<br />
| type=USB2.0<br />
| fw=dvb-usb-wt220u-02.fw<br />
| comment=Pen-sized. Sold as Mac exclusive, but exterior seems to be the same as dnt EuroStick.<br />
| pic=[http://www.miglia.com/tvminiexpress/]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Redbell DVB-T USB Stick (TDT-2GO)<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-01.fw or dvb-usb-wt220u-fc03.fw or dvb-usb-wt220u-zl0353-01.fw<br />
| comment=Pen-sized. Valid for PCMCIA version.<br />
| pic=[http://www.redbell.es/products/show_item/RB-TDTUSB2] [http://www.redbell.es/products/show_item/RB-TDTCBUS] [http://www.umdonline.com/guest/showitem?no_=RB-TDTUSB2]<br />
}}<br />
{{DvbDevice<br />
| device=Typhoon USB2.0 DVB-T Box<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-dtt200u-01.fw<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Typhoon DVB-T USB Drive<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-01.fw<br />
| comment=Pen-sized.<br />
| pic=[http://www.typhoon.de/de/art.php?p=826&c=]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=V-Gear PocketDTV USB2.0 DVB-T TVBox<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-dtt200u-01.fw<br />
| comment=Small container.<br />
| pic=[http://www.vgear.com/products/list1.asp?ProdID=AMVG1-016-001&SUB_NUM=1998/]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=V-Gear MobiDTV<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-01.fw or dvb-usb-wt220u-02.fw<br />
| comment=Pen-sized.<br />
| pic=[http://www.vgear.com/products/list.asp?ProdID=AMVG1-016-002]<br />
}}<br />
{{DvbDevice<br />
| device=WideView USB2.0 DVB-T Receiver<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-dtt200u-01.fw<br />
| pic=[http://www.wv.com.tw/]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=WideView Pentype DVB-T-Receiver (WT-220U)<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-01.fw<br />
| comment=Pen-sized.<br />
| pic=[http://www.wv.com.tw/]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Yakumo DVB-T mobile USB<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-dtt200u-01.fw<br />
| comment=A.K.A DTT200U<br />
| pic=[http://www.yakumo.de/produkte/index.php?pid=1&ag=DVB-T]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Yakumo QuickStick DVB-T USB<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-01.fw<br />
| comment=Pen-sized<br />
| pic=[http://www.yakumo.de/produkte/index.php?pid=1&ag=DVB-T]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Yakumo QuickStick Basic DVB-T USB<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-zl0353-01.fw<br />
| comment=Pen-sized<br />
| pic=[http://www.yakumo.de/produkte/index.php?pid=1&ag=DVB-T]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Yakumo QuickStick Basic DVB-T USB<br />
| type=USB2.0<br />
| fw=dvb-usb-wt220u-fc03.fw<br />
| comment=Pen-sized.<br />USB ID 14aa:0225 (cold state, before firmware).<br />USB ID 14aa:0226 (warm state, after firmware).<br />
| pic=[http://www.yakumo.de/produkte/index.php?pid=1&ag=DVB-T]<br />
}}<br />
{{DvbDevice<br />
| device=Yuan DVB2GO UB300<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-dtt200u-01.fw<br />
| pic=[http://www.yuan.com.tw/en/products/vdo_ub300.html]<br />
}}<br />
{{DvbDeviceCommented<br />
| device=ELTA 8652 DVB-T<br />
| type=USB2.0<br />
| fw=dvb-usb-dtt200u-01.fw<br />
| comment=External box.<br />USB ID 14aa:0201 (cold, before firmware).<br />USB ID 14aa:0301 (warm, firmware installed).<br />
}}<br />
{{DvbDevice<br />
| device=Yuan PD300 DVB-T mini<br />
| type=USB2.0, USB1.1<br />
| fw=dvb-usb-wt220u-01.fw<br />
| hw=MT2060 silicon tuner?<br />
| pic=[http://www.yuan.com.tw/en/products/vdo_pd300.html]<br />
}}<br />
}}<br />
<br />
=== Supported Em2880/Em2870 Based USB DVB-T devices ===<br />
<br />
Official project site: [http://www.mcentral.de/wiki/index.php5/Em2880 Em2880]<br />
<br />
{{DvbDeviceList<br />
| content=<br />
{{DvbDeviceCommented<br />
| device=BestBuy Easy TV USB hybrid<br />
| type=USB<br />
| comment=USB ID EB1A:2881<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Dazzle TV Hybrid Stick<br />
| type=USB<br />
| comment=USB ID EB1A:2881<br />
| pic=[http://doc.ubuntu-fr.org/pctv_hybrid_pro_stick?s=tnt]<br />
}}<br />
{{DvbDevice<br />
| device=DNT DA2 Hybrid<br />
| type=USB<br />
| pic=[http://www.dnt.de/index.php?dir=produkte/detail&id=20205]<br />
}}<br />
{{DvbDevice<br />
| device=Empire USB 2.0 Pen Dual TV<br />
| type=USB<br />
| pic=[http://www.empiremedia.it/site/prodotto.asp?idprodotto=231]<br />
}}<br />
{{DvbDevice<br />
| device=Hauppauge WinTV HVR 900 (rev. 1.0)<br />
| type=USB<br />
| pic=[http://www.hauppauge.co.uk/pages/products/data_hvr900.html]<br />
}}<br />
{{DvbDevice<br />
| device=Kworld 350 U DVB-T<br />
| type=USB<br />
}}<br />
{{DvbDevice<br />
| device=MSI DigiVox A/D<br />
| type=USB2.0<br />
| pic=[http://www.msi.com.tw/program/products/multimedia/mut/pro_mut_detail.php?UID=612]<br />
}}<br />
{{DvbDevice<br />
| device=[[MSI DigiVox A/D II]]<br />
| type=USB2.0<br />
| pic=<br />
}}<br />
{{DvbDevice<br />
| device=Pinnacle PCTV USB Stick<br />
| type=USB<br />
| pic=[http://linuxtv.org/v4lwiki/index.php/Em2880/PinnaclePCTV Device notes] [http://www.pinnaclesys.com/PublicSite/uk/Products/Consumer+Products/PCTV+Tuners/PCTV+Digital+PVR+(DVB-S_DVB-T)/PCTV+USB+Stick.htm]<br />
}}<br />
{{DvbDevice<br />
| device=Pinnacle PCTV Hybrid Pro Stick 330e<br />
| type=USB<br />
}}<br />
{{DvbDevice<br />
| device=Pinnacle PCTV Hybrid Pro Stick<br />
| type=USB<br />
| pic=[http://www.pinnaclesys.com/PublicSite/de/Products/Consumer+Products/PCTV+Tuners/PCTV+Analog_Digital+PVR/PCTV+Hybrid+Pro+Stick+(320e)]<br />
}}<br />
{{DvbDevice<br />
| device=[[TerraTec Cinergy Hybrid T USB XS]]<br />
| type=USB<br />
| hw=ZL10353<br />
| pic=[http://tvde.terratec.net/modules.php?op=modload&name=News&file=article&sid=249]<br />
}}<br />
{{DvbDevice<br />
| device=[[TerraTec Cinergy Hybrid T USB XS]]<br />
| type=USB<br />
| hw=MT352<br />
| pic=[http://tvde.terratec.net/modules.php?op=modload&name=News&file=article&sid=249]<br />
}}<br />
{{DvbDevice<br />
| device=[[TerraTec Cinergy T USB XS|TerraTec Cinergy T XS]]<br />
| type=USB<br />
| hw=XC3028<br />
| pic=[http://tvde.terratec.net/modules.php?op=modload&name=News&file=article&sid=253]<br />
}}<br />
{{DvbDevice<br />
| device=[[TerraTec Cinergy T USB XS|TerraTec Cinergy T XS]]<br />
| type=USB<br />
| hw=MT2060<br />
}}<br />
{{DvbDevice<br />
| device=[[TerraTec Prodigy Hybrid T XS]]<br />
| type=USB<br />
| hw=usbbridge:em2880 tuner:xc3028<br />
}}<br />
}}<br />
<br />
<br />
{{DvbDeviceList<br />
| content=<br />
{{DvbDeviceCommented<br />
| device=Sundtek MediaTV Pro<br />
| type=USB<br />
| comment=DVB-C, DVB-T, AnalogTV, Composite, S-Video, FM-Radio. Features fully supported by manufacturer's closed source driver but no open source driver available.<br />
| pic=[http://sundtek.de/shop/Digital-TV-Sticks/Sundtek-MediaTV-Pro.html]<br />
}}<br />
}}<br />
<br />
=== Supported TM5600/6000/6010 Based USB DVB-T devices ===<br />
<br />
Official project site: [[Trident_TM6000|TM6000]]<br />
<br />
{{DvbDeviceList<br />
| content=<br />
{{DvbDeviceCommented<br />
| device=TerraTec Cinergy Hybrid XE<br />
| type=USB2.0<br />
| hw=xc3028L, zl10353, IR<br />
| comment=USB ID 0CCD:0086<br />
| fw=xc3028L-v36.fw<br />
}}<br />
{{DvbDeviceCommented<br />
| device=TerraTec Cinergy Hybrid-Stick<br />
| type=USB2.0<br />
| hw=xc3028L, zl10353, IR<br />
| comment=USB ID 0CCD:00a5<br />
| fw=xc3028L-v36.fw<br />
}}<br />
{{DvbDeviceCommented<br />
| device=Hauppauge WinTV HVR-900H<br />
| type=USB2.0<br />
| hw=xc3028L, zl10353, IR<br />
| comment=USB ID 2040:6600<br />
| fw=xc3028L-v36.fw<br />
}}<br />
}}<br />
<br />
==Currently Unsupported DVB-T USB Devices==<br />
{{help to support}}<br />
* [[ASUS My Cinema-U3000]]<br />
* [[DViCO FusionHDTV DVB-T NANO+]] usb id : 0fe9:db74<br />
* [[Emtec]] [[Emtec S830|S830]]<br />
* [[Lumanate Wave PAL SECAM DVBT Device]] [http://www.lumanate.com/aspx/sptwavedvbt.aspx] usb id : 1009:0015 (Emuzed, In).<br />
* [[Pinnacle PCTV 200e]]<br />
* Sweex MM002V<br />
* [[TerraTec Cinergy Piranha]]: work-in-progress, see [http://www.linuxtv.org/pipermail/linux-dvb/2008-June/026384.html mailing list] (June 2008)<br />
* [[Tongshi DVB-T USB]] [http://www.tongshi.com/cp_dvb_e.htm] ... Is this just a reference design? <br />
* [[WideView DVB-T/CATV USB2.0 Hybrid]] [http://www.wv.com.tw/]<br />
* [[WithView DMB Receiver]] [http://www.withview.co.kr]<br />
=== ASUS My Cinema-U3000 ===<br />
<br />
The U3000 (!= U3000 Mini) device is currently unrecognized by the Linux kernel. It is supposedly based on the dib3000p chipset. Picture and USB-info can be found [http://www.bttv-gallery.de/ here]<br />
<br />
=== DViCO FusionHDTV DVB-T NANO+ ===<br />
Not to be confused with the DViCO FusionHDTV DVB-T NANO which is supported. The Nano+ does not appear to have any drivers available for Linux.<br />
<br />
=== Freecom rev 4 DVB-T USB 2.0 tuner ===<br />
The latest Freecom/Yacumo usb stick has a Realtek 2831U chipset and any of the following usb id's: 14aa:0160, 0bda:2831, 2304:022b, 185b:0100, 13d3:3216, 13d3:3220, 13d3:3236, 13d3:3244, 08dd:2103. Latest Windows drivers dates january 2007 and can be downloaded at freecom.com<br />
<br />
More info is in the wiki's [[Realtek RTL2831U]] article.<br />
<br />
Chipset info at http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=35&Level=4&Conn=3&ProdID=147<br />
<br />
UPDATE: Realtek submitted a v0.0.2 of their driver feb 20th 2008. This has been confirmed to function for this Freecom (or Conceptronic) stick with usb id: 14aa:0160 on a 2.6.22.17 kernel. This stick has a MT2061F tuner chip, but this driver also supports the MLX5005 tuner chip. No additional firmware file is needed.<br />
<br />
The driver source can be downloaded from [http://www.megaupload.com/?d=DPE2C8I5], but be aware it has only be confirmed to work on devices with usb id 14aa:0160, and is not compatible with the current code base.<br />
<br />
===Geniatech T328 DVB-T ===<br />
[http://www.geniatech.com/pa/t682.htm]<br />
*chip: MT2060F, CY7C68013A and ZL10353. usb id: 04b4:8613. <br />
* It seems that this usb stick uses the same chips as FREEcom DVB-T usb stick and Yakumo Quickstick basic, but they have different usb id.<br />
<br />
=== LifeView TV Walker DVB-T (P/Q/Hybrid) ===<br />
<br />
P Stick<br />
<br />
* Now it doesn't exist in the Lifeview's page, not in discontinued products and not in External TV solutions, only a P Plus but I suppose that is different like the Q (now unsupported) and the Q PLus in External TV solutions. ¿Somebody can confirm this and also put info about the new product of lifeview if they're different?<br />
<br />
Q Stick [http://www.lifeview.com.tw/html/products/discontinued_products/q_dvbt.htm]<br />
<br />
* USB 2.0 stick. idProduct: 1506 ID: idVendor 0x10fd Anubis Electronics, Ltd<br />
<br />
* Chips visible on card:<br />
** Frontend: TDA10046A OFDM channel demodulator<br />
** Tuner: [http://www.semiconductors.philips.com/acrobat_download/literature/9397/75014128.pdf TDA8275A]Silicon Tuner<br />
<br />
There is a DVB-T-only box: [http://www.lifeview.com.tw/html/products/external_tv/tv_walker_dvbt.htm] I'm not able to find it in the discontinued products and correct the url to a new working one.<br />
<br />
There is a DVB-T/Analogue box (with external power): [http://www.lifeview.com.tw/html/products/discontinued_products/tv_walker_studio_hybrid.htm]<br />
<br />
=== Sweex MM002V2 === <br />
[http://www.sweex.com/producten.php?sectie=2&subsectie=2&item=127&artikel=879]<br />
* Just bought this to find out it doesn't work. Unfortunately I have no experience creating drivers :-(<br />
<br />
This is as much as I know, according to their site ...<br />
<br />
Specification<br />
# Interface: USB 2.0<br />
# [[Microtune MT2060]] silicon tuner<br />
# Chipsets: [[E3C_EC168|E3C, EC168]]<br />
<br />
Looking at dmesg in ubuntu 8.10 running kernel 2.6.27 I can see its being detected as a keyboard<br />
<br />
* [ 2893.200071] usb 5-5: new high speed USB device using ehci_hcd and address 6<br />
* [ 2893.342542] usb 5-5: configuration #1 chosen from 1 choice<br />
* [ 2893.344136] input: HID 18b4:1689 as /devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5:1.0/input/input10<br />
* [ 2893.387617] input,hidraw0: USB HID v1.11 Keyboard [HID 18b4:1689] on usb-0000:00:1d.7-5<br />
<br />
Hopefully someone can help with driver development.<br />
<br />
/Steve<br />
<br />
UPDATE: "Anttip" linuxtv HG [http://linuxtv.org/hg/~anttip/] repository has EC168 development drivers (not yet part of 2.6.31.1 Kernel v4l drivers), which work with EC168 based dvb-t sticks (18b4:1689 device id). Numerous other re-branded sticks use the same chipset.<br />
<br />
=== TVISTO DVB-T USB === <br />
There are different TVISTO usb dongles and some are supported, see [[TVISTO DVB-T USB]] for more information.<br />
<br />
=== [http://www.twinhan.com/product_AD-TU200.asp TwinHan/AzureWave AD-TU200 (7047) DVB-T] ===<br />
Uses a [[Realtek RTL2831U]] decoder chip and [[Maxlinear]] [[MXL5003S]] tuner. USB ID is 13d3:3216. It seems to work with the realtek experimental driver (see freecom v4 above):<br />
<br />
[ 3841.997121] DVB: registering new adapter (DTV-DVB UDTT 7047-USB 2.0 DVB-T Driver)<br />
[ 3841.998753] DVB: registering frontend 0 (Realtek RTL2831 DVB-T)...<br />
<br />
=== [http://www.twinhan.com/product_terrestrial_7049.asp TwinhanDTV Twister (7049) DVB-T] ===<br />
In germany a similar device seems to be sold as dnt EuroMini200 [http://www.dnt.de/index.php?dir=produkte/detail&id=20206].<br />
<br />
We tried to get information about the usb interface at Twinhan, but there was none avaiable. The chip vendor Uli [http://www.uli.com.tw/] refuses to open all relevant information.<br />
<br />
Maybe the same applies for the TwinhanDTV Hurricne (704D) [http://www.twinhan.com/product_704D.asp].<br />
<br />
=== [http://www.twinhan.com/product_D%2BA_3.asp TwinhanDTV MagicBox Pro (DVB-T/Analogue)] ===<br />
A [[hybrid]] USB2.0 box based on the [http://www.uli.com.tw/product_dm/m9207dm_web.pdf ULI M9207] chipset. Also based on this chipset is the Pinnacle [http://www.pinnaclesys.com/PublicSite/uk/Products/Consumer+Products/PCTV+Tuners/PCTV+Analog_Digital+PVR/PCTV+310e PCTV 310e], [http://www.lifeview.com/usa/html/products/multimedia/tvwalker_hybrid.htm LifeView TV Walker Hybrid] and [http://www.nurido.at/news/computer/testgericomtvtunerusb20beihofer.html Gericom USB 2.0 Hybrid Box] sold by Aldi (Germany) and Hofer (Austria).<br />
<br />
<br />
=== YUAN UB701 (DVB-T/Analogue) ===<br />
A [[hybrid]] USB2.0-only box. Maybe it is a clone of the Conexant Hybrid Reference design?<br />
It has an em2880 and a xc3028 tuner. USB id eb1a:2881<br />
[http://www.yuan.com.tw/en/products/vdo_ub701.html]<br />
<br />
<br />
=== WithView DMB Receiver ===<br />
* Model No : HDMB-T100A<br />
* lsusb : ID 10c4:0010 Cygnal Integrated Products, Inc.<br />
[http://www.withview.co.kr/eshop/contents.html?layout=t100a]<br />
<br />
<br />
=== WandTV ===<br />
AF9035 based. Check out the [[Afatech AF9035]] page for information on support. And please add details so that the device can be added to the big table above.<br />
<br />
There is also IT9135 based WandTV, id is: 048d:9006. You can try the way described for Kworld_UB499-2T. It "kind of works" for me with the older driver http://wasietsmet.nl/wp-content/uploads/2010/07/IT9135_SRC_i686_patch.tar.gz (scans the channels). The newer driver http://wasietsmet.nl/wp-content/uploads/2010/07/V10.12.30.1.zip compiles with unknown symbol errors: “__stack_chk_fail” and “mcount”.<br />
<br />
==Also See==<br />
* [[DVB via USB|General Information Regarding DVB via USB]]<br />
<br />
[[Category:DVB-T| ]]<br />
[[Category:Hardware| ]]<br />
[[Category:DVB-T USB Devices| ]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=User:CityK&diff=30605User:CityK2012-03-11T07:31:58Z<p>Js: Reverted edits by Seputarsoftware (talk) to last revision by CityK</p>
<hr />
<div>This is my sandbox. Being a sandbox, everything you see here is a work in progress. <br />
<br />
<br />
<br />
==Wiki Main Page:==<br />
[[Image:Graphic_banner_rough_idea_test3.png]]<br />
<br />
<br />
== User Sign up /Login Subpage:==<br />
'''A Few Notes Before you Begin'''<br />
<br />
Before you jump in and make your contribution, please first familiarize yourself with the layout of the site. Doing so will help you to place your information in the right location. As the wiki grows, it takes an increasing amount of effort and discipline to keep it from quickly turning into a tangled mess. So it's up to each of us to make sure the information submitted is easy for everybody to find and access.<br />
<br />
If you make a contibution and later find that your submission has been edited or moved to another area of the wiki, please don't <br />
feel offended. Everyone understands and appreciates the time and efforts you took, but bear in mind that a factual and well-organized resource for everyone interested in analog or digital TV is the ultimate aim of the LinuxTV wiki.<br />
<br />
Submitters should also know that, to keep the information contained in the wiki free, all contributions are automatically licensed under the GNU General Public License GPL. If you wish, you may specify in each case that your contribution is dual-licensed under the MIT License. Please do not reproduce or submit copyrighted works without obtaining the express consent of the owner or its agent.<br />
<br />
Lastly, to help keep the wiki free from spam, contributors are required to set up an account and to sign in before they can post to the wiki. (This is a painless process that only takes a few seconds). To sign up an<br />
<br />
Now enjoy and have fun! -- The LinuxTV WikiTeam [People behind V4L]<br />
<br />
<br />
<br />
==[[Image:Software_viewing_apps_icon.png|50px]] TV Related Software SubPage:==<br />
<br />
It would seem that, instead of re-inventing the wheel, the existing [[TV Related Software]] page is an ideal candidate to be reworked as the TV Software SubPage <br />
<br />
'''TV related items/issues''' that should be addressed are:<br />
* scanning <br />
* tuning/zapping<br />
* watching/recording<br />
* teletex/CC<br />
<br />
* streaming<br />
<br />
<br />
distinguish between tuner/tuning/to tune/receiver ...<br />
in contemporary dialogue/common language:<br />
the terms "tuner" and "receiver" are often used interchangeably ... but its more appropriate to call it a receiver, with the tuner being part of the receiver <br />
<br />
[[tuning]]<br />
In electronics, tuning refers to a process in which, first, a specific [[RF]] signal is acquired and, second, is subsequently acted upon such that any underlying content (information/data) may be extracted.<br />
<br />
One may "tune" to a specific frequency and find that there is no underlining content to be found -- in the context of radio or TV signal reception, this would be characteristic of static or white noise.<br />
<br />
in which case the RF carrier signal <br />
list of known frequencies or obtained via a frequency scan <br />
<br />
<br />
<br />
<br />
==Just toying ==<br />
Would like to try to setup a table for the chipsets using templates such that, with using logic to define relevant fields, we have all the data contained in one spot (I guess much like Henrik was doing with the DVB-T USB stuff), but can then parse the info for display in relevant articles, such that there isn't duplication. Present duplication example:<br />
* [[USB interface chipsets]]<br />
* [[Demodulator#Digital_Demodulators|Demodulator]]<br />
<br />
{| class="wikitable sortable" <br />
|+'''A Sortable List of Chipsets'''<br />
|-<br />
! Vendor !! Chipset !! style="background-color:#ffffcc;" | Tuner !! style="background-color:#B0C4DE;"| Analog <br>Demodulator !! style="background-color:#B0C4DE;" | Digital<br> Demodulator !! style="background-color:#B0C4DE;" | Standard !! style="background-color:#B0C4DE;" | Modulation<br>Schemes !! A/V <br> decoder !! MPEG <br>encoder !! MPEG<br>decoder !! style="background-color:#F08080;"| Interface<br> chipset !! style="background-color:#F08080;"|Bridge <br> Type !! style="background-color:#F08080;"|DVB <br>support !! style="background-color:#F5DEB3;"| Linux <br>Support !! style="background-color:#F5DEB3;" | Associated <br>Kernel Modules !! style="background-color:#F5DEB3;" | Firmware !! class="unsortable"| Comments<br />
|-<br />
| [[Afatech]] || [[Afatech AF9005|AF9005]] || {{No}} || {{No}} || {{Yes}} || [[DVB-T]] || [[COFDM]] || {{No}} || {{No}} || {{No}} || {{Yes}} || [[USB]] || {{Yes}} || {{Yes}} || ? || {{Yes}} || <br />
* A combo USB bridge & demod IC<br />
|-<br />
|}<br />
<br />
<br />
==Misc Info & ideas for me:==<br />
<br />
'''Timestamp'''<br />
* <nowiki>~~~~~</nowiki><br />
<br />
'''Colours'''<br />
* [http://en.wikipedia.org/wiki/Web_colors Web colours]<br />
* v4l --> style="background-color:#006600;<br />
* DVB --> style="background-color:#6289AB;<br />
<br />
<br />
'''Tables'''<br />
* [http://www.mediawiki.org/wiki/Help:Tables table formating]<br />
* [http://en.wikipedia.org/wiki/Table_markup Table_markup]<br />
<br><br />
style="color:green; background-color:#ffffcc;"<br><br />
style="color:#e76700;"<br><br />
style="background-color:# ;"<br />
<br />
<br />
'''Icons wanted''': <br />
* need to find or create a chain link icon for "links"<br />
* * terrestrial broadcast tower<br />
* sat dish <br />
* * pcmcia<br />
* pci<br />
* pcie<br />
* firewire<br />
<br />
<br />
'''Special Links'''<br />
* Works: [{{SERVER}}{{localurl:Special:Allpages|{{ns:100}}}} {{ns:100}}]<br />
* Doesn't work: {{Note|[{{SERVER}}{{localurl:Special:Allpages|{{ns:100}}}} {{ns:100}}]}} ... stupid wiki.<br />
* also see http://www.mediawiki.org/wiki/Plainlinks<br />
<br />
<br />
'''Clickable Icons or Images using templates'''<br />
* http://www.mediawiki.org/wiki/Extension:ImageLink<br />
* http://www.mediawiki.org/wiki/Extension:ImageMap<br />
* http://www.mediawiki.org/wiki/Extension:Icon <--- *** <br />
* http://meta.wikimedia.org/wiki/Template:Click (depreciated)<br />
* http://en.wikipedia.org/wiki/Template:Click-Inline</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Multiproto&diff=30482Multiproto2012-02-08T19:44:55Z<p>Js: Reverted edits by Sanders Dowdy (talk) to last revision by Jon2856</p>
<hr />
<div>Multiproto was a proposal for version 5.0 of the LinuxDVB API (see also [[S2API]]) which includes extensions for cards which support multiple DVB protocols (DVB-S, DVB-S2, DVB-T, DVB-C, DVB-H, ATSC, DSS).<br />
An alternative proposal, [[S2API]], was evenutally selected as the new API and was released in <br />
kernel 2.6.28 on 24 Dec 2008.<br />
<br />
Multiproto was an experimental project and was not implemented in any released version of Linux. Notably,<br />
the author of some of the main parts of multiproto has in the past incomprehensibly attempted<br />
to block its inclusion in Linux, highlighting both misunderstanding of the implications of the GPL and the need<br />
for stricter project management within the Linux DVB community<br />
http://www.linuxtv.org/pipermail/linux-dvb/2008-January/023355.html. After more than two years, a pull request<br />
for the API (excluding drivers) was eventually issued hours after the competing project [[S2API]] was<br />
announced http://linuxtv.org/pipermail/linux-dvb/2008-September/028896.html.<br />
<br />
[[S2API]] and multiproto were reviewed at the Linux Plumbers' Conference in Portland, Oregon, Wed 17th - Fri 19th September 2008: http://linuxplumbersconf.org/program/microconfs/getmc.php?mc=chehab08. See http://www.linuxtv.org/downloads/plumbers2008/stoth_dvb_round_table_new_api.pdf.<br />
<br />
An announcement regarding the conclusions of the review was made by the maintainer :<br />
http://www.linuxtv.org/news.php?entry=2008-09-23.mchehab,<br />
http://linuxtv.org/pipermail/linux-dvb/2008-September/029155.html,<br />
http://linuxtv.org/pipermail/linux-dvb/2008-September/029181.html,<br />
http://linuxtv.org/pipermail/linux-dvb/2008-September/029232.html.<br />
By unanimous vote, [[S2API]] was selected for inclusion in kernel 2.6.28.<br />
The multiproto API will therefore not be merged into<br />
the kernel. The decision is final. The device support in the multiproto tree will not be lost -- drivers<br />
can be easily converted to work with the S2API. It is intended to add<br />
support for products with the STB0899 demodulator (TT-3200 and others) to S2API before the merge.<br />
<br />
==Overview/Features==<br />
''Discuss the features and facets of the project here ... this means you''<br />
<br />
===Design Decisions===<br />
''explain the choices made ... this means you''<br />
<br />
===Technical Details===<br />
''give a technical description of how the API change has been implemented ... this means you''<br />
<br />
New structs and enums have been added to expand the API for multiple frontends and the parameters required for protocols DVB-S, DSS, DVB-S2, DVB-T, DVB-H and ATSC. These are prefixed (at least for now) with "dvbfe_" and "DVBFE_" as opposed to the old "fe_" and "FE_". For details compare the old and new versions of include/linux/dvb/frontend.h. Currently multiproto implements both the new and old APIs and a glue layer to manage old/new drivers with new/old API calls. Presumably the plan is eventually to move to a pure 3.3 API and update all the drivers.<br />
<br />
Simple enough you might think, but progress has been very slow. Since the first version, way back in April 2006, ten (10!) versions of the entire Linux kernel have been released. See http://www.linuxtv.org/pipermail/linux-dvb/2006-April/009522.html and http://kernelnewbies.org/Linux26Changes.<br />
<br />
===Evaluation===<br />
''explain whether the design goals have been met or not ... this means you''<br />
<br />
1. Some application of [http://en.wikipedia.org/wiki/Occam's_razor Occam's Razor] still needs to be made. There is '''repetition''' in the multiproto API arising from the use of<br />
unions of structs to hold parameters (often the same ones) for each type of frontend.<br />
However API calls (eg. ioctl dvbfe_params) '''can be addressed to individual frontends''', i.e. <br />
/dev/dvb/adapterN/frontendM, so this repetition could be removed to create a cleaner API. For example these variables:<br />
<br />
dvbfe_params.delsys.dvbs.fec<br />
dvbfe_params.delsys.dss.fec<br />
dvbfe_params.delsys.dvbs2.fec<br />
dvbfe_params.delsys.dvbc.fec<br />
<br />
could be replaced by the simpler:<br />
<br />
dvbfe_params.fec<br />
<br />
and these<br />
<br />
dvbfe_info.delsys.dvbs.fec<br />
dvbfe_info.delsys.dss.fec<br />
dvbfe_info.delsys.dvbs2.fec<br />
<br />
could be replaced by the simpler:<br />
<br />
dvbfe_info.fec<br />
<br />
If we simplify in this way, the relevant section of linux/include/linux/dvb/frontend.h would look like this:<br />
(note I added '''_caps''' to some variables to indicate that they are actually ORd sets of ''capabilities'')<br />
<br />
struct dvbfe_info {<br />
char name[128];<br />
enum dvbfe_delsys delsys; //curr delivery sys, READABLE by user, not WRITEABLE<br />
enum dvbfe_modulation modulation_caps; //valid for DVB-S,S2,C,T,H,DSS,ATSC<br />
enum dvbfe_fec fec_caps; //valid for DVB-S,S2,DSS<br />
enum dvbfe_stream_priority stream_priority_caps; //valid for DVB-T,H<br />
__u32 frequency_min;<br />
__u32 frequency_max;<br />
__u32 frequency_step;<br />
__u32 frequency_tolerance;<br />
__u32 symbol_rate_min;<br />
__u32 symbol_rate_max;<br />
__u32 symbol_rate_tolerance;<br />
enum fe_spectral_inversion inversion;<br />
__u8 pad[128];<br />
};<br />
<br />
instead of the multiproto version which is more complex and repetitive:<br />
<br />
/* DVB-S capability bitfields */<br />
struct dvbfe_dvbs_info {<br />
enum dvbfe_modulation modulation;<br />
enum dvbfe_fec fec;<br />
};<br />
/* DSS capability bitfields */<br />
struct dvbfe_dss_info {<br />
enum dvbfe_modulation modulation;<br />
enum dvbfe_fec fec;<br />
};<br />
/* DVB-S2 capability bitfields */<br />
struct dvbfe_dvbs2_info {<br />
enum dvbfe_modulation modulation;<br />
enum dvbfe_fec fec;<br />
__u8 pad[32];<br />
};<br />
/* DVB-C capability bitfields */<br />
struct dvbfe_dvbc_info {<br />
enum dvbfe_modulation modulation;<br />
};<br />
/* DVB-T capability bitfields */<br />
struct dvbfe_dvbt_info {<br />
enum dvbfe_modulation modulation;<br />
enum dvbfe_stream_priority stream_priority;<br />
__u8 pad[32]; <br />
};<br />
/* DVB-H capability bitfields */<br />
struct dvbfe_dvbh_info {<br />
enum dvbfe_modulation modulation;<br />
enum dvbfe_stream_priority stream_priority;<br />
__u8 pad[32];<br />
};<br />
/* ATSC capability bitfields */<br />
struct dvbfe_atsc_info {<br />
enum dvbfe_modulation modulation;<br />
__u8 pad[32];<br />
};<br />
struct dvbfe_info {<br />
char name[128];<br />
union {<br />
struct dvbfe_dvbs_info dvbs;<br />
struct dvbfe_dss_info dss;<br />
struct dvbfe_dvbs2_info dvbs2;<br />
struct dvbfe_dvbc_info dvbc;<br />
struct dvbfe_dvbt_info dvbt;<br />
struct dvbfe_dvbh_info dvbh;<br />
struct dvbfe_atsc_info atsc;<br />
__u8 pad[128];<br />
} delsys;<br />
__u32 frequency_min;<br />
__u32 frequency_max;<br />
__u32 frequency_step;<br />
__u32 frequency_tolerance;<br />
__u32 symbol_rate_min;<br />
__u32 symbol_rate_max;<br />
__u32 symbol_rate_tolerance;<br />
enum fe_spectral_inversion inversion;<br />
__u8 pad[128];<br />
};<br />
<br />
<br />
2.''' There was a problem with the design of the multiproto API'''. The routine DVBFE_GET_INFO actually ''changed'' the kernel state (in particular the variable which holds the delivery system). Simply calling DVBFE_SET_PARAMS with a complete correct set of parameters does not work. The corresponding screwy userspace code can be seen in the patched http://abraham.manu.googlepages.com/szap.c where DVBFE_GET_INFO is used to SET the delivery system variable before DVBFE_SET_PARAMS is called. Such odd unexpected behaviour is confusing and should not be accepted in the Linux kernel. At the very least some work needs to be done to rename the routines sensibly. DVBFE_GET_INFO appears to have been<br />
originally intended to provide information about the capabilities of the frontend, which is currently not apparent in its name. See http://www.linuxtv.org/pipermail/linux-dvb/2008-March/024266.html and http://www.linuxtv.org/pipermail/linux-dvb/2008-March/024281.html.<br />
<br />
UPDATE March 09 2008: This appears to have been changed with the introduction of DVBFE_SET_DELSYS which is now used<br />
to set the delivery system. Tuning is done with szap2. Unfortunately the variable delsys has been completely removed from the struct dvbfe_info, instead of just making it a user-''readable'' variable (not a writeable one), analogous to the "type" variable in the old dvb_frontend_info (but with a different range of values, i.e. DVB-S/S2/C/T/H/DSS/ATSC vs. QPSK/QAM/OFDM/ATSC). It would be nice if delsys were put back in, with code to set its <br />
value appropriately on DVBFE_GET_INFO calls.<br />
<br />
===Alternatives===<br />
'''[[S2API]]: Tag/Value-based API proposal'''<br />
<br />
Following long standing frustration amongst developers and users about the lack of progress in getting multiproto into<br />
the Linux kernel, a group of four senior developers including the maintainer has proposed an alternative<br />
(Aug 29 2008) and announced that they no longer support multiproto.<br />
See http://linuxtv.org/pipermail/linux-dvb/2008-August/028313.html.<br />
The idea had been proposed earlier http://linuxtv.org/pipermail/linux-dvb/2007-November/021618.html. Technically it is quite different from multiproto. Control<br />
of the frontend is implemented using a command sequence of (tag,value)<br />
pairs to set all the required parameters and<br />
then initiate tuning. Thus it no longer depends on fixed structs to hold parameter data.<br />
A notable advantage of the tag/value technique is that it should make it much easier<br />
to keep up with future DVB transmission standards because this will at most require the definition<br />
of additional tags (i.e. commands)<br />
rather than a revision of the API.<br />
Commands can be made atomic by passing a whole command sequence in a single ioctl (for example a set of<br />
parameters followed by the tune command). Alternatively a sequence may be sent one command at a time.<br />
The development repository is available at http://linuxtv.org/hg/~stoth/s2. Work still<br />
needs to be done to finish the API design and port the existing DVB-S2 drivers to work with it. Other drivers<br />
are not affected.<br />
<br />
'''APIs used in the HVR4000 drivers'''<br />
An alternative API has been created for the [[Hauppauge]] [[Hauppauge WinTV-HVR-4000|WinTV-HVR-4000]] which makes minimal changes to the current v4l-dvb API in order to provide multifrontend support for DVB-T,DVB-S and DVB-S2 for that device. It offers backwards compatibility with existing binary multimedia applications for DVB-T and DVB-S without recompilation. Patches providing DVB-S2 support for szap and mythtv have been posted. See http://dev.kewl.org/hauppauge/experimental/, http://dev.kewl.org/hauppauge and http://www.linuxtv.org/pipermail/linux-dvb/2008-March/024243.html.<br />
<br />
A different method was used to provide support for DVB-S2 in the HVR4000 single frontend (sfe) driver.<br />
<br />
'''Use multiproto drivers with old API'''<br />
A patch exists which allows basic use of drivers developed for multiproto with the current API (3.2).<br />
See http://linuxtv.org/pipermail/linux-dvb/2008-May/026246.html and<br />
http://linuxtv.org/pipermail/linux-dvb/2008-August/027979.html.<br />
<br />
===Status and Migration Plan===<br />
''explain how a migration from the current API to multiproto could be achieved ... this means you''<br />
<br />
The multiproto API will not be included in the Linux kernel (see above). Device support in the multiproto<br />
tree will simply be converted to work with [[S2API]] where necessary.<br />
<br />
The mantis tree (http://jusst.de/hg/mantis) which also uses the multiproto API has not yet been merged into multiproto, meaning that there is unnecessary duplication of the core code and any code fixes in either<br />
tree are not automatically applied to both trees.<br />
<br />
==Making it Work==<br />
<br />
How to get it from the author's repository:<br />
<br />
hg clone http://jusst.de/hg/multiproto<br />
or<br />
http://jusst.de/hg/multiproto/archive/tip.tar.bz2<br />
<br />
UPDATE 1st Aug 2008: Igor Liplianin has created another repository containing multiproto code and szap2 at http://liplianindvb.sourceforge.net/hg/, reported to be working with the HVR-4000.<br />
See<br />
http://www.linuxtv.org/pipermail/linux-dvb/2008-July/027514.html. This appears to be<br />
similar to the V4L/DVB staging development repository at http://linuxtv.org/hg/v4l-dvb/<br />
but with the addition of multiproto code.<br />
<br />
hg clone http://liplianindvb.sourceforge.net/hg/liplianindvb<br />
hg clone http://liplianindvb.sourceforge.net/hg/szap2<br />
<br />
<br />
===Drivers===<br />
There are currently no in-kernel multiproto drivers. There are several cards which have experimental support in the multiproto tree, perhaps with additional patches.<br />
<br />
''Provide details of which drivers work with multiproto ... this means you''<br />
<br />
See the descriptions for the following cards:<br />
<br />
[[Azurewave AD SP400 CI (VP-1041)|Azurewave AD-SP400 CI (Twinhan VP-1041)]]<br />
<br />
[[Hauppauge]] [[Hauppauge WinTV-HVR-4000|WinTV-HVR-4000]] <br />
<br />
[[KNC1]] [[KNC1 DVB-S2 TV Station|DVB-S2 TV Station]] (PCI32, supports CI)<br />
<br />
[[TechnoTrend]] [[TechnoTrend TT-budget S2-3200|TT-budget S2-3200]]<br />
<br />
[[TerraTec]] [[TerraTec Cinergy S2 PCI HD CI| Cinergy S2 PCI HD CI]] (PCI32, CI)<br />
<br />
''provide the details of where the drivers and patches and necessary tools are available ... this means you''<br />
<br />
''provide details of how to compile for recent kernels -- this means you''<br />
<br />
===Sample kernel output===<br />
''provide the relevant portion of dmesg here''<br />
<br />
===Tuner / DiSEqC / Player support===<br />
''provide comprehensive details of how to upgrade multimedia applications to work with the new API ... this means you''<br />
<br />
Scanning and tuning applications generally will not work with the new API unless they are modified. The situation is arguably improving but the lack of patched applications (and guidance on patching) has hindered completion and testing of multiproto and new drivers, and adoption of the new API. Needless to say, patching drivers and multiple applications is a step too far for most potential testers.<br />
<br />
'''dvb-apps''' : There is ''still'' no patched dvb-apps tree. Someone needs to create one ... why don't you?<br />
<br />
'''scan''' : see patched version at http://jusst.de/manu/scan.tar.bz2<br />
<br />
'''szap''': see patched version at http://abraham.manu.googlepages.com/szap.c<br />
Also see information about szap2 at http://allrussian.info/thread.php?postid=187408#post187408<br />
and http://www.linuxtv.org/pipermail/linux-dvb/2008-February/023836.html.<br />
<br />
'''[[MPlayer]]''' : someone needs to write a patch ... why don't you?<br />
<br />
'''[[Kaffeine]]''' / '''xine-lib''' : someone needs to write a patch ... why don't you? There are some posts about getting Kaffeine to work with multiproto in these threads: http://www.linuxtv.org/pipermail/linux-dvb/2008-May/025882.html,<br />
http://www.linuxtv.org/pipermail/linux-dvb/2008-July/027141.html<br />
and in these two messages:<br />
http://sourceforge.net/mailarchive/forum.php?thread_name=48217036.3090709%40gmail.com&forum_name=kaffeine-devel<br />
and<br />
http://sourceforge.net/mailarchive/forum.php?thread_name=481DE023.9000903%40gmail.com&forum_name=kaffeine-devel<br />
.<br />
<br />
'''[[VDR]]''' : Ugh, patch hell. Why is there no VDR development repository? History: VDR version 1.5.14 required multiproto (v1.5.14 announcement: http://www.linuxtv.org/pipermail/vdr/2008-January/015302.html) but this was revoked in 1.5.15 to make a<br />
multiproto-free release 1.6.0 due to the unavailability of multiproto in the Linux kernel mainstream (not a <br />
surprise to anyone). The requirement for multiproto was reinstated in version 1.7.0 (again jumping the gun),<br />
but it needs an old multiproto (from before delsys was removed (see above)), so you still have to patch it (multiproto-update.diff) to work with the current multiproto. But that patch is now broken -- you will have<br />
to fix it by hand. There is even a patch which can be used to revert that (1.7.0+multiproto-update.diff) to<br />
work with the v3.2 API drivers, and another newer one which will work with both APIs!<br />
See http://linuxtv.org/pipermail/vdr/2008-August/017534.html and<br />
http://www.udo-richter.de/vdr/patches.en.html#dvb-api-wrapper. [Prediction: VDR will remove the multiproto<br />
requirement again before v1.8.0, flip,flop,flip,flop...]. <br />
<br />
And you need yet another patch if you want H.264 support (http://www.linuxtv.org/pipermail/vdr/2008-April/016513.html). There are patches for vdr-rotor and GotoX too.<br />
<br />
Version 1.7.1 has now been released, this time requiring multiproto_plus. See http://linuxtv.org/pipermail/linux-dvb/2008-September/028818.html.<br />
<br />
Following the decision to merge S2API into the kernel (and not multiproto) the multiproto support in VDR <br />
needs to be replaced with S2API support. An initial patch supporting S2API for DVB-S only has been written,<br />
see http://linuxtv.org/pipermail/vdr/2008-September/017910.html.<br />
<br />
'''[[MythTV]]''' : Two patches (one DVB-S/S2, one DVB-S only) have been posted http://www.linuxtv.org/pipermail/linux-dvb/2008-January/022757.html. Current status?<br />
<br />
'''[[dvbstream]]''' : Someone needs to write a patch ... why don't you? See http://www.linuxtv.org/pipermail/linux-dvb/2008-February/024056.html.<br />
<br />
''provide details of how to use with DiSEqC -- this means you''<br />
<br />
===How to patch an application for Multiproto===<br />
''provide guidance on patching applications to use multiproto -- this means you''<br />
<br />
'''To tune to a channel''' : using the patched szap above as a guide we see that<br />
<br />
struct dvb_frontend_parameters tuneto;<br />
...<br />
ioctl(fefd, FE_SET_FRONTEND, &tuneto);<br />
<br />
must be replaced by<br />
<br />
struct dvbfe_params fe_params;<br />
...<br />
ioctl(fefd, DVBFE_SET_PARAMS, &fe_params);<br />
<br />
where the parts of dvbfe_params.delsys relevant for the delivery system used (DVB-S/DSS/DVB-S2) need to be set before the call.<br />
<br />
To make the userspace code a lot cleaner C preprocessor macros can be used to hide the full details of the multiproto api - here is a short example:<br />
<br />
#if (DVB_API_VERSION==3) && (DVB_API_VERSION_MINOR>=3)<br />
#define FE_PARAM struct dvbfe_params<br />
#define IOCTL_SET_FE DVBFE_SET_PARAMS<br />
#define DVB_SET_DELIVERY(a, b) (a)->delivery=(b)<br />
#define DVBC_SET_SYMBOLRATE(a, b) (a)->delsys.dvbc.symbol_rate=(b)<br />
#else<br />
#define FE_PARAM struct dvb_frontend_parameters<br />
#define IOCTL_SET_FE FE_SET_FRONTEND<br />
#define DVB_SET_DELIVERY(a, b) do{ } while(0)<br />
#define DVBC_SET_SYMBOLRATE(a, b) (a)->u.qam.symbol_rate=(b)<br />
#endif<br />
<br />
void tune(int fefd) {<br />
FE_PARAM fparm;<br />
<br />
memset(&fparm, 0, sizeof(FE_PARM));<br />
<br />
DVB_SET_DELIVERY(&fparm, DVBFE_DELSYS_DVBC);<br />
...<br />
DVBC_SET_SYMBOLRATE(&fparm, symbolrate)<br />
<br />
if (ioctl(fefd, IOCTL_SET_FE, &fparm) < 0) {<br />
printf("Tuning failed");<br />
}<br />
}<br />
<br />
The code itself will stay clean of ifdef spaghetti and the compatibility macros can be hidden in some header file. See getstream [http://silicon-verl.de/home/flo/projects/streaming/] for<br />
a multiproto capable tuner coder without a single ifdef.<br />
<br />
==External Links==<br />
<br />
[[Category:Development]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Pixelview_PlayTV_Pro_Ultra&diff=30481Pixelview PlayTV Pro Ultra2012-02-08T19:44:49Z<p>Js: Reverted edits by Sanders Dowdy (talk) to last revision by Jimbley</p>
<hr />
<div>==Features/Overview==<br />
An analog PCI Card from [[ProLink]]<br />
==Making it Work==<br />
Autodetect is not possible for this card so you need use option card=27:<br />
<br />
echo "options cx88xx card=27" > /etc/modprobe.d/cx88xx<br />
<br />
With this setting TV image and channel tuning seems work, but sound with loopback cable still not heard.<br />
If anybody know how to get this card completelly work write down please.<br />
<br />
<br />
<br />
Discussion in video4linux mailing list about sound and fm tuner problem with this card:<br />
<br />
http://threebit.net/mail-archive/video4linux/msg01145.html<br />
<br />
http://threebit.net/mail-archive/video4linux/msg01166.html<br />
<br />
> I have a PixelView PlayTV Pro Ultra (identified in windows as Prolink<br />
> PV-TV303/304) for which I can get image, scan channels, etc., but: no radio<br />
> yet, and no sound (unless I have warm-booted into windows and used the card's<br />
> software there before). If I've cold booted into linux I don't get any sound at all.<br />
> Kernel version is 2.6.15.6, gcc 4.0.3.<br />
<br />
Those boards really sucks, since they don't offer any tveeprom and<br />
several different models are selled with the same codename.<br />
Radio should be working now, with mercurial version, available at<br />
http://linuxtv.org/hg, with tuner=65.<br />
[[Category:Analog PCI Cards]]<br />
About sound, probably some gpio are wrong for your specific model. You<br />
should run regspy (it cames with dscaller) and run at windows. There are<br />
some instructions about how you can use it to generate an entry to v4l<br />
code at wiki, on linuxtv.<br />
==External Links==<br />
http://www.prolink-usa.com/english/product/tv-cx883p+_ultra.html</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Template_talk:Help_to_support&diff=30054Template talk:Help to support2011-12-02T23:05:19Z<p>Js: </p>
<hr />
<div>==Typo==<br />
I don't have permission to edit the template.<br />
<br />
"it is possible that you will peak the(se) developer's interest"<br />
<br />
s/peak/pique/<br />
<br />
--[[User:Pepsiman|Pepsiman]] 15:31, 2 December 2011 (CET)<br />
<br />
:: Thanks...I'm not sure why you wouldn't have been able to edit the template (they should, as far as I know, be editable by all users), though I've heard that from several others in the past too ... --[[User:CityK|CityK]] 21:44, 2 December 2011 (CET)<br />
<br />
::: Blame the spammers. New accounts are blocked from editing templates for the first 24h. --[[User:Js|js]] 00:05, 3 December 2011 (CET)</div>Jshttps://www.linuxtv.org/wiki/index.php?title=User_talk:CityK&diff=29655User talk:CityK2011-10-02T20:08:58Z<p>Js: </p>
<hr />
<div>[[User:CityK|CityK]] 19:46, 3 February 2007 (CET)<br />
<br />
Spent a bunch of time last night and this morning creating and rearranging ATSC devices stuff.<br />
There is a LOT of work that could be done.<br />
<br />
<br />
[[User:CityK|CityK]] 01:02, 5 February 2007 (CET)<br />
<br />
I got to find a WYSIWYG wiki editor, else using code takes me ages<br />
<br />
<br />
[[User:CityK|CityK]] 08:23, 7 February 2007 (CET)<br />
<br />
made a mess of the categories tonight ... will clean that whole thing up soon.<br />
Started with the renaming and relinking of the DVB pages ... a lot more work than I thought. Oh well, it will be nice to have a consistant look and nomenclature across the board.<br />
<br />
Definitely several months of work to get this thing ship shape!<br />
<br />
<br />
[[User:JGXenite|JGXenite]] 14:25, 20 April 2007 (CEST)<br />
<br />
Hi CityK,<br />
<br />
Sorry about that :(. I'll make my changes to Mplayer now.<br />
<br />
<br />
[[User:JGXenite|JGXenite]] 14:56, 21 April 2007 (CEST)<br />
<br />
No worries with the countries thing - I thought it would make more sense moving it to channels.conf, as that is the correct file name. I then decided to make a "Europe" sub-category as there were quite a few European entries. I've also contributed one for United Kingdom (Sheffield) detailing my experience with setting it up :).<br />
<br />
<br />
[[User:Howl|howl]] 00:01, 27 July 2007 (CEST)<br />
<br />
I like the look of the page that you purpose and also i think that this can benefit a lot for people who only want information, actual desing is more confuse.<br />
<br />
: Thanks Howl. If you did not see the message previously, here is a (more-or-less) recent status report: http://www.linuxtv.org/pipermail/linux-dvb/2007-June/018429.html --[[User:CityK|CityK]] 07:03, 27 July 2007 (CEST)<br />
<br />
:: I like a lot the idea and also the Nick Andrew's one in the reply of making a database. I don't know if there is a system to integrate a SQL db style like MySQL in wiki but if it exists it could be a powerful tool that will help to test different templates for the devices pages making the data independient of the style. --[[User:Howl|howl]] 01:08, 30 July 2007 (CEST)<br />
<br />
:::I do too, but I have no idea (or time to investigate, let alone implement) about a db in a wiki ... maybe in the future --[[User:CityK|CityK]] 19:14, 30 July 2007 (CEST)<br />
<br />
<br />
[[User:Specto|Specto]] 20:34, 2 January 2008 (GMT)<br />
<br />
Hi CityK,<br />
<br />
I noticed that you reverted my additions to the "How_to_install_DVB_device_drivers" page of the Linux TV Wiki.<br />
<br />
I just wondered why you decided to do this ?<br />
<br />
Thinking about it in more detail I realise the statements I added might well have been wrong in which case I apologise for polluting otherwise clear instructions.<br />
<br />
I am a bit of a Linux-newbie and was finding with v4l enabled within the kernel (configured from menuconfig) and trying to use the latest v4l sources I received a large number of warnings in dmesg output (something about the kernel defining symbols which the modules did as well).<br />
A reboot did not remove these errors.<br />
I fixed this by disabling v4l in my kernel and rebuilding it before proceeding to the 'make install' phase.<br />
(Drivers for my device already existed within the kernel but I need to use the newer ones which supported the remote control).<br />
<br />
:Hi Spectro ... yes, it was just a case of being that the statements were incorrect -- what you had written shouldn't be necessary, and what is outlined in the Hg instructions is all that is required (make, make install, make unload, modprobe drivers). That said, I believe that there was an error in the driver set from last week or so -- I remember seeing a number of postings on the m/l, and also on the irc channel, about errors similar to the ones you encountered. But that's what you have to expect with the bleeding edge -- from time to time, regressions unfortunately crop up/get introduced. In any regard, I think those problems have likely been amended now. As an aside, when I rolled back the article from your edit to the previous state, I forgot to note a reason (like: "inaccurate statement" or whatever), and hence that's why a comment/explanation is missing in the article's history feature for the rollback or from the wiki's list of "recent changes" feature. --[[User:CityK|CityK]] 17:04, 4 January 2008 (CET)<br />
<br />
<br />
[[User:Bpringlemeir|Bpringlemeir]] 06:26, 27 November 2008 (CET)<br />
<br />
Do you have a place to put module parameters. Ie, proc/module/tuner/parameter/ntsc can be one of M,J,K setting special frequency bands for user in ???, Japan and Korea. Case doesn't matter.<br />
:Hi Bpringlemeir ... Some parameters might already be documented in some of the articles remaining in the old V4L wiki (http://www.linuxtv.org/v4lwiki/index.php/Special:Allpages); perhaps in one of the tuner articles or in the chip interface (i.e. bt878 etc etc) articles. All these articles will be transfered into here in the near future. There are also the duplicate articles for some of the interface chipsets found here, in this wiki.<br />
<br />
<br />
[[User:Howl|howl]] 20:52, 31 December 2008 (CET)<br />
<br />
C'mon man, take a rest, is the last day of the year :)<br />
: Ah, but I had! (The wiki is on Grenwich MT. I'm on -5GMT, so the edits you saw were from the day prior)<br />
<br />
<br />
[[User:Hlangos|Hlangos]] 10:16, 7 April 2009 (CEST)<br />
<br />
Hi there, could you remove DVB-T_USB_Devices_Table ? It doesn't add any information, and the information it duplicates from [[DVB-T_USB_Devices]] is not more readable or more accessible.<br />
: I'll archive the page...its a shame that person elected to create a new page instead of working on the original, as they likely spent some time on it. Oh well.<br />
:: Same goes for [[MSI_Digi_VOX_mini_II_v3.0]] . I Informed the author about [[MSI_DigiVox_mini_II_V3.0]] , asked him to add his information there and to ask one of the wiki admins to remove his new page. pity... --[[User:Hlangos|Hlangos]] 15:07, 13 April 2009 (CEST) <br />
::: Doh! Thanks. I haven't anything from them yet. I'll see about cleaning it up soon, otherwise.--[[User:CityK|CityK]] 04:41, 17 April 2009 (CEST) <br />
<br />
Also, you seem to have removed the DVB_USB page a while back but the Talk:DVB_USB page still exists. It only contains a redirect, but so did DVB_USB. So how about getting rid of that artifact, too?<br />
: DVB_USB got moved to DVB_via_USB. When you use the wiki's "move" feature on an article, the old page automagically gets set up as a redirect to the new page -- similarly with the associated article Talk page. I then deleted the DVB_USB page (as I don't like to have useless redirects cluttering up the wiki's index), but obviously forgot to also delete the Talk:DVB_USB page...its gone now. --[[User:CityK|CityK]] 20:16, 12 April 2009 (CEST)<br />
:: Thanks! BTW: Is there a way to make redirect pages invisible for the index without deleting them? They might still be useful for old links from the outside.. --[[User:Hlangos|Hlangos]] 15:07, 13 April 2009 (CEST)<br />
<br />
<br />
[[User:Howl|howl]] 10:50, 22 September 2009 (UTC)<br />
<br />
Good point putting the web archive page for the [[AF9005]] ;)<br />
<br />
== [[TechniSat AirStar USB / Air2PC DVB USB]] link on [[DVB-T USB Devices]] ==<br />
<br />
A long time ago you added this to the "supported" section:<br />
* [[TechniSat AirStar USB / Air2PC DVB USB]]<br />
The article itself says the device is still not working properly. Can you confirm it is supported? --[[User:Hlangos|Hlangos]] 12:37, 28 April 2009 (CEST)<br />
<br />
:Hi Henrik, I believe that the original device did indeed work (if IIRC, Patrick added suppport for it), but I think that are a couple of different revisions (i.e. differing slightly by tuner and/or demod), and that the later revisions were problematic at some point....I really have no idea otherwise about the current support status<br />
<br />
== Sysop status ==<br />
<br />
Hi,<br />
<br />
Thanks for the extra privileges! I'm pretty much finished with categories; most of the remaining pages are incomplete with regard to their interface and whether they are analogue or digital etc. Is there anything else that needs attention that I could have a look at? I've had a look at your user page and that all seems in hand.<br />
<br />
Hope you're well<br />
<br />
Cheers<br />
<br />
Jim<br />
<br />
:Hi Jim, I'm good (just very busy). Thanks again for the cat. work! A nice little project would be to implement graphical boxes for stub pages or needs expanding etc type features like wikipedia and other wikis employ. Examples:<br />
:http://en.wikipedia.org/wiki/PCIe<br />
:http://en.wikipedia.org/wiki/Template:Ambox<br />
:http://en.wikipedia.org/wiki/Wikipedia:Stub<br />
:--[[User:CityK|CityK]] 02:04, 11 May 2009 (CEST)<br />
<br />
== Help with wiki integration ==<br />
<br />
Hi CityK,<br />
<br />
I've had a quiet week or so on the wiki front. I've been holding out while Henrik gets his ParserFunction project sorted out as I think it will be replicated across the site if all goes well. In the meantime, can I help with the V4L wiki integration? Just let me know if there's anything I can do.<br />
<br />
I've also started to prepare a document showing the current structure and content of LinuxTV.org. I notice in your user page that you have given some consideration to the layout of LinuxTV.org and I think that the site as a whole could use some updating/beautification. I'll start a new page and insert the document into it or something and send you the link. Again, any thought that you have would be gratefully received.<br />
<br />
Cheers<br />
<br />
Jim<br />
<br />
: Hi Jim & CityK, <br />
: Js installed the missing extensions and I've since written a [[Template:Device_List_Low_Detail/Row|template]] for the low detail version of the device table that takes two additional arguments (selectionvalue and selectionattribute) and only displays a row if "selectionvalue" is found in "selectionattribute" of the data that is passed to it. Here are some examples of the usage: [[HLPlayground2#Row_Selections]]. I would be more happy if I had found the time to crunch the different levels of detail that currently are implemented by different templates into one template. It should be relatively easy, now that ParserFunctions are there. I just didn't have the time yet. On the other hand the code will get less and less readable if I do that. So we might as well call it "good enough". Now what needs to be done is <br />
: a) decide which data we want to collect on the devices (this [[Template:USB_Device_Data#Syntax_and_Semantics|list]] is just my proposal)<br />
:: I agree with most of your choices for data to collect. However, there are three areas where I can see some wrangling will be necessary.<br />
::# The support status of the devices. Your suggestion of the status of drivers with regard to the kernel/v4l/experimental/branch/external support takes account of all the possible values at present. However, support for devices also varies according to the level of support and I think it might be prudent to indicate that in the table. As I mentioned before, there could be five different levels of support: not working, partial support for some features, support unknown, most features working or fully supported.<br />
::: Agreed. There needs to be more detailed information on the support for different features. The data about where to find which level of support (vanilla kernel or developer VCS) can be left to the device's page. However I'd like to have one overall "supported" field. Question is: should the field contain the highest level of support available, even if that support is only available for people who compile their own kernel, or should it be the vanilla kernel support of the latest stable kernel? (I am a bit worried about the amount of work this generates.)<br />
::# The use of machine-readable fields. I can see that this might offer the only option bearing in mind the limitations of the wiki backend. However, I wonder how likely it is that two chips will have the same part number from different manufacturers?<br />
::: ''We'' give those names. If a conflict occurs and we need to rename an existing chip, we run a simple search and replace on the existing data and on the pages that do queries with that selectionvalue.<br />
::# The comments field. Given that the table is meant to be a summary of the data available about various devices, is this field really necessary? I can see it being filled with fairly similar comments, which would suggest that another field would be more appropriate. In particular, I think that remote control support would dominate the comments and the addition of a field for remote control status (perhaps using the five-level system I proposed above with the addition of a 'not applicable' value for devices without remotes) might be a good idea. Any informatiive comments beyond this are surely the realm of a device page?<br />
::: Agreed.<br />
: b) to decide on the details that go into the different versions of the table and where to deploy which version (the stuff on [[HLPlayground2#first_scale_try]] is just my first idea) and <br />
::As we discussed before, users can be split into three broad categories depending on their level of tech-savvy. However, their reason for looking on the wiki could be for:<br />
::#Pre-purchase information about devices and support.<br />
::#Post-purchase information about devices and support.<br />
::#Technical background on DTV.<br />
::#Programming information for drivers<br />
::#Programming information for software<br />
::and probably others (please add to this list!!).<br />
::: When talking about the data on devices, we can skip the programmers and concentrate on the less tech-savvy users. They will always be the majority.<br />
::I suppose that the most immediately useful page would be a page of fully supported devices, regardless of the method by which support is offered. This could eventually include devices from all architectures and would fulfil the criteria of 1. above. I think this would probably be the most visited page on the site.<br />
:::Agreed and it can be easily done. Take a look at the "tuner : mt2060 or vendor : TerraTec" table at [[HLPlayground2#Low_Detail_Table_2]]. You can combine data from different sources as long as it arrives in table rows with the right number and order of table cells. This way you don't need to throw all devices into one "database" article. You can keep USB DVB-T devices separate of PCIe DVB-S devices and of PCI Analog-TV devices.<br />
: c) add the data of at least all the devices that are in [[DVB-T_USB_Devices|the old article]] into [[Template:USB_Device_Data|the "database"]].<br />
: cheers -henrik --[[User:Hlangos|Hlangos]] 11:18, 11 June 2009 (UTC)<br />
: PS: Is it a lot of work to set up another mailinglist? One for the linuxtv wiki? (linux-media or linux-dvb are way too noisy) It would help to coordinate and keep people informed without the need to subscribe to those high volume lists.<br />
:: I concur with this idea. I can see that an extra mailing list might well be the way to go.<br />
:: Once again, fine work Henrik. Please let me know what you think of my comments.<br />
:: Cheers<br />
::Jim<br />
::: Maybe we should hijack the linux-media mailing list and flood it with our talk of reoganizing the wiki until ''they'' offer to make a mailinglist for us :-)<br />
<br />
== Files to delete ==<br />
<br />
Hi CityK, there are two image files that aren't needed anymore and can be deleted.<br />
<br />
--[[User:Howl|howl]] 00:40, 1 October 2009 (UTC)<br />
<br />
== New Software to watch Digital TV ==<br />
<br />
Hi, I took a look at the history and it looks like you're one of the main contributors to the page [[TV_Related_Software]] Now, I am the author of a new software to watch digital television on linux, it's open source and it's name is Antenna DTV, website: [http://antenna-dtv.sf.net Antenna DTV]. It's a new project which focuses on the signal, and not only to watching tv alone. Might I add it to the list of software to watch digital tv? Thanks! Any question is welcome!<br />
<br />
::But of course, feel free -- it is, after all, a community wiki ! You could create an article page for the app too --[[User:CityK|CityK]] 07:42, 9 January 2011 (UTC)<br />
<br />
:::: Did it. Hope it fits well. :) [[User:Antoniop|Antoniop]] 22:39, 18 January 2011 (UTC)<br />
<br />
== Spam users in the pipe ==<br />
<br />
Hi there,<br />
I just noticed that we have recently gained a lot of new users with names that seem to indicate German language spam.<br />
<br />
These are the Users and the translation of their names:<br />
<br />
[[User:xAbnehmen]] (lose weight) <br />
[[User:xAnbieterstrom]] (supplier electricity) <br />
[[User:xEnergie]] (energy)<br />
[[User:xFirtenlernen]] (learning to flirt) <br />
[[User:xForexanbieter]] (forex supplier)<br />
[[User:xGastarife]] (gas rates)<br />
[[User:xGasvergleich]] (gas comparison)<br />
[[User:xLottozahlen]] (lottery numbers)<br />
[[User:xNaturstrom]] (nature electricity)<br />
[[User:xOekostrom]] (eco electricity)<br />
[[User:xPreisvergleichstrom]] (price comparison electricity)<br />
[[User:xStrombilliger]] (electricity cheaper)<br />
[[User:xStrompreise]] (electricity prices)<br />
[[User:xVergleichstrom]] (comparison electricity)<br />
[[User:xVersorgerstrom]] (supplier electricity)<br />
<br />
I'd go ahead and simply block those users but I can't figure out why they havn't been used to spam the wiki yet.<br />
Do we have a policy in place that enforces email address verification before allowing edits?<br />
<br />
<br />
BTW: it would have been easier to find those users if the user table could be sorted by creation date but "Sort by creation date" yields the following error on [[Special:ListUsers]] <br />
<br />
A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:<br />
<br />
(SQL query hidden)<br />
<br />
from within function "IndexPager::reallyDoQuery (UsersPager)". Database returned error "1176: Key 'PRIMARY' doesn't exist in table 'user' (localhost)".<br />
<br />
cheers<br />
--[[User:Hlangos|Hlangos]] 19:34, 29 September 2011 (CEST)<br />
<br />
: None of those users did actually do spamming yet. So there's no reason to block them so far. --[[User:Wirbel|wirbel]] 19:51, 29 September 2011 (CEST)<br />
<br />
: The SQL error should be fixed now. --[[User:Js|js]] 00:32, 30 September 2011 (CEST)<br />
<br />
: I hadn't really noticed the German language spam, but that is pretty funny (given the translations, the names that are being used). About a month or so ago, I noticed that the new user spambot pattern seemed to be an English_name-prefix_followed_by_number (e.g. george1107). Anyway, I was thinking that perhaps we should deploy a reCaptcha (http://www.mediawiki.org/wiki/Extension:ReCAPTCHA) for our user registration, though I don't know how useful it would be. I note that the thinkpads forum ( http://www.thinkpads.com/forum/) has one of the more elaborate registrations that I've encountered in attempts to ward off spam... With the point being that spam still gets through--[[User:CityK|CityK]] 04:07, 30 September 2011 (CEST)<br />
<br />
:: @wirbel: True, and if it was a single user I wouldn't even have noticed, but 15 users that just happen to have similarly spamy names?<br />
::: It really looks like preparations/tests for spam, agree. But as users in this wiki can freely choose their login name to whatever they want and no spamming happened so far, i just wanted to remind, that blocking users should be taken into account only if they actively destroy something. reCaptcha or similar is a good idea anyway. --[[User:Wirbel|wirbel]] 18:25, 30 September 2011 (CEST)<br />
<br />
:: @js: Thanks! Works like a charm now!<br />
<br />
:: @CityK: The translations are literal. ''Most'' of the names are perfectly OK in German. You can stick word together like "chicken" and "soup" to make "chickensoup" (a soup with chicken) or "soupchicken" (a chicken destined for ending up in a soup). Some of the user names however don't ''work''. E.g. ''Stromanbieter'' is a common word for your electricity supplier while ''Anbieterstrom'' would describe the electricity that comes from a supplier, and doesn't make much sense. I was a big fan of recaptcha, before they were bought by that one big company that is giving M$ a run for its money in the evil empire contest. Nowadays their privacy policy reads like a joke:<br />
We log information related to reCAPTCHA, such as the Internet Protocol address of the end-user,<br />
an identifier for the implementing site, the URL of the site accessed,<br />
the CAPTCHA solution, the result of the CAPTCHA grading, the date and time of requests,<br />
and one or more cookies that may uniquely identify the end-user browser.<br />
In our logs, we will delete any information that identifies the individual URLs<br />
within the implementing site within 30 days of the event logged.<br />
:: The cookies are particularly evil as they allow them to follow your surfing habit across every site that happens to show a recaptcha. (You don't even have to solve that captcha. Just downloading the captcha image will tell them which page you have been looking at, from which IP at which time and so on...<br />
:: There are [http://www.sitepoint.com/captcha-problems-alternatives/ alternatives] to recaptcha but we also need to consider what we spend our time on, and if recaptcha is available and installable here without much fuzz, Using recaptcha may be ok for the sign-on process but I'd rather not have it pop up every now and then. cheers --[[User:Hlangos|Hlangos]] 12:18, 30 September 2011 (CEST)<br />
<br />
::: Thanks for all the info Hlangos. Looks like one of our German spambots got through tonight. I'll leave it up right now for you guys to have a look-see. I was unaware of the reCaptcha stuff ... I note that when I read your remark about them being bought by a member of the "evil empire" club, I was expecting it was to have been Apple :P (Google hasn't offended me too much yet, but they are definitely on my watchlist). Yeah, I was just thinking of having something on registration only. I don't know what JS thinks would be the best solution to implement, or if he has other feelings about it. --[[User:CityK|CityK]] 05:50, 1 October 2011 (CEST)<br />
<br />
Hey CityK, your mail bounces. Please contact me. --[[User:Js|js]] 22:08, 2 October 2011 (CEST)</div>Jshttps://www.linuxtv.org/wiki/index.php?title=User_talk:CityK&diff=29609User talk:CityK2011-09-29T22:32:03Z<p>Js: </p>
<hr />
<div>[[User:CityK|CityK]] 19:46, 3 February 2007 (CET)<br />
<br />
Spent a bunch of time last night and this morning creating and rearranging ATSC devices stuff.<br />
There is a LOT of work that could be done.<br />
<br />
<br />
[[User:CityK|CityK]] 01:02, 5 February 2007 (CET)<br />
<br />
I got to find a WYSIWYG wiki editor, else using code takes me ages<br />
<br />
<br />
[[User:CityK|CityK]] 08:23, 7 February 2007 (CET)<br />
<br />
made a mess of the categories tonight ... will clean that whole thing up soon.<br />
Started with the renaming and relinking of the DVB pages ... a lot more work than I thought. Oh well, it will be nice to have a consistant look and nomenclature across the board.<br />
<br />
Definitely several months of work to get this thing ship shape!<br />
<br />
<br />
[[User:JGXenite|JGXenite]] 14:25, 20 April 2007 (CEST)<br />
<br />
Hi CityK,<br />
<br />
Sorry about that :(. I'll make my changes to Mplayer now.<br />
<br />
<br />
[[User:JGXenite|JGXenite]] 14:56, 21 April 2007 (CEST)<br />
<br />
No worries with the countries thing - I thought it would make more sense moving it to channels.conf, as that is the correct file name. I then decided to make a "Europe" sub-category as there were quite a few European entries. I've also contributed one for United Kingdom (Sheffield) detailing my experience with setting it up :).<br />
<br />
<br />
[[User:Howl|howl]] 00:01, 27 July 2007 (CEST)<br />
<br />
I like the look of the page that you purpose and also i think that this can benefit a lot for people who only want information, actual desing is more confuse.<br />
<br />
: Thanks Howl. If you did not see the message previously, here is a (more-or-less) recent status report: http://www.linuxtv.org/pipermail/linux-dvb/2007-June/018429.html --[[User:CityK|CityK]] 07:03, 27 July 2007 (CEST)<br />
<br />
:: I like a lot the idea and also the Nick Andrew's one in the reply of making a database. I don't know if there is a system to integrate a SQL db style like MySQL in wiki but if it exists it could be a powerful tool that will help to test different templates for the devices pages making the data independient of the style. --[[User:Howl|howl]] 01:08, 30 July 2007 (CEST)<br />
<br />
:::I do too, but I have no idea (or time to investigate, let alone implement) about a db in a wiki ... maybe in the future --[[User:CityK|CityK]] 19:14, 30 July 2007 (CEST)<br />
<br />
<br />
[[User:Specto|Specto]] 20:34, 2 January 2008 (GMT)<br />
<br />
Hi CityK,<br />
<br />
I noticed that you reverted my additions to the "How_to_install_DVB_device_drivers" page of the Linux TV Wiki.<br />
<br />
I just wondered why you decided to do this ?<br />
<br />
Thinking about it in more detail I realise the statements I added might well have been wrong in which case I apologise for polluting otherwise clear instructions.<br />
<br />
I am a bit of a Linux-newbie and was finding with v4l enabled within the kernel (configured from menuconfig) and trying to use the latest v4l sources I received a large number of warnings in dmesg output (something about the kernel defining symbols which the modules did as well).<br />
A reboot did not remove these errors.<br />
I fixed this by disabling v4l in my kernel and rebuilding it before proceeding to the 'make install' phase.<br />
(Drivers for my device already existed within the kernel but I need to use the newer ones which supported the remote control).<br />
<br />
:Hi Spectro ... yes, it was just a case of being that the statements were incorrect -- what you had written shouldn't be necessary, and what is outlined in the Hg instructions is all that is required (make, make install, make unload, modprobe drivers). That said, I believe that there was an error in the driver set from last week or so -- I remember seeing a number of postings on the m/l, and also on the irc channel, about errors similar to the ones you encountered. But that's what you have to expect with the bleeding edge -- from time to time, regressions unfortunately crop up/get introduced. In any regard, I think those problems have likely been amended now. As an aside, when I rolled back the article from your edit to the previous state, I forgot to note a reason (like: "inaccurate statement" or whatever), and hence that's why a comment/explanation is missing in the article's history feature for the rollback or from the wiki's list of "recent changes" feature. --[[User:CityK|CityK]] 17:04, 4 January 2008 (CET)<br />
<br />
<br />
[[User:Bpringlemeir|Bpringlemeir]] 06:26, 27 November 2008 (CET)<br />
<br />
Do you have a place to put module parameters. Ie, proc/module/tuner/parameter/ntsc can be one of M,J,K setting special frequency bands for user in ???, Japan and Korea. Case doesn't matter.<br />
:Hi Bpringlemeir ... Some parameters might already be documented in some of the articles remaining in the old V4L wiki (http://www.linuxtv.org/v4lwiki/index.php/Special:Allpages); perhaps in one of the tuner articles or in the chip interface (i.e. bt878 etc etc) articles. All these articles will be transfered into here in the near future. There are also the duplicate articles for some of the interface chipsets found here, in this wiki.<br />
<br />
<br />
[[User:Howl|howl]] 20:52, 31 December 2008 (CET)<br />
<br />
C'mon man, take a rest, is the last day of the year :)<br />
: Ah, but I had! (The wiki is on Grenwich MT. I'm on -5GMT, so the edits you saw were from the day prior)<br />
<br />
<br />
[[User:Hlangos|Hlangos]] 10:16, 7 April 2009 (CEST)<br />
<br />
Hi there, could you remove DVB-T_USB_Devices_Table ? It doesn't add any information, and the information it duplicates from [[DVB-T_USB_Devices]] is not more readable or more accessible.<br />
: I'll archive the page...its a shame that person elected to create a new page instead of working on the original, as they likely spent some time on it. Oh well.<br />
:: Same goes for [[MSI_Digi_VOX_mini_II_v3.0]] . I Informed the author about [[MSI_DigiVox_mini_II_V3.0]] , asked him to add his information there and to ask one of the wiki admins to remove his new page. pity... --[[User:Hlangos|Hlangos]] 15:07, 13 April 2009 (CEST) <br />
::: Doh! Thanks. I haven't anything from them yet. I'll see about cleaning it up soon, otherwise.--[[User:CityK|CityK]] 04:41, 17 April 2009 (CEST) <br />
<br />
Also, you seem to have removed the DVB_USB page a while back but the Talk:DVB_USB page still exists. It only contains a redirect, but so did DVB_USB. So how about getting rid of that artifact, too?<br />
: DVB_USB got moved to DVB_via_USB. When you use the wiki's "move" feature on an article, the old page automagically gets set up as a redirect to the new page -- similarly with the associated article Talk page. I then deleted the DVB_USB page (as I don't like to have useless redirects cluttering up the wiki's index), but obviously forgot to also delete the Talk:DVB_USB page...its gone now. --[[User:CityK|CityK]] 20:16, 12 April 2009 (CEST)<br />
:: Thanks! BTW: Is there a way to make redirect pages invisible for the index without deleting them? They might still be useful for old links from the outside.. --[[User:Hlangos|Hlangos]] 15:07, 13 April 2009 (CEST)<br />
<br />
<br />
[[User:Howl|howl]] 10:50, 22 September 2009 (UTC)<br />
<br />
Good point putting the web archive page for the [[AF9005]] ;)<br />
<br />
== [[TechniSat AirStar USB / Air2PC DVB USB]] link on [[DVB-T USB Devices]] ==<br />
<br />
A long time ago you added this to the "supported" section:<br />
* [[TechniSat AirStar USB / Air2PC DVB USB]]<br />
The article itself says the device is still not working properly. Can you confirm it is supported? --[[User:Hlangos|Hlangos]] 12:37, 28 April 2009 (CEST)<br />
<br />
:Hi Henrik, I believe that the original device did indeed work (if IIRC, Patrick added suppport for it), but I think that are a couple of different revisions (i.e. differing slightly by tuner and/or demod), and that the later revisions were problematic at some point....I really have no idea otherwise about the current support status<br />
<br />
== Sysop status ==<br />
<br />
Hi,<br />
<br />
Thanks for the extra privileges! I'm pretty much finished with categories; most of the remaining pages are incomplete with regard to their interface and whether they are analogue or digital etc. Is there anything else that needs attention that I could have a look at? I've had a look at your user page and that all seems in hand.<br />
<br />
Hope you're well<br />
<br />
Cheers<br />
<br />
Jim<br />
<br />
:Hi Jim, I'm good (just very busy). Thanks again for the cat. work! A nice little project would be to implement graphical boxes for stub pages or needs expanding etc type features like wikipedia and other wikis employ. Examples:<br />
:http://en.wikipedia.org/wiki/PCIe<br />
:http://en.wikipedia.org/wiki/Template:Ambox<br />
:http://en.wikipedia.org/wiki/Wikipedia:Stub<br />
:--[[User:CityK|CityK]] 02:04, 11 May 2009 (CEST)<br />
<br />
== Help with wiki integration ==<br />
<br />
Hi CityK,<br />
<br />
I've had a quiet week or so on the wiki front. I've been holding out while Henrik gets his ParserFunction project sorted out as I think it will be replicated across the site if all goes well. In the meantime, can I help with the V4L wiki integration? Just let me know if there's anything I can do.<br />
<br />
I've also started to prepare a document showing the current structure and content of LinuxTV.org. I notice in your user page that you have given some consideration to the layout of LinuxTV.org and I think that the site as a whole could use some updating/beautification. I'll start a new page and insert the document into it or something and send you the link. Again, any thought that you have would be gratefully received.<br />
<br />
Cheers<br />
<br />
Jim<br />
<br />
: Hi Jim & CityK, <br />
: Js installed the missing extensions and I've since written a [[Template:Device_List_Low_Detail/Row|template]] for the low detail version of the device table that takes two additional arguments (selectionvalue and selectionattribute) and only displays a row if "selectionvalue" is found in "selectionattribute" of the data that is passed to it. Here are some examples of the usage: [[HLPlayground2#Row_Selections]]. I would be more happy if I had found the time to crunch the different levels of detail that currently are implemented by different templates into one template. It should be relatively easy, now that ParserFunctions are there. I just didn't have the time yet. On the other hand the code will get less and less readable if I do that. So we might as well call it "good enough". Now what needs to be done is <br />
: a) decide which data we want to collect on the devices (this [[Template:USB_Device_Data#Syntax_and_Semantics|list]] is just my proposal)<br />
:: I agree with most of your choices for data to collect. However, there are three areas where I can see some wrangling will be necessary.<br />
::# The support status of the devices. Your suggestion of the status of drivers with regard to the kernel/v4l/experimental/branch/external support takes account of all the possible values at present. However, support for devices also varies according to the level of support and I think it might be prudent to indicate that in the table. As I mentioned before, there could be five different levels of support: not working, partial support for some features, support unknown, most features working or fully supported.<br />
::: Agreed. There needs to be more detailed information on the support for different features. The data about where to find which level of support (vanilla kernel or developer VCS) can be left to the device's page. However I'd like to have one overall "supported" field. Question is: should the field contain the highest level of support available, even if that support is only available for people who compile their own kernel, or should it be the vanilla kernel support of the latest stable kernel? (I am a bit worried about the amount of work this generates.)<br />
::# The use of machine-readable fields. I can see that this might offer the only option bearing in mind the limitations of the wiki backend. However, I wonder how likely it is that two chips will have the same part number from different manufacturers?<br />
::: ''We'' give those names. If a conflict occurs and we need to rename an existing chip, we run a simple search and replace on the existing data and on the pages that do queries with that selectionvalue.<br />
::# The comments field. Given that the table is meant to be a summary of the data available about various devices, is this field really necessary? I can see it being filled with fairly similar comments, which would suggest that another field would be more appropriate. In particular, I think that remote control support would dominate the comments and the addition of a field for remote control status (perhaps using the five-level system I proposed above with the addition of a 'not applicable' value for devices without remotes) might be a good idea. Any informatiive comments beyond this are surely the realm of a device page?<br />
::: Agreed.<br />
: b) to decide on the details that go into the different versions of the table and where to deploy which version (the stuff on [[HLPlayground2#first_scale_try]] is just my first idea) and <br />
::As we discussed before, users can be split into three broad categories depending on their level of tech-savvy. However, their reason for looking on the wiki could be for:<br />
::#Pre-purchase information about devices and support.<br />
::#Post-purchase information about devices and support.<br />
::#Technical background on DTV.<br />
::#Programming information for drivers<br />
::#Programming information for software<br />
::and probably others (please add to this list!!).<br />
::: When talking about the data on devices, we can skip the programmers and concentrate on the less tech-savvy users. They will always be the majority.<br />
::I suppose that the most immediately useful page would be a page of fully supported devices, regardless of the method by which support is offered. This could eventually include devices from all architectures and would fulfil the criteria of 1. above. I think this would probably be the most visited page on the site.<br />
:::Agreed and it can be easily done. Take a look at the "tuner : mt2060 or vendor : TerraTec" table at [[HLPlayground2#Low_Detail_Table_2]]. You can combine data from different sources as long as it arrives in table rows with the right number and order of table cells. This way you don't need to throw all devices into one "database" article. You can keep USB DVB-T devices separate of PCIe DVB-S devices and of PCI Analog-TV devices.<br />
: c) add the data of at least all the devices that are in [[DVB-T_USB_Devices|the old article]] into [[Template:USB_Device_Data|the "database"]].<br />
: cheers -henrik --[[User:Hlangos|Hlangos]] 11:18, 11 June 2009 (UTC)<br />
: PS: Is it a lot of work to set up another mailinglist? One for the linuxtv wiki? (linux-media or linux-dvb are way too noisy) It would help to coordinate and keep people informed without the need to subscribe to those high volume lists.<br />
:: I concur with this idea. I can see that an extra mailing list might well be the way to go.<br />
:: Once again, fine work Henrik. Please let me know what you think of my comments.<br />
:: Cheers<br />
::Jim<br />
::: Maybe we should hijack the linux-media mailing list and flood it with our talk of reoganizing the wiki until ''they'' offer to make a mailinglist for us :-)<br />
<br />
== Files to delete ==<br />
<br />
Hi CityK, there are two image files that aren't needed anymore and can be deleted.<br />
<br />
--[[User:Howl|howl]] 00:40, 1 October 2009 (UTC)<br />
<br />
== New Software to watch Digital TV ==<br />
<br />
Hi, I took a look at the history and it looks like you're one of the main contributors to the page [[TV_Related_Software]] Now, I am the author of a new software to watch digital television on linux, it's open source and it's name is Antenna DTV, website: [http://antenna-dtv.sf.net Antenna DTV]. It's a new project which focuses on the signal, and not only to watching tv alone. Might I add it to the list of software to watch digital tv? Thanks! Any question is welcome!<br />
<br />
::But of course, feel free -- it is, after all, a community wiki ! You could create an article page for the app too --[[User:CityK|CityK]] 07:42, 9 January 2011 (UTC)<br />
<br />
:::: Did it. Hope it fits well. :) [[User:Antoniop|Antoniop]] 22:39, 18 January 2011 (UTC)<br />
<br />
== Spam users in the pipe ==<br />
<br />
Hi there,<br />
I just noticed that we have recently gained a lot of new users with names that seem to indicate German language spam.<br />
<br />
These are the Users and the translation of their names:<br />
<br />
[[User:Abnehmen]] (lose weight) <br />
[[User:Anbieterstrom]] (supplier electricity) <br />
[[User:Energie]] (energy)<br />
[[User:Firtenlernen]] (learning to flirt) <br />
[[User:Forexanbieter]] (forex supplier)<br />
[[User:Gastarife]] (gas rates)<br />
[[User:Gasvergleich]] (gas comparison)<br />
[[User:Lottozahlen]] (lottery numbers)<br />
[[User:Naturstrom]] (nature electricity)<br />
[[User:Oekostrom]] (eco electricity)<br />
[[User:Preisvergleichstrom]] (price comparison electricity)<br />
[[User:Strombilliger]] (electricity cheaper)<br />
[[User:Strompreise]] (electricity prices)<br />
[[User:Vergleichstrom]] (comparison electricity)<br />
[[User:Versorgerstrom]] (supplier electricity)<br />
<br />
I'd go ahead and simply block those users but I can't figure out why they havn't been used to spam the wiki yet.<br />
Do we have a policy in place that enforces email address verification before allowing edits?<br />
<br />
<br />
BTW: it would have been easier to find those users if the user table could be sorted by creation date but "Sort by creation date" yields the following error on [[Special:ListUsers]] <br />
<br />
A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:<br />
<br />
(SQL query hidden)<br />
<br />
from within function "IndexPager::reallyDoQuery (UsersPager)". Database returned error "1176: Key 'PRIMARY' doesn't exist in table 'user' (localhost)".<br />
<br />
cheers<br />
--[[User:Hlangos|Hlangos]] 19:34, 29 September 2011 (CEST)<br />
<br />
: None of those users did actually do spamming yet. So there's no reason to block them so far. --[[User:Wirbel|wirbel]] 19:51, 29 September 2011 (CEST)<br />
<br />
: The SQL error should be fixed now. --[[User:Js|js]] 00:32, 30 September 2011 (CEST)</div>Jshttps://www.linuxtv.org/wiki/index.php?title=TeVii_S480&diff=29533TeVii S4802011-09-18T08:28:56Z<p>Js: Reverted edits by Yilin168 (talk) to last revision by Torsten73</p>
<hr />
<div>[[Image:S480.jpg|thumb|right|200px|TeVii S480 Card]]<br />
A dual DVB-S2 PCIe card from [[TeVii]].<br />
<br />
==Hardware/Features==<br />
* PCIe x1 low profile<br />
* Dual Tuner<br />
* The card consists of a USB Host Controller and two [[TeVii S660]] equivalent cards.<br />
* LNB power supply via floppy connector<br />
<br />
The Retail packaging includes full-height and low profile brackets, an IR receiver cable, an IR handset (incl. 2 AAA batteries), a windows drivers CD and an install manual. <br />
<br />
===Components Used===<br />
* RF Tuner (twice): [[Montage]] [[Montage M88TS2020|M88TS2020]]<br />
* Demodulator (twice): [[Montage]] [[Montage M88DS3000|M88DS3002]]<br />
* USB Peripheral Controller (twice): Cypress CY7C68013A-56<br />
* PCIe bridge/USB Host Controller: MosChip MCS9990CV<br />
<br />
===Identification===<br />
lspci -nnk:<br />
04:00.0 USB Controller [0c03]: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0 Host Controller [9710:9990]<br />
Subsystem: Device [a000:4000]<br />
Kernel driver in use: ohci_hcd<br />
04:00.1 USB Controller [0c03]: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0 Host Controller [9710:9990]<br />
Subsystem: Device [a000:4000]<br />
Kernel driver in use: ehci_hcd<br />
04:00.2 USB Controller [0c03]: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0 Host Controller [9710:9990]<br />
Subsystem: Device [a000:4000]<br />
Kernel driver in use: ohci_hcd<br />
04:00.3 USB Controller [0c03]: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0 Host Controller [9710:9990]<br />
Subsystem: Device [a000:4000]<br />
Kernel driver in use: ehci_hcd<br />
04:00.4 USB Controller [0c03]: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0 Host Controller [9710:9990]<br />
Subsystem: Device [a000:4000]<br />
Kernel driver in use: ohci_hcd<br />
04:00.5 USB Controller [0c03]: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0 Host Controller [9710:9990]<br />
Subsystem: Device [a000:4000]<br />
Kernel driver in use: ehci_hcd<br />
04:00.6 USB Controller [0c03]: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0 Host Controller [9710:9990]<br />
Subsystem: Device [a000:4000]<br />
Kernel driver in use: ohci_hcd<br />
04:00.7 USB Controller [0c03]: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0 Host Controller [9710:9990]<br />
Subsystem: Device [a000:4000]<br />
Kernel driver in use: ehci_hcd<br />
<br />
lsusb:<br />
Bus 003 Device 002: ID 9022:d482 TeVii Technology Ltd. <br />
Bus 002 Device 002: ID 9022:d481 TeVii Technology Ltd.<br />
<br />
Once the module/firmware is loaded it's listed as two TeVii S660 cards.<br />
<br />
== Linux support ==<br />
The [[s2-liplianin]] v4l branch includes support for the card.<br />
<br />
From kernel 2.6.39 and above native support will be provided for the S480 Card.<br />
<br />
== Howto compile ==<br />
# these lines are only nessesary for building new version<br />
<br />
# cd /usr/local/src/s2-liplianin <br />
# make distclean <br />
# make rminstall<br />
cd /usr/local/src<br />
# rm -r s2-liplianin.BAK<br />
# mv s2-liplianin s2-liplianin.BAK<br />
hg clone http://mercurial.intuxication.org/hg/s2-liplianin<br />
cd s2-liplianin<br />
make KERNELRELEASE=$(uname -r) -i -j4<br />
make KERNELRELEASE=$(uname -r) install<br />
make makelinks<br />
reboot<br />
<br />
The yavdr ppa has also a dkms driver for liplianin. Its not up to date but in a few days it should ;)<br />
<br />
You must confirm to use the correct firmware from Tevii [http://www.tevii.com/s2_liplianin_1.tar], wich normally is automatically installed by the driver:<br />
md5sum dvb-usb-s660.fw*<br />
c359c7616f8dc637db49c5c9fb6c8a41 dvb-usb-s660.fw<br />
c359c7616f8dc637db49c5c9fb6c8a41 dvb-usb-s660.fw.forum<br />
2946e99fe3a4973ba905fcf59111cf40 dvb-usb-s660.fw.keep<br />
<br />
We normally needs the last one dvb-usb-S660.fw.keep<br />
If there are different firmwares, try this way:<br />
<br />
cd /usr/local/src<br />
wget http://www.tevii.com/s2_liplianin_1.tar<br />
tar xvf s2_liplianin_1.tar<br />
cd tevii_s2_liplianin-eb8a914cd499/linux/firmware/<br />
md5sum dvb-usb-s660.fw<br />
#2946e99fe3a4973ba905fcf59111cf40 dvb-usb-s660.fw<br />
cp dvb-usb-s660.fw /lib/firmware/<br />
<br />
== Driver Status ==<br />
27.02.2011 with actual liplianin tree from 27.02.2011:<br />
* DVB-S is working fine with fast zappings around 1s<br />
* DVB-S2 is working fine with fast zappings arround 1-2s<br />
* S3 is working, you have to unload/load dvb modules for the suspend and wakeup<br />
* without LNB Power the card uses 4,5W more with a 300W 82% powersupply BQT-L7 300W<br />
<br />
* everything is tested on Astra 19.2E, diseque hasn´t been tested yet with the latest source<br />
* tested with Kernel 2.6.32-28 (Torsten73) and 2.6.35 (Igor himself)<br />
* tested with Kernel 3.0.3 (Torsten73) for working without v4l or s2-liplianin<br />
<br />
==External Links==<br />
[http://www.tevii.com/Products_S480_1.asp Official Website]<br />
[http://www.vdrportal.de/board/thread.php?threadid=102390&threadview=0&hilight=&hilightuser=0&page=1 technical discussion on vdrportal in german]<br />
<br />
[[Category:DVB-S PCIe Cards]]<br />
[[Category:DVB-S2 PCIe Cards]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Wiki_-_New_Device_Copy_%26_Paste_Template&diff=29503Wiki - New Device Copy & Paste Template2011-09-05T21:33:13Z<p>Js: restore after bad move</p>
<hr />
<div>{{Note|In essence, this page is a "copy and paste" template which users should use when establishing a new device article within the wiki. Its intended purpose is to serve as the basis for the format/layout of device articles; thereby striving to establish a general consistency throughout the wiki.<br />
<br />
Usage:<br />
* Once you have logged in, simply click the edit tab at the top of this page<br />
* Then from within the editing box at the bottom of the editing page, copy the entire contents of this article<br />
* 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" <br />
* 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)}} <br />
<br />
''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:''<br /><br />
<br />
[[Image:Kworld_ATSC_115_front.jpg|right|thumb|200px|Example Image: Add a good overall image of what the device looks like here and perhaps a very brief description]]<br />
<br />
An [[ATSC]] [[ATSC PCI cards]] from [[KWORLD]]. <br />
<br />
The ATSC 115 is supported under Linux since kernel 2.6.24.<br />
<br />
''Note: The page contents menu will automagically build itself, so you need not worry about it''<br />
<br />
==Overview/Features==<br />
''Discuss the features and facets of the device here. For example:''<br><br />
<br />
* PCI interface<br />
* Inputs: Antenna (Composite), Remote and S-Video In <br />
<br />
===Components Used===<br />
''List the hardware ICs and modules used by the device here. For example:''<br><br />
* [[Quantek QT1010]] (tuner)<br />
* [[Zarlink MT352|Intel/Zarlink MT352]] (demodulator)<br />
* [[Philips SAA7134|NXP/Philips SAA7130HL]] (A/V decoder and PCI Interface)<br />
<br />
===Other Images===<br />
''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:''<br><br />
<gallery perrow=5><br />
Image:VideoMate_DVB-T220_box.jpg|VideoMate DVB-T220 Box<br />
Image:VideoMate_DVB-T220_remote.jpg|VideoMate DVB-T220 Remote<br />
</gallery><br />
<br />
===Identification===<br />
''Provide here, for PCI/PCIe devices, the relevant output of <code>lspci -vnn</code> or, in the case of USB devices, <code>lsusb -v </code>. 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:''<br><br />
# lspci -vvvnn<br />
04:03.0 Multimedia controller [0480]: Philips Semiconductors SAA7130 Video Broadcast Decoder [1131:7130] (rev 01)<br />
Subsystem: Compro Technology, Inc. Videomate DVB-T200 [185b:c901]<br />
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-<br />
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-<br />
Latency: 84 (21000ns min, 8000ns max)<br />
Interrupt: pin A routed to IRQ 20<br />
Region 0: Memory at fdcfe000 (32-bit, non-prefetchable) [size=1K]<br />
Capabilities: [40] Power Management version 1<br />
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)<br />
Status: D0 PME-Enable- DSel=0 DScale=1 PME-<br />
<br />
==Making it Work==<br />
''Is it supported under Linux? Are there experimental drivers? Does it partially work or identify as another card? (if yes, add this information below)''<br />
<br />
===Firmware===<br />
''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.''<br />
<br />
===Drivers===<br />
''Provide the details of where the drivers and patches and necessary tools are available.''<br />
<br />
===Sample Kernel Output===<br />
''Provide the '''relevant''' portion of dmesg here. For example:''<br><br />
# dmesg<br />
[ 45.569669] saa7130/34: v4l2 driver version 0.2.14 loaded<br />
[ 45.569739] saa7130[0]: found at 0000:04:03.0, rev: 1, irq: 20, latency: 84, mmio: 0xfdcfe000<br />
[ 45.569745] saa7130[0]: subsystem: 185b:c901, board: Compro Videomate DVB-T200 [card=71,autodetected]<br />
[ 45.569753] saa7130[0]: board init: gpio is 843f00<br />
[ 45.569809] input: saa7134 IR (Compro Videomate DV as /devices/pci0000:00/0000:00:1e.0/0000:04:03.0/input/input7<br />
[ 45.755429] saa7130[0]: i2c eeprom 00: 5b 18 01 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92<br />
[ 45.755437] saa7130[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff<br />
[ 45.755443] saa7130[0]: i2c eeprom 20: 01 40 01 03 03 ff 03 01 08 ff 00 88 ff ff ff ff<br />
[ 45.755449] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff<br />
[ 45.755454] saa7130[0]: i2c eeprom 40: ff d5 00 c4 86 1e ff ff ff ff ff ff ff ff ff ff<br />
[ 45.755460] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb<br />
[ 45.755466] saa7130[0]: i2c eeprom 60: 30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff<br />
[ 45.755471] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff<br />
[ 45.755478] saa7130[0]: Unexpected tuner type info: d5 in eeprom<br />
[ 45.755532] saa7130[0]: registered device video0 [v4l2]<br />
[ 45.755550] saa7130[0]: registered device vbi0<br />
[ 45.873425] saa7134 ALSA driver for DMA sound loaded<br />
[ 45.873448] saa7130[0]/alsa: saa7130[0] at 0xfdcfe000 irq 20 registered as card -2<br />
[ 45.943354] saa7130[0]/dvb: frontend initialization failed<br />
<br />
===Remote Control Support===<br />
''Discuss support for the remote control here.''<br />
<br />
==External Links==<br />
''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:''<br><br />
* [http://www.comprousa.com/en/product/t100t220/t220.html Compro T-220 product page]<br />
<br />
<br />
''Finally, add anything else that you think might be relevant under an appropriate heading.''<br />
<br />
''Very last thing is add a catergory. (Remove the nowiki tags). For example''<br><br />
<nowiki>[[Category:DVB-T PCI Devices]]</nowiki></div>Jshttps://www.linuxtv.org/wiki/index.php?title=TBS5980_(aka_TBS_Qbox_CI)&diff=29493TBS5980 (aka TBS Qbox CI)2011-09-03T20:47:07Z<p>Js: revert spam</p>
<hr />
<div>The Qbox DVB-S2 CI USB2.0, as the name suggests, is a [[DVB-S2]] [[DVB-S2_USB_Devices|USB 2.0]] adapter from [http://www.tbsdtv.com/ TurboSight]. It has been on the market since early 2011. The company has no distribution network, but their products can be ordered online. Shipping of my device to Western Europe took less than three days.<br />
<br />
The Qbox DVB-S2 CI is supported under Linux. The minimum required kernel version is (yet) unknown, the driver requires DVB version 5.1.<br />
<br />
[[Image:Qbox_red.jpg|right|thumb|200px|The Qbox CI switched on. The CAM module has not been inserted]]<br />
<br />
==Overview/Features==<br />
<br />
* USB 2.0 interface (B-connector)<br />
* Inputs: Antenna (F-connector), remote and CI-slot <br />
* Separate power supply: 7.5V, 3.5A<br />
* Indication LED, mostly red, sometimes blue, meaning yet unknown.<br />
<br />
===Components Used===<br />
* [[STMicroelectronics STB6100]] (tuner)<br />
* [[STMicroelectronics STV0903]] (demodulator)<br />
<br />
===Other Images===<br />
<gallery perrow=4><br />
Image:Qbox_blue.jpg|Qbox with LED turned blue<br />
Image:Qbox_CAM.jpg|Qbox with astoncrypt CAM<br />
Image:Qbox_remote.jpg|Qbox remote control<br />
Image:Qbox_package.jpg|Qbox package<br />
</gallery><br />
<br />
===Identification===<br />
lsusb output: <br />
# lsusb -v<br />
Bus 001 Device 009: ID 734c:5980 TBS Technologies China <br />
Device Descriptor:<br />
bLength 18<br />
bDescriptorType 1<br />
bcdUSB 2.00<br />
bDeviceClass 0 (Defined at Interface level)<br />
bDeviceSubClass 0 <br />
bDeviceProtocol 0 <br />
bMaxPacketSize0 64<br />
idVendor 0x734c TBS Technologies China<br />
idProduct 0x5980 <br />
bcdDevice 0.00<br />
iManufacturer 1 TBS-Tech<br />
iProduct 2 DVBS2BOX<br />
iSerial 0 <br />
bNumConfigurations 1<br />
Configuration Descriptor:<br />
bLength 9<br />
bDescriptorType 2<br />
wTotalLength 32<br />
bNumInterfaces 1<br />
bConfigurationValue 1<br />
iConfiguration 0 <br />
bmAttributes 0x80<br />
(Bus Powered)<br />
MaxPower 100mA<br />
Interface Descriptor:<br />
bLength 9<br />
bDescriptorType 4<br />
bInterfaceNumber 0<br />
bAlternateSetting 0<br />
bNumEndpoints 2<br />
bInterfaceClass 255 Vendor Specific Class<br />
bInterfaceSubClass 0 <br />
bInterfaceProtocol 0 <br />
iInterface 0 <br />
Endpoint Descriptor:<br />
bLength 7<br />
bDescriptorType 5<br />
bEndpointAddress 0x82 EP 2 IN<br />
bmAttributes 2<br />
Transfer Type Bulk<br />
Synch Type None<br />
Usage Type Data<br />
wMaxPacketSize 0x0200 1x 512 bytes<br />
bInterval 1<br />
Endpoint Descriptor:<br />
bLength 7<br />
bDescriptorType 5<br />
bEndpointAddress 0x81 EP 1 IN<br />
bmAttributes 2<br />
Transfer Type Bulk<br />
Synch Type None<br />
Usage Type Data<br />
wMaxPacketSize 0x0200 1x 512 bytes<br />
bInterval 0<br />
Device Qualifier (for other device speed):<br />
bLength 10<br />
bDescriptorType 6<br />
bcdUSB 2.00<br />
bDeviceClass 0 (Defined at Interface level)<br />
bDeviceSubClass 0 <br />
bDeviceProtocol 0 <br />
bMaxPacketSize0 64<br />
bNumConfigurations 1<br />
Device Status: 0x0000<br />
(Bus Powered)<br />
<br />
==Making it Work==<br />
The device is actively supported to run under Linux. Every few months the driver gets updated, and the company actively supports users through a forum.<br />
By downloading, compiling and installing the drivers and firmware, the device works (at least, in my distro, Fedora 14 x86-64). Together with the manufacturer-supplied source code for scanning and zapping (slightly modified versions of scan-s2 and szap-s2) DVB-S2 reception works. Newer versions of szap and scan work just as well.<br />
<br />
===Firmware===<br />
The driver software package contains the firmware file: dvb-usb-tbsqbox-id5980.fw. Just install it in /lib/firmware.<br />
<br />
===Drivers===<br />
Available [http://www.tbsdtv.com/english/Download.html here]. Look for the TBS5980 driver. Latest update: july 10. Apart from the firmware file, there is no closed-source object code included in the software. All code has been released under GPLv2.<br />
<br />
===Sample Kernel Output===<br />
The kernel outputs the information below, CAM module inserted (with module verbosity wide open):<br />
# dmesg<br />
[18814.387092] usb 1-7: new high speed USB device using ehci_hcd and address 9<br />
[18814.502322] usb 1-7: New USB device found, idVendor=734c, idProduct=5980<br />
[18814.502334] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=0<br />
[18814.502343] usb 1-7: Product: DVBS2BOX<br />
[18814.502349] usb 1-7: Manufacturer: TBS-Tech<br />
[18814.684522] dvb-usb: found a 'TBS Qbox DVB-S2 CI USB2.0' in cold state, will try to load a firmware<br />
[18814.688745] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5980.fw'<br />
[18814.691532] tbsqbox2ci: start downloading TBSQBOX2CI firmware<br />
[18814.810199] dvb-usb: found a 'TBS Qbox DVB-S2 CI USB2.0' in warm state.<br />
[18814.810330] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.<br />
[18814.810751] DVB: registering new adapter (TBS Qbox DVB-S2 CI USB2.0)<br />
[18815.048073] dvb-usb: MAC address: xx:xx:xx:xx:xx:xx ''(edited by me)''<br />
[18815.048077] <br />
[18815.050881] stv090x_attach: Create New Internal Structure!<br />
[18815.156679] stv090x_attach: Attaching STV0903 demodulator(1) Cut=0x30<br />
[18815.156689] tbsqbox2ci: Attached stv0903!<br />
[18815.156692] <br />
[18815.157478] tbsqbox2ci: CI initialized.<br />
[18815.157488] DVB: registering adapter 0 frontend 0 (STV090x Multistandard)...<br />
[18815.157590] stb6100_attach: Attaching STB6100 <br />
[18815.159811] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.7/usb1/1-7/input/input12<br />
[18815.159952] dvb-usb: schedule remote query interval to 150 msecs.<br />
[18815.159961] dvb-usb: TBS Qbox DVB-S2 CI USB2.0 successfully initialized and connected.<br />
[18815.160051] usbcore: registered new interface driver tbsqbox2ci<br />
[18861.422201] tbsqbox2ci: CI enabled.<br />
[18861.422211] dvb_ca adapter 0: DVB CAM detected and initialised successfully<br />
<br />
To get maximum verbosity, relevant parts of /etc/modprobe.d/modprobe.conf were set as follows:<br />
<br />
options dvb_usb debug=511<br />
options dvb_usb_tbsqbox2ci debug=3<br />
options stb6100 verbose=3<br />
options stv090x verbose=3<br />
<br />
===Remote Control Support===<br />
The device comes with a remote, but that has not been tested yet. Tbsdtv forum members complain about poor interoperability with LIRC.<br />
<br />
==External Links==<br />
* [http://www.tbsdtv.com/english/product/QBoxS2CI.html Qbox 2 CI product page]<br />
* [http://www.tbsdtv.com/forum/index.php TBSDTV forum]<br />
==Issues==<br />
Remote control needs further research.<br />
<br />
CAM support is underway. So far, the astoncrypt v1.07 has been tested. Before this can be finalized, a working smartcard is required. Haven't got one yet ;-).<br />
<br />
Network support has not been addressed yet.<br />
<br />
[[Category:DVB-S2_USB_Devices]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=TeVii_S660&diff=29492TeVii S6602011-09-03T20:45:42Z<p>Js: Reverted edits by Tony168 (talk) to last revision by Jlazkano</p>
<hr />
<div>[[Image:S660.jpg|thumb|right|200px|TeVii S660 Card]]<br />
DVB-S/S2 USB box manufactured by [[TeVii]]<br />
<br />
==Hardware/Features==<br />
* USB 2.0<br />
* Power Supply is via 7.5V - that is outstanding, and I wonder how this come?!<br />
<br />
===Components Used===<br />
* RF Tuner: [[Montage]] [[Montage M88TS2020|M88TS2020]]<br />
* Demodulator: [[Montage]] [[Montage M88DS3000|M88DS3000]]<br />
<br />
===Identification===<br />
lsusb:<br />
Bus 003 Device 002: ID 9022:d660 TeVii Technology Ltd.<br />
<br />
== Linux support ==<br />
Supported by the vanilla kernel and the [[s2-liplianin]] v4l branch.<br />
<br />
This works for me on a Debian Squeeze (2.6.32):<br />
<br />
apt-get install linux-headers-`uname -r` build-essential<br />
mkdir /usr/local/src/dvb<br />
cd /usr/local/src/dvb<br />
wget http://mercurial.intuxication.org/hg/s2-liplianin/archive/tip.zip<br />
unzip s2-liplianin-0b7d3cc65161.zip <br />
cd s2-liplianin-0b7d3cc65161<br />
make CONFIG_DVB_FIREDTV:=n<br />
make install<br />
<br />
The firmware is downloaded from the Ubuntu forums (External Links), there are lots of different versions. This works for me:<br />
<br />
http://ubuntuforums.org/attachment.php?attachmentid=192768&d=1305964408<br />
<br />
== Pictures ==<br />
<br />
<gallery perrow=5><br />
Image:TeVii_S660_top.JPG|Top side<br />
Image:TeVii_S660_bottom.JPG|Bottom side<br />
</gallery><br />
<br />
==External Links==<br />
[http://www.tevii.com/Products_S660_1.asp Official Website]<br />
<br />
[http://ubuntuforums.org/showthread.php?t=1378994 Support Thread for Ubuntu]<br />
<br />
[http://www.gilzad.de/blog/pivot/entry.php?id=7 How to upload firmware to the device]<br />
<br />
[[Category: DVB-S2 USB Devices]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=AzureWave_DVB-S2_USB_CI_-_AD-SB300_(7050)&diff=29491AzureWave DVB-S2 USB CI - AD-SB300 (7050)2011-09-03T20:45:30Z<p>Js: Reverted edits by Tony168 (talk) to last revision by Jimbley</p>
<hr />
<div>A [[DVB-S2]] [[DVB-S2 USB Devices|USB 2.0 Device]] from [http://www.digitalnow.com.au/product_pages/USBSat_CI.html Azurewave]<br />
It is currently unsupported.<br />
<br />
It seems to be an clone of [[Technisat SkyStar USB 2 HD CI]] from [http://www.technisat.de Technisat]<br />
<br />
==Overview/Features==<br />
This is a USB 2.0 device capable of receiving DVB-S and DVB-S2 tranponders including a CI-Slot.<br />
<br />
<br />
Output of <code>lsusb -v</code>:<br />
<pre><br />
Bus 005 Device 004: ID 13d3:3245 IMC Networks <br />
Device Descriptor:<br />
bLength 18<br />
bDescriptorType 1<br />
bcdUSB 2.00<br />
bDeviceClass 0 (Defined at Interface level)<br />
bDeviceSubClass 0 <br />
bDeviceProtocol 0 <br />
bMaxPacketSize0 64<br />
idVendor 0x13d3 IMC Networks<br />
idProduct 0x3245 <br />
bcdDevice 0.02<br />
iManufacturer 1 DTV-DVB<br />
iProduct 2 UDST70XX<br />
iSerial 3 0008CA1DB4B3<br />
bNumConfigurations 1<br />
Configuration Descriptor:<br />
bLength 9<br />
bDescriptorType 2<br />
wTotalLength 32<br />
bNumInterfaces 1<br />
bConfigurationValue 1<br />
iConfiguration 0 <br />
bmAttributes 0xc0<br />
Self Powered<br />
MaxPower 100mA<br />
Interface Descriptor:<br />
bLength 9<br />
bDescriptorType 4<br />
bInterfaceNumber 0<br />
bAlternateSetting 0<br />
bNumEndpoints 2<br />
bInterfaceClass 255 Vendor Specific Class<br />
bInterfaceSubClass 0 <br />
bInterfaceProtocol 0 <br />
iInterface 0 <br />
Endpoint Descriptor:<br />
bLength 7<br />
bDescriptorType 5<br />
bEndpointAddress 0x81 EP 1 IN<br />
bmAttributes 2<br />
Transfer Type Bulk<br />
Synch Type None<br />
Usage Type Data<br />
wMaxPacketSize 0x0200 1x 512 bytes<br />
bInterval 100<br />
Endpoint Descriptor:<br />
bLength 7<br />
bDescriptorType 5<br />
bEndpointAddress 0x82 EP 2 IN<br />
bmAttributes 2<br />
Transfer Type Bulk<br />
Synch Type None<br />
Usage Type Data<br />
wMaxPacketSize 0x0200 1x 512 bytes<br />
bInterval 1<br />
Device Qualifier (for other device speed):<br />
bLength 10<br />
bDescriptorType 6<br />
bcdUSB 2.00<br />
bDeviceClass 0 (Defined at Interface level)<br />
bDeviceSubClass 0 <br />
bDeviceProtocol 0 <br />
bMaxPacketSize0 64<br />
bNumConfigurations 1<br />
Device Status: 0x0002<br />
(Bus Powered)<br />
Remote Wakeup Enabled<br />
</pre><br />
<br />
===Components Used===<br />
[[STMicroelectronics]] [[STMicroelectronics STB0899|STB0899]] multistandard demodulator (DVB-S and DVB-S2).<br />
<br />
[[STMicroelectronics]] [[STMicroelectronics STB6100|STB6100]] 8PSK/QPSK direct conversion (zero IF) tuner for DVB-S2. <br />
<br />
===Identification===<br />
<br />
Vendor ID: 13d3<br />
Product ID: 3245<br />
<br />
AzureWave DVB-S2 USB CI - AD-SB300 (7050) images:<br />
<br />
{| border=1 cellpadding=10 cellspacing=0 valign="top"<br />
|- bgcolor=#efefef valign="top"<br />
|[[Image:AD-SB300-1.jpg|50px|]]<br />
|[[Image:AD-SB300-2.jpg|50px|]]<br />
|}<br />
<br />
==Making it Work==<br />
According to this post it should work with multiproto tree : [http://www.linuxtv.org/pipermail/linux-dvb/2008-September/028796.html] but I've not been able to find the driver.<br />
<br />
==External Links==<br />
* Available from [http://www.digitalnow.com.au/product_pages/USBSat_CI.html DigitalNow]<br />
[[Category:DVB-S2 USB Devices]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=AVerMedia_AverTV_Hybrid_Volar_HX_(A827)&diff=29454AVerMedia AverTV Hybrid Volar HX (A827)2011-08-22T15:09:28Z<p>Js: revert spam</p>
<hr />
<div>==Device Features==<br />
<br />
{{Device_List_Low_Detail/Header<br />
| content = <br />
{{USB_Device_Data<br />
|renderwith=Device_List_Low_Detail/Row<br />
|selatt1=did<br />
|selval1=avermedia-a827<br />
}}<br />
}}<br />
<br />
===Specifications===<br />
<br />
<br />
Interface: [[USB]] 2.0<br />
Supported Broadcast Formats: [[DVB-T]], Analog, FM<br />
<br />
This is what the USB DVB-T Database knows about this device:<br />
{{Device_List_Full_Detail/Header<br />
| content = <br />
{{USB_Device_Data<br />
|renderwith=Device_List_Full_Detail/Row<br />
|selatt1=did<br />
|selval1=avermedia-a827<br />
}}<br />
}}<br />
<br />
===Chips===<br />
* Cypress CY7C68013A<br />
* NXP SAA7136E<br />
* NXP TDA18271HDC1<br />
* Afatech AF9013-N1<br />
==Getting it to work==<br />
Tested and worked on Fedora-11-i386, Kernel-2.6.29.4-167-PAE.fc11, Fedora 12 and Fedora 13 (both stock kernel)<br />
Dependencies needed <br />
(from installation DVD)<br />
* kernel,<br />
* kernel-headers,<br />
* kernel-devel,<br />
* gcc.<br />
(yum install)<br />
* dialog<br />
* tvtime<br />
* mplayer (with all it's dependencies, including codecs).<br />
(drivers from [[AVerMedia|Avermedia]] website, as posted bellow)<br />
* July 2009 - 0.07 beta driver for i386 or x86_64 - tested on Fedora-11<br />
* January 2010 - 0.10 beta driver for i386 or x86_64 - tested on Ubuntu Karmic 910 and on ArchLinux(i386) with 2.6.33 kernel<br />
* May 2010 - 0.10 beta driver for x86_64 - works great on Fedora 13 (stock kernel)<br />
* November 2010 - 0.10 beta driver unusable for Fedora 14. Fedora 14 (kernel-2.6.35) correctly detects the Avermedia tuner, but that's all. <br />
* '''''Avermedia's official answer is they stopped updating the driver for AverTV Hybrid Volar HX (A827)'''''. <br />
* '''So, driver needed for this device with Kernels greater than 2.6.33 !!!'''.<br />
* For me, the driver + kernel 2.6.35 seems to work. For 2.6.36, the functions "param_array_get" and "param_array_set" are not declared any more. Hex edit the binary files provided with the driver and replace the two occurences by "param_array_ops".<br />
* '''Appreciate your support. The driver fails to install on FC14 even with a manual install. Can you be more specific regarding your specifications for kernel 2.6.35?!'''<br />
<br />
<br />
Plug in the USB Volar HX ( A827 ) tuner.<br />
Install driver in normal mode, and should see the installation concluded succesfully.<br />
Next, the messages is to unplug the device (do so) and to replug it (do so) <br />
Next is the sound testing. Modify the parameters according with your area.<br />
You should hear a tv sound like (with or without station). The ideea is to get sound from the USB tuner.<br />
After that there is the h826d-tools the software wants to install. You can install it, but there<br />
is no need of it (some sh scripts tv-player, audio, radio-player).<br />
<br />
The thing is after that, you should see in dmesg, the tuner loaded and then devices created<br />
video0 vbi1 radio0 and even adapter0 (for dvb) and of course the alsa emulation for the tuner:<br />
*A827 registered V4L2 device video0[video]<br />
*[ 4373.455456] A827 registered V4L2 device vbi1[vbi]<br />
*[ 4373.455486] A827 registered V4L2 device radio0[radio]<br />
*[ 4373.455835] A827 registered ALSA sound card 1<br />
*[ 4373.455844] DVB: registering new adapter (A827[0] DVB-T)<br />
*[ 4373.455847] A827[0] DVB-T registered DVB adapter 0<br />
*[ 4373.457303] DVB: registering adapter 0 frontend 0 (A827[0] DVB-T)...<br />
A cat /proc/asound/cards should display 1: your system sound card (let's say ALC 826 analog device)<br />
and 2: the sound emulation of your usb tv tuner.<br />
Of course if you have a webcam installed, these devices will show up different: video1 and so on and they should work with no problem.<br />
<br />
===Kernel 2.6.36, 2.6.37, 2.6.38 and 2.6.39===<br />
<br />
For 2.6.36 hex edit file H826D-expert-install/aver/osdep_dvb.o_shipped and replace '''param_array_get''' and '''param_array_set''' by '''param_array_ops'''<br />
<br />
For 2.6.37:<br />
*in file '''H826D-expert-install/aver/osdep.c''' replace '''init_MUTEX(tmp);''' by '''sema_init(tmp, 1);''' and '''init_MUTEX_LOCKED(tmp);''' by '''sema_init(tmp, 0);'''<br />
*in file '''H826D-expert-install/aver/osdep_dvb.c''' replace '''init_MUTEX(&p->feedlock);''' by '''sema_init(&p->feedlock, 1);'''<br />
*add '''#define VFL_TYPE_VTX 3''' to top of file '''H826D-expert-install/aver/osdep_v4l2.c'''<br />
Tested on [http://www.abclinuxu.cz/hardware/pridavne-karty/televizni-karty/dvb-t/usb/aver-tv-hybrid-volar-hx Archlinux] and [http://station-mir.livejournal.com/162612.html Slackware 13.1]<br />
<br />
For 2.6.38 (with Big Kernel Lock (BKL) disabled by default) - Solution from [[AVerMedia_A828]]:<br />
*'''Apply the solution for 2.6.36 and 2.6.37 before.'''<br />
<pre><br />
1. In aver/osdep.c : <br />
Replace : <br />
void SysLockKernel()<br />
{<br />
lock_kernel();<br />
}<br />
<br />
void SysUnlockKernel()<br />
{<br />
unlock_kernel();<br />
}<br />
By<br />
static DEFINE_MUTEX(dvbdev_mutex);<br />
void SysLockKernel()<br />
{<br />
mutex_lock(&dvbdev_mutex);<br />
}<br />
<br />
void SysUnlockKernel()<br />
{<br />
mutex_unlock(&dvbdev_mutex);<br />
}<br />
2. In aver/osdep_th2.c :<br />
2.a After : <br />
#include "osdep_th2.h"<br />
Add : <br />
#include "osdep.h"<br />
2.b Replace : <br />
lock_kernel();<br />
By : <br />
SysLockKernel();<br />
<br />
2.c and Replace : <br />
unlock_kernel();<br />
By:<br />
SysUnlockKernel();<br />
</pre><br />
<br />
For 2.6.39:<br />
*'''Apply the solution for 2.6.36, 2.6.37 and 2.6.38 before.'''<br />
Remove '''#include <linux/smp_lock.h>''' in file<br />
* H826D-expert-install/aver/osdep.c<br />
* H826D-expert-install/aver/osdep_dvb.c<br />
* H826D-expert-install/aver/osdep_th2.c<br />
* H826D-expert-install/aver/osdep_v4l2.c<br />
<br />
=== Analog TV and composite ===<br />
<br />
I only tested on analog tv and composite. <br />
For video I used tvtime (scan and watch analog channels but no sound) and<br />
mplayer - watched analog tv channels with sound on alsa server (I removed pulse as I always do.)<br />
There is no need to start arecord, or aplay, or sox, or so if you are gonna use mplayer to watch TV,<br />
as mplayer supports ALSA directly, but in this case, you must specify the hardware id:<br />
Ex: <br />
* if dmesg shows your Volar HX as: A827 registered ALSA sound card 1, you should declare in mplayer commandline adevice=hw.1<br />
* if dmesg shows your Volar HX as: A827 registered ALSA sound card 2, you should declare in mplayer commandline adevice=hw.2<br />
(Example:)<br />
* mplayer tv:// -driver=v4l2:device=/dev/video0:norm=PAL:chanlist=europe-east:input=0:channel=R9:alsa:adevice=hw.1:forceaudio:immediatemode=0 tv://<br />
(Similar for mencoder)<br />
The only mention that it deserve to be made, is to install all the alsa-plugins.<br />
Enjoy!<br />
<br />
=== DVB-T ===<br />
<br />
[[Kaffeine]] works like a charm, [[Klear]] (which is app I use on another machine over a year) work up to 10 seconds, then takes 100% of 1 processor <br />
(fortunately today almost everyone has dual or quad), and you have no other choice then to close it (or kill it in some cases).<br />
<br />
[[MPlayer]] and [[Xine]] work fine once you provide them channels.conf made by [[scan]] in theirs respective config direcotries. Switching programs in Gnome Mplayer may cause some troubles (if you use channels as playlist) so recommended way is to turn off (gnome) mplayer instance you are currently watching and then open another with different channel.<br />
<br />
=== FM-radio ===<br />
<br />
As written above, 0.10 beta driver for i386 or x86_64 makes /dev/radio0 device, I added user to video & audio group (even tried as root), but gnomeradio doesn't give a sound.<br />
That's probably some issue with mixer, as it is grayed. As in Windows both DVB-T and FM work, so there is obviously needed some tweaking to get FM radio working (haven't tried<br />
yet DVB radio either in Windows/linux).<br />
<br />
===USB-Interfaces===<br />
<br />
/proc/bus/usb/devices-output (shorter then lsusb -v):<br />
<br />
T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 5 Spd=480 MxCh= 0<br />
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1<br />
P: Vendor=07ca ProdID=a827 Rev= 1.03<br />
S: Manufacturer=AVerMedia<br />
S: Product=AVerTV<br />
S: SerialNumber=300871601647<br />
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA<br />
I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)<br />
E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms<br />
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms<br />
E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms<br />
I: If#= 0 Alt= 1 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)<br />
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=500us<br />
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms<br />
E: Ad=82(I) Atr=01(Isoc) MxPS=3030 Ivl=125us<br />
I: If#= 0 Alt= 2 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)<br />
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=500us<br />
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms<br />
E: Ad=82(I) Atr=01(Isoc) MxPS=2178 Ivl=125us<br />
I: If#= 0 Alt= 3 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)<br />
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=500us<br />
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms<br />
E: Ad=82(I) Atr=01(Isoc) MxPS=2058 Ivl=125us<br />
I: If#= 0 Alt= 4 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)<br />
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=500us<br />
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms<br />
E: Ad=82(I) Atr=01(Isoc) MxPS= 970 Ivl=125us<br />
I: If#= 0 Alt= 5 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)<br />
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=500us<br />
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms<br />
E: Ad=82(I) Atr=01(Isoc) MxPS= 684 Ivl=125us<br />
I: If#= 0 Alt= 6 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)<br />
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=500us<br />
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms<br />
E: Ad=82(I) Atr=01(Isoc) MxPS= 940 Ivl=125us<br />
<br />
===Drivers===<br />
You can download drivers for Linux i586/x86_64 here:<br />
<br />
* [http://www.avermedia.com/avertv/Product/ProductDetail.aspx?Id=293&tab=APDriver AVerTV Hybrid Volar HX]<br />
<br />
This is official beta version 0.10 for OpenSuSE, Mandriva, Fedora and Ubuntu but it will most probably work with any other distro as well.<br />
[[Category:DVB-T USB Devices]]<br />
<br />
==Kernel driver status==<br />
<br />
* Avermedia stopped developing the driver for newer kernels, as posted above.<br />
* Help appreciated!<br />
<br />
This device is currently unsupported by drivers in the regular kernel<br />
http://www.linuxtv.org/pipermail/linux-dvb/2008-October/029714.html</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Main_Page&diff=29170Main Page2011-06-09T16:27:03Z<p>Js: Reverted edits by Jamesbzr (Talk) to last version by Js</p>
<hr />
<div>__NOTOC__<br />
__NOEDITSECTION__<br />
<br />
<div style="background-color:#6289AB; padding:0.3em; color:#ffffff; font-weight:bold; font-size:150%; text-align:center"><br />
Welcome to the linuxtv.org V4L-DVB Wiki !<br />
</div><br />
{|valign=top background=none<br />
|valign=top|<br />
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff"><br />
<br />
This wiki is intended to become an authoritative source of information regarding the use of analog video and digital TV sources under Linux -- i.e. the subject matters covered under the V4L-DVB framework. The basic plan is to aggregate information about: available hardware; how v4l or dvb work; software used with the hardware and so forth. <br />
Like all other wikis, the V4L-DVB wiki relies upon the contributions of its users. Hence, it will only be as useful as we make it! So we encourage you to share your knowledge and help with the task of turning this site into a grand repository of knowledge. Your input (whether it be by providing a set of instructions for how to get a certain device working; a minor improvement to an existing article; or an explanation for some complex concept) will be highly appreciated.<br />
<br />
-- [[LinuxTVWiki:People|The LinuxTV V4L-DVB wiki team]] / [[People behind V4L-DVB]]<br />
<br />
</div><br />
|}<br />
<br />
<br />
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff"><br />
{|valign=top cellpadding=0 cellspacing=5 width=100%<br />
| valign=top | [[Image:News_icon2.png|50px]] <br />
| '''GENERAL NEWS:''' <br><br />
'''Free at Last, Free at Last: A Final Fairwell to V4L1 ... And Just What the Heck is xf86-video-v4l Anyway ?'''<br><br />
Upon release of the forthcoming 2.6.38 kernel, all but a very few vestiges of the antiquated V4L1 API will have been removed forever in favour of its successor, the V4L2 API (which, itself, now resides within the larger [[Development: Linux Media Infrastructure API|Linux Media Infrastructure API]]). <br />
<br />
One of the more obvious ramifications of this significant change is ... <span style="font-size: 50%;">''[[News Archive|cont'd here]]''</span> -- 03:43, 13 February 2011 (UTC)<br />
<br />
'''Introducing the "Media_build" System:'''<br><br />
If you hadn't noticed, over the course of the past year, there has been some monumental changes in the revision control systems employed for V4L-DVB development. These changes have had an impact not only upon developers, but also on end users seeking to use the latest drivers set ... <span style="font-size: 50%;">''[[News Archive|cont'd here]]''</span> --09:22, 9 January 2011 (UTC)<br />
|-<br />
| || align=right| <span style="font-size: 50%;">''For older news items see [[News Archive|here]]</span><br />
|}<br />
</div><br />
<br />
<br />
<br />
{| style="border: solid 1px; border-color:#6289AB; margin: oem; background-color: #6289AB;" cellspacing=5 cellpadding=1 width="100%"<br />
| valign=top |<br />
<br />
{| cellspacing=0 cellpadding=5 border=0 width="100%"<br />
<br />
<br />
| valign=top | [[Image:index.png|50px]]<br />
| valign=top | '''[[Special:Allpages|The Wiki's Indexes]]'''<br><small>Article, category, image, .... <br />
| valign=top ; style="background-color:#FFFFCC;" | [[Image:User_Info_icon.png|50px]]<br />
| valign=top ; style="background-color:#FFFFCC;" | '''[[User Information]]'''<br><small>How to install drivers for your hardware, and software to use with your device, ... <br />
| valign=top ; style="background-color:#F5DEB3;" | [[Image:Technical_background_icon.png|50px]]<br />
| valign=top ; style="background-color:#F5DEB3;" | '''[[Technical Background]]'''<br><small>Technical details on standards and hardware components/chipsets, etc<br />
|-<br />
|-<br />
|-<br />
<br />
| valign=top | [[Image:More_info.png|50px|]]<br />
| valign=top | '''[[Other Sources of Info]]'''<br><small>Mailing lists, #irc channels....<br />
| valign=top ; style="background-color:#FFFFCC;" | [[Image:Hardware_icon.png|50px]]<br />
| valign=top ; style="background-color:#FFFFCC;" | '''[[Hardware Device Information]]'''<br><small>Information on hardware devices <br />
| valign=top ; style="background-color:#F5DEB3;" | [[Image:Developer_icon.png|50px]]<br />
| valign=top ; style="background-color:#F5DEB3;" | '''[[Developer Section]]'''<br><small>Information to help device driver development<br />
|-<br />
|-<br />
|-<br />
<br />
|}<br />
|}<br />
<br />
<br />
<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;"><br />
{|valign=top cellpadding=0 cellspacing=0 width=100%<br />
|valign=top bgcolor=#F7F9FB width=32%|<br />
=='''The Wiki - How Can I Help?'''==<br />
* [[Help:Contents|Everything you need to know about editing wiki pages but were afraid to ask]]<br />
** [http://www.mediawiki.org/wiki/Help:Moving_a_page Help: Renaming/Moving a Page]<br />
* [[Wiki - Help Wanted List|A list of things that need to be tackled]] <br />
* [[Wiki - New Device Copy & Paste Template|New Device Copy & Paste Template]]<br />
<br />
|valign=top bgcolor=#F7F9FB width=4%|<br />
|valign=top bgcolor=#F7F9FB width=32%|<br />
<br />
|}<br />
</div><br />
<br />
[[Category:LinuxTV]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Main_Page&diff=29094Main Page2011-05-17T17:42:53Z<p>Js: revert spam</p>
<hr />
<div>__NOTOC__<br />
__NOEDITSECTION__<br />
<br />
<div style="background-color:#6289AB; padding:0.3em; color:#ffffff; font-weight:bold; font-size:150%; text-align:center"><br />
Welcome to the linuxtv.org V4L-DVB Wiki !<br />
</div><br />
{|valign=top background=none<br />
|valign=top|<br />
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff"><br />
<br />
This wiki is intended to become an authoritative source of information regarding the use of analog video and digital TV sources under Linux -- i.e. the subject matters covered under the V4L-DVB framework. The basic plan is to aggregate information about: available hardware; how v4l or dvb work; software used with the hardware and so forth. <br />
Like all other wikis, the V4L-DVB wiki relies upon the contributions of its users. Hence, it will only be as useful as we make it! So we encourage you to share your knowledge and help with the task of turning this site into a grand repository of knowledge. Your input (whether it be by providing a set of instructions for how to get a certain device working; a minor improvement to an existing article; or an explanation for some complex concept) will be highly appreciated.<br />
<br />
-- [[LinuxTVWiki:People|The LinuxTV V4L-DVB wiki team]] / [[People behind V4L-DVB]]<br />
<br />
</div><br />
|}<br />
<br />
<br />
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff"><br />
{|valign=top cellpadding=0 cellspacing=5 width=100%<br />
| valign=top | [[Image:News_icon2.png|50px]] <br />
| '''GENERAL NEWS:''' <br><br />
'''Free at Last, Free at Last: A Final Fairwell to V4L1 ... And Just What the Heck is xf86-video-v4l Anyway ?'''<br><br />
Upon release of the forthcoming 2.6.38 kernel, all but a very few vestiges of the antiquated V4L1 API will have been removed forever in favour of its successor, the V4L2 API (which, itself, now resides within the larger [[Development: Linux Media Infrastructure API|Linux Media Infrastructure API]]). <br />
<br />
One of the more obvious ramifications of this significant change is ... <span style="font-size: 50%;">''[[News Archive|cont'd here]]''</span> -- 03:43, 13 February 2011 (UTC)<br />
<br />
'''Introducing the "Media_build" System:'''<br><br />
If you hadn't noticed, over the course of the past year, there has been some monumental changes in the revision control systems employed for V4L-DVB development. These changes have had an impact not only upon developers, but also on end users seeking to use the latest drivers set ... <span style="font-size: 50%;">''[[News Archive|cont'd here]]''</span> --09:22, 9 January 2011 (UTC)<br />
|-<br />
| || align=right| <span style="font-size: 50%;">''For older news items see [[News Archive|here]]</span><br />
|}<br />
</div><br />
<br />
<br />
<br />
{| style="border: solid 1px; border-color:#6289AB; margin: oem; background-color: #6289AB;" cellspacing=5 cellpadding=1 width="100%"<br />
| valign=top |<br />
<br />
{| cellspacing=0 cellpadding=5 border=0 width="100%"<br />
<br />
<br />
| valign=top | [[Image:index.png|50px]]<br />
| valign=top | '''[[Special:Allpages|The Wiki's Indexes]]'''<br><small>Article, category, image, .... <br />
| valign=top ; style="background-color:#FFFFCC;" | [[Image:User_Info_icon.png|50px]]<br />
| valign=top ; style="background-color:#FFFFCC;" | '''[[User Information]]'''<br><small>How to install drivers for your hardware, and software to use with your device, ... <br />
| valign=top ; style="background-color:#F5DEB3;" | [[Image:Technical_background_icon.png|50px]]<br />
| valign=top ; style="background-color:#F5DEB3;" | '''[[Technical Background]]'''<br><small>Technical details on standards and hardware components/chipsets, etc<br />
|-<br />
|-<br />
|-<br />
<br />
| valign=top | [[Image:More_info.png|50px|]]<br />
| valign=top | '''[[Other Sources of Info]]'''<br><small>Mailing lists, #irc channels....<br />
| valign=top ; style="background-color:#FFFFCC;" | [[Image:Hardware_icon.png|50px]]<br />
| valign=top ; style="background-color:#FFFFCC;" | '''[[Hardware Device Information]]'''<br><small>Information on hardware devices <br />
| valign=top ; style="background-color:#F5DEB3;" | [[Image:Developer_icon.png|50px]]<br />
| valign=top ; style="background-color:#F5DEB3;" | '''[[Developer Section]]'''<br><small>Information to help device driver development<br />
|-<br />
|-<br />
|-<br />
<br />
|}<br />
|}<br />
<br />
<br />
<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;"><br />
{|valign=top cellpadding=0 cellspacing=0 width=100%<br />
|valign=top bgcolor=#F7F9FB width=32%|<br />
=='''The Wiki - How Can I Help?'''==<br />
* [[Help:Contents|Everything you need to know about editing wiki pages but were afraid to ask]]<br />
** [http://www.mediawiki.org/wiki/Help:Moving_a_page Help: Renaming/Moving a Page]<br />
* [[Wiki - Help Wanted List|A list of things that need to be tackled]] <br />
* [[Wiki - New Device Copy & Paste Template|New Device Copy & Paste Template]]<br />
<br />
|valign=top bgcolor=#F7F9FB width=4%|<br />
|valign=top bgcolor=#F7F9FB width=32%|<br />
<br />
|}<br />
</div><br />
<br />
[[Category:LinuxTV]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Talk:Main_Page&diff=29020Talk:Main Page2011-04-28T06:12:27Z<p>Js: Reverted edits by Chjchj (Talk) to last version by Howl</p>
<hr />
<div>== main page hacked ==<br />
<br />
Main Page was "hacked" by a stupid guy: http://www.linuxtv.org/wiki/index.php?title=Main_Page&oldid=11512 <br />
someone should consider taking some actions towards his account. <br />
<br />
I would like to say something to that guy: <br />
do you really think you are an hacker just because you changed the main page of a wiki that can be edited by whoever wants?<br />
<br />
If you just sit down and think you will realize the real hackers here are all those coders here behind who hack inside closed devices and manage to free them through a gpl driver written from scratch.<br />
<br />
Instead of abusing open source communities where nobody has got the power because everybody does have the power (for istance I registered just in order to change back the homepage, exactly as you did to destroy it), focus your efforts on big evil corporations websites: there you can fight against a webadmin and maybe eventually win, but never would you win over a linux community, it's simply too big (and does not code for money)!<br />
<br />
== Categories articles organization ==<br />
<br />
I just added some trivial categories to the ISDB-T devices pages, but, I have a little trouble. Watching the existing scheme in another standard, for example DVB-T, we can find categories like "DVB-T PCI Cards" in the same name page, but in the "DVB-T PCie Cards" we have the "PCIe" category. There are anything "official" about the procedures of Categories? --[[User:Howl|howl]] 01:15, 1 October 2009 (UTC)</div>Jshttps://www.linuxtv.org/wiki/index.php?title=TerraTec_Cinergy_C_DVB-C&diff=29019TerraTec Cinergy C DVB-C2011-04-28T06:11:43Z<p>Js: Reverted edits by Chjchj (Talk) to last version by Rho</p>
<hr />
<div>[[Image:Cinergy-c.jpg|thumb|right|250px|Cinergy C DVB-C by Terratec]]<br />
<br />
A [[DVB-C]] [[DVB-C PCI Cards|PCI card]] from [[TerraTec]].<br />
<br />
==Overview/Features==<br />
<br />
Looks to be a clone of the Azurewave/Twinhan AD-CP400 (VP-2040) [http://www.twinhan.com/product_AD-CP400.asp]<br />
<br />
===Components Used===<br />
<br />
* NXP/Philips CU1216 module<br />
* NXP/Philips TDA10023 (demodulator)<br />
* Mantis (bridge)<br />
<br />
===Other Images===<br />
<gallery perrow=5><br />
Image:Cinergy-c.jpg|The card<br />
</gallery><br />
<br />
===Identification===<br />
<br />
$ lspci -v -s 01:01.0<br />
01:01.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01)<br />
Subsystem: TERRATEC Electronic GmbH Unknown device 1178<br />
Flags: bus master, medium devsel, latency 64, IRQ 22<br />
Memory at cfdff000 (32-bit, prefetchable) [size=4K]<br />
<br />
$ lspci -vvn -s 01:01.0<br />
01:01.0 0480: 1822:4e35 (rev 01)<br />
Subsystem: 153b:1178<br />
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-<br />
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort+ <MAbort- >SERR- <PERR-<br />
Latency: 64 (2000ns min, 63750ns max)<br />
Interrupt: pin A routed to IRQ 22<br />
Region 0: Memory at cfdff000 (32-bit, prefetchable) [size=4K]<br />
<br />
==Making it Work==<br />
The card is working under Linux using the Mantis driver.<br />
Kernel support is available since Kernel version 2.6.33. For kernel versions prior to 2.6.33, see the corresponding sections under Drivers below.<br />
<br />
===Firmware===<br />
No firmware required.<br />
<br />
===Drivers===<br />
====Kernel Driver====<br />
The Mantis Driver is part of the vanilla linux kernel[http://git390.marist.edu/cgi-bin/gitweb.cgi?p=linux-2.6.git;a=commit;h=2faae42233778676607a2a45b95aeb375bebe2c6] since 2.6.33.<br />
<br />
====S2API Driver for Kernel Versions < 2.6.33 ====<br />
Install the latest mantis drivers:<br />
<br />
sudo apt-get install mercurial linux-headers-$(uname -r) build-essential<br />
hg clone http://mercurial.intuxication.org/hg/s2-liplianin<br />
cd s2-liplianin<br />
make<br />
sudo make install<br />
sudo reboot<br />
<br />
If you have a distribution which uses [http://linux.dell.com/projects.shtml#dkms DKMS] (like Ubuntu), [[Mantis with DKMS]] is a convenient way to install the driver and keep it running for new kernel releases.<br />
<br />
You should/could also use the sudo make menuconfig and remove all the unnecessary modules.<br />
<br />
====Old Multiproto Driver====<br />
Old mantis-multiproto (obsolete API) repository instructions. Won't compile with latest kernels, if in doubt, try the vanilla kernel module or the S2API instructions above.<br />
<br />
cd /usr/src<br />
sudo apt-get install mercurial<br />
sudo hg clone http://jusst.de/hg/mantis <br />
cd mantis<br />
sudo make<br />
sudo make install<br />
sudo reboot<br />
<br />
===Sample kernel output===<br />
Output from [http://mercurial.intuxication.org/hg/s2-liplianin s2-liplianin] driver under Kernel 2.6.28-15<br />
[ 10.158595] Mantis 0000:04:09.0: PCI INT A -> Link[LNKB] -> GSI 17 (level, low) -> IRQ 17<br />
[ 10.158700] irq: 17, latency: 64<br />
[ 10.158701] memory: 0xdfeff000, mmio: 0xffffc20000054000<br />
[ 10.158706] found a VP-2040 PCI DVB-C device on (04:09.0),<br />
[ 10.158708] Mantis Rev 1 [153b:1178], irq: 17, latency: 64<br />
[ 10.158710] memory: 0xdfeff000, mmio: 0xffffc20000054000<br />
[ 10.161444] MAC Address=[00:08:ca:1d:b7:60]<br />
[ 10.161482] mantis_alloc_buffers (0): DMA=0x3d5f0000 cpu=0xffff88003d5f0000 size=65536<br />
[ 10.161488] mantis_alloc_buffers (0): RISC=0x3d129000 cpu=0xffff88003d129000 size=1000<br />
[ 10.161491] DVB: registering new adapter (Mantis dvb adapter)<br />
[ 10.681124] mantis_frontend_init (0): Probing for CU1216 (DVB-C)<br />
[ 10.684607] TDA10023: i2c-addr = 0x0c, id = 0x7d<br />
[ 10.684609] mantis_frontend_init (0): found Philips CU1216 DVB-C frontend (TDA10023) @ 0x0c<br />
[ 10.684612] mantis_frontend_init (0): Mantis DVB-C Philips CU1216 frontend attach success<br />
[ 10.684616] DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)...<br />
[ 10.684684] mantis_ca_init (0): Registering EN50221 device<br />
[ 10.684961] mantis_ca_init (0): Registered EN50221 device<br />
[ 10.684971] mantis_hif_init (0): Adapter(0) Initializing Mantis Host Interface<br />
[ 10.685048] input: Mantis VP-2040 IR Receiver as /devices/virtual/input/input5<br />
[ 10.815684] Mantis VP-2040 IR Receiver: unknown key: key=0x00 raw=0x00 down=1<br />
<br />
<br />
With latest build from [http://jusst.de/hg/mantis http://jusst.de/hg/mantis]:<br />
[ 47.563542] found a VP-2040 PCI DVB-C device on (01:01.0),<br />
[ 47.563543] Mantis Rev 1 [153b:1178], irq: 22, latency: 64<br />
[ 47.563545] memory: 0xcfdff000, mmio: 0xf89de000<br />
[ 47.566227] MAC Address=[00:08:ca:1c:73:1d]<br />
[ 47.566254] mantis_alloc_buffers (0): DMA=0x37850000 cpu=0xf7850000 size=65536<br />
[ 47.566292] mantis_alloc_buffers (0): RISC=0x37913000 cpu=0xf7913000 size=1000<br />
[ 47.566332] DVB: registering new adapter (Mantis dvb adapter)<br />
[ 48.086203] mantis_frontend_init (0): Probing for CU1216 (DVB-C)<br />
[ 48.088334] mantis_frontend_init (0): found Philips CU1216 DVB-C frontend 0x0c<br />
[ 48.088378] mantis_frontend_init (0): Mantis DVB-C Philips CU1216 frontend attach success<br />
[ 48.088424] DVB: registering frontend 0 (Philips TDA10023 DVB-C)...<br />
[ 54.367799] mantis_ack_wait (0): Slave RACK Fail !<br />
<br />
===Remote Control Support===<br />
Supported under the vanilla kernel module.<br />
<br />
Works for the old mantis multiproto driver after applying the following patch. See [http://pauli.borodulin.fi/blog/?p=8]<br />
<br />
===CI support===<br />
CI/CAM support for the optional CI module is not working yet ({{CURRENTDAY}}.{{CURRENTMONTH}}.{{CURRENTYEAR}})<br />
<br />
==Known Issues==<br />
<br />
====Working around i2c bus probing interference with ivtv====<br />
If the mantis module won't load (hangs) with the error message<br />
<br />
mantis_ack_wait (0): Slave RACK Fail !<br />
<br />
you should check [[http://www.linuxtv.org/pipermail/linux-dvb/2007-August/020087.html]]<br />
<br />
----<br />
<br />
<pre><br />
TDA10023(0): tda10023_writereg, writereg error (reg == 0x08, val == 0x23, ret == -121)<br />
</pre><br />
<br />
----<br />
<br />
femon output is not correct (statistics aren't implemented correctly in the driver)<br />
<pre><br />
FE: Philips TDA10023 DVB-C (DVBC)<br />
status SCVYL | signal ffff | snr ffff | ber 000f9f9f | unc 9f9f9f9f | FE_HAS_LOCK<br />
status SCVYL | signal ffff | snr ffff | ber 000f9f9f | unc 9f9f9f9f | FE_HAS_LOCK<br />
</pre><br />
<br />
==External Links==<br />
* [http://tven.terratec.net/modules.php?op=modload&name=News&file=article&sid=267 Terratec product page]<br />
<br />
[[Category:DVB-C PCI Cards]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Main_Page&diff=29018Main Page2011-04-28T06:10:10Z<p>Js: Reverted edits by Chjchj (Talk) to last version by CityK</p>
<hr />
<div>__NOTOC__<br />
__NOEDITSECTION__<br />
<br />
<div style="background-color:#6289AB; padding:0.3em; color:#ffffff; font-weight:bold; font-size:150%; text-align:center"><br />
Welcome to the linuxtv.org V4L-DVB Wiki !<br />
</div><br />
{|valign=top background=none<br />
|valign=top|<br />
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff"><br />
<br />
This wiki is intended to become an authoritative source of information regarding the use of analog video and digital TV sources under Linux -- i.e. the subject matters covered under the V4L-DVB framework. The basic plan is to aggregate information about: available hardware; how v4l or dvb work; software used with the hardware and so forth. <br />
Like all other wikis, the V4L-DVB wiki relies upon the contributions of its users. Hence, it will only be as useful as we make it! So we encourage you to share your knowledge and help with the task of turning this site into a grand repository of knowledge. Your input (whether it be by providing a set of instructions for how to get a certain device working; a minor improvement to an existing article; or an explanation for some complex concept) will be highly appreciated.<br />
<br />
-- [[LinuxTVWiki:People|The LinuxTV V4L-DVB wiki team]] / [[People behind V4L-DVB]]<br />
<br />
</div><br />
|}<br />
<br />
<br />
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff"><br />
{|valign=top cellpadding=0 cellspacing=5 width=100%<br />
| valign=top | [[Image:News_icon2.png|50px]] <br />
| '''GENERAL NEWS:''' <br><br />
'''Free at Last, Free at Last: A Final Fairwell to V4L1 ... And Just What the Heck is xf86-video-v4l Anyway ?'''<br><br />
Upon release of the forthcoming 2.6.38 kernel, all but a very few vestiges of the antiquated V4L1 API will have been removed forever in favour of its successor, the V4L2 API (which, itself, now resides within the larger [[Development: Linux Media Infrastructure API|Linux Media Infrastructure API]]). <br />
<br />
One of the more obvious ramifications of this significant change is ... <span style="font-size: 50%;">''[[News Archive|cont'd here]]''</span> -- 03:43, 13 February 2011 (UTC)<br />
<br />
'''Introducing the "Media_build" System:'''<br><br />
If you hadn't noticed, over the course of the past year, there has been some monumental changes in the revision control systems employed for V4L-DVB development. These changes have had an impact not only upon developers, but also on end users seeking to use the latest drivers set ... <span style="font-size: 50%;">''[[News Archive|cont'd here]]''</span> --09:22, 9 January 2011 (UTC)<br />
|-<br />
| || align=right| <span style="font-size: 50%;">''For older news items see [[News Archive|here]]</span><br />
|}<br />
</div><br />
<br />
<br />
<br />
{| style="border: solid 1px; border-color:#6289AB; margin: oem; background-color: #6289AB;" cellspacing=5 cellpadding=1 width="100%"<br />
| valign=top |<br />
<br />
{| cellspacing=0 cellpadding=5 border=0 width="100%"<br />
<br />
<br />
| valign=top | [[Image:index.png|50px]]<br />
| valign=top | '''[[Special:Allpages|The Wiki's Indexes]]'''<br><small>Article, category, image, .... <br />
| valign=top ; style="background-color:#FFFFCC;" | [[Image:User_Info_icon.png|50px]]<br />
| valign=top ; style="background-color:#FFFFCC;" | '''[[User Information]]'''<br><small>How to install drivers for your hardware, and software to use with your device, ... <br />
| valign=top ; style="background-color:#F5DEB3;" | [[Image:Technical_background_icon.png|50px]]<br />
| valign=top ; style="background-color:#F5DEB3;" | '''[[Technical Background]]'''<br><small>Technical details on standards and hardware components/chipsets, etc<br />
|-<br />
|-<br />
|-<br />
<br />
| valign=top | [[Image:More_info.png|50px|]]<br />
| valign=top | '''[[Other Sources of Info]]'''<br><small>Mailing lists, #irc channels....<br />
| valign=top ; style="background-color:#FFFFCC;" | [[Image:Hardware_icon.png|50px]]<br />
| valign=top ; style="background-color:#FFFFCC;" | '''[[Hardware Device Information]]'''<br><small>Information on hardware devices <br />
| valign=top ; style="background-color:#F5DEB3;" | [[Image:Developer_icon.png|50px]]<br />
| valign=top ; style="background-color:#F5DEB3;" | '''[[Developer Section]]'''<br><small>Information to help device driver development<br />
|-<br />
|-<br />
|-<br />
<br />
|}<br />
|}<br />
<br />
<br />
<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;"><br />
{|valign=top cellpadding=0 cellspacing=0 width=100%<br />
|valign=top bgcolor=#F7F9FB width=32%|<br />
=='''The Wiki - How Can I Help?'''==<br />
* [[Help:Contents|Everything you need to know about editing wiki pages but were afraid to ask]]<br />
** [http://www.mediawiki.org/wiki/Help:Moving_a_page Help: Renaming/Moving a Page]<br />
* [[Wiki - Help Wanted List|A list of things that need to be tackled]] <br />
* [[Wiki - New Device Copy & Paste Template|New Device Copy & Paste Template]]<br />
<br />
|valign=top bgcolor=#F7F9FB width=4%|<br />
|valign=top bgcolor=#F7F9FB width=32%|<br />
<br />
|}<br />
</div><br />
<br />
[[Category:LinuxTV]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=TV-Viewer&diff=28198TV-Viewer2010-11-15T16:27:26Z<p>Js: Reverted edits by Underwear001 (Talk) to last version by CityK</p>
<hr />
<div>An analogue TV viewing application for devices equipped with a hardware MPEG2 encoder. TV-Viewer achieves its functionality by utilizing [[MPlayer]] as its backend.<br />
<br />
==External Links==<br />
* [http://tv-viewer.sourceforge.net/mediawiki/index.php/Main_Page TV-Viewer Homepage]<br />
<br />
[[Category:Software]]<br />
[[Category:Apps & Utilities]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Iomega_BUZ&diff=28025Iomega BUZ2010-10-13T11:45:22Z<p>Js: Reverted edits by Anjila428 (Talk) to last version by Jimbley</p>
<hr />
<div>==Card Features==<br />
Inputs: Composite and S-video<br /><br />
Norms: PAL, SECAM (720x576 @ 25 fps), NTSC (720x480 @ 29.97 fps)<br />
<br />
=== Chipsets ===<br />
* Zoran zr36067 PCI controller<br />
* Zoran zr36060 MJPEG codec<br />
* Philips saa7111 TV decoder<br />
* Philips saa7185 TV encoder<br />
<br />
=== How to make it work ===<br />
Drivers to use: videodev, i2c-core, i2c-algo-bit, videocodec, saa7111, saa7185, zr36060, zoran<br /><br />
Card number: 7<br />
<br />
=== References ===<br />
[http://www.trix.com/buz/faq.html http://www.trix.com/buz/faq.html]<br />
[[Category:PCI]]<br />
[[Category:Analog]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=B2C2_FlexCop&diff=27977B2C2 FlexCop2010-09-28T17:22:05Z<p>Js: Reverted edits by MergeMac (Talk) to last version by Jimbley</p>
<hr />
<div>The FlexCop is a quite interesting and well-designed [[PCI interface chipsets|PCI interface chipset]] by [[B2C2 Inc.]]. The FlexCop/FlexCop2 family is comprised of the FlexCopII, FlexCopIIb and FlexCopIII variants. It is worthwhile to point out that the FlexCop ASICs have no analog input handling capabilities, but rather are designed strictly for digital receiver applications. These chips contain a flexible [[MPEG-2 Transport Stream]] interface with hardware [[PID]] filters which, if delivery of a complete Transport Stream payload is not desired, allow for the removal of unwanted packets from the stream, and thus reduce the bandwidth utilized when transferred across the host system bus. <br />
<br />
PID filtering is most useful in scenarios such as when recording one HD program (typically 14-17Mbps) from a 256-QAM stream (having a demodulated payload ~38.8Mbps), or when recording low resolution program streams from any given Transport Stream. In other scenarios, such as when recording an HD stream encoded with 8-VSB (~19.4Mbps), PID filtering is not as impactive in terms of the relative bandwidth savings, since the saved program usually constitutes most of the original Tranport Stream's bandwidth to begin with. The hardware filters impact may also be limited if in the case of collecting EIT data. <br />
<br />
As far we know the FlexCop chipsets contain a [[Smartcard interface]] and a [[CSA Descrambler]]. As the FlexCop tends to display some quirks in the [[I²C Protocol]] interface, the PCI bridge driver thus needs to know which clients are allowed on the bus in order to avoid lockups.<br />
<br />
The Linux driver works quite well and has no known drawbacks. Support for the IC's [[Smartcard Interface]] and [[CSA Descrambler]] features, however, are missing. <br />
<br />
The FlexCop family of chips can be found employed in several [[TechniSat]] DVB cards and USB devices.<br />
<br />
<br />
<br />
== External Links ==<br />
* [http://www.b2c2.com/ B2C2 Inc.]<br />
* [http://www.b2c2.com/docs/flexcop.pdf FlexCop PDF]<br />
<br />
[[Category:Chipsets]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Main_Page&diff=27676Main Page2010-08-18T08:30:51Z<p>Js: Reverted edits by Alice.thomas222 (Talk) to last version by CityK</p>
<hr />
<div>__NOTOC__<br />
__NOEDITSECTION__<br />
<br />
<div style="background-color:#6289AB; padding:0.3em; color:#ffffff; font-weight:bold; font-size:150%; text-align:center"><br />
Welcome to the linuxtv.org V4L-DVB Wiki !<br />
</div><br />
{|valign=top background=none<br />
|valign=top|<br />
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff"><br />
<br />
This wiki is intended to become an authoritative source of information regarding the use of analog video and digital TV sources under Linux -- i.e. the subject matters covered under the V4L-DVB framework. The basic plan is to aggregate information about: available hardware; how v4l or dvb work; software used with the hardware and so forth. <br />
Like all other wikis, the V4L-DVB wiki relies upon the contributions of its users. Hence, it will only be as useful as we make it! So we encourage you to share your knowledge and help with the task of turning this site into a grand repository of knowledge. Your input (whether it be by providing a set of instructions for how to get a certain device working; a minor improvement to an existing article; or an explanation for some complex concept) will be highly appreciated.<br />
<br />
-- [[LinuxTVWiki:People|The LinuxTV V4L-DVB wiki team]] / [[People behind V4L-DVB]]<br />
<br />
</div><br />
|}<br />
<br />
<br />
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff"><br />
{|valign=top cellpadding=0 cellspacing=5 width=100%<br />
| valign=top | [[Image:News_icon2.png|50px]] <br />
| '''GENERAL NEWS:''' <br><br />
'''Merger of Wikis Comes to a Close:''' After running some $47Million dollars over budget and 18 months late, the merger of the V4L and DVB wikis is finally complete! When asked about the glaring cost and time overruns, a well tanned project coordinator candidly replied that "there were, ummm, some issues", before hurrying away in a private limousine, escorted in arm by two, equally as tanned, attractive women, whom this reporter can only assume were the project's creative advisors. --23:10, 27 June 2010 (UTC)<br />
|-<br />
| || align=right| <small> ''For older news items see [[News Archive|here]]</small><br />
|}<br />
</div><br />
<br />
<br />
<br />
{| style="border: solid 1px; border-color:#6289AB; margin: oem; background-color: #6289AB;" cellspacing=5 cellpadding=1 width="100%"<br />
| valign=top |<br />
<br />
{| cellspacing=0 cellpadding=5 border=0 width="100%"<br />
<br />
<br />
| valign=top | [[Image:index.png|50px]]<br />
| valign=top | '''[[Special:Allpages|The Wiki's Indexes]]'''<br><small>Article, category, image, .... <br />
| valign=top ; style="background-color:#FFFFCC;" | [[Image:User_Info_icon.png|50px]]<br />
| valign=top ; style="background-color:#FFFFCC;" | '''[[User Information]]'''<br><small>How to install drivers for your hardware, and software to use with your device, ... <br />
| valign=top ; style="background-color:#F5DEB3;" | [[Image:Technical_background_icon.png|50px]]<br />
| valign=top ; style="background-color:#F5DEB3;" | '''[[Technical Background]]'''<br><small>Technical details on standards and hardware components/chipsets, etc<br />
|-<br />
|-<br />
|-<br />
<br />
| valign=top | [[Image:More_info.png|50px|]]<br />
| valign=top | '''[[Other Sources of Info]]'''<br><small>Mailing lists, #irc channels....<br />
| valign=top ; style="background-color:#FFFFCC;" | [[Image:Hardware_icon.png|50px]]<br />
| valign=top ; style="background-color:#FFFFCC;" | '''[[Hardware Device Information]]'''<br><small>Information on hardware devices <br />
| valign=top ; style="background-color:#F5DEB3;" | [[Image:Developer_icon.png|50px]]<br />
| valign=top ; style="background-color:#F5DEB3;" | '''[[Developer Section]]'''<br><small>Information to help device driver development<br />
|-<br />
|-<br />
|-<br />
<br />
|}<br />
|}<br />
<br />
<br />
<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;"><br />
{|valign=top cellpadding=0 cellspacing=0 width=100%<br />
|valign=top bgcolor=#F7F9FB width=32%|<br />
=='''The Wiki - How Can I Help?'''==<br />
* [[Help:Contents|Everything you need to know about editing wiki pages but were afraid to ask]]<br />
** [http://www.mediawiki.org/wiki/Help:Moving_a_page Help: Renaming/Moving a Page]<br />
* [[Wiki - Help Wanted List|A list of things that need to be tackled]] <br />
* [[Wiki - New Device Copy & Paste Template|New Device Copy & Paste Template]]<br />
<br />
|valign=top bgcolor=#F7F9FB width=4%|<br />
|valign=top bgcolor=#F7F9FB width=32%|<br />
<br />
|}<br />
</div><br />
<br />
[[Category:LinuxTV]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Main_Page&diff=27122Main Page2010-04-23T04:54:35Z<p>Js: </p>
<hr />
<div>__NOTOC__<br />
__NOEDITSECTION__<br />
<br />
<div style="background-color:#6289AB; padding:0.3em; color:#ffffff; font-weight:bold; font-size:150%; text-align:center"><br />
Welcome to the linuxtv.org V4L-DVB Wiki !<br />
</div><br />
{|valign=top background=none<br />
|valign=top|<br />
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff"><br />
<br />
This wiki is intended to become an authoritative source of information regarding the use of analog video and digital TV sources under Linux -- i.e. the subject matters covered under the V4L-DVB framework. The basic plan is to aggregate information about: available hardware; how v4l or dvb work; software used with the hardware and so forth. <br />
Like all other wikis, the V4L-DVB wiki relies upon the contributions of its users. Hence, it will only be as useful as we make it! So we encourage you to share your knowledge and help with the task of turning this site into a grand repository of knowledge. Your input (whether it be by providing a set of instructions for how to get a certain device working; a minor improvement to an existing article; or an explanation for some complex concept) will be highly appreciated.<br />
<br />
-- [[LinuxTVWiki:People|The LinuxTV V4L-DVB wiki team]] / [[People behind V4L-DVB]]<br />
<br />
</div><br />
|}<br />
<br />
<br />
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff"><br />
{|valign=top cellpadding=0 cellspacing=5 width=100%<br />
| [[Image:Exclaimation.png|75px]] <br />
| '''IMPORTANT NOTICE:''' Hi everyone, the merger of the V4L and DVB wikis is now underway! Articles within the [http://www.linuxtv.org/v4lwiki/index.php/Main_Page V4L wiki] will progressively be transferred into this wiki. Please see [[Wiki merger|here for the important details]].<br />
|}<br />
</div><br />
<br />
<br />
<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;"><br />
{|valign=top cellpadding=0 cellspacing=0 width=100%<br />
|valign=top bgcolor=#F7F9FB width=32%|<br />
== '''User Section:'''==<br />
* [[Special:Allpages|The Wiki's Indexes]]<br />
'''Getting Started:'''<br />
* [[What is V4L or DVB?]]<br />
* [[Supported Hardware]]<br />
* [[How to Obtain, Build and Install V4L-DVB Device Drivers]]<br />
** Driver List<br />
'''Having Trouble?:'''<br />
* [[FAQ & Troubleshooting]]<br />
* [[Testing your DVB device]] (PCI, USB, ...)<br />
* [[V4L Test Suite]]<br />
* [[Testing reception quality]]<br />
* [[Bug Report|Filing a Bug Report]]<br />
'''Software Applications and Usage:''' <br />
* ''Applications to watch and record TV''<br />
** [[software#Standalone_Software_to_Watch_Digital_TV|Software to Watch Digital TV]]<br />
** [[Software#Standalone_Software_to_Watch_Analogue_TV|Software to Watch Analogue TV]] ... also see [[V4L TV Viewing]] <br />
** [[V4L capturing]] ... also see [[Transcode]]<br />
* [[software#Media_Center_Software|Full Media Centers]]<br />
* [[software#DVB_Utility_Suites_or_Standalone_Tools|Applications to show Videotext/Teletext/Closed Captioning]]<br />
** [[Text capture]]<br />
* [[software#DVB_Utility_Suites_or_Standalone_Tools|Tools for testing, tuning, streaming]]<br />
* [[software#DVB_Utility_Suites_or_Standalone_Tools|Tools for unattended/headless recording]]<br />
* [[Radio Listening Applications|Radio Listening]]<br />
'''Tutorials, Howtos, Usage Info & Guides:'''<br />
* Howto record [[multiple programs]] at once<br />
* [[Post-processing]] of recorded material<br />
* [[Further V4L and DVB Links]]<br />
'''Examples of User Hardware and Software Configurations:'''<br />
* [[Example setups]]<br />
* [[Mailing List survey of devices in use]]<br />
* [[Conditional Access Module Usage Examples]] (sorted by country)<br />
* [[User Modifications to Supported Devices]]<br />
<br />
<br />
=='''The Wiki - How Can I Help?'''==<br />
* [[Help:Contents|Everything you need to know about editing wiki pages but were afraid to ask]]<br />
** [http://www.mediawiki.org/wiki/Help:Moving_a_page Help: Renaming/Moving a Page]<br />
* [[Wiki - Help Wanted List|A list of things that need to be tackled]] <br />
* [[Wiki - New Device Copy & Paste Template|New Device Copy & Paste Template]]<br />
<br />
|valign=top bgcolor=#F7F9FB width=4%|<br />
|valign=top bgcolor=#F7F9FB width=32%|<br />
=='''Technical Background:'''==<br />
'''Systems:'''<br />
* [[Analog TV]]<br />
* [[Radio Data System (RDS)]]<br />
* [[Digital TV|Digital TV (DTV)]]<br />
** [[ATSC|ATSC Standards]]<br />
** [[DVB Standards]]<br />
** [[DMB-T/H|DMB-T/H Standard]]<br />
** [[ISDB|ISDB Standards]]<br />
* [[Modulation Scheme]]s used for Analog & DTV<br />
* [[MPEG-2 Standard]]<br />
** [[DSM-CC Object Carousel Protocol]]<br />
* [[DiSEqC|DiSEqC Protocols]]<br />
'''Hardware Component Related:'''<br />
* [[List of Chipset Vendors|Sortable List of Chipset Vendors]]<br />
* [[Anatomy of V4L-DVB devices]]<br />
** [[Tuner]]s<br />
** [[Demodulator]]s<br />
** [[A/V Decoders]]<br />
*** [[Radio devices|Radio Decoder Chipsets]]<br />
** [[GPIO pins]]<br />
** [[I²C Protocol]]<br />
** [[Hardware or Software Decoder?]] (MPEG)<br />
** [[Hardware vs software encoders]] (MPEG)<br />
** [[Remote Controller chipsets]]<br />
** [[Interface chipsets]]<br />
<br />
<br />
== '''Developer Section:'''==<br />
'''Repos:'''<br />
* [http://git.linuxtv.org/v4l-dvb.git Git V4L-DVB development repository]<br />
* [http://linuxtv.org/hg/v4l-dvb Mercurial V4L-DVB backport repository]<br />
* [http://git.linuxtv.org/ A list of LinuxTV hosted Git development repositories]<br />
* [http://linuxtv.org/hg/ A list of LinuxTV hosted Mercurial development repositories]<br />
* [http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/mchehab/v4l-dvb.git;a=log Current git log]<br />
* [[Maintaining Git trees]]<br />
* [[Using a git driver development tree]]<br />
* [[Maintaining Mercurial (Hg) trees]]<br />
'''Kernel Driver Development:'''<br />
* [http://jungla.dit.upm.es/%7Ejmseyas/linux/kernel/hackers-docs.html Linux kernel development documentation index]<br />
* ''Application Programming Interface (API):''<br />
** [[Development: Linux Media Infrastructure API|Linux Media Infrastructure API]]<br />
* ''Drivers:''<br />
** [[Anatomy of a V4L driver]]<br />
** [[Anatomy of a DVB driver]]<br />
** [[Development: How to add support for a device|How to add support for a device]]<br />
** [[Development: How to develop drivers for USB based devices|How to develop drivers for USB based devices]]<br />
*** [[DVB via USB|General Information Regarding DVB via USB]]<br />
*** [[Development: Reverse Engineering USB Webcams|Reverse Engineering USB Webcams]]<br />
** [[Development: Hints for Refactoring Existing Drivers|Hints for Refactoring Existing Drivers]]<br />
* ''Submitting your work:''<br />
** [[Development: Coding Style|Coding Style]]<br />
** [[Development: Code Review|Invitation for Code Review]]<br />
** [[Development: How_to_submit_patches |How to submit patches]]<br />
*** [[Development: Submitting Patches|Rules for submitting patches]]<br />
*** [[Development: Linux Kernel patch submittal checklist|Linux Kernel patch submittal checklist]]<br />
*** [[Development: Submitting Drivers|Rules for submitting drivers]]<br />
* ''Development miscellanea:''<br />
** [[Bus snooping/sniffing]]<br />
** [[Development: How to extract a firmware|How to extract a firmware]]<br />
** [[Development: The DVB Decoder Challenge|The DVB Decoder Challenge]]<br />
** [[TODO - main tasks]]<br />
** [[V4L framework progress]]<br />
** [[Libv4l Progress]]<br />
'''Userspace Development:'''<br />
* [[V4L2 Userspace Library]]<br />
<br />
|valign=top bgcolor=#F7F9FB width=4%|<br />
|valign=top bgcolor=#F7F9FB width=32%|<br />
=='''Hardware Device Information:'''==<br />
* [[List of Device Vendors|Sortable List of Device Vendors]]<br />
'''Analogue Devices (V4L):'''<br />
* [[Graphics cards with TV Tuner and/or Capture facilities]]<br />
* [[Video via PCI]]<br />
* [[Video via PCI Express (PCIe)]]<br />
* [[Video via USB]]<br />
* ''Other analogue devices:''<br />
** [[V4L IEEE1394 devices|IEEE1394 devices]] (aka FireWire or i.LINK)<br />
** [[Loopback]]<br />
** [[Radio devices|Radio]]<br />
** [[Scanners]]<br />
** [[Webcams]]<br />
'''Digital Devices (DVB):'''<br />
* [[ATSC Devices]]<br />
* [[DMB-T/H Devices]]<br />
* [[DVB-C Devices]]<br />
* [[DVB-S Devices]]<br />
* [[DVB-S2 Devices]]<br />
* [[8-PSK Turbo Coded Devices]]<br />
* [[DVB-T Devices]]<br />
* [[ISDB-T Devices]]<br />
* [[Pre-configured DVB Systems and Set Top Hardware]]''<br />
'''Peripheral Components:'''<br />
* [[Antenna]]s (Rooftop, Indoor, Satellite Dishes) <br />
* [[DD receiver|Dolby Digital receiver]]<br />
* [[DiSEqC related hardware]]<br />
** Switches, attenuators, and amplifiers<br />
* [[DVB Conditional Access Modules]]<br />
* [[Remote Controllers]]<br />
** [[Remote controllers-V4L|Remote controllers (V4L article)]]<br />
<br />
|}<br />
</div><br />
<br />
[[Category:LinuxTV]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Main_Page&diff=26703Main Page2010-02-17T20:34:59Z<p>Js: Reverted edits by Manu (Talk) to last version by Nmarci</p>
<hr />
<div>__NOTOC__<br />
__NOEDITSECTION__<br />
<br />
<div style="background-color:#6289AB; padding:0.3em; color:#ffffff; font-weight:bold; font-size:150%; text-align:center"><br />
Welcome to the linuxtv.org V4L-DVB Wiki !<br />
</div><br />
{|valign=top background=none<br />
|valign=top|<br />
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff"><br />
<br />
This wiki is intended to become an authoritative source of information regarding the use of analog video and digital TV sources under Linux -- i.e. the subject matters covered under the V4L-DVB framework. The basic plan is to aggregate information about: available hardware; how v4l or dvb work; software used with the hardware and so forth. <br />
<br />
Like all other wikis, the V4L-DVB wiki relies upon the contributions of its users. Hence, it will only be as useful as we make it! So we encourage you to share your knowledge and help with the task of turning this site into a grand repository of knowledge. Your input (whether it be by providing a set of instructions for how to get a certain device working; a minor improvement to an existing article; or an explanation for some complex concept) will be highly appreciated.<br />
<br />
-- [[LinuxTVWiki:People|The LinuxTV V4L-DVB wiki team]] / [[People behind V4L-DVB]]<br />
<br />
</div><br />
|}<br />
<br />
<br />
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff"><br />
{|valign=top cellpadding=0 cellspacing=5 width=100%<br />
| [[Image:Exclaimation.png|75px]] <br />
| '''IMPORTANT NOTICE:''' Hi everyone, the merger of the V4L and DVB wikis is now underway! Articles within the [http://www.linuxtv.org/v4lwiki/index.php/Main_Page V4L wiki] will progressively be transferred into this wiki. Please see [[Wiki merger|here for the important details]].<br />
|}<br />
</div><br />
<br />
<br />
<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;"><br />
{|valign=top cellpadding=0 cellspacing=0 width=100%<br />
|valign=top bgcolor=#F7F9FB width=32%|<br />
== '''User Section:'''==<br />
* [[Special:Allpages|The Wiki's Indexes]]<br />
'''Getting Started:'''<br />
* [[What is V4L or DVB?]]<br />
* [[Supported Hardware]]<br />
* [[How to Obtain, Build and Install V4L-DVB Device Drivers]]<br />
** Driver List<br />
'''Having Trouble?:'''<br />
* [[FAQ & Troubleshooting]]<br />
* [[Testing your DVB device]] (PCI, USB, ...)<br />
* [[V4L Test Suite]]<br />
* [[Testing reception quality]]<br />
* [[Bug Report|Filing a Bug Report]]<br />
'''Software Applications and Usage:''' <br />
* ''Applications to watch and record TV''<br />
** [[software#Standalone_Software_to_Watch_Digital_TV|Software to Watch Digital TV]]<br />
** [[Software#Standalone_Software_to_Watch_Analogue_TV|Software to Watch Analogue TV]] ... also see [[V4L TV Viewing]] <br />
** [[V4L capturing]] ... also see [[Transcode]]<br />
* [[software#Media_Center_Software|Full Media Centers]]<br />
* [[software#DVB_Utility_Suites_or_Standalone_Tools|Applications to show Videotext/Teletext/Closed Captioning]]<br />
** [[Text capture]]<br />
* [[software#DVB_Utility_Suites_or_Standalone_Tools|Tools for testing, tuning, streaming]]<br />
* [[software#DVB_Utility_Suites_or_Standalone_Tools|Tools for unattended/headless recording]]<br />
* [[Radio Listening Applications|Radio Listening]]<br />
'''Tutorials, Howtos, Usage Info & Guides:'''<br />
* Howto record [[multiple programs]] at once<br />
* [[Post-processing]] of recorded material<br />
* [[Further V4L and DVB Links]]<br />
'''Examples of User Hardware and Software Configurations:'''<br />
* [[Example setups]]<br />
* [[Mailing List survey of devices in use]]<br />
* [[Conditional Access Module Usage Examples]] (sorted by country)<br />
* [[User Modifications to Supported Devices]]<br />
<br />
<br />
=='''The Wiki - How Can I Help?'''==<br />
* [[Help:Contents|Everything you need to know about editing wiki pages but were afraid to ask]]<br />
** [http://www.mediawiki.org/wiki/Help:Moving_a_page Help: Renaming/Moving a Page]<br />
* [[Wiki - Help Wanted List|A list of things that need to be tackled]] <br />
* [[Wiki - New Device Copy & Paste Template|New Device Copy & Paste Template]]<br />
<br />
|valign=top bgcolor=#F7F9FB width=4%|<br />
|valign=top bgcolor=#F7F9FB width=32%|<br />
=='''Technical Background:'''==<br />
'''Systems:'''<br />
* [[Analog TV]]<br />
* [[Radio Data System (RDS)]]<br />
* [[Digital TV|Digital TV (DTV)]]<br />
** [[ATSC|ATSC Standards]]<br />
** [[DVB Standards]]<br />
** [[DMB-T/H|DMB-T/H Standard]]<br />
** [[ISDB|ISDB Standards]]<br />
* [[Modulation Scheme]]s used for Analog & DTV<br />
* [[MPEG-2 Standard]]<br />
** [[DSM-CC Object Carousel Protocol]]<br />
* [[DiSEqC|DiSEqC Protocols]]<br />
'''Hardware Component Related:'''<br />
* [[List of Chipset Vendors|Sortable List of Chipset Vendors]]<br />
* ''Anatomy of a V4L-DVB device''<br />
** [[Anatomy of a V4L device]]<br />
** [[Anatomy of a DVB device]]<br />
** [[Tuner]]s<br />
** [[Demodulator]]s<br />
** [[Interface chipsets]]<br />
** [[Radio devices|Radio Chipsets]]<br />
** [[GPIO pins]]<br />
** [[I²C Protocol]]<br />
** [[Hardware or Software Decoder?]]<br />
** [[Hardware vs software encoders]] <br />
** [[Remote Controllers]]<br />
<br />
<br />
== '''Developer Section:'''==<br />
'''Repos:'''<br />
* [http://linuxtv.org/hg/v4l-dvb Master V4L-DVB development repository]<br />
* [http://linuxtv.org/hg/ A list of LinuxTV hosted V4L-DVB development repositories]<br />
* [http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/mchehab/v4l-dvb.git;a=log Current git log]<br />
* [[Maintaining Git trees]]<br />
* [[Maintaining Mercurial (Hg) trees]]<br />
'''Kernel Driver Development:'''<br />
* [http://jungla.dit.upm.es/%7Ejmseyas/linux/kernel/hackers-docs.html Linux kernel development documentation index]<br />
* ''Application Programming Interface (API):''<br />
** [[Development: Linux Media Infrastructure API|Linux Media Infrastructure API]]<br />
* ''Drivers:''<br />
** [[Anatomy of a V4L driver]]<br />
** [[Anatomy of a DVB driver]]<br />
** [[Development: How to add support for a device|How to add support for a device]]<br />
** [[Development: How to develop drivers for USB based devices|How to develop drivers for USB based devices]]<br />
*** [[DVB via USB|General Information Regarding DVB via USB]]<br />
*** [[Development: Reverse Engineering USB Webcams|Reverse Engineering USB Webcams]]<br />
** [[Development: Hints for Refactoring Existing Drivers|Hints for Refactoring Existing Drivers]]<br />
* ''Submitting your work:''<br />
** [[Development: Coding Style|Coding Style]]<br />
** [[Development: Code Review|Invitation for Code Review]]<br />
** [[Development: How_to_submit_patches |How to submit patches]]<br />
*** [[Development: Submitting Patches|Rules for submitting patches]]<br />
*** [[Development: Linux Kernel patch submittal checklist|Linux Kernel patch submittal checklist]]<br />
*** [[Development: Submitting Drivers|Rules for submitting drivers]]<br />
* ''Development miscellanea:''<br />
** [[Bus snooping/sniffing]]<br />
** [[Development: How to extract a firmware|How to extract a firmware]]<br />
** [[Development: The DVB Decoder Challenge|The DVB Decoder Challenge]]<br />
** [[TODO - main tasks]]<br />
** [[Libv4l Progress]]<br />
'''Userspace Development:'''<br />
* [[V4L2 Userspace Library]]<br />
<br />
|valign=top bgcolor=#F7F9FB width=4%|<br />
|valign=top bgcolor=#F7F9FB width=32%|<br />
=='''Hardware Device Information:'''==<br />
* [[List of Device Vendors|Sortable List of Device Vendors]]<br />
'''Analogue Devices (V4L):'''<br />
* ''Graphics cards with TV Tuner and/or Capture facilities:''<br />
** [[ATI/AMD#ATI Graphic cards with_TV Tuners and/or Capture facilities|ATI/AMD based combo cards]]<br />
** [[RivaTV|NVIDIA based combo cards]]<br />
** [[3Dfx Interactive|3Dfx Voodoo3 3500 TV]]<br />
* ''Video via PCI:''<br />
** [[Bttv devices (bt848, bt878)]]<br />
** [[cx18 devices (cx23418)]]<br />
** [[cx88 devices (cx2388x)]]<br />
** [[ivtv devices (cx23415, cx23416)]]<br />
** [[Matrox Meteor II cards]] (not working)<br />
** [[saa713x devices]]<br />
** [[saa7146 devices]]<br />
** [[zoran devices (zr36057, zr36067)|zr360x7 devices (zr36057, zr36067)]]<br />
** [[zr3612x devices]]<br />
* ''Video via PCI Express (PCIe):''<br />
** [[nGene devices]] (not supported)<br />
** [[saa7162 devices]] (will be supported)<br />
* ''Video via USB:''<br />
** [[DiBcom USB devices]]<br />
** [[Em28xx devices]]<br />
** [[OmniVision USB devices (OV511, etc)]]<br />
** [[PixArt PAC7301/PAC7302]]<br />
** [[Pvrusb2|pvrusb2 devices]] <br />
** [[Rtl2831_devices]]<br />
** [[Trident TM6000#TM6000 based Devices|TM60x0 based devices]]<br />
** [[USBVision devices]]<br />
* ''Other devices:''<br />
** [[V4L IEEE1394 devices|IEEE1394 devices]] (aka FireWire or i.LINK)<br />
** [[Loopback]]<br />
** [[Radio devices|Radio]]<br />
** [[Remote controllers-V4L|Remote controllers]]<br />
** [[Scanners]]<br />
** [[Webcams]]<br />
'''Digital Devices (DVB):'''<br />
* ''Some descriptive name for the section''<br />
** [[ATSC Devices]]<br />
** [[DMB-T/H Devices]]<br />
** [[DVB-C Devices]]<br />
** [[DVB-S Devices]]<br />
** [[DVB-S2 Devices]]<br />
** [[8-PSK Turbo Coded Devices]]<br />
** [[DVB-T Devices]]<br />
** [[ISDB-T Devices]]<br />
<br />
* ''Pre-configured DVB Systems and Set Top Hardware:''<br />
** [[Barebones and bundles]]<br />
** [[Commercial solutions]]<br />
*** [[VDR-based STBs]]<br />
*** [[MythTV STBs]]<br />
*** [[Enigma on the dbox2]]<br />
*** [[Neutrino on the dbox2]]<br />
*** [[Enigma on the Dreambox]]<br />
** [[Streaming clients]]<br />
* ''Peripheral Components:''<br />
** [[DD receiver|Dolby Digital receiver]]<br />
** [[DiSEqC related hardware]]<br />
** [[DVB Conditional Access Modules]]<br />
** [[Antenna]]s (Rooftop, Indoor, Satellite Dishes) <br />
** [[Remote Controllers]]<br />
** Switches, attenuators, and amplifiers<br />
<br />
|}<br />
</div><br />
<br />
[[Category:LinuxTV]]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Archived:Main_Page-V4L&diff=24625Archived:Main Page-V4L2009-05-13T21:37:02Z<p>Js: Reverted edits by Mazyy (Talk); changed back to last version by CityK</p>
<hr />
<div>__NOTOC__<br />
__NOEDITSECTION__<br />
<br />
<div style="background-color:#006600; padding:0.3em; color:#ffffff; font-weight:bold; font-size:150%; text-align:center"><br />
Welcome to the video4linux wiki (For DVB wiki, click [http://www.linuxtv.org/wiki here])<br />
</div><br />
<br />
{|valign=top background=none<br />
|valign=top|<br />
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff"><br />
<br />
This wiki is designed to serve as a community focus and the resource of reference for users and developers of the Video4Linux framework. In the short term, the task is to document the operation and quirks of hardware supported by v4l applications, to complement and offload the [https://listman.redhat.com/mailman/listinfo/video4linux-list v4l mailing list] -- cf. [http://marc.theaimsgroup.com/?l=linux-video searchable archives].<br />
<br />
We are also encouraging developers to turn this site into a repository of knowledge about v4l, helping to ensure that expertise acquired through much hard labor and long dedication won't get lost, but can be passed on to new developers and keep free software thriving.<br />
<br />
If you are a user looking for help, please try searching the [http://marc.theaimsgroup.com/?l=linux-video mailing list archives] first, before asking a question on the [https://listman.redhat.com/mailman/listinfo/video4linux-list v4l mailing list]. Don't leave your question on the wiki -- ask on the mailing list!<br />
<br />
For immediate help, log on to the #v4l irc channel on irc.freenode.net a try (see the [http://linuxtv.org/irc/v4l/ log]) -- hopefully someone there will be able to help you! <br />
<br />
The wiki will only be as useful as we make it. Every user of video4linux has something to contribute, and we encourage you to begin right away. Whatever you can contribute will be warmly appreciated, whether it is a set of instructions for how to get a certain card working, a report on the audio and video quality of a working card, suggestions for how to extend an existing driver or write a new one, or an explanation of the internal logic of v4l itself.<br />
<br />
To keep these instructions free, all contributions to this wiki are automatically licensed under the GNU General Public License [http://www.gnu.org/copyleft/gpl.html GPL]. If you wish, you may specify in each case that your contribution is dual-licensed under the [http://www.opensource.org/licenses/mit-license.html MIT License]. Please help us keep spam away by signing in before you post.<br />
<br />
Enjoy!<br />
<br />
[[People behind V4L]]<br />
<br />
<br />
'''To make a contribution, please begin by familiarizing yourself with the layout of the site, so that your contribution will end up in the right location. As the site grows, it takes increasing discipline to keep it from turning into a tangle. We want to aggregate information about available hardware, v4l experiences, HOWTOs, and technical information about the workings of v4l devices work, and it's up to each of us to do this in a way that makes the information easy to access -- a useful and well-organized resource for everyone interested in video4linux.<br />
</div><br />
|}<br />
<br />
<br />
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff"><br />
{|valign=top cellpadding=0 cellspacing=5 width=100%<br />
| [[Image:Exclaimation.png|75px]] <br />
| '''IMPORTANT NOTICE:''' Hi everyone, the merger of the V4L and DVB wikis is now underway! Articles within this wiki will progressively be transferred into the [http://www.linuxtv.org/wiki/index.php/Main_Page LinuxTV wiki]. Please see [[Wiki merger|here for the important details]].<br />
|}<br />
</div><br />
<br />
<br />
<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;"><br />
{|valign=top cellpadding=0 cellspacing=0 width=100%<br />
|valign=top bgcolor=#F7F9FB width=5%|<br />
|valign=top bgcolor=#F7F9FB width=45%|<br />
<br />
* '''User Section'''<br />
** [[How to build from Mercurial|How to build drivers from Mercurial]]<br />
** [[How to write good problem report |How to write a good problem report]]<br />
*** [[Test Suite]]<br />
** Software Applications:<br />
*** [[TV Viewing]]<br />
*** [[TV Recording]] <br />
*** [[Streaming]]<br />
*** [[Text capture]] (Teletext/Closed Captioning)<br />
*** [[Radio Listening Applications|Radio Listening]]<br />
** [[v4l Links]]<br />
<br />
<br />
* '''Technical Background<br />
** Systems:<br />
*** [[Analog TV]]<br />
*** [[Digital TV]]<br />
*** [[Radio Data System (RDS)]]<br />
** Hardware Related:<br />
*** [[Anatomy of a v4l device]]<br />
**** [[PCI interface chipsets used for v4l cards]]<br />
**** [[GPIO pins]]<br />
**** [[i2c Protocol]]<br />
**** [[Hardware vs software encoders]] <br />
**** [[Audio Decoders]]<br />
<br />
<br />
* '''Developer Section'''<br />
** Kernel Development:<br />
*** [[Anatomy of a v4l driver]]<br />
*** [[Development: How to add support for a device|How to add support for a device]]<br />
*** [[Development: USB based video drivers|USB based video drivers]] <br />
*** [[SubmittingPatches | Rules for submitting patches]]<br />
*** [[Development: How_to_submit_patches |How to submit patches]]<br />
*** [[Documentation/SubmittingDrivers | Rules for submitting drivers]]<br />
*** [[Documentation/CodingStyle | Coding Style]]<br />
*** [[Documentation index]]<br />
*** [[TODO - main tasks]]<br />
** Userspace Development:<br />
*** [[V4L2UserspaceLibrary|V4L2 Userspace library]]<br />
<br />
<br />
|valign=top bgcolor=#F7F9FB width=45%|<br />
* '''Supported Hardware'''<br />
** Graphics cards with TV Tuner and/or Capture facilities:<br />
*** [[ATI/AMD#ATI Graphic cards with_TV Tuners and/or Capture facilities|ATI/AMD based combo cards]]<br />
*** [[RivaTV|NVIDIA based combo cards]]<br />
** TV cards and drivers:<br />
*** [[v4l card vendors]]<br />
*** [[List survey of cards in use now]]<br />
*** [[Tuners: Supported Tuners|Supported Tuners]]<br />
*** Video via PCI:<br />
**** [[bttv devices (bt848, bt878)]]<br />
***** [[bttv kernel options]] documentation<br />
***** [[btaudio (bt878)]]<br />
***** [[snd-bt87x (alsa bt878 driver)]]<br />
**** [[cx88 devices (cx2388x) ]]<br />
**** [[ivtv devices (cx23415, cx23416)]]<br />
**** [[cx18 devices (cx23418)]]<br />
**** [[Matrox Meteor II cards]] (not working)<br />
**** [[saa713x devices]]<br />
***** [[saa7134-alsa]]<br />
**** [[saa7146 devices]]<br />
**** [[zoran devices (zr36057, zr36067)]]<br />
**** [[zoran devices (zr36120, zr36125)]]<br />
*** Video via PCI Express:<br />
**** [[nGene devices]] (not supported)<br />
**** [[saa7162 devices]] (will be supported)<br />
*** Video via USB:<br />
**** [[Hauppauge PVRUSB2]] (not to be confused with the wintv-usb2)<br />
**** [[DiBcom USB devices]]<br />
**** Em2820 <br />
**** [[Em28xx devices]] <br />
**** [[OmniVision USB devices (OV511, etc)]]<br />
**** [[Trident TM6000#TM6000 based Devices|TM6000 based devices]]<br />
**** [[USBVision devices]]<br />
** Other devices:<br />
*** [[Firewire devices|Firewire]]<br />
*** [[Loopback]]<br />
*** [[Radio devices|Radio]]<br />
*** [[Remote controllers]]<br />
*** [[Scanners]]<br />
*** [[Webcams]]<br />
<br />
<br />
|}<br />
</div><br />
<br />
[http://linuxtv.org Category:LinuxTV]</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Development:_Submitting_Drivers&diff=17389Development: Submitting Drivers2008-10-21T09:06:26Z<p>Js: Reverted edits by Kz1Lg2 (Talk); changed back to last version by Js</p>
<hr />
<div>This article is intended to explain how to submit device drivers to the various development trees of the Linux kernel. Note that if you are interested in video card drivers you should probably talk to [http://x.org/ X.Org] and/or [http://www.xfree86.org/ XFree86] instead.<br />
<br />
Also read the [[SubmittingPatches|Documentation/SubmittingPatches]] document.<br />
<br />
<br />
== Allocating Device Numbers ==<br />
Major and minor numbers for block and character devices are allocated by the Linux assigned name and number authority (currently better known as H Peter Anvin). The site is http://www.lanana.org/. This also deals with allocating numbers for devices that are not going to be submitted to the mainstream kernel.<br />
<br />
If you don't use assigned numbers then when you device is submitted it will get given an assigned number even if that is different from values you may<br />
have shipped to customers before.<br />
<br />
<br />
== Who To Submit Drivers To ==<br />
;Linux 2.0: No new drivers are accepted for this kernel tree<br />
<br />
;Linux 2.2: If the code area has a general maintainer then please submit it to the maintainer listed in MAINTAINERS in the kernel file. If the maintainer does not respond or you cannot find the appropriate maintainer then please contact Alan Cox <alan@lxorguk.ukuu.org.uk><br />
<br />
;Linux 2.4: The same rules apply as 2.2. The final contact point for Linux 2.4 submissions is Marcelo Tosatti <marcelo.tosatti@cyclades.com>.<br />
<br />
;Linux 2.6: The same rules apply as 2.4 except that you should follow linux-kernel to track changes in API's. The final contact point for Linux 2.6 submissions is Andrew Morton <akpm@osdl.org>.<br />
<br />
<br />
== What Criteria Determine Acceptance ==<br />
;Licensing: The code must be released to us under the GNU General Public License. We don't insist on any kind of exclusively GPL licensing, and if you wish the driver to be useful to other communities such as BSD you may well wish to release under multiple licenses.<br />
<br />
;Copyright: The copyright owner must agree to use of GPL. It's best if the submitter and copyright owner are the same person/entity. If not, the name of the person/entity authorizing use of GPL should be listed in case it's necessary to verify the will of the copright owner.<br />
<br />
:Interfaces: If your driver uses existing interfaces and behaves like other drivers in the same class it will be much more likely to be accepted than if it invents gratuitous new ones. If you need to implement a common API over Linux and NT drivers do it in userspace.<br />
<br />
;Code: Please use the Linux style of code formatting as documented in Documentation/CodingStyle. If you have sections of code that need to be in other formats, for example because they are shared with a windows driver kit and you want to maintain them just once separate them out nicely and note this fact.<br />
<br />
;Portability: Pointers are not always 32bits, not all computers are little endian, people do not all have floating point and you shouldn't use inline x86 assembler in your driver without careful thought. Pure x86 drivers generally are not popular. If you only have x86 hardware it is hard to test portability but it is easy to make sure the code can easily be made portable.<br />
<br />
;Clarity: It helps if anyone can see how to fix the driver. It helps you because you get patches not bug reports. If you submit a driver that intentionally obfuscates how the hardware works it will go in the bitbucket.<br />
<br />
;Control: In general if there is active maintainance of a driver by the author then patches will be redirected to them unless they are totally obvious and without need of checking. If you want to be the contact and update point for the driver it is a good idea to state this in the comments, and include an entry in MAINTAINERS for your driver.<br />
<br />
<br />
== What Criteria Do Not Determine Acceptance ==<br />
<br />
;Vendor: Being the hardware vendor and maintaining the driver is often a good thing. If there is a stable working driver from other people already in the tree don't expect 'we are the vendor' to get your driver chosen. Ideally work with the existing driver author to build a single perfect driver. <br />
<br />
;Author: It doesn't matter if a large Linux company wrote the driver, or you did. Nobody has any special access to the kernel tree. Anyone who tells you otherwise isn't telling the whole story.<br />
<br />
== Resources ==<br />
;Linux kernel master tree: ftp.??.kernel.org:/pub/linux/kernel/...<br> where ?? is your country code, such as "us", "uk", "fr", etc.<br />
<br />
;Linux kernel mailing list: linux-kernel@vger.kernel.org <br> [mail majordomo@vger.kernel.org to subscribe]<br />
<br />
;Linux Device Drivers, Third Edition (covers 2.6.10): http://lwn.net/Kernel/LDD3/ (free version)<br />
<br />
;Kernel traffic [http://www.kerneltraffic.org/kernel-traffic/]: Weekly summary of kernel list activity (much easier to read)<br />
<br />
;LWN.net [http://lwn.net/]: Weekly summary of kernel development activity <br> * [http://lwn.net/Articles/2.6-kernel-api/ 2.6 API changes] <br> * [http://lwn.net/Articles/driver-porting/ Porting drivers from prior kernels to 2.6] <br />
<br />
;KernelTrap [http://kerneltrap.org/]: Occasional Linux kernel articles and developer interviews<br />
<br />
; KernelNewbies [http://kernelnewbies.org/]: Documentation and assistance for new kernel programmers<br />
<br />
;Linux USB project [http://sourceforge.net/projects/linux-usb/]: Helpful for the development of USB based device drivers</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Maintaining_Mercurial_(Hg)_trees&diff=17190Maintaining Mercurial (Hg) trees2008-10-21T09:06:19Z<p>Js: Reverted edits by SreHz3 (Talk); changed back to last version by Mkrufky</p>
<hr />
<div>== The history of VCS for v4l ==<br />
<br />
Up until 2006-01-30, the source code for the v4l kernel modules was available via CVS; cf. [http://linuxtv.org/cgi-bin/viewcvs.cgi/?root=v4l v4l CVS root]. There are old snapshots available from [http://www.linuxtv.org/downloads/video4linux/ June to November 2005]. Before that, the code was housed at [http://dl.bytesex.org/patches/ Gerd Knorr's site].<br />
<br />
As of 2006-01-30, V4L and DVB kernel modules are available via [http://www.selenic.com/mercurial/wiki/index.cgi Mercurial], a lightweight Source Control Management system. See the current [http://linuxtv.org/repo/ instructions for source access]. <br />
<br />
== Notes for maintainers ==<br />
<br />
(See also file README.HG in the sources)<br />
<br />
Current V4L/DVB tree uses a modern SCM system that fits better into <br />
kernel development model, called Mercurial (aka hg).<br />
<br />
There are some tutorials, FAQs and other valuable informations at<br />
http://selenic.com/mercurial<br />
<br />
Mercurial is a distributed SCM, which means every developer gets his <br />
own full copy of the repository (including the complete revision <br />
history), and can work and commit locally without network connection. <br />
The resulting changesets can then be exchanged between repositories and <br />
finally published to the master repository in linuxtv.org. A list of<br />
current available repositories is available at: http://linuxtv.org/hg<br />
<br />
The master repository with stable patches is available at:<br />
http://linuxtv.org/hg/v4l-dvb<br />
<br />
Mercurial is organized with a master tag, called tip. This tag contains <br />
the master repository that will be used by normal users and to generate <br />
patches to kernel.<br />
<br />
This file postulates some simple rules for maintaing hg trees, as stated below:<br />
<br />
It is strongly recommended that each developer be active at IRC channels (irc://irc.freenode.net) #v4l (for analog) and/or #linuxtv (for digital). It helps to have more discussions at major changes;<br />
<br />
Each developer may have one or more development trees, for his daily work. It is recommended to have a tree called 'v4l-dvb' for each developer with their stable patches.<br />
<br />
After the patches are ready, developer should send an email to v4l-dvb-maintainer list asking the maintainer to pull it from developer repository, pushing it at master. The maintainer will analyse the patch and publish at master hg if everything looks ok.<br />
<br />
Medium or major changes that needs modification on card coding, creating a new card type or requiring changes at core structs should be discussed first at the Mailing Lists video4linux-list@redhat.com (analog/common parts) and/or linux-dvb@linuxtv.org and at IRC to allow other contributors to discuss about the way it will be included.<br />
<br />
Every developer should follow the "rules of thumb" of kernel development stated at Linux source code, especially:<br />
<br />
* Documentation/SubmittingPatches<br />
* Documentation/SubmittingDrivers<br />
* Documentation/CodingStyle<br />
<br />
All commits should have a consistent message. On v4l-dvb, this is done by using:<br />
<br />
make commit<br />
<br />
This will run some scripts that will check changed files, generating a ChangeLog like comment (that will be removed from the commit) and prepare the last Signed-off-by field, as described bellow.<br />
<br />
Files can be added, removed or renamed at hg repository. This should be done by using:<br />
<br />
hg add <files><br />
hg remove <files><br />
hg rename <source> <dest><br />
hg addremove [<files>]<br />
<br />
<b>Warning</b> hg addremove will add/removes all files, including object files. Be careful! You can remove wrongly added files with hg remove.<br />
<br />
If the commit went wrong, hg allows you to undo the last commit, by using the command:<br />
<br />
hg undo<br />
<br />
This command will preserve the changes at the files. So, a new hg commit will redo the desired commit.<br />
<br />
To push the change to the repository you need to run:<br />
<br />
hg push <url><br />
<br />
To update from the master repository, it is needed to do:<br />
<br />
make pull<br />
<br />
After pulling from master, if there are some changes at local repository, hg will require to merge it. This is done by <br />
<br />
hg update -m<br />
make commit<br />
<br />
For hg to work properly, these vars should be defined (replacing the names at the left):<br />
<br />
HGUSER="Maintainer Name <maintainer-email@cvsmaintainersite.com>"<br />
<br />
If you use a different login name at the repo, you may use:<br />
<br />
CHANGE_LOG_LOGIN=my_log_name<br />
<br />
You may also have it at ~/.hgrc, but, in this case, make commit will not generate From: and Signed-off-by fields automatically. Don't forget to export the vars, like:<br />
<br />
export CHANGE_LOG_LOGIN HGUSER<br />
<br />
It is strongly recommended to have these lines at .bashrc or .profile.<br />
<br />
All commit messages shall have a Developers Certificate of Origin version 1.1 at commit log, as postulated at kernel's source at:<br />
<br />
Documentation/SubmittingPatches<br />
<br />
This is done by using Signed-off-by: fields at hg commit message.<br />
<br />
It is not acceptable to use fake signatures like:<br />
<br />
Signed-off-by: Fake me <me@snakeoilcompany.com><br />
<br />
The email should be a valid one. The bottom signed-off-by should be the commiter.<br />
<br />
Commit messages are very relevant, since they will be used when generating the patches for v4l-dvb.git and to mainstream. The format of commit message shall be:<br />
<br />
patch subject<br />
From: Patch Developer <patchdeveloper@patchdevelopersite.com><br />
<br />
patch descriptions<br />
<br />
Signed-off-by: Patch Developer <patchdeveloper@patchdevelopersite.com><br />
Signed-off-by: Cvs Maintainer <cvsmaintainer@cvsmaintainersite.com><br />
<br />
All lines starting with # will be removed by make commit stripts. Subject should be a brief description of the patch. Please notice that, with hg, there's no need (and not desired) to define a Subject: tag. The *first* msg line will be used as subject, just like git. *WARNING* Be careful not to leave the first line blank, otherwise hg will leave subject in blank.<br />
<br />
From: line shouldn't be suppressed, since it will be used when <br />
converting to -git as patch author.<br />
<br />
You may add other signers, if the patch were tested /co-developed by somebody else and he also wants to sign. The committer signed-off-by should be the last one.<br />
<br />
If the patch also affects other parts of kernel (like alsa or i2c), it is required that, at upstream submitting, the patch also goes to the maintainers of that subsystem. To do this, CVS maintainer shall add one or more cc: fields to the commit message, after the subject:<br />
<br />
CC: someotherkerneldeveloper@someplace<br />
<br />
Please notice that this is manually handled by the -git maintainer, so unnecessary usage should be avoided.<br />
<br />
Sometimes, mainstream changes do affect v4l-dvb tree, and requires to apply some kernel patches at the tree. This kind of commit should follow the rules above and should also have a line like:<br />
<br />
kernel-sync<br />
<br />
Patches with such lines will not be submitted upstream.<br />
<br />
sometimes it is necessary to introduce some testing code inside a module or remove parts that are not yet finished. Also, compatibility tests may be required to provide backporting. To allow compatibility tests, "compat.h" should be included first. It does include also linux/version.h.<br />
<br />
To include testing code, #if 0 or #if 1 may be used. If this code is meant to go also to kernel, this struct should be used:<br />
<br />
#if 0 /* keep */<br />
or<br />
#if 1 /* keep */<br />
<br />
Nested #ifs are allowed, but the #elif macro shouldn't be used, since the macro preprocessing script used to prepare kernel upstream patches (v4l/scripts/gentree.pl) is not able to handle it.<br />
<br />
To import contributed stuff, a script is provided at tree and allows easy import of a mbox-based patch emails. This is done with: ./mailimport <mbox file> For it to work properly, git tools need to be installed at local machine, since git have a gitimport script that is used by mailimport. Also, hg have a feature, called mqueue, that allows having several patches that can be applied/unapplied for testing. mailimport trusts on it to work, so, this extension should be enabled for mailimport script to work.<br />
<br />
<br />
== Some quotations about development ==<br />
<br />
"The most difficult problem isn't fixing bugs, but fixing bugs<br />
without breaking other configurations. There are many: different<br />
cards, different TV norms, whereas most of the developers can test<br />
only one TV norm." - Gerd Knorr<br />
<br />
"Anyone who has never made a mistake has never tried anything new." - Albert Einstein</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Audio_Decoders&diff=15890Audio Decoders2008-09-16T19:30:04Z<p>Js: Reverted edits by OpyGc0 (Talk); changed back to last version by Gmy</p>
<hr />
<div>== TV Sound Standards ==<br />
{| border=1 cellspacing=0 cellpadding=5<br />
|TV-System <br />
| Sound Carrier [MHz]<br />
| Sound Modulation <br />
| Color System <br />
| Country<br />
|-<br />
|B/G <br />
|5.5/5.7421875<br />
| FM-Stereo<br />
|PAL<br />
|Germany<br />
|-<br />
|B/G<br />
| 5.5/5.85<br />
|FM-Mono/NICAM<br />
|PAL<br />
|Scandinavia,Spain<br />
|-<br />
|L<br />
|6.5/5.85<br />
|AM-Mono/NICAM<br />
|SECAM-L<br />
|France<br />
|-<br />
|I<br />
|6.0/6.552<br />
|FM-Mono/NICAM<br />
|PAL<br />
|UK<br />
|-<br />
|D/K<br />
|6.5/6.2578125 D/K1<br />
6.5/6.7421875 D/K2<br />
<br />
6.5/5.85 D/K/NICAM<br />
|FM-Stereo<br />
FM-Stereo<br />
<br />
FM-Mono/NICAM<br />
|SECAM-East<br />
|USSR<br />
Peoples Rep. of China<br />
<br />
Hungary<br />
|-<br />
|M<br />
M-Korea<br />
|4.5<br />
4.5/4.724212<br />
|FM-Mono<br />
FM-Stereo<br />
|NTSC<br />
|USA<br />
Korea<br />
|-<br />
|Satellite<br />
|6.5<br />
7.02/7.20<br />
|FM-Mono<br />
FM-Stereo<br />
|PAL<br />
|ASTRA<br />
|}<br />
==TV Sound Decoding ==<br />
The TV sound needs to be decoded in order to receive an Audio Frequency (Sound_AF) signal.<br />
<br />
There are various possibilities <br />
<br />
* Sound_AF provided by the tuner <br> Some tuners have mono out /stereo out /radio out<br />
<br />
* Sound_IF provided by the tuner, this needs an extra decoder<br />
** discrete decoding module (e.g. NE41S fpr BTSC stereo)<br />
** simple audio decoder chip (e.g. tda9820)<br />
** DSP audio decoder chip (e.g. MSP3415)<br />
*** all DSP audio chips provide Sound_AF<br />
*** some can provide I2S signal<br />
** Audio decoding function built into the PCI bridge chip (e.g. cx25840)<br />
<br />
== Sound Routing ==<br />
<br />
There are multiple sound sources on the TV card, as there is only one<br />
output, there must be a switch to select from these:<br />
* Sound_AF from tuner (mono/stereo/radio)<br />
* Sound_AF from decoder chip<br />
* Line In<br />
<br />
There can be these switches (aka mux or crossbars)<br />
* HEF4052: this selects from 4 inputs<br />
* some DSP audio decoder chips have multiple inputs<br />
* some PCI bridge chips have multiple input<br />
<br />
If wired propoerly by the IHV, the I2S can be read directly by the PCI bdrige chip (so you have one less D/A -> D/A conversion, this should result in less noise).<br />
<br />
== Sound Output ==<br />
<br />
Sound can be output to:<br />
* Line out <br />
** Line out connected to sound card<br />
** Line out connected to active speakers<br />
* Speaker or headphone out (some cards had a headphone amplifier)<br />
* A/D digitizer on PCI chips (e.g. btaudio), this can be directly transferred to memory or can be sent to the audio card for output<br />
* also see I2S above</div>Jshttps://www.linuxtv.org/wiki/index.php?title=Archived:How_to_write_good_problem_report&diff=17321Archived:How to write good problem report2008-08-29T09:16:34Z<p>Js: Reverted edits by OrlR0u (Talk); changed back to last version by CarlFK</p>
<hr />
<div>Good problem report should include<br />
<br />
0. Note that you are using V4L CVS. <br />
<br />
1. Name of card<br />
<br />
2. lspci -vn <br />
<br />
3. Dmesg log of module tuning and probing. It also nice to add audio_debug options to modules, tuner_debug option to tuner module and debug option to tda9887<br />
<br />
4. Television standard for your country.<br />
<br />
5. Exact sequence of actions that causes your problem.<br />
<br />
6. Generally, "your problem" is a combination of an app and a driver. Also generally, the problem only exists in one of those, but it isn't always easy to tell where. A big help is to check each part with various tools in the [[Test_Suite]].</div>Js