LinuxTVWiki - User contributions [en]

SIGMACOM SIGMA HDTV5 X1

2013-02-01T14:24:27Z

Js: Reverted edits by JoshuaBrooks (talk) to last revision by Jimbley

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.

{| border="1" cellspacing="0" cellpadding="5" bgcolor="yellow" style="background:white;"
|- style="background:#efefef;" |- align="center"
! - align="left"|'''Vendor <BR> Model''' !! Added to<BR>Kernel !! align="left"|'''Frontend'''|!! '''Bridge Interface''' !! '''8VSB''' !! '''QAM''' !! '''NTSC''' !! '''Other Features'''
|- align="center"
| - 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
|}

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:
* there is scant difference in the appearance between the older SIGMA Cyber HDTV II, the SIGMA HDTV5 Penta and the SIGMA HDTV5 X1
** the Penta model even has 'Cyber HDTV II' silk screened on the PCB, whereas the X1 has "SMT-30"
* 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")
** 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.
** the X1 365 also has what appears to be a 2nd S-Video port

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.

The X1 cards are highly similar to the [[DViCO FusionHDTV5 Gold]].

[[image:sigmax1.jpg]]

==External Links==
* [http://www.sigmacom.co.kr/m1/m1_view.htm?p=&no=132 SIGMA HDTV5 X1]
* [http://www.sigmacom.co.kr/m1/m1_view.htm?no=166 SIGMA HDTV5 X1 Star]
* [http://www.sigmacom.co.kr/m1/m1_view.htm?p=&no=150 SIGMA HDTV5 X1 365]
* [http://www.sigmacom.co.kr/eng/m1/m1_view.htm?p=1&no=6 SIGMA HDTV5 Penta]
* [http://www.sigmacom.co.kr/m1/m1_view.htm?p=&no=22 SIGMA Cyber HDTV II]
[[Category:ATSC PCI Cards]]

Decoder

2013-01-16T16:27:00Z

Js: Reverted edits by Badrieastham (talk) to last revision by Alec v

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]

The best know TV standards are NTSC/PAL/SECAM. but for decoding a frame that
information is not enough. There are several formats of the TV standards.
And not every TV decoder is able to handle every format. Also the every
combination is supported by the driver. There are currently 11 different
tv broadcast formats all aver the world.

The CCIR defines parameters needed for broadcasting the signal.
The CCIR has defined different standards: A,B,D,E,F,G,D,H,I,K,K1,L,M,N,...
The CCIR says not much about the colorsystem used !!!
And talking about a colorsystem says not to much about how it is broadcast.

The CCIR standards A,E,F are not used any more.

When you speak about NTSC, you usually mean the standard: CCIR - M using
the NTSC colorsystem which is used in the USA, Japan, Mexico, Canada
and a few others.

When you talk about PAL, you usually mean: CCIR - B/G using the PAL
colorsystem which is used in many Countries.

When you talk about SECAM, you mean: CCIR - L using the SECAM Colorsystem
which is used in France, and a few others.

There the other version of SECAM, CCIR - D/K is used in Bulgaria, China,
Slovakai, Hungary, Korea (Rep.), Poland, Rumania and a others.

The CCIR - H uses the PAL colorsystem (sometimes SECAM) and is used in
Egypt, Libya, Sri Lanka, Syrain Arab. Rep.

The CCIR - I uses the PAL colorsystem, and is used in Great Britain, Hong Kong,
Ireland, Nigeria, South Africa.

The CCIR - N uses the PAL colorsystem and PAL frame size but the NTSC framerate,
and is used in Argentinia, Uruguay, an a few others

We do not talk about how the audio is broadcast !

A rather good sites about the TV standards are:
http://www.sony.jp/ServiceArea/Voltage_map/
http://info.electronicwerkstatt.de/bereiche/fernsehtechnik/frequenzen_und_normen/Fernsehnormen/
and http://www.cabl.com/restaurant/channel.html

Other weird things around: NTSC 4.43 is a modificated NTSC, which is mainly
used in PAL VCR's that are able to play back NTSC. PAL 60 seems to be the same
as NTSC 4.43 . The Datasheets also talk about NTSC 44, It seems as if it would
be the same as NTSC 4.43.
NTSC Combs seems to be a decoder mode where the decoder uses a comb filter
to split coma and luma instead of a Delay line.

But I did not defiantly find out what NTSC Comb is.

Philips saa7111 TV decoder
: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

Philips saa7110a TV decoder
:was introduced in 1995, is used in the Pinnacle/Miro DC10(new), DC10+ and can handle: PAL B/G, NTSC M and SECAM

Philips saa7114 TV decoder
: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

Brooktree bt819 TV decoder
:was introduced in 1996, and is used in the LML33 and can handle: PAL B/D/G/H/I, NTSC M

Micronas vpx3220a TV decoder
: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

Samsung ks0127 TV decoder
: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

Radio Listening Software

2012-10-26T17:11:46Z

Js: Reverted edits by Ipodsoft (talk) to last revision by CityK

__NOTOC__
__NOEDITSECTION__
<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;">
{| style="background-color:#F7F9FB;" cellspacing=0 cellpadding=5 border=0
| valign=top | [[Image:Radio_icon.png|50px]]
|
== '''Radio Listening Software:'''==
|}
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.

== Radio Applications ==
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.

* [[fftv]] [http://fftv.sourceforge.net/]
* [[fmtools]]
* [http://gkrellm.luon.net/gkrellm-radio.phtml gkrellm-radio] -- minimalistic [http://gkrellm.net gkrellm] plugin to control radio tuners
* [http://www.wh-hms.uni-ulm.de/~mfcn/gnomeradio gnomeradio] -- for Gnome, capable of recording
* [http://www.gnu.org/software/gnuradio/ GNU Radio] -- the GNU software radio, testing phase; cf. [http://comsec.com/wiki?GnuRadio2.X wiki]
* [http://foobazco.org/projects/gradio/ gradio] -- in Debian, but not currently active
* [[ivtv-radio]] [http://ivtvdriver.org/index.php/Howto:Radio_tuner] -- part of the ivtv-utils package
* [http://kradio.sourceforge.net/ KRadio] for KDE
* [[MPlayer#Using_MPlayer_for_Radio_Listening|MPlayer]] -- media player for Linux. See link for radio usage information
* [[radio]] -- a n-curses-based radio application (part of the [[Xawtv#Associated_Utilities|xawtv package]])
* [http://whats.all.this.brouhaha.com/?p=199 radioshark] -- application to control the griffin radioshark
* [https://sourceforge.net/projects/xdradio/ XDRadio] --- XDialog wrapper for radio listening
* [http://goodies.xfce.org/projects/panel-plugins/xfce4-radio-plugin/ xfce4-radio-plugin] -- plugin for the [http://www.xfce.org/ Xfce] panel
* [http://silicone.free.fr/xmms-FMRadio/ xmms-fmradio] -- plugin for [http://www.xmms.org/ XMMS], last version autumn 2004, Debian and Red Hat packages

==Also See==
* 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]].
* [[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

</div>

== User experiences ==

If you're a user, post your installation and user experiences here!

=== gnomeradio ===
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.

=== gradio ===
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

gradio -d /dev/radio2

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.

[[Category:Radio]]
[[Category:Software]]

Main Page

2012-09-28T06:32:20Z

Js: Reverted edits by Jasonsi (talk) to last revision by CityK

How to Obtain, Build and Install V4L-DVB Device Drivers

2012-08-20T06:04:33Z

Js: Reverted edits by Llnbig (talk) to last revision by Kjoekjoe

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.

{{Note|This article assumes that:
* 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.
* you have already physically installed the hardware device into, or connected it to, your system. (Refer to the manufacturer's instructions for such details)}}.

== Software Requirements ==
===Kernel Support===
The LinuxTV V4L-DVB drivers will work only in conjunction with relatively modern 2.6 kernels; specifically,

{{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.}}

===Additional Software Requrirements===
In order to be able to build the V4L-DVB kernel driver modules, you will need:
* kernel-source or kernel-headers
* (OpenSuSE and fedora only) kernel-devel
* (Debian) libdigest-sha1-perl
* make
* gcc
* git
* patch
* patchutils
* libproc-processtable-perl ("perl-Proc-ProcessTable")
If these packages are not currently installed on your system, you should do so now.

==Retrieving and Building/Compiling the Latest V4L-DVB Source Code==
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.

{{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>
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>.}}

{{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]] }}

{| class="wikitable"
|+'''Retrieving the Source Code & Building/Compiling the Modules'''
|-
! "Basic" Approach !! Developer's Approach !! More "Manually Intensive" Approach

|-
| valign=top |
git clone git://linuxtv.org/media_build.git
cd media_build
./build

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.

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.
| valign=top |
~ $ git clone git://linuxtv.org/media_build.git
~ $ cd media_build
~/media_build $./build --main-git
{{Note|'''The build script will clone the entire media-tree.git, with will take some time'''}}

In order to modify a driver foo.c:

~/media_build $ cd media
~/media $ gedit drivers/media/video/foo.c
~/media $ make -C ../v4l
~/media $ make -C ../ install
~/media $ make -C .. rmmod
~/media $ modprobe foo

(some procedure to test the "foo" driver)

To generate a patch, use:

~/media $ git commit -as

Then submit the patch upstream. If your sendmail is properly configured, you can easily send the patch upstream with:

~/media $ git send-email HEAD^1

or, to send a patch series:

~/media $ git send-email ''initial_branch''

Where ''initial_branch'' is the name of a branch of a changeset number for the last patch before your changes.

|
git clone git://linuxtv.org/media_build.git
cd media_build/linux
make tar DIR=<some dir with media -git tree>
make untar
cd ..

If you need to make any sort of change or modification to the source code, now is the time.

<div style="border: solid 1px; border-color: blue; margin: 1em; padding: 1em; background-color: Lavender;">
'''Optional Pre-Compilation Steps'''<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.
* <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)
* <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
* <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

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>

Next, build/compile the modules from the source code with the command:
make
{{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'' )}}

|}
===Information Regarding the Build Process===
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.

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.

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.

{{Note|'''The Daily Automated Build Tests'''<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].}}

If you do run into any problems during the build step, you should:
* first, see whether the issue is already known or not -- consult the results of the daily automated build tests (see note above)
* 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).
* you may also wish to consult any errata that might be found on this article's talk page

In general, if the source builds correctly, it is likely that the drivers will work, though this is not a guarantee.

== Installing the Compiled Driver Modules ==
The next step is to install the kernel driver modules by executing:
sudo make install
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.

{{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.:
su
make install
}}
<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>

== First Use: Out with the Old, In with the New==
{|
| valign=top |
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.

To achieve a [[Wikipedia:Tabula rasa |clean slate]] state, you could either: <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.

Or, on the other hand,

'''2. Take care of business yourself:''' More experienced users might prefer to use more eloquent approaches. For example, using
sudo make unload
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
modprobe ''driver_name''
commands.

| valign=top halign=right width=30% |
<div style="border: solid 1px; border-color: blue; margin: 1em; padding: 1em; background-color: Lavender;">
'''For Advanced Users'''<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:
* remove all older modules from memory at once using "make unload" and
* then insert all the newly built modules into memory for the running kernel with "make load"
Alternatively, to perform the previous two commands ("make unload" and "make load") in a single step, you can use "make reload"

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.
</div>
|}
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.

===If the Modules load correctly:===
Provided that the modules were loaded correctly into system memory:

'''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.

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!)

'''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.

'''3. The device manager [[Wikipedia:udev|udev]] will "automagically" create appropriate [[Device nodes and character devices|device nodes]] on ''/dev''''': <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:
: <code>ls -l /dev/dvb/</code>
(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,
: <code>ls -l /dev/dvb/adapter0 </code>
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
: <code>ls -l /dev/dvb/adapter* </code>

'''(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:
: <code>ls -l /dev/v4l</code>
Digging further,
: <code>ls -l /dev/v4l/by-path </code>
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
: <code>ls -l /dev/video* </code>

===If the Modules did not load correctly or the device is still not configured correctly for use:===
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:

'''Module Load Order Can Matter'''
* in cases where loading more then one module is necessary, the order in which you load the modules can matter!

'''Sometimes Automagic just isn't Automagic'''
* If a module was, for whatever reason, not loaded, you can try manually loading it with the appropriate ''modprobe'' command.

'''Unresolved Symbols'''
* 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:
sudo modprobe saa7134
FATAL: Error inserting saa7134 (/lib/modules/''[your kernel version]''/kernel/drivers/media/video/saa7134/saa7134.ko):\
Unknown symbol in module, or unknown parameter (see dmesg)
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.

* 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:
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
Usually all conflicting module files resulting of v4l-dvb installation will be located in:
/lib/modules/''[your kernel version]''/kernel/drivers/media
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):
make reload
depmod -a
Your new modules should now be loaded correctly.

'''A Note on Firmware'''
* 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.

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:
<pre> dvb-ttpci: could not load firmware, file not found: dvb-ttpci-01.fw
dvb-ttpci: usually this should be in /usr/lib/hotplug/firmware or /lib/firmware
dvb-ttpci: and can be downloaded from http://www.linuxtv.org/download/dvb/firmware/</pre>
Resolving that missing firmware issue should then result in proper detection and configuration of your device.
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.

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:
*/lib/firmware
Consult resources for your distro if its preferred location is somewhere otherwise.

==Some Further Documentation==
* See [[Testing your DVB device]] for instructions on testing your newly installed DVB device

[[Category:Software]]
[[Category:Drivers]]

DVB-T USB Devices

2012-08-20T06:03:58Z

Js: Reverted edits by Llnbig (talk) to last revision by Devin.heitmueller

On this page you will find information regarding [[DVB-T]] [[USB]] devices.

{{non-exhaustive list}}
<br>
__TOC__
<br>

==Firmwares==
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].

==DVB-T USB Devices==
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)

If you need more technical information on a device, have a look at its device specific wiki article if there is one.

The device specific article is linked via the device's name but not all are linked yet.
If you find an article (e.g. via the search feature on the left) then please edit the device entry here add that link.
Just click on the edit icon in the last column of the device's row.

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.
Please feel free to create a device specific page if there is enough worthwhile information that doesn't fit in the comments field.

There is also a [[DVB-T USB Devices/Full|full detail table]].

If you'd like to add a new device (supported or unsupported), please go to [[Template:USB_Device_Data]] and follow the instruction there.
If a device is unsupported, please add with which OS/kernel version you tested last.

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).

{{Device_List_Medium_Detail/Header
| content =
{{USB_Device_Data|renderwith=Device_List_Medium_Detail/Row
| selatt1=hostinterface
| selval1=USB
| selatt2=standard
| selval2=DVB-T
}}
}}

==Supported DVB-T USB Devices (old data)==

{{DvbDeviceList
|content=
{{DvbDeviceCommented
| device=Easylite<br/>[[Easylite DVB-T stick|Easylite DVB-T Stick USB 2.0]]
| type=USB2.0
| comment=Supported in ?? since ??
}}
{{DvbDeviceCommented
| vendor=ForwardVideo
| device=ForwardVideo (If you own such a device please add the model. 616/618?)<br/>EzTV USB Hybrid TV Receiver
| type=USB2.0
| comment=Supported in ?? since ??
| pic=[http://www.szforwardvideo.com/product/product_List_13.html]
}}
{{DvbDeviceCommented
| vendor=[[Hauppauge]]
| device=[[Hauppauge]]<br/>[[Hauppauge WinTV-HVR-900]]
| type=USB2.0
| comment=Supported in kernel since 2.6.26 [http://www.hauppauge.com/site/support/linux.html]
| supported=kernel >= 2.6.26
}}
{{DvbDeviceCommented
| vendor=[[Hauppauge]]
| device=[[Hauppauge]]<br/>Hauppauge WinTV-HVR-930
| type=USB2.0
| comment=Supported in ?? since ??
}}
{{DvbDeviceCommented
| vendor=[[Hauppauge]]
| device=[[Hauppauge]]<br/>[[Hauppauge WinTV-HVR-1900]]
| type=USB2.0
| comment=Supported in kernel since 2.6.26 [http://www.hauppauge.com/site/support/linux.html]
| supported=kernel >= 2.6.26
}}
{{DvbDeviceCommented
| vendor=[[Hauppauge]]
| device=[[Hauppauge]]<br/>[[Hauppauge WinTV-NOVA-T USB]]
| type=USB1.1
| comment=Supported in kernel since 2.6.??
| supported=kernel >= ??
}}
{{DvbDeviceCommented
| vendor=[[Hauppauge]]
| device=[[Hauppauge]]<br/>[[Hauppauge DEC2000-T USB]]
| type=USB1.1
| comment=Supported in kernel since 2.6.??
| supported=kernel >= ??
}}
{{DvbDeviceCommented
| vendor=[[Hauppauge]]
| device=[[Hauppauge]]<br/>[[Hauppauge DEC2540-T USB]]
| type=USB1.1
| comment=Supported in kernel since 2.6.??
| supported=kernel >= ??
}}
}}




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.

* [[Medion MD95700 (DVB-T)]] (''note, this thing is hybrid and offers also an FM radio tuner'')

* [[TechniSat AirStar USB / Air2PC DVB USB]]

Hybrid devices have a DVB-demodulator and a analogue capturing chip. Normally they share a tuner.

------------

{{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}}
[[Category:Clean_up]]

=== WideView/Yakumo/Hama/Typhoon/Yuan Boxes and Pens ===

All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:
- dvb-usb.ko
- dvb-usb-dtt200u.ko

These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:
- [[Zarlink MT352]]
- The new units use the Zarlink ZL10353 instead of MT352
- for pentype design it is unknown (but it doesn't matter at all)

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.

There is apparently another Yakumo model not covered:

<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>

'''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.

'''Warning:''' When checking the table below, check the USB ID to see if you have an old or new revision of the firmware.

{{DvbDeviceList
| content=
{{DvbDeviceCommented
| device=Bestbuy Easy TV
| type=USB2.0
| fw=dvb-usb-wt220u-02.fw
| comment=This is a WideView WT-220U PenType Receiver (Typhoon/Freecom). It works with newest linuxtv driver version.
}}
{{DvbDeviceCommented
| device=Club 3D ZAP-TV250mini
| type=USB2.0, USB1.1
| fw=dvb-usb-wt220u-02.fw (dvb-usb-wt220u-01.fw untested)
| hw=MT2060 silicon tuner
| comment=USB ID (before firmware): 14aa:0220
| pic=[http://www.club-3d.nl/productshow_zaptv.php?ordercode=ZAP-TV250M&show=&p=&l=en]
}}
{{DvbDeviceCommented
| device=dnt EuroStick USB-Stick DVB-T Receiver
| type=USB2.0, USB1.1
| fw=dvb-usb-wt220u-01.fw
| comment=Pen-sized.
| pic=[http://www.dnt.de/index.php?dir=details&pid=20201&cat=dvbt&m_id=dvbt&h_curr=]
}}
{{DvbDeviceCommented
| device=Freecom DVB-T USB Stick
| type=USB2.0, USB1.1
| fw=dvb-usb-wt220u-01.fw
| comment=Pen-sized.
| pic=[http://www.freecom.com/ecProduct_detail.asp?ID=2234]
}}
{{DvbDeviceCommented
| device=Freecom DVB-T USB Stick (25451 rev3)
| type=USB2.0
| fw=dvb-usb-wt220u-fc03.fw
| comment=Pen-sized.<br />USB ID (before firmware): 14aa:0225
| pic=[http://www.freecom.com/ecProduct_detail.asp?ID=2234]
}}
{{DvbDeviceCommented
| device=Freecom DVB-T USB Stick. New revision of those devices with ZL0353 inside
| type=USB2.0, USB1.1
| fw=dvb-usb-wt220u-zl0353-01.fw
| comment=Pen-sized.<br />USB ID (before firmware): 14aa:022a.
[mailto:david@myforest.com Someone] has three of these running just fine in parallel; USB IDs 14aa:0221 and 14aa:022b.
| pic=[http://www.amazon.co.uk/gp/product/B000ALAWQ6/026-5347660-4657208?v=glance&n=560798]
}}
{{DvbDeviceCommented
| device=Gainward DVB2go
| type=USB2.0
| fw=dvb-usb-wt220u-01.fw or dvb-usb-wt220u-02.fw
| comment=Clone of YUAN PD300.
}}
{{DvbDevice
| device=Hama DVB-T Box
| type=USB2.0, USB1.1
| fw=dvb-usb-wt220u-02.fw
| pic=[http://www.hama.de/portal/articleId*114663/action*2563]
}}
{{DvbDeviceCommented
| device=Miglia TVMini Express
| type=USB2.0
| fw=dvb-usb-wt220u-02.fw
| comment=Pen-sized. Sold as Mac exclusive, but exterior seems to be the same as dnt EuroStick.
| pic=[http://www.miglia.com/tvminiexpress/]
}}
{{DvbDeviceCommented
| device=Redbell DVB-T USB Stick (TDT-2GO)
| type=USB2.0, USB1.1
| fw=dvb-usb-wt220u-01.fw or dvb-usb-wt220u-fc03.fw or dvb-usb-wt220u-zl0353-01.fw
| comment=Pen-sized. Valid for PCMCIA version.
| 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]
}}
{{DvbDevice
| device=Typhoon USB2.0 DVB-T Box
| type=USB2.0, USB1.1
| fw=dvb-usb-dtt200u-01.fw
}}
{{DvbDeviceCommented
| device=Typhoon DVB-T USB Drive
| type=USB2.0, USB1.1
| fw=dvb-usb-wt220u-01.fw
| comment=Pen-sized.
| pic=[http://www.typhoon.de/de/art.php?p=826&c=]
}}
{{DvbDeviceCommented
| device=V-Gear PocketDTV USB2.0 DVB-T TVBox
| type=USB2.0, USB1.1
| fw=dvb-usb-dtt200u-01.fw
| comment=Small container.
| pic=[http://www.vgear.com/products/list1.asp?ProdID=AMVG1-016-001&SUB_NUM=1998/]
}}
{{DvbDeviceCommented
| device=V-Gear MobiDTV
| type=USB2.0, USB1.1
| fw=dvb-usb-wt220u-01.fw or dvb-usb-wt220u-02.fw
| comment=Pen-sized.
| pic=[http://www.vgear.com/products/list.asp?ProdID=AMVG1-016-002]
}}
{{DvbDevice
| device=WideView USB2.0 DVB-T Receiver
| type=USB2.0, USB1.1
| fw=dvb-usb-dtt200u-01.fw
| pic=[http://www.wv.com.tw/]
}}
{{DvbDeviceCommented
| device=WideView Pentype DVB-T-Receiver (WT-220U)
| type=USB2.0, USB1.1
| fw=dvb-usb-wt220u-01.fw
| comment=Pen-sized.
| pic=[http://www.wv.com.tw/]
}}
{{DvbDeviceCommented
| device=Yakumo DVB-T mobile USB
| type=USB2.0, USB1.1
| fw=dvb-usb-dtt200u-01.fw
| comment=A.K.A DTT200U
| pic=[http://www.yakumo.de/produkte/index.php?pid=1&ag=DVB-T]
}}
{{DvbDeviceCommented
| device=Yakumo QuickStick DVB-T USB
| type=USB2.0, USB1.1
| fw=dvb-usb-wt220u-01.fw
| comment=Pen-sized
| pic=[http://www.yakumo.de/produkte/index.php?pid=1&ag=DVB-T]
}}
{{DvbDeviceCommented
| device=Yakumo QuickStick Basic DVB-T USB
| type=USB2.0, USB1.1
| fw=dvb-usb-wt220u-zl0353-01.fw
| comment=Pen-sized
| pic=[http://www.yakumo.de/produkte/index.php?pid=1&ag=DVB-T]
}}
{{DvbDeviceCommented
| device=Yakumo QuickStick Basic DVB-T USB
| type=USB2.0
| fw=dvb-usb-wt220u-fc03.fw
| comment=Pen-sized.<br />USB ID 14aa:0225 (cold state, before firmware).<br />USB ID 14aa:0226 (warm state, after firmware).
| pic=[http://www.yakumo.de/produkte/index.php?pid=1&ag=DVB-T]
}}
{{DvbDevice
| device=Yuan DVB2GO UB300
| type=USB2.0, USB1.1
| fw=dvb-usb-dtt200u-01.fw
| pic=[http://www.yuan.com.tw/en/products/vdo_ub300.html]
}}
{{DvbDeviceCommented
| device=ELTA 8652 DVB-T
| type=USB2.0
| fw=dvb-usb-dtt200u-01.fw
| comment=External box.<br />USB ID 14aa:0201 (cold, before firmware).<br />USB ID 14aa:0301 (warm, firmware installed).
}}
{{DvbDevice
| device=Yuan PD300 DVB-T mini
| type=USB2.0, USB1.1
| fw=dvb-usb-wt220u-01.fw
| hw=MT2060 silicon tuner?
| pic=[http://www.yuan.com.tw/en/products/vdo_pd300.html]
}}
}}

=== Supported Em2880/Em2870 Based USB DVB-T devices ===

Official project site: [http://www.mcentral.de/wiki/index.php5/Em2880 Em2880]

{{DvbDeviceList
| content=
{{DvbDeviceCommented
| device=BestBuy Easy TV USB hybrid
| type=USB
| comment=USB ID EB1A:2881
}}
{{DvbDeviceCommented
| device=Dazzle TV Hybrid Stick
| type=USB
| comment=USB ID EB1A:2881
| pic=[http://doc.ubuntu-fr.org/pctv_hybrid_pro_stick?s=tnt]
}}
{{DvbDevice
| device=DNT DA2 Hybrid
| type=USB
| pic=[http://www.dnt.de/index.php?dir=produkte/detail&id=20205]
}}
{{DvbDevice
| device=Empire USB 2.0 Pen Dual TV
| type=USB
| pic=[http://www.empiremedia.it/site/prodotto.asp?idprodotto=231]
}}
{{DvbDevice
| device=Hauppauge WinTV HVR 900 (rev. 1.0)
| type=USB
| pic=[http://www.hauppauge.co.uk/pages/products/data_hvr900.html]
}}
{{DvbDevice
| device=Kworld 350 U DVB-T
| type=USB
}}
{{DvbDevice
| device=MSI DigiVox A/D
| type=USB2.0
| pic=[http://www.msi.com.tw/program/products/multimedia/mut/pro_mut_detail.php?UID=612]
}}
{{DvbDevice
| device=[[MSI DigiVox A/D II]]
| type=USB2.0
| pic=
}}
{{DvbDevice
| device=Pinnacle PCTV USB Stick
| type=USB
| 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]
}}
{{DvbDevice
| device=Pinnacle PCTV Hybrid Pro Stick 330e
| type=USB
}}
{{DvbDevice
| device=Pinnacle PCTV Hybrid Pro Stick
| type=USB
| pic=[http://www.pinnaclesys.com/PublicSite/de/Products/Consumer+Products/PCTV+Tuners/PCTV+Analog_Digital+PVR/PCTV+Hybrid+Pro+Stick+(320e)]
}}
{{DvbDevice
| device=[[TerraTec Cinergy Hybrid T USB XS]]
| type=USB
| hw=ZL10353
| pic=[http://tvde.terratec.net/modules.php?op=modload&name=News&file=article&sid=249]
}}
{{DvbDevice
| device=[[TerraTec Cinergy Hybrid T USB XS]]
| type=USB
| hw=MT352
| pic=[http://tvde.terratec.net/modules.php?op=modload&name=News&file=article&sid=249]
}}
{{DvbDevice
| device=[[TerraTec Cinergy T USB XS|TerraTec Cinergy T XS]]
| type=USB
| hw=XC3028
| pic=[http://tvde.terratec.net/modules.php?op=modload&name=News&file=article&sid=253]
}}
{{DvbDevice
| device=[[TerraTec Cinergy T USB XS|TerraTec Cinergy T XS]]
| type=USB
| hw=MT2060
}}
{{DvbDevice
| device=[[TerraTec Prodigy Hybrid T XS]]
| type=USB
| hw=usbbridge:em2880 tuner:xc3028
}}
}}

{{DvbDeviceList
| content=
{{DvbDeviceCommented
| device=Sundtek MediaTV Pro
| type=USB
| 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.
| pic=[http://sundtek.de/shop/Digital-TV-Sticks/Sundtek-MediaTV-Pro.html]
}}
}}

=== Supported TM5600/6000/6010 Based USB DVB-T devices ===

Official project site: [[Trident_TM6000|TM6000]]

{{DvbDeviceList
| content=
{{DvbDeviceCommented
| device=TerraTec Cinergy Hybrid XE
| type=USB2.0
| hw=xc3028L, zl10353, IR
| comment=USB ID 0CCD:0086
| fw=xc3028L-v36.fw
}}
{{DvbDeviceCommented
| device=TerraTec Cinergy Hybrid-Stick
| type=USB2.0
| hw=xc3028L, zl10353, IR
| comment=USB ID 0CCD:00a5
| fw=xc3028L-v36.fw
}}
{{DvbDeviceCommented
| device=Hauppauge WinTV HVR-900H
| type=USB2.0
| hw=xc3028L, zl10353, IR
| comment=USB ID 2040:6600
| fw=xc3028L-v36.fw
}}
}}

==Currently Unsupported DVB-T USB Devices==
{{help to support}}
* [[ASUS My Cinema-U3000]]
* [[DViCO FusionHDTV DVB-T NANO+]] usb id : 0fe9:db74
* [[Emtec]] [[Emtec S830|S830]]
* [[Lumanate Wave PAL SECAM DVBT Device]] [http://www.lumanate.com/aspx/sptwavedvbt.aspx] usb id : 1009:0015 (Emuzed, In).
* [[Pinnacle PCTV 200e]]
* Sweex MM002V
* [[TerraTec Cinergy Piranha]]: work-in-progress, see [http://www.linuxtv.org/pipermail/linux-dvb/2008-June/026384.html mailing list] (June 2008)
* [[Tongshi DVB-T USB]] [http://www.tongshi.com/cp_dvb_e.htm] ... Is this just a reference design?
* [[WideView DVB-T/CATV USB2.0 Hybrid]] [http://www.wv.com.tw/]
* [[WithView DMB Receiver]] [http://www.withview.co.kr]
=== ASUS My Cinema-U3000 ===

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]

=== DViCO FusionHDTV DVB-T NANO+ ===
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.

=== Freecom rev 4 DVB-T USB 2.0 tuner ===
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

More info is in the wiki's [[Realtek RTL2831U]] article.

Chipset info at http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=35&Level=4&Conn=3&ProdID=147

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.

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.

===Geniatech T328 DVB-T ===
[http://www.geniatech.com/pa/t682.htm]
*chip: MT2060F, CY7C68013A and ZL10353. usb id: 04b4:8613.
* 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.

=== LifeView TV Walker DVB-T (P/Q/Hybrid) ===

P Stick

* 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?

Q Stick [http://www.lifeview.com.tw/html/products/discontinued_products/q_dvbt.htm]

* USB 2.0 stick. idProduct: 1506 ID: idVendor 0x10fd Anubis Electronics, Ltd

* Chips visible on card:
** Frontend: TDA10046A OFDM channel demodulator
** Tuner: [http://www.semiconductors.philips.com/acrobat_download/literature/9397/75014128.pdf TDA8275A]Silicon Tuner

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.

There is a DVB-T/Analogue box (with external power): [http://www.lifeview.com.tw/html/products/discontinued_products/tv_walker_studio_hybrid.htm]

=== Sweex MM002V2 ===
[http://www.sweex.com/producten.php?sectie=2&subsectie=2&item=127&artikel=879]
* Just bought this to find out it doesn't work. Unfortunately I have no experience creating drivers :-(

This is as much as I know, according to their site ...

Specification
# Interface: USB 2.0
# [[Microtune MT2060]] silicon tuner
# Chipsets: [[E3C_EC168|E3C, EC168]]

Looking at dmesg in ubuntu 8.10 running kernel 2.6.27 I can see its being detected as a keyboard

* [ 2893.200071] usb 5-5: new high speed USB device using ehci_hcd and address 6
* [ 2893.342542] usb 5-5: configuration #1 chosen from 1 choice
* [ 2893.344136] input: HID 18b4:1689 as /devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5:1.0/input/input10
* [ 2893.387617] input,hidraw0: USB HID v1.11 Keyboard [HID 18b4:1689] on usb-0000:00:1d.7-5

Hopefully someone can help with driver development.

/Steve

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.

=== TVISTO DVB-T USB ===
There are different TVISTO usb dongles and some are supported, see [[TVISTO DVB-T USB]] for more information.

=== [http://www.twinhan.com/product_AD-TU200.asp TwinHan/AzureWave AD-TU200 (7047) DVB-T] ===
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):

[ 3841.997121] DVB: registering new adapter (DTV-DVB UDTT 7047-USB 2.0 DVB-T Driver)
[ 3841.998753] DVB: registering frontend 0 (Realtek RTL2831 DVB-T)...

=== [http://www.twinhan.com/product_terrestrial_7049.asp TwinhanDTV Twister (7049) DVB-T] ===
In germany a similar device seems to be sold as dnt EuroMini200 [http://www.dnt.de/index.php?dir=produkte/detail&id=20206].

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.

Maybe the same applies for the TwinhanDTV Hurricne (704D) [http://www.twinhan.com/product_704D.asp].

=== [http://www.twinhan.com/product_D%2BA_3.asp TwinhanDTV MagicBox Pro (DVB-T/Analogue)] ===
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).

=== YUAN UB701 (DVB-T/Analogue) ===
A [[hybrid]] USB2.0-only box. Maybe it is a clone of the Conexant Hybrid Reference design?
It has an em2880 and a xc3028 tuner. USB id eb1a:2881
[http://www.yuan.com.tw/en/products/vdo_ub701.html]

=== WithView DMB Receiver ===
* Model No : HDMB-T100A
* lsusb : ID 10c4:0010 Cygnal Integrated Products, Inc.
[http://www.withview.co.kr/eshop/contents.html?layout=t100a]

=== WandTV ===
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.

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”.

==Also See==
* [[DVB via USB|General Information Regarding DVB via USB]]

[[Category:DVB-T| ]]
[[Category:Hardware| ]]
[[Category:DVB-T USB Devices| ]]

How to Obtain, Build and Install V4L-DVB Device Drivers

2012-04-04T14:38:17Z

Js: Reverted edits by Promenado645 (talk) to last revision by Bobatlcpmbdx

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.

{{Note|This article assumes that:
* 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.
* you have already physically installed the hardware device into, or connected it to, your system. (Refer to the manufacturer's instructions for such details)}}.

== Software Requirements ==
===Kernel Support===
The LinuxTV V4L-DVB drivers will work only in conjunction with relatively modern 2.6 kernels; specifically,

{{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.}}

===Additional Software Requrirements===
In order to be able to build the V4L-DVB kernel driver modules, you will need:
* kernel-source or kernel-headers
* (OpenSuSE and fedora only) kernel-devel
* (Debian) libdigest-sha1-perl
* make
* gcc
* git
* patch
* patchutils
* libproc-processtable-perl ("perl-Proc-ProcessTable")
If these packages are not currently installed on your system, you should do so now.

==Retrieving and Building/Compiling the Latest V4L-DVB Source Code==
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.

{{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>
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>.}}

{{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]] }}

{| class="wikitable"
|+'''Retreiving the Source Code & Building/Compiling the Modules'''
|-
! "Basic" Approach !! More "Manually Intensive" Approach

|-
| valign=top |
git clone git://linuxtv.org/media_build.git
cd media_build
./build

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.

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.
|
git clone git://linuxtv.org/media_build.git
cd media_build/linux
make tar DIR=<some dir with media -git tree>
make untar
cd ..

If you need to make any sort of change or modification to the source code, now is the time.

<div style="border: solid 1px; border-color: blue; margin: 1em; padding: 1em; background-color: Lavender;">
'''Optional Pre-Compilation Steps'''<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.
* <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)
* <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
* <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

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>

Next, build/compile the modules from the source code with the command:
make
{{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'' )}}

|}
===Information Regarding the Build Process===
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.

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.

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.

{{Note|'''The Daily Automated Build Tests'''<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].}}

If you do run into any problems during the build step, you should:
* first, see whether the issue is already known or not -- consult the results of the daily automated build tests (see note above)
* 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).
* you may also wish to consult any errata that might be found on this article's talk page

In general, if the source builds correctly, it is likely that the drivers will work, though this is not a guarantee.

== Installing the Compiled Driver Modules ==
The next step is to install the kernel driver modules by executing:
sudo make install
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.

{{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.:
su
make install
}}
<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>

== First Use: Out with the Old, In with the New==
{|
| valign=top |
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.

To achieve a [[Wikipedia:Tabula rasa |clean slate]] state, you could either: <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.

Or, on the other hand,

'''2. Take care of business yourself:''' More experienced users might prefer to use more eloquent approaches. For example, using
sudo make unload
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
modprobe ''driver_name''
commands.

| valign=top halign=right width=30% |
<div style="border: solid 1px; border-color: blue; margin: 1em; padding: 1em; background-color: Lavender;">
'''For Advanced Users'''<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:
* remove all older modules from memory at once using "make unload" and
* then insert all the newly built modules into memory for the running kernel with "make load"
Alternatively, to perform the previous two commands ("make unload" and "make load") in a single step, you can use "make reload"

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.
</div>
|}
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.

===If the Modules load correctly:===
Provided that the modules were loaded correctly into system memory:

'''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.

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!)

'''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.

'''3. The device manager [[Wikipedia:udev|udev]] will "automagically" create appropriate [[Device nodes and character devices|device nodes]] on ''/dev''''': <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:
: <code>ls -l /dev/dvb/</code>
(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,
: <code>ls -l /dev/dvb/adapter0 </code>
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
: <code>ls -l /dev/dvb/adapter* </code>

'''(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:
: <code>ls -l /dev/v4l</code>
Digging further,
: <code>ls -l /dev/v4l/by-path </code>
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
: <code>ls -l /dev/video* </code>

===If the Modules did not load correctly or the device is still not configured correctly for use:===
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:

'''Module Load Order Can Matter'''
* in cases where loading more then one module is necessary, the order in which you load the modules can matter!

'''Sometimes Automagic just isn't Automagic'''
* If a module was, for whatever reason, not loaded, you can try manually loading it with the appropriate ''modprobe'' command.

'''Unresolved Symbols'''
* 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:
sudo modprobe saa7134
FATAL: Error inserting saa7134 (/lib/modules/''[your kernel version]''/kernel/drivers/media/video/saa7134/saa7134.ko):\
Unknown symbol in module, or unknown parameter (see dmesg)
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.

* 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:
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
Usually all conflicting module files resulting of v4l-dvb installation will be located in:
/lib/modules/''[your kernel version]''/kernel/drivers/media
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):
make reload
depmod -a
Your new modules should now be loaded correctly.

'''A Note on Firmware'''
* 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.

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:
<pre> dvb-ttpci: could not load firmware, file not found: dvb-ttpci-01.fw
dvb-ttpci: usually this should be in /usr/lib/hotplug/firmware or /lib/firmware
dvb-ttpci: and can be downloaded from http://www.linuxtv.org/download/dvb/firmware/</pre>
Resolving that missing firmware issue should then result in proper detection and configuration of your device.
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.

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:
*/lib/firmware
Consult resources for your distro if its preferred location is somewhere otherwise.

==Some Further Documentation==
* See [[Testing your DVB device]] for instructions on testing your newly installed DVB device

[[Category:Software]]
[[Category:Drivers]]

DVB-T USB Devices

2012-03-11T17:25:22Z

Js: Reverted edits by Sucipto82 (talk) to last revision by Jmiezitis

User:CityK

2012-03-11T07:31:58Z

Js: Reverted edits by Seputarsoftware (talk) to last revision by CityK

This is my sandbox. Being a sandbox, everything you see here is a work in progress.

==Wiki Main Page:==
[[Image:Graphic_banner_rough_idea_test3.png]]

== User Sign up /Login Subpage:==
'''A Few Notes Before you Begin'''

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.

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
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.

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.

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

Now enjoy and have fun! -- The LinuxTV WikiTeam [People behind V4L]

==[[Image:Software_viewing_apps_icon.png|50px]] TV Related Software SubPage:==

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

'''TV related items/issues''' that should be addressed are:
* scanning
* tuning/zapping
* watching/recording
* teletex/CC

* streaming

distinguish between tuner/tuning/to tune/receiver ...
in contemporary dialogue/common language:
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

[[tuning]]
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.

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.

in which case the RF carrier signal
list of known frequencies or obtained via a frequency scan

==Just toying ==
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:
* [[USB interface chipsets]]
* [[Demodulator#Digital_Demodulators|Demodulator]]

{| class="wikitable sortable"
|+'''A Sortable List of Chipsets'''
|-
! 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
|-
| [[Afatech]] || [[Afatech AF9005|AF9005]] || {{No}} || {{No}} || {{Yes}} || [[DVB-T]] || [[COFDM]] || {{No}} || {{No}} || {{No}} || {{Yes}} || [[USB]] || {{Yes}} || {{Yes}} || ? || {{Yes}} ||
* A combo USB bridge & demod IC
|-
|}

==Misc Info & ideas for me:==

'''Timestamp'''
* <nowiki>~~~~~</nowiki>

'''Colours'''
* [http://en.wikipedia.org/wiki/Web_colors Web colours]
* v4l --> style="background-color:#006600;
* DVB --> style="background-color:#6289AB;

'''Tables'''
* [http://www.mediawiki.org/wiki/Help:Tables table formating]
* [http://en.wikipedia.org/wiki/Table_markup Table_markup]
<br>
style="color:green; background-color:#ffffcc;"<br>
style="color:#e76700;"<br>
style="background-color:# ;"

'''Icons wanted''':
* need to find or create a chain link icon for "links"
* * terrestrial broadcast tower
* sat dish
* * pcmcia
* pci
* pcie
* firewire

'''Special Links'''
* Works: [{{SERVER}}{{localurl:Special:Allpages|{{ns:100}}}} {{ns:100}}]
* Doesn't work: {{Note|[{{SERVER}}{{localurl:Special:Allpages|{{ns:100}}}} {{ns:100}}]}} ... stupid wiki.
* also see http://www.mediawiki.org/wiki/Plainlinks

'''Clickable Icons or Images using templates'''
* http://www.mediawiki.org/wiki/Extension:ImageLink
* http://www.mediawiki.org/wiki/Extension:ImageMap
* http://www.mediawiki.org/wiki/Extension:Icon <--- ***
* http://meta.wikimedia.org/wiki/Template:Click (depreciated)
* http://en.wikipedia.org/wiki/Template:Click-Inline

Multiproto

2012-02-08T19:44:55Z

Js: Reverted edits by Sanders Dowdy (talk) to last revision by Jon2856

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).
An alternative proposal, [[S2API]], was evenutally selected as the new API and was released in
kernel 2.6.28 on 24 Dec 2008.

Multiproto was an experimental project and was not implemented in any released version of Linux. Notably,
the author of some of the main parts of multiproto has in the past incomprehensibly attempted
to block its inclusion in Linux, highlighting both misunderstanding of the implications of the GPL and the need
for stricter project management within the Linux DVB community
http://www.linuxtv.org/pipermail/linux-dvb/2008-January/023355.html. After more than two years, a pull request
for the API (excluding drivers) was eventually issued hours after the competing project [[S2API]] was
announced http://linuxtv.org/pipermail/linux-dvb/2008-September/028896.html.

[[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.

An announcement regarding the conclusions of the review was made by the maintainer :
http://www.linuxtv.org/news.php?entry=2008-09-23.mchehab,
http://linuxtv.org/pipermail/linux-dvb/2008-September/029155.html,
http://linuxtv.org/pipermail/linux-dvb/2008-September/029181.html,
http://linuxtv.org/pipermail/linux-dvb/2008-September/029232.html.
By unanimous vote, [[S2API]] was selected for inclusion in kernel 2.6.28.
The multiproto API will therefore not be merged into
the kernel. The decision is final. The device support in the multiproto tree will not be lost -- drivers
can be easily converted to work with the S2API. It is intended to add
support for products with the STB0899 demodulator (TT-3200 and others) to S2API before the merge.

==Overview/Features==
''Discuss the features and facets of the project here ... this means you''

===Design Decisions===
''explain the choices made ... this means you''

===Technical Details===
''give a technical description of how the API change has been implemented ... this means you''

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.

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.

===Evaluation===
''explain whether the design goals have been met or not ... this means you''

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
unions of structs to hold parameters (often the same ones) for each type of frontend.
However API calls (eg. ioctl dvbfe_params) '''can be addressed to individual frontends''', i.e.
/dev/dvb/adapterN/frontendM, so this repetition could be removed to create a cleaner API. For example these variables:

dvbfe_params.delsys.dvbs.fec
dvbfe_params.delsys.dss.fec
dvbfe_params.delsys.dvbs2.fec
dvbfe_params.delsys.dvbc.fec

could be replaced by the simpler:

dvbfe_params.fec

and these

dvbfe_info.delsys.dvbs.fec
dvbfe_info.delsys.dss.fec
dvbfe_info.delsys.dvbs2.fec

could be replaced by the simpler:

dvbfe_info.fec

If we simplify in this way, the relevant section of linux/include/linux/dvb/frontend.h would look like this:
(note I added '''_caps''' to some variables to indicate that they are actually ORd sets of ''capabilities'')

struct dvbfe_info {
char name[128];
enum dvbfe_delsys delsys; //curr delivery sys, READABLE by user, not WRITEABLE
enum dvbfe_modulation modulation_caps; //valid for DVB-S,S2,C,T,H,DSS,ATSC
enum dvbfe_fec fec_caps; //valid for DVB-S,S2,DSS
enum dvbfe_stream_priority stream_priority_caps; //valid for DVB-T,H
__u32 frequency_min;
__u32 frequency_max;
__u32 frequency_step;
__u32 frequency_tolerance;
__u32 symbol_rate_min;
__u32 symbol_rate_max;
__u32 symbol_rate_tolerance;
enum fe_spectral_inversion inversion;
__u8 pad[128];
};

instead of the multiproto version which is more complex and repetitive:

/* DVB-S capability bitfields */
struct dvbfe_dvbs_info {
enum dvbfe_modulation modulation;
enum dvbfe_fec fec;
};
/* DSS capability bitfields */
struct dvbfe_dss_info {
enum dvbfe_modulation modulation;
enum dvbfe_fec fec;
};
/* DVB-S2 capability bitfields */
struct dvbfe_dvbs2_info {
enum dvbfe_modulation modulation;
enum dvbfe_fec fec;
__u8 pad[32];
};
/* DVB-C capability bitfields */
struct dvbfe_dvbc_info {
enum dvbfe_modulation modulation;
};
/* DVB-T capability bitfields */
struct dvbfe_dvbt_info {
enum dvbfe_modulation modulation;
enum dvbfe_stream_priority stream_priority;
__u8 pad[32];
};
/* DVB-H capability bitfields */
struct dvbfe_dvbh_info {
enum dvbfe_modulation modulation;
enum dvbfe_stream_priority stream_priority;
__u8 pad[32];
};
/* ATSC capability bitfields */
struct dvbfe_atsc_info {
enum dvbfe_modulation modulation;
__u8 pad[32];
};
struct dvbfe_info {
char name[128];
union {
struct dvbfe_dvbs_info dvbs;
struct dvbfe_dss_info dss;
struct dvbfe_dvbs2_info dvbs2;
struct dvbfe_dvbc_info dvbc;
struct dvbfe_dvbt_info dvbt;
struct dvbfe_dvbh_info dvbh;
struct dvbfe_atsc_info atsc;
__u8 pad[128];
} delsys;
__u32 frequency_min;
__u32 frequency_max;
__u32 frequency_step;
__u32 frequency_tolerance;
__u32 symbol_rate_min;
__u32 symbol_rate_max;
__u32 symbol_rate_tolerance;
enum fe_spectral_inversion inversion;
__u8 pad[128];
};

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
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.

UPDATE March 09 2008: This appears to have been changed with the introduction of DVBFE_SET_DELSYS which is now used
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
value appropriately on DVBFE_GET_INFO calls.

===Alternatives===
'''[[S2API]]: Tag/Value-based API proposal'''

Following long standing frustration amongst developers and users about the lack of progress in getting multiproto into
the Linux kernel, a group of four senior developers including the maintainer has proposed an alternative
(Aug 29 2008) and announced that they no longer support multiproto.
See http://linuxtv.org/pipermail/linux-dvb/2008-August/028313.html.
The idea had been proposed earlier http://linuxtv.org/pipermail/linux-dvb/2007-November/021618.html. Technically it is quite different from multiproto. Control
of the frontend is implemented using a command sequence of (tag,value)
pairs to set all the required parameters and
then initiate tuning. Thus it no longer depends on fixed structs to hold parameter data.
A notable advantage of the tag/value technique is that it should make it much easier
to keep up with future DVB transmission standards because this will at most require the definition
of additional tags (i.e. commands)
rather than a revision of the API.
Commands can be made atomic by passing a whole command sequence in a single ioctl (for example a set of
parameters followed by the tune command). Alternatively a sequence may be sent one command at a time.
The development repository is available at http://linuxtv.org/hg/~stoth/s2. Work still
needs to be done to finish the API design and port the existing DVB-S2 drivers to work with it. Other drivers
are not affected.

'''APIs used in the HVR4000 drivers'''
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.

A different method was used to provide support for DVB-S2 in the HVR4000 single frontend (sfe) driver.

'''Use multiproto drivers with old API'''
A patch exists which allows basic use of drivers developed for multiproto with the current API (3.2).
See http://linuxtv.org/pipermail/linux-dvb/2008-May/026246.html and
http://linuxtv.org/pipermail/linux-dvb/2008-August/027979.html.

===Status and Migration Plan===
''explain how a migration from the current API to multiproto could be achieved ... this means you''

The multiproto API will not be included in the Linux kernel (see above). Device support in the multiproto
tree will simply be converted to work with [[S2API]] where necessary.

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
tree are not automatically applied to both trees.

==Making it Work==

How to get it from the author's repository:

hg clone http://jusst.de/hg/multiproto
or
http://jusst.de/hg/multiproto/archive/tip.tar.bz2

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.
See
http://www.linuxtv.org/pipermail/linux-dvb/2008-July/027514.html. This appears to be
similar to the V4L/DVB staging development repository at http://linuxtv.org/hg/v4l-dvb/
but with the addition of multiproto code.

hg clone http://liplianindvb.sourceforge.net/hg/liplianindvb
hg clone http://liplianindvb.sourceforge.net/hg/szap2

===Drivers===
There are currently no in-kernel multiproto drivers. There are several cards which have experimental support in the multiproto tree, perhaps with additional patches.

''Provide details of which drivers work with multiproto ... this means you''

See the descriptions for the following cards:

[[Azurewave AD SP400 CI (VP-1041)|Azurewave AD-SP400 CI (Twinhan VP-1041)]]

[[Hauppauge]] [[Hauppauge WinTV-HVR-4000|WinTV-HVR-4000]]

[[KNC1]] [[KNC1 DVB-S2 TV Station|DVB-S2 TV Station]] (PCI32, supports CI)

[[TechnoTrend]] [[TechnoTrend TT-budget S2-3200|TT-budget S2-3200]]

[[TerraTec]] [[TerraTec Cinergy S2 PCI HD CI| Cinergy S2 PCI HD CI]] (PCI32, CI)

''provide the details of where the drivers and patches and necessary tools are available ... this means you''

''provide details of how to compile for recent kernels -- this means you''

===Sample kernel output===
''provide the relevant portion of dmesg here''

===Tuner / DiSEqC / Player support===
''provide comprehensive details of how to upgrade multimedia applications to work with the new API ... this means you''

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.

'''dvb-apps''' : There is ''still'' no patched dvb-apps tree. Someone needs to create one ... why don't you?

'''scan''' : see patched version at http://jusst.de/manu/scan.tar.bz2

'''szap''': see patched version at http://abraham.manu.googlepages.com/szap.c
Also see information about szap2 at http://allrussian.info/thread.php?postid=187408#post187408
and http://www.linuxtv.org/pipermail/linux-dvb/2008-February/023836.html.

'''[[MPlayer]]''' : someone needs to write a patch ... why don't you?

'''[[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,
http://www.linuxtv.org/pipermail/linux-dvb/2008-July/027141.html
and in these two messages:
http://sourceforge.net/mailarchive/forum.php?thread_name=48217036.3090709%40gmail.com&forum_name=kaffeine-devel
and
http://sourceforge.net/mailarchive/forum.php?thread_name=481DE023.9000903%40gmail.com&forum_name=kaffeine-devel
.

'''[[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
multiproto-free release 1.6.0 due to the unavailability of multiproto in the Linux kernel mainstream (not a
surprise to anyone). The requirement for multiproto was reinstated in version 1.7.0 (again jumping the gun),
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
to fix it by hand. There is even a patch which can be used to revert that (1.7.0+multiproto-update.diff) to
work with the v3.2 API drivers, and another newer one which will work with both APIs!
See http://linuxtv.org/pipermail/vdr/2008-August/017534.html and
http://www.udo-richter.de/vdr/patches.en.html#dvb-api-wrapper. [Prediction: VDR will remove the multiproto
requirement again before v1.8.0, flip,flop,flip,flop...].

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.

Version 1.7.1 has now been released, this time requiring multiproto_plus. See http://linuxtv.org/pipermail/linux-dvb/2008-September/028818.html.

Following the decision to merge S2API into the kernel (and not multiproto) the multiproto support in VDR
needs to be replaced with S2API support. An initial patch supporting S2API for DVB-S only has been written,
see http://linuxtv.org/pipermail/vdr/2008-September/017910.html.

'''[[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?

'''[[dvbstream]]''' : Someone needs to write a patch ... why don't you? See http://www.linuxtv.org/pipermail/linux-dvb/2008-February/024056.html.

''provide details of how to use with DiSEqC -- this means you''

===How to patch an application for Multiproto===
''provide guidance on patching applications to use multiproto -- this means you''

'''To tune to a channel''' : using the patched szap above as a guide we see that

struct dvb_frontend_parameters tuneto;
...
ioctl(fefd, FE_SET_FRONTEND, &tuneto);

must be replaced by

struct dvbfe_params fe_params;
...
ioctl(fefd, DVBFE_SET_PARAMS, &fe_params);

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.

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:

#if (DVB_API_VERSION==3) && (DVB_API_VERSION_MINOR>=3)
#define FE_PARAM struct dvbfe_params
#define IOCTL_SET_FE DVBFE_SET_PARAMS
#define DVB_SET_DELIVERY(a, b) (a)->delivery=(b)
#define DVBC_SET_SYMBOLRATE(a, b) (a)->delsys.dvbc.symbol_rate=(b)
#else
#define FE_PARAM struct dvb_frontend_parameters
#define IOCTL_SET_FE FE_SET_FRONTEND
#define DVB_SET_DELIVERY(a, b) do{ } while(0)
#define DVBC_SET_SYMBOLRATE(a, b) (a)->u.qam.symbol_rate=(b)
#endif

void tune(int fefd) {
FE_PARAM fparm;

memset(&fparm, 0, sizeof(FE_PARM));

DVB_SET_DELIVERY(&fparm, DVBFE_DELSYS_DVBC);
...
DVBC_SET_SYMBOLRATE(&fparm, symbolrate)

if (ioctl(fefd, IOCTL_SET_FE, &fparm) < 0) {
printf("Tuning failed");
}
}

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
a multiproto capable tuner coder without a single ifdef.

==External Links==

[[Category:Development]]

Pixelview PlayTV Pro Ultra

2012-02-08T19:44:49Z

Js: Reverted edits by Sanders Dowdy (talk) to last revision by Jimbley

==Features/Overview==
An analog PCI Card from [[ProLink]]
==Making it Work==
Autodetect is not possible for this card so you need use option card=27:

echo "options cx88xx card=27" > /etc/modprobe.d/cx88xx

With this setting TV image and channel tuning seems work, but sound with loopback cable still not heard.
If anybody know how to get this card completelly work write down please.

Discussion in video4linux mailing list about sound and fm tuner problem with this card:

http://threebit.net/mail-archive/video4linux/msg01145.html

http://threebit.net/mail-archive/video4linux/msg01166.html

> I have a PixelView PlayTV Pro Ultra (identified in windows as Prolink
> PV-TV303/304) for which I can get image, scan channels, etc., but: no radio
> yet, and no sound (unless I have warm-booted into windows and used the card's
> software there before). If I've cold booted into linux I don't get any sound at all.
> Kernel version is 2.6.15.6, gcc 4.0.3.

Those boards really sucks, since they don't offer any tveeprom and
several different models are selled with the same codename.
Radio should be working now, with mercurial version, available at
http://linuxtv.org/hg, with tuner=65.
[[Category:Analog PCI Cards]]
About sound, probably some gpio are wrong for your specific model. You
should run regspy (it cames with dscaller) and run at windows. There are
some instructions about how you can use it to generate an entry to v4l
code at wiki, on linuxtv.
==External Links==
http://www.prolink-usa.com/english/product/tv-cx883p+_ultra.html

Template talk:Help to support

2011-12-02T23:05:19Z

Js:

==Typo==
I don't have permission to edit the template.

"it is possible that you will peak the(se) developer's interest"

s/peak/pique/

--[[User:Pepsiman|Pepsiman]] 15:31, 2 December 2011 (CET)

:: 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)

::: Blame the spammers. New accounts are blocked from editing templates for the first 24h. --[[User:Js|js]] 00:05, 3 December 2011 (CET)

User talk:CityK

2011-10-02T20:08:58Z

Js:

[[User:CityK|CityK]] 19:46, 3 February 2007 (CET)

Spent a bunch of time last night and this morning creating and rearranging ATSC devices stuff.
There is a LOT of work that could be done.

[[User:CityK|CityK]] 01:02, 5 February 2007 (CET)

I got to find a WYSIWYG wiki editor, else using code takes me ages

[[User:CityK|CityK]] 08:23, 7 February 2007 (CET)

made a mess of the categories tonight ... will clean that whole thing up soon.
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.

Definitely several months of work to get this thing ship shape!

[[User:JGXenite|JGXenite]] 14:25, 20 April 2007 (CEST)

Hi CityK,

Sorry about that :(. I'll make my changes to Mplayer now.

[[User:JGXenite|JGXenite]] 14:56, 21 April 2007 (CEST)

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 :).

[[User:Howl|howl]] 00:01, 27 July 2007 (CEST)

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.

: 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)

:: 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)

:::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)

[[User:Specto|Specto]] 20:34, 2 January 2008 (GMT)

Hi CityK,

I noticed that you reverted my additions to the "How_to_install_DVB_device_drivers" page of the Linux TV Wiki.

I just wondered why you decided to do this ?

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.

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).
A reboot did not remove these errors.
I fixed this by disabling v4l in my kernel and rebuilding it before proceeding to the 'make install' phase.
(Drivers for my device already existed within the kernel but I need to use the newer ones which supported the remote control).

: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)

[[User:Bpringlemeir|Bpringlemeir]] 06:26, 27 November 2008 (CET)

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.
: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.

[[User:Howl|howl]] 20:52, 31 December 2008 (CET)

C'mon man, take a rest, is the last day of the year :)
: Ah, but I had! (The wiki is on Grenwich MT. I'm on -5GMT, so the edits you saw were from the day prior)

[[User:Hlangos|Hlangos]] 10:16, 7 April 2009 (CEST)

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.
: 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.
:: 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)
::: 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)

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?
: 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)
:: 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)

[[User:Howl|howl]] 10:50, 22 September 2009 (UTC)

Good point putting the web archive page for the [[AF9005]] ;)

== [[TechniSat AirStar USB / Air2PC DVB USB]] link on [[DVB-T USB Devices]] ==

A long time ago you added this to the "supported" section:
* [[TechniSat AirStar USB / Air2PC DVB USB]]
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)

: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

== Sysop status ==

Hi,

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.

Hope you're well

Cheers

Jim

: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:
:http://en.wikipedia.org/wiki/PCIe
:http://en.wikipedia.org/wiki/Template:Ambox
:http://en.wikipedia.org/wiki/Wikipedia:Stub
:--[[User:CityK|CityK]] 02:04, 11 May 2009 (CEST)

== Help with wiki integration ==

Hi CityK,

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.

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.

Cheers

Jim

: Hi Jim & CityK,
: 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
: a) decide which data we want to collect on the devices (this [[Template:USB_Device_Data#Syntax_and_Semantics|list]] is just my proposal)
:: 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.
::# 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.
::: 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.)
::# 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?
::: ''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.
::# 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?
::: Agreed.
: 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
::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:
::#Pre-purchase information about devices and support.
::#Post-purchase information about devices and support.
::#Technical background on DTV.
::#Programming information for drivers
::#Programming information for software
::and probably others (please add to this list!!).
::: 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.
::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.
:::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.
: 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"]].
: cheers -henrik --[[User:Hlangos|Hlangos]] 11:18, 11 June 2009 (UTC)
: 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.
:: I concur with this idea. I can see that an extra mailing list might well be the way to go.
:: Once again, fine work Henrik. Please let me know what you think of my comments.
:: Cheers
::Jim
::: 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 :-)

== Files to delete ==

Hi CityK, there are two image files that aren't needed anymore and can be deleted.

--[[User:Howl|howl]] 00:40, 1 October 2009 (UTC)

== New Software to watch Digital TV ==

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!

::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)

:::: Did it. Hope it fits well. :) [[User:Antoniop|Antoniop]] 22:39, 18 January 2011 (UTC)

== Spam users in the pipe ==

Hi there,
I just noticed that we have recently gained a lot of new users with names that seem to indicate German language spam.

These are the Users and the translation of their names:

[[User:xAbnehmen]] (lose weight)
[[User:xAnbieterstrom]] (supplier electricity)
[[User:xEnergie]] (energy)
[[User:xFirtenlernen]] (learning to flirt)
[[User:xForexanbieter]] (forex supplier)
[[User:xGastarife]] (gas rates)
[[User:xGasvergleich]] (gas comparison)
[[User:xLottozahlen]] (lottery numbers)
[[User:xNaturstrom]] (nature electricity)
[[User:xOekostrom]] (eco electricity)
[[User:xPreisvergleichstrom]] (price comparison electricity)
[[User:xStrombilliger]] (electricity cheaper)
[[User:xStrompreise]] (electricity prices)
[[User:xVergleichstrom]] (comparison electricity)
[[User:xVersorgerstrom]] (supplier electricity)

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.
Do we have a policy in place that enforces email address verification before allowing edits?

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]]

A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:

(SQL query hidden)

from within function "IndexPager::reallyDoQuery (UsersPager)". Database returned error "1176: Key 'PRIMARY' doesn't exist in table 'user' (localhost)".

cheers
--[[User:Hlangos|Hlangos]] 19:34, 29 September 2011 (CEST)

: 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)

: The SQL error should be fixed now. --[[User:Js|js]] 00:32, 30 September 2011 (CEST)

: 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)

:: @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?
::: 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)

:: @js: Thanks! Works like a charm now!

:: @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:
We log information related to reCAPTCHA, such as the Internet Protocol address of the end-user,
an identifier for the implementing site, the URL of the site accessed,
the CAPTCHA solution, the result of the CAPTCHA grading, the date and time of requests,
and one or more cookies that may uniquely identify the end-user browser.
In our logs, we will delete any information that identifies the individual URLs
within the implementing site within 30 days of the event logged.
:: 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...
:: 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)

::: 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)

Hey CityK, your mail bounces. Please contact me. --[[User:Js|js]] 22:08, 2 October 2011 (CEST)

User talk:CityK

2011-09-29T22:32:03Z

Js:

[[User:CityK|CityK]] 19:46, 3 February 2007 (CET)

Spent a bunch of time last night and this morning creating and rearranging ATSC devices stuff.
There is a LOT of work that could be done.

[[User:CityK|CityK]] 01:02, 5 February 2007 (CET)

I got to find a WYSIWYG wiki editor, else using code takes me ages

[[User:CityK|CityK]] 08:23, 7 February 2007 (CET)

made a mess of the categories tonight ... will clean that whole thing up soon.
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.

Definitely several months of work to get this thing ship shape!

[[User:JGXenite|JGXenite]] 14:25, 20 April 2007 (CEST)

Hi CityK,

Sorry about that :(. I'll make my changes to Mplayer now.

[[User:JGXenite|JGXenite]] 14:56, 21 April 2007 (CEST)

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 :).

[[User:Howl|howl]] 00:01, 27 July 2007 (CEST)

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.

: 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)

:: 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)

:::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)

[[User:Specto|Specto]] 20:34, 2 January 2008 (GMT)

Hi CityK,

I noticed that you reverted my additions to the "How_to_install_DVB_device_drivers" page of the Linux TV Wiki.

I just wondered why you decided to do this ?

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.

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).
A reboot did not remove these errors.
I fixed this by disabling v4l in my kernel and rebuilding it before proceeding to the 'make install' phase.
(Drivers for my device already existed within the kernel but I need to use the newer ones which supported the remote control).

: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)

[[User:Bpringlemeir|Bpringlemeir]] 06:26, 27 November 2008 (CET)

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.
: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.

[[User:Howl|howl]] 20:52, 31 December 2008 (CET)

C'mon man, take a rest, is the last day of the year :)
: Ah, but I had! (The wiki is on Grenwich MT. I'm on -5GMT, so the edits you saw were from the day prior)

[[User:Hlangos|Hlangos]] 10:16, 7 April 2009 (CEST)

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.
: 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.
:: 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)
::: 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)

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?
: 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)
:: 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)

[[User:Howl|howl]] 10:50, 22 September 2009 (UTC)

Good point putting the web archive page for the [[AF9005]] ;)

== [[TechniSat AirStar USB / Air2PC DVB USB]] link on [[DVB-T USB Devices]] ==

A long time ago you added this to the "supported" section:
* [[TechniSat AirStar USB / Air2PC DVB USB]]
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)

: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

== Sysop status ==

Hi,

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.

Hope you're well

Cheers

Jim

: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:
:http://en.wikipedia.org/wiki/PCIe
:http://en.wikipedia.org/wiki/Template:Ambox
:http://en.wikipedia.org/wiki/Wikipedia:Stub
:--[[User:CityK|CityK]] 02:04, 11 May 2009 (CEST)

== Help with wiki integration ==

Hi CityK,

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.

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.

Cheers

Jim

: Hi Jim & CityK,
: 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
: a) decide which data we want to collect on the devices (this [[Template:USB_Device_Data#Syntax_and_Semantics|list]] is just my proposal)
:: 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.
::# 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.
::: 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.)
::# 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?
::: ''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.
::# 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?
::: Agreed.
: 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
::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:
::#Pre-purchase information about devices and support.
::#Post-purchase information about devices and support.
::#Technical background on DTV.
::#Programming information for drivers
::#Programming information for software
::and probably others (please add to this list!!).
::: 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.
::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.
:::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.
: 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"]].
: cheers -henrik --[[User:Hlangos|Hlangos]] 11:18, 11 June 2009 (UTC)
: 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.
:: I concur with this idea. I can see that an extra mailing list might well be the way to go.
:: Once again, fine work Henrik. Please let me know what you think of my comments.
:: Cheers
::Jim
::: 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 :-)

== Files to delete ==

Hi CityK, there are two image files that aren't needed anymore and can be deleted.

--[[User:Howl|howl]] 00:40, 1 October 2009 (UTC)

== New Software to watch Digital TV ==

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!

::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)

:::: Did it. Hope it fits well. :) [[User:Antoniop|Antoniop]] 22:39, 18 January 2011 (UTC)

== Spam users in the pipe ==

Hi there,
I just noticed that we have recently gained a lot of new users with names that seem to indicate German language spam.

These are the Users and the translation of their names:

[[User:Abnehmen]] (lose weight)
[[User:Anbieterstrom]] (supplier electricity)
[[User:Energie]] (energy)
[[User:Firtenlernen]] (learning to flirt)
[[User:Forexanbieter]] (forex supplier)
[[User:Gastarife]] (gas rates)
[[User:Gasvergleich]] (gas comparison)
[[User:Lottozahlen]] (lottery numbers)
[[User:Naturstrom]] (nature electricity)
[[User:Oekostrom]] (eco electricity)
[[User:Preisvergleichstrom]] (price comparison electricity)
[[User:Strombilliger]] (electricity cheaper)
[[User:Strompreise]] (electricity prices)
[[User:Vergleichstrom]] (comparison electricity)
[[User:Versorgerstrom]] (supplier electricity)

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.
Do we have a policy in place that enforces email address verification before allowing edits?

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]]

A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:

(SQL query hidden)

from within function "IndexPager::reallyDoQuery (UsersPager)". Database returned error "1176: Key 'PRIMARY' doesn't exist in table 'user' (localhost)".

cheers
--[[User:Hlangos|Hlangos]] 19:34, 29 September 2011 (CEST)

: 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)

: The SQL error should be fixed now. --[[User:Js|js]] 00:32, 30 September 2011 (CEST)

TeVii S480

2011-09-18T08:28:56Z

Js: Reverted edits by Yilin168 (talk) to last revision by Torsten73

[[Image:S480.jpg|thumb|right|200px|TeVii S480 Card]]
A dual DVB-S2 PCIe card from [[TeVii]].

==Hardware/Features==
* PCIe x1 low profile
* Dual Tuner
* The card consists of a USB Host Controller and two [[TeVii S660]] equivalent cards.
* LNB power supply via floppy connector

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.

===Components Used===
* RF Tuner (twice): [[Montage]] [[Montage M88TS2020|M88TS2020]]
* Demodulator (twice): [[Montage]] [[Montage M88DS3000|M88DS3002]]
* USB Peripheral Controller (twice): Cypress CY7C68013A-56
* PCIe bridge/USB Host Controller: MosChip MCS9990CV

===Identification===
lspci -nnk:
04:00.0 USB Controller [0c03]: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0 Host Controller [9710:9990]
Subsystem: Device [a000:4000]
Kernel driver in use: ohci_hcd
04:00.1 USB Controller [0c03]: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0 Host Controller [9710:9990]
Subsystem: Device [a000:4000]
Kernel driver in use: ehci_hcd
04:00.2 USB Controller [0c03]: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0 Host Controller [9710:9990]
Subsystem: Device [a000:4000]
Kernel driver in use: ohci_hcd
04:00.3 USB Controller [0c03]: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0 Host Controller [9710:9990]
Subsystem: Device [a000:4000]
Kernel driver in use: ehci_hcd
04:00.4 USB Controller [0c03]: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0 Host Controller [9710:9990]
Subsystem: Device [a000:4000]
Kernel driver in use: ohci_hcd
04:00.5 USB Controller [0c03]: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0 Host Controller [9710:9990]
Subsystem: Device [a000:4000]
Kernel driver in use: ehci_hcd
04:00.6 USB Controller [0c03]: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0 Host Controller [9710:9990]
Subsystem: Device [a000:4000]
Kernel driver in use: ohci_hcd
04:00.7 USB Controller [0c03]: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0 Host Controller [9710:9990]
Subsystem: Device [a000:4000]
Kernel driver in use: ehci_hcd

lsusb:
Bus 003 Device 002: ID 9022:d482 TeVii Technology Ltd.
Bus 002 Device 002: ID 9022:d481 TeVii Technology Ltd.

Once the module/firmware is loaded it's listed as two TeVii S660 cards.

== Linux support ==
The [[s2-liplianin]] v4l branch includes support for the card.

From kernel 2.6.39 and above native support will be provided for the S480 Card.

== Howto compile ==
# these lines are only nessesary for building new version

# cd /usr/local/src/s2-liplianin
# make distclean
# make rminstall
cd /usr/local/src
# rm -r s2-liplianin.BAK
# mv s2-liplianin s2-liplianin.BAK
hg clone http://mercurial.intuxication.org/hg/s2-liplianin
cd s2-liplianin
make KERNELRELEASE=$(uname -r) -i -j4
make KERNELRELEASE=$(uname -r) install
make makelinks
reboot

The yavdr ppa has also a dkms driver for liplianin. Its not up to date but in a few days it should ;)

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:
md5sum dvb-usb-s660.fw*
c359c7616f8dc637db49c5c9fb6c8a41 dvb-usb-s660.fw
c359c7616f8dc637db49c5c9fb6c8a41 dvb-usb-s660.fw.forum
2946e99fe3a4973ba905fcf59111cf40 dvb-usb-s660.fw.keep

We normally needs the last one dvb-usb-S660.fw.keep
If there are different firmwares, try this way:

cd /usr/local/src
wget http://www.tevii.com/s2_liplianin_1.tar
tar xvf s2_liplianin_1.tar
cd tevii_s2_liplianin-eb8a914cd499/linux/firmware/
md5sum dvb-usb-s660.fw
#2946e99fe3a4973ba905fcf59111cf40 dvb-usb-s660.fw
cp dvb-usb-s660.fw /lib/firmware/

== Driver Status ==
27.02.2011 with actual liplianin tree from 27.02.2011:
* DVB-S is working fine with fast zappings around 1s
* DVB-S2 is working fine with fast zappings arround 1-2s
* S3 is working, you have to unload/load dvb modules for the suspend and wakeup
* without LNB Power the card uses 4,5W more with a 300W 82% powersupply BQT-L7 300W

* everything is tested on Astra 19.2E, diseque hasn´t been tested yet with the latest source
* tested with Kernel 2.6.32-28 (Torsten73) and 2.6.35 (Igor himself)
* tested with Kernel 3.0.3 (Torsten73) for working without v4l or s2-liplianin

==External Links==
[http://www.tevii.com/Products_S480_1.asp Official Website]
[http://www.vdrportal.de/board/thread.php?threadid=102390&threadview=0&hilight=&hilightuser=0&page=1 technical discussion on vdrportal in german]

[[Category:DVB-S PCIe Cards]]
[[Category:DVB-S2 PCIe Cards]]

Wiki - New Device Copy & Paste Template

2011-09-05T21:33:13Z

Js: restore after bad move

{{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.

Usage:
* Once you have logged in, simply click the edit tab at the top of this page
* Then from within the editing box at the bottom of the editing page, copy the entire contents of this article
* From within the editing box at the bottom of the new device page you are creating, paste the copied content from the "new device copy and paste template"
* Proceed to fill in the information relevant for the device and delete the italic directional comment sections provided by the template (as well as this notice)}}

''First, if possible, we would like a good overall image of what the device looks like (Note: do NOT use proprietary images unless you have obtained permission to do so). Next, provide a brief summary of what the device is and by whom it is provided (include wiki links to the card type and the vendor -- and, ideally, after you have finished editing this page, you should add links from those pages back to this one). The last introductory piece of information is the all important indication of whether or not the device is supported under Linux. Here's an example:''<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]]

An [[ATSC]] [[ATSC PCI cards]] from [[KWORLD]].

The ATSC 115 is supported under Linux since kernel 2.6.24.

''Note: The page contents menu will automagically build itself, so you need not worry about it''

==Overview/Features==
''Discuss the features and facets of the device here. For example:''<br>

* PCI interface
* Inputs: Antenna (Composite), Remote and S-Video In

===Components Used===
''List the hardware ICs and modules used by the device here. For example:''<br>
* [[Quantek QT1010]] (tuner)
* [[Zarlink MT352|Intel/Zarlink MT352]] (demodulator)
* [[Philips SAA7134|NXP/Philips SAA7130HL]] (A/V decoder and PCI Interface)

===Other Images===
''Use the included code to insert other images if necessary. Add as many high resolution pictures as you can i.e the card, the original box, the remote and, when uploading the files to the wiki, give them detailed specific names. Note: only use images taken by yourself or those 3rd party images for which you have received express written consent (such as from a vendor) that permits their usage. For example:''<br>
<gallery perrow=5>
Image:VideoMate_DVB-T220_box.jpg|VideoMate DVB-T220 Box
Image:VideoMate_DVB-T220_remote.jpg|VideoMate DVB-T220 Remote
</gallery>

===Identification===
''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>
# lspci -vvvnn
04:03.0 Multimedia controller [0480]: Philips Semiconductors SAA7130 Video Broadcast Decoder [1131:7130] (rev 01)
Subsystem: Compro Technology, Inc. Videomate DVB-T200 [185b:c901]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 84 (21000ns min, 8000ns max)
Interrupt: pin A routed to IRQ 20
Region 0: Memory at fdcfe000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-

==Making it Work==
''Is it supported under Linux? Are there experimental drivers? Does it partially work or identify as another card? (if yes, add this information below)''

===Firmware===
''Is there any firmware specific information for this device? if so, list it here. If your device doesn't require a firmware, simply mention that this is the case.''

===Drivers===
''Provide the details of where the drivers and patches and necessary tools are available.''

===Sample Kernel Output===
''Provide the '''relevant''' portion of dmesg here. For example:''<br>
# dmesg
[ 45.569669] saa7130/34: v4l2 driver version 0.2.14 loaded
[ 45.569739] saa7130[0]: found at 0000:04:03.0, rev: 1, irq: 20, latency: 84, mmio: 0xfdcfe000
[ 45.569745] saa7130[0]: subsystem: 185b:c901, board: Compro Videomate DVB-T200 [card=71,autodetected]
[ 45.569753] saa7130[0]: board init: gpio is 843f00
[ 45.569809] input: saa7134 IR (Compro Videomate DV as /devices/pci0000:00/0000:00:1e.0/0000:04:03.0/input/input7
[ 45.755429] saa7130[0]: i2c eeprom 00: 5b 18 01 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
[ 45.755437] saa7130[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff
[ 45.755443] saa7130[0]: i2c eeprom 20: 01 40 01 03 03 ff 03 01 08 ff 00 88 ff ff ff ff
[ 45.755449] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 45.755454] saa7130[0]: i2c eeprom 40: ff d5 00 c4 86 1e ff ff ff ff ff ff ff ff ff ff
[ 45.755460] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb
[ 45.755466] saa7130[0]: i2c eeprom 60: 30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 45.755471] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 45.755478] saa7130[0]: Unexpected tuner type info: d5 in eeprom
[ 45.755532] saa7130[0]: registered device video0 [v4l2]
[ 45.755550] saa7130[0]: registered device vbi0
[ 45.873425] saa7134 ALSA driver for DMA sound loaded
[ 45.873448] saa7130[0]/alsa: saa7130[0] at 0xfdcfe000 irq 20 registered as card -2
[ 45.943354] saa7130[0]/dvb: frontend initialization failed

===Remote Control Support===
''Discuss support for the remote control here.''

==External Links==
''Provide a link to the vendor's product page here along with any other external link to information that is generally helpful in relation to the device. For example:''<br>
* [http://www.comprousa.com/en/product/t100t220/t220.html Compro T-220 product page]

''Finally, add anything else that you think might be relevant under an appropriate heading.''

''Very last thing is add a catergory. (Remove the nowiki tags). For example''<br>
<nowiki>[[Category:DVB-T PCI Devices]]</nowiki>

TBS Qbox DVB-S2 CI USB2.0

2011-09-03T20:47:07Z

Js: revert spam

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.

The Qbox DVB-S2 CI is supported under Linux. The minimum required kernel version is (yet) unknown, the driver requires DVB version 5.1.

[[Image:Qbox_red.jpg|right|thumb|200px|The Qbox CI switched on. The CAM module has not been inserted]]

==Overview/Features==

* USB 2.0 interface (B-connector)
* Inputs: Antenna (F-connector), remote and CI-slot
* Separate power supply: 7.5V, 3.5A
* Indication LED, mostly red, sometimes blue, meaning yet unknown.

===Components Used===
* [[STMicroelectronics STB6100]] (tuner)
* [[STMicroelectronics STV0903]] (demodulator)

===Other Images===
<gallery perrow=4>
Image:Qbox_blue.jpg|Qbox with LED turned blue
Image:Qbox_CAM.jpg|Qbox with astoncrypt CAM
Image:Qbox_remote.jpg|Qbox remote control
Image:Qbox_package.jpg|Qbox package
</gallery>

===Identification===
lsusb output:
# lsusb -v
Bus 001 Device 009: ID 734c:5980 TBS Technologies China
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x734c TBS Technologies China
idProduct 0x5980
bcdDevice 0.00
iManufacturer 1 TBS-Tech
iProduct 2 DVBS2BOX
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

==Making it Work==
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.
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.

===Firmware===
The driver software package contains the firmware file: dvb-usb-tbsqbox-id5980.fw. Just install it in /lib/firmware.

===Drivers===
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.

===Sample Kernel Output===
The kernel outputs the information below, CAM module inserted (with module verbosity wide open):
# dmesg
[18814.387092] usb 1-7: new high speed USB device using ehci_hcd and address 9
[18814.502322] usb 1-7: New USB device found, idVendor=734c, idProduct=5980
[18814.502334] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[18814.502343] usb 1-7: Product: DVBS2BOX
[18814.502349] usb 1-7: Manufacturer: TBS-Tech
[18814.684522] dvb-usb: found a 'TBS Qbox DVB-S2 CI USB2.0' in cold state, will try to load a firmware
[18814.688745] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5980.fw'
[18814.691532] tbsqbox2ci: start downloading TBSQBOX2CI firmware
[18814.810199] dvb-usb: found a 'TBS Qbox DVB-S2 CI USB2.0' in warm state.
[18814.810330] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[18814.810751] DVB: registering new adapter (TBS Qbox DVB-S2 CI USB2.0)
[18815.048073] dvb-usb: MAC address: xx:xx:xx:xx:xx:xx ''(edited by me)''
[18815.048077]
[18815.050881] stv090x_attach: Create New Internal Structure!
[18815.156679] stv090x_attach: Attaching STV0903 demodulator(1) Cut=0x30
[18815.156689] tbsqbox2ci: Attached stv0903!
[18815.156692]
[18815.157478] tbsqbox2ci: CI initialized.
[18815.157488] DVB: registering adapter 0 frontend 0 (STV090x Multistandard)...
[18815.157590] stb6100_attach: Attaching STB6100
[18815.159811] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.7/usb1/1-7/input/input12
[18815.159952] dvb-usb: schedule remote query interval to 150 msecs.
[18815.159961] dvb-usb: TBS Qbox DVB-S2 CI USB2.0 successfully initialized and connected.
[18815.160051] usbcore: registered new interface driver tbsqbox2ci
[18861.422201] tbsqbox2ci: CI enabled.
[18861.422211] dvb_ca adapter 0: DVB CAM detected and initialised successfully

To get maximum verbosity, relevant parts of /etc/modprobe.d/modprobe.conf were set as follows:

options dvb_usb debug=511
options dvb_usb_tbsqbox2ci debug=3
options stb6100 verbose=3
options stv090x verbose=3

===Remote Control Support===
The device comes with a remote, but that has not been tested yet. Tbsdtv forum members complain about poor interoperability with LIRC.

==External Links==
* [http://www.tbsdtv.com/english/product/QBoxS2CI.html Qbox 2 CI product page]
* [http://www.tbsdtv.com/forum/index.php TBSDTV forum]
==Issues==
Remote control needs further research.

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 ;-).

Network support has not been addressed yet.

[[Category:DVB-S2_USB_Devices]]

TeVii S660

2011-09-03T20:45:42Z

Js: Reverted edits by Tony168 (talk) to last revision by Jlazkano

[[Image:S660.jpg|thumb|right|200px|TeVii S660 Card]]
DVB-S/S2 USB box manufactured by [[TeVii]]

==Hardware/Features==
* USB 2.0
* Power Supply is via 7.5V - that is outstanding, and I wonder how this come?!

===Components Used===
* RF Tuner: [[Montage]] [[Montage M88TS2020|M88TS2020]]
* Demodulator: [[Montage]] [[Montage M88DS3000|M88DS3000]]

===Identification===
lsusb:
Bus 003 Device 002: ID 9022:d660 TeVii Technology Ltd.

== Linux support ==
Supported by the vanilla kernel and the [[s2-liplianin]] v4l branch.

This works for me on a Debian Squeeze (2.6.32):

apt-get install linux-headers-`uname -r` build-essential
mkdir /usr/local/src/dvb
cd /usr/local/src/dvb
wget http://mercurial.intuxication.org/hg/s2-liplianin/archive/tip.zip
unzip s2-liplianin-0b7d3cc65161.zip
cd s2-liplianin-0b7d3cc65161
make CONFIG_DVB_FIREDTV:=n
make install

The firmware is downloaded from the Ubuntu forums (External Links), there are lots of different versions. This works for me:

http://ubuntuforums.org/attachment.php?attachmentid=192768&d=1305964408

== Pictures ==

<gallery perrow=5>
Image:TeVii_S660_top.JPG|Top side
Image:TeVii_S660_bottom.JPG|Bottom side
</gallery>

==External Links==
[http://www.tevii.com/Products_S660_1.asp Official Website]

[http://ubuntuforums.org/showthread.php?t=1378994 Support Thread for Ubuntu]

[http://www.gilzad.de/blog/pivot/entry.php?id=7 How to upload firmware to the device]

[[Category: DVB-S2 USB Devices]]

AzureWave DVB-S2 USB CI - AD-SB300 (7050)

2011-09-03T20:45:30Z

Js: Reverted edits by Tony168 (talk) to last revision by Jimbley

A [[DVB-S2]] [[DVB-S2 USB Devices|USB 2.0 Device]] from [http://www.digitalnow.com.au/product_pages/USBSat_CI.html Azurewave]
It is currently unsupported.

It seems to be an clone of [[Technisat SkyStar USB 2 HD CI]] from [http://www.technisat.de Technisat]

==Overview/Features==
This is a USB 2.0 device capable of receiving DVB-S and DVB-S2 tranponders including a CI-Slot.

Output of <code>lsusb -v</code>:
<pre>
Bus 005 Device 004: ID 13d3:3245 IMC Networks
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x13d3 IMC Networks
idProduct 0x3245
bcdDevice 0.02
iManufacturer 1 DTV-DVB
iProduct 2 UDST70XX
iSerial 3 0008CA1DB4B3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 100
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0002
(Bus Powered)
Remote Wakeup Enabled
</pre>

===Components Used===
[[STMicroelectronics]] [[STMicroelectronics STB0899|STB0899]] multistandard demodulator (DVB-S and DVB-S2).

[[STMicroelectronics]] [[STMicroelectronics STB6100|STB6100]] 8PSK/QPSK direct conversion (zero IF) tuner for DVB-S2.

===Identification===

Vendor ID: 13d3
Product ID: 3245

AzureWave DVB-S2 USB CI - AD-SB300 (7050) images:

{| border=1 cellpadding=10 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
|[[Image:AD-SB300-1.jpg|50px|]]
|[[Image:AD-SB300-2.jpg|50px|]]
|}

==Making it Work==
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.

==External Links==
* Available from [http://www.digitalnow.com.au/product_pages/USBSat_CI.html DigitalNow]
[[Category:DVB-S2 USB Devices]]

AVerMedia AverTV Hybrid Volar HX (A827)

2011-08-22T15:09:28Z

Js: revert spam

==Device Features==

{{Device_List_Low_Detail/Header
| content =
{{USB_Device_Data
|renderwith=Device_List_Low_Detail/Row
|selatt1=did
|selval1=avermedia-a827
}}
}}

===Specifications===

Interface: [[USB]] 2.0
Supported Broadcast Formats: [[DVB-T]], Analog, FM

This is what the USB DVB-T Database knows about this device:
{{Device_List_Full_Detail/Header
| content =
{{USB_Device_Data
|renderwith=Device_List_Full_Detail/Row
|selatt1=did
|selval1=avermedia-a827
}}
}}

===Chips===
* Cypress CY7C68013A
* NXP SAA7136E
* NXP TDA18271HDC1
* Afatech AF9013-N1
==Getting it to work==
Tested and worked on Fedora-11-i386, Kernel-2.6.29.4-167-PAE.fc11, Fedora 12 and Fedora 13 (both stock kernel)
Dependencies needed
(from installation DVD)
* kernel,
* kernel-headers,
* kernel-devel,
* gcc.
(yum install)
* dialog
* tvtime
* mplayer (with all it's dependencies, including codecs).
(drivers from [[AVerMedia|Avermedia]] website, as posted bellow)
* July 2009 - 0.07 beta driver for i386 or x86_64 - tested on Fedora-11
* 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
* May 2010 - 0.10 beta driver for x86_64 - works great on Fedora 13 (stock kernel)
* 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.
* '''''Avermedia's official answer is they stopped updating the driver for AverTV Hybrid Volar HX (A827)'''''.
* '''So, driver needed for this device with Kernels greater than 2.6.33 !!!'''.
* 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".
* '''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?!'''

Plug in the USB Volar HX ( A827 ) tuner.
Install driver in normal mode, and should see the installation concluded succesfully.
Next, the messages is to unplug the device (do so) and to replug it (do so)
Next is the sound testing. Modify the parameters according with your area.
You should hear a tv sound like (with or without station). The ideea is to get sound from the USB tuner.
After that there is the h826d-tools the software wants to install. You can install it, but there
is no need of it (some sh scripts tv-player, audio, radio-player).

The thing is after that, you should see in dmesg, the tuner loaded and then devices created
video0 vbi1 radio0 and even adapter0 (for dvb) and of course the alsa emulation for the tuner:
*A827 registered V4L2 device video0[video]
*[ 4373.455456] A827 registered V4L2 device vbi1[vbi]
*[ 4373.455486] A827 registered V4L2 device radio0[radio]
*[ 4373.455835] A827 registered ALSA sound card 1
*[ 4373.455844] DVB: registering new adapter (A827[0] DVB-T)
*[ 4373.455847] A827[0] DVB-T registered DVB adapter 0
*[ 4373.457303] DVB: registering adapter 0 frontend 0 (A827[0] DVB-T)...
A cat /proc/asound/cards should display 1: your system sound card (let's say ALC 826 analog device)
and 2: the sound emulation of your usb tv tuner.
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.

===Kernel 2.6.36, 2.6.37, 2.6.38 and 2.6.39===

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'''

For 2.6.37:
*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);'''
*in file '''H826D-expert-install/aver/osdep_dvb.c''' replace '''init_MUTEX(&p->feedlock);''' by '''sema_init(&p->feedlock, 1);'''
*add '''#define VFL_TYPE_VTX 3''' to top of file '''H826D-expert-install/aver/osdep_v4l2.c'''
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]

For 2.6.38 (with Big Kernel Lock (BKL) disabled by default) - Solution from [[AVerMedia_A828]]:
*'''Apply the solution for 2.6.36 and 2.6.37 before.'''
<pre>
1. In aver/osdep.c :
Replace :
void SysLockKernel()
{
lock_kernel();
}

void SysUnlockKernel()
{
unlock_kernel();
}
By
static DEFINE_MUTEX(dvbdev_mutex);
void SysLockKernel()
{
mutex_lock(&dvbdev_mutex);
}

void SysUnlockKernel()
{
mutex_unlock(&dvbdev_mutex);
}
2. In aver/osdep_th2.c :
2.a After :
#include "osdep_th2.h"
Add :
#include "osdep.h"
2.b Replace :
lock_kernel();
By :
SysLockKernel();

2.c and Replace :
unlock_kernel();
By:
SysUnlockKernel();
</pre>

For 2.6.39:
*'''Apply the solution for 2.6.36, 2.6.37 and 2.6.38 before.'''
Remove '''#include <linux/smp_lock.h>''' in file
* H826D-expert-install/aver/osdep.c
* H826D-expert-install/aver/osdep_dvb.c
* H826D-expert-install/aver/osdep_th2.c
* H826D-expert-install/aver/osdep_v4l2.c

=== Analog TV and composite ===

I only tested on analog tv and composite.
For video I used tvtime (scan and watch analog channels but no sound) and
mplayer - watched analog tv channels with sound on alsa server (I removed pulse as I always do.)
There is no need to start arecord, or aplay, or sox, or so if you are gonna use mplayer to watch TV,
as mplayer supports ALSA directly, but in this case, you must specify the hardware id:
Ex:
* if dmesg shows your Volar HX as: A827 registered ALSA sound card 1, you should declare in mplayer commandline adevice=hw.1
* if dmesg shows your Volar HX as: A827 registered ALSA sound card 2, you should declare in mplayer commandline adevice=hw.2
(Example:)
* mplayer tv:// -driver=v4l2:device=/dev/video0:norm=PAL:chanlist=europe-east:input=0:channel=R9:alsa:adevice=hw.1:forceaudio:immediatemode=0 tv://
(Similar for mencoder)
The only mention that it deserve to be made, is to install all the alsa-plugins.
Enjoy!

=== DVB-T ===

[[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
(fortunately today almost everyone has dual or quad), and you have no other choice then to close it (or kill it in some cases).

[[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.

=== FM-radio ===

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.
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
yet DVB radio either in Windows/linux).

===USB-Interfaces===

/proc/bus/usb/devices-output (shorter then lsusb -v):

T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 5 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=07ca ProdID=a827 Rev= 1.03
S: Manufacturer=AVerMedia
S: Product=AVerTV
S: SerialNumber=300871601647
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I: If#= 0 Alt= 1 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=500us
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=82(I) Atr=01(Isoc) MxPS=3030 Ivl=125us
I: If#= 0 Alt= 2 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=500us
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=82(I) Atr=01(Isoc) MxPS=2178 Ivl=125us
I: If#= 0 Alt= 3 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=500us
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=82(I) Atr=01(Isoc) MxPS=2058 Ivl=125us
I: If#= 0 Alt= 4 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=500us
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=82(I) Atr=01(Isoc) MxPS= 970 Ivl=125us
I: If#= 0 Alt= 5 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=500us
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=82(I) Atr=01(Isoc) MxPS= 684 Ivl=125us
I: If#= 0 Alt= 6 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=500us
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=82(I) Atr=01(Isoc) MxPS= 940 Ivl=125us

===Drivers===
You can download drivers for Linux i586/x86_64 here:

* [http://www.avermedia.com/avertv/Product/ProductDetail.aspx?Id=293&tab=APDriver AVerTV Hybrid Volar HX]

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.
[[Category:DVB-T USB Devices]]

==Kernel driver status==

* Avermedia stopped developing the driver for newer kernels, as posted above.
* Help appreciated!

This device is currently unsupported by drivers in the regular kernel
http://www.linuxtv.org/pipermail/linux-dvb/2008-October/029714.html

Main Page

2011-06-09T16:27:03Z

Js: Reverted edits by Jamesbzr (Talk) to last version by Js

Main Page

2011-05-17T17:42:53Z

Js: revert spam

Talk:Main Page

2011-04-28T06:12:27Z

Js: Reverted edits by Chjchj (Talk) to last version by Howl

== main page hacked ==

Main Page was "hacked" by a stupid guy: http://www.linuxtv.org/wiki/index.php?title=Main_Page&oldid=11512
someone should consider taking some actions towards his account.

I would like to say something to that guy:
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?

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.

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)!

== Categories articles organization ==

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)

TerraTec Cinergy C DVB-C

2011-04-28T06:11:43Z

Js: Reverted edits by Chjchj (Talk) to last version by Rho

[[Image:Cinergy-c.jpg|thumb|right|250px|Cinergy C DVB-C by Terratec]]

A [[DVB-C]] [[DVB-C PCI Cards|PCI card]] from [[TerraTec]].

==Overview/Features==

Looks to be a clone of the Azurewave/Twinhan AD-CP400 (VP-2040) [http://www.twinhan.com/product_AD-CP400.asp]

===Components Used===

* NXP/Philips CU1216 module
* NXP/Philips TDA10023 (demodulator)
* Mantis (bridge)

===Other Images===
<gallery perrow=5>
Image:Cinergy-c.jpg|The card
</gallery>

===Identification===

$ lspci -v -s 01:01.0
01:01.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01)
Subsystem: TERRATEC Electronic GmbH Unknown device 1178
Flags: bus master, medium devsel, latency 64, IRQ 22
Memory at cfdff000 (32-bit, prefetchable) [size=4K]

$ lspci -vvn -s 01:01.0
01:01.0 0480: 1822:4e35 (rev 01)
Subsystem: 153b:1178
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort+ <MAbort- >SERR- <PERR-
Latency: 64 (2000ns min, 63750ns max)
Interrupt: pin A routed to IRQ 22
Region 0: Memory at cfdff000 (32-bit, prefetchable) [size=4K]

==Making it Work==
The card is working under Linux using the Mantis driver.
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.

===Firmware===
No firmware required.

===Drivers===
====Kernel Driver====
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.

====S2API Driver for Kernel Versions < 2.6.33 ====
Install the latest mantis drivers:

sudo apt-get install mercurial linux-headers-$(uname -r) build-essential
hg clone http://mercurial.intuxication.org/hg/s2-liplianin
cd s2-liplianin
make
sudo make install
sudo reboot

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.

You should/could also use the sudo make menuconfig and remove all the unnecessary modules.

====Old Multiproto Driver====
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.

cd /usr/src
sudo apt-get install mercurial
sudo hg clone http://jusst.de/hg/mantis
cd mantis
sudo make
sudo make install
sudo reboot

===Sample kernel output===
Output from [http://mercurial.intuxication.org/hg/s2-liplianin s2-liplianin] driver under Kernel 2.6.28-15
[ 10.158595] Mantis 0000:04:09.0: PCI INT A -> Link[LNKB] -> GSI 17 (level, low) -> IRQ 17
[ 10.158700] irq: 17, latency: 64
[ 10.158701] memory: 0xdfeff000, mmio: 0xffffc20000054000
[ 10.158706] found a VP-2040 PCI DVB-C device on (04:09.0),
[ 10.158708] Mantis Rev 1 [153b:1178], irq: 17, latency: 64
[ 10.158710] memory: 0xdfeff000, mmio: 0xffffc20000054000
[ 10.161444] MAC Address=[00:08:ca:1d:b7:60]
[ 10.161482] mantis_alloc_buffers (0): DMA=0x3d5f0000 cpu=0xffff88003d5f0000 size=65536
[ 10.161488] mantis_alloc_buffers (0): RISC=0x3d129000 cpu=0xffff88003d129000 size=1000
[ 10.161491] DVB: registering new adapter (Mantis dvb adapter)
[ 10.681124] mantis_frontend_init (0): Probing for CU1216 (DVB-C)
[ 10.684607] TDA10023: i2c-addr = 0x0c, id = 0x7d
[ 10.684609] mantis_frontend_init (0): found Philips CU1216 DVB-C frontend (TDA10023) @ 0x0c
[ 10.684612] mantis_frontend_init (0): Mantis DVB-C Philips CU1216 frontend attach success
[ 10.684616] DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)...
[ 10.684684] mantis_ca_init (0): Registering EN50221 device
[ 10.684961] mantis_ca_init (0): Registered EN50221 device
[ 10.684971] mantis_hif_init (0): Adapter(0) Initializing Mantis Host Interface
[ 10.685048] input: Mantis VP-2040 IR Receiver as /devices/virtual/input/input5
[ 10.815684] Mantis VP-2040 IR Receiver: unknown key: key=0x00 raw=0x00 down=1

With latest build from [http://jusst.de/hg/mantis http://jusst.de/hg/mantis]:
[ 47.563542] found a VP-2040 PCI DVB-C device on (01:01.0),
[ 47.563543] Mantis Rev 1 [153b:1178], irq: 22, latency: 64
[ 47.563545] memory: 0xcfdff000, mmio: 0xf89de000
[ 47.566227] MAC Address=[00:08:ca:1c:73:1d]
[ 47.566254] mantis_alloc_buffers (0): DMA=0x37850000 cpu=0xf7850000 size=65536
[ 47.566292] mantis_alloc_buffers (0): RISC=0x37913000 cpu=0xf7913000 size=1000
[ 47.566332] DVB: registering new adapter (Mantis dvb adapter)
[ 48.086203] mantis_frontend_init (0): Probing for CU1216 (DVB-C)
[ 48.088334] mantis_frontend_init (0): found Philips CU1216 DVB-C frontend 0x0c
[ 48.088378] mantis_frontend_init (0): Mantis DVB-C Philips CU1216 frontend attach success
[ 48.088424] DVB: registering frontend 0 (Philips TDA10023 DVB-C)...
[ 54.367799] mantis_ack_wait (0): Slave RACK Fail !

===Remote Control Support===
Supported under the vanilla kernel module.

Works for the old mantis multiproto driver after applying the following patch. See [http://pauli.borodulin.fi/blog/?p=8]

===CI support===
CI/CAM support for the optional CI module is not working yet ({{CURRENTDAY}}.{{CURRENTMONTH}}.{{CURRENTYEAR}})

==Known Issues==

====Working around i2c bus probing interference with ivtv====
If the mantis module won't load (hangs) with the error message

mantis_ack_wait (0): Slave RACK Fail !

you should check [[http://www.linuxtv.org/pipermail/linux-dvb/2007-August/020087.html]]

----

<pre>
TDA10023(0): tda10023_writereg, writereg error (reg == 0x08, val == 0x23, ret == -121)
</pre>

----

femon output is not correct (statistics aren't implemented correctly in the driver)
<pre>
FE: Philips TDA10023 DVB-C (DVBC)
status SCVYL | signal ffff | snr ffff | ber 000f9f9f | unc 9f9f9f9f | FE_HAS_LOCK
status SCVYL | signal ffff | snr ffff | ber 000f9f9f | unc 9f9f9f9f | FE_HAS_LOCK
</pre>

==External Links==
* [http://tven.terratec.net/modules.php?op=modload&name=News&file=article&sid=267 Terratec product page]

[[Category:DVB-C PCI Cards]]

Main Page

2011-04-28T06:10:10Z

Js: Reverted edits by Chjchj (Talk) to last version by CityK

TV-Viewer

2010-11-15T16:27:26Z

Js: Reverted edits by Underwear001 (Talk) to last version by CityK

An analogue TV viewing application for devices equipped with a hardware MPEG2 encoder. TV-Viewer achieves its functionality by utilizing [[MPlayer]] as its backend.

==External Links==
* [http://tv-viewer.sourceforge.net/mediawiki/index.php/Main_Page TV-Viewer Homepage]

[[Category:Software]]
[[Category:Apps & Utilities]]

Iomega BUZ

2010-10-13T11:45:22Z

Js: Reverted edits by Anjila428 (Talk) to last version by Jimbley

==Card Features==
Inputs: Composite and S-video<br />
Norms: PAL, SECAM (720x576 @ 25 fps), NTSC (720x480 @ 29.97 fps)

=== Chipsets ===
* Zoran zr36067 PCI controller
* Zoran zr36060 MJPEG codec
* Philips saa7111 TV decoder
* Philips saa7185 TV encoder

=== How to make it work ===
Drivers to use: videodev, i2c-core, i2c-algo-bit, videocodec, saa7111, saa7185, zr36060, zoran<br />
Card number: 7

=== References ===
[http://www.trix.com/buz/faq.html http://www.trix.com/buz/faq.html]
[[Category:PCI]]
[[Category:Analog]]

B2C2 FlexCop

2010-09-28T17:22:05Z

Js: Reverted edits by MergeMac (Talk) to last version by Jimbley

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.

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.

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.

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.

The FlexCop family of chips can be found employed in several [[TechniSat]] DVB cards and USB devices.

== External Links ==
* [http://www.b2c2.com/ B2C2 Inc.]
* [http://www.b2c2.com/docs/flexcop.pdf FlexCop PDF]

[[Category:Chipsets]]

Main Page

2010-08-18T08:30:51Z

Js: Reverted edits by Alice.thomas222 (Talk) to last version by CityK

Main Page

2010-04-23T04:54:35Z

Js:

__NOTOC__
__NOEDITSECTION__

<div style="background-color:#6289AB; padding:0.3em; color:#ffffff; font-weight:bold; font-size:150%; text-align:center">
Welcome to the linuxtv.org V4L-DVB Wiki !
</div>
{|valign=top background=none
|valign=top|
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff">

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.
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.

-- [[LinuxTVWiki:People|The LinuxTV V4L-DVB wiki team]] / [[People behind V4L-DVB]]

</div>
|}

<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff">
{|valign=top cellpadding=0 cellspacing=5 width=100%
| [[Image:Exclaimation.png|75px]]
| '''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]].
|}
</div>

<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;">
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
== '''User Section:'''==
* [[Special:Allpages|The Wiki's Indexes]]
'''Getting Started:'''
* [[What is V4L or DVB?]]
* [[Supported Hardware]]
* [[How to Obtain, Build and Install V4L-DVB Device Drivers]]
** Driver List
'''Having Trouble?:'''
* [[FAQ & Troubleshooting]]
* [[Testing your DVB device]] (PCI, USB, ...)
* [[V4L Test Suite]]
* [[Testing reception quality]]
* [[Bug Report|Filing a Bug Report]]
'''Software Applications and Usage:'''
* ''Applications to watch and record TV''
** [[software#Standalone_Software_to_Watch_Digital_TV|Software to Watch Digital TV]]
** [[Software#Standalone_Software_to_Watch_Analogue_TV|Software to Watch Analogue TV]] ... also see [[V4L TV Viewing]]
** [[V4L capturing]] ... also see [[Transcode]]
* [[software#Media_Center_Software|Full Media Centers]]
* [[software#DVB_Utility_Suites_or_Standalone_Tools|Applications to show Videotext/Teletext/Closed Captioning]]
** [[Text capture]]
* [[software#DVB_Utility_Suites_or_Standalone_Tools|Tools for testing, tuning, streaming]]
* [[software#DVB_Utility_Suites_or_Standalone_Tools|Tools for unattended/headless recording]]
* [[Radio Listening Applications|Radio Listening]]
'''Tutorials, Howtos, Usage Info & Guides:'''
* Howto record [[multiple programs]] at once
* [[Post-processing]] of recorded material
* [[Further V4L and DVB Links]]
'''Examples of User Hardware and Software Configurations:'''
* [[Example setups]]
* [[Mailing List survey of devices in use]]
* [[Conditional Access Module Usage Examples]] (sorted by country)
* [[User Modifications to Supported Devices]]

=='''The Wiki - How Can I Help?'''==
* [[Help:Contents|Everything you need to know about editing wiki pages but were afraid to ask]]
** [http://www.mediawiki.org/wiki/Help:Moving_a_page Help: Renaming/Moving a Page]
* [[Wiki - Help Wanted List|A list of things that need to be tackled]]
* [[Wiki - New Device Copy & Paste Template|New Device Copy & Paste Template]]

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=32%|
=='''Technical Background:'''==
'''Systems:'''
* [[Analog TV]]
* [[Radio Data System (RDS)]]
* [[Digital TV|Digital TV (DTV)]]
** [[ATSC|ATSC Standards]]
** [[DVB Standards]]
** [[DMB-T/H|DMB-T/H Standard]]
** [[ISDB|ISDB Standards]]
* [[Modulation Scheme]]s used for Analog & DTV
* [[MPEG-2 Standard]]
** [[DSM-CC Object Carousel Protocol]]
* [[DiSEqC|DiSEqC Protocols]]
'''Hardware Component Related:'''
* [[List of Chipset Vendors|Sortable List of Chipset Vendors]]
* [[Anatomy of V4L-DVB devices]]
** [[Tuner]]s
** [[Demodulator]]s
** [[A/V Decoders]]
*** [[Radio devices|Radio Decoder Chipsets]]
** [[GPIO pins]]
** [[I²C Protocol]]
** [[Hardware or Software Decoder?]] (MPEG)
** [[Hardware vs software encoders]] (MPEG)
** [[Remote Controller chipsets]]
** [[Interface chipsets]]

== '''Developer Section:'''==
'''Repos:'''
* [http://git.linuxtv.org/v4l-dvb.git Git V4L-DVB development repository]
* [http://linuxtv.org/hg/v4l-dvb Mercurial V4L-DVB backport repository]
* [http://git.linuxtv.org/ A list of LinuxTV hosted Git development repositories]
* [http://linuxtv.org/hg/ A list of LinuxTV hosted Mercurial development repositories]
* [http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/mchehab/v4l-dvb.git;a=log Current git log]
* [[Maintaining Git trees]]
* [[Using a git driver development tree]]
* [[Maintaining Mercurial (Hg) trees]]
'''Kernel Driver Development:'''
* [http://jungla.dit.upm.es/%7Ejmseyas/linux/kernel/hackers-docs.html Linux kernel development documentation index]
* ''Application Programming Interface (API):''
** [[Development: Linux Media Infrastructure API|Linux Media Infrastructure API]]
* ''Drivers:''
** [[Anatomy of a V4L driver]]
** [[Anatomy of a DVB driver]]
** [[Development: How to add support for a device|How to add support for a device]]
** [[Development: How to develop drivers for USB based devices|How to develop drivers for USB based devices]]
*** [[DVB via USB|General Information Regarding DVB via USB]]
*** [[Development: Reverse Engineering USB Webcams|Reverse Engineering USB Webcams]]
** [[Development: Hints for Refactoring Existing Drivers|Hints for Refactoring Existing Drivers]]
* ''Submitting your work:''
** [[Development: Coding Style|Coding Style]]
** [[Development: Code Review|Invitation for Code Review]]
** [[Development: How_to_submit_patches |How to submit patches]]
*** [[Development: Submitting Patches|Rules for submitting patches]]
*** [[Development: Linux Kernel patch submittal checklist|Linux Kernel patch submittal checklist]]
*** [[Development: Submitting Drivers|Rules for submitting drivers]]
* ''Development miscellanea:''
** [[Bus snooping/sniffing]]
** [[Development: How to extract a firmware|How to extract a firmware]]
** [[Development: The DVB Decoder Challenge|The DVB Decoder Challenge]]
** [[TODO - main tasks]]
** [[V4L framework progress]]
** [[Libv4l Progress]]
'''Userspace Development:'''
* [[V4L2 Userspace Library]]

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=32%|
=='''Hardware Device Information:'''==
* [[List of Device Vendors|Sortable List of Device Vendors]]
'''Analogue Devices (V4L):'''
* [[Graphics cards with TV Tuner and/or Capture facilities]]
* [[Video via PCI]]
* [[Video via PCI Express (PCIe)]]
* [[Video via USB]]
* ''Other analogue devices:''
** [[V4L IEEE1394 devices|IEEE1394 devices]] (aka FireWire or i.LINK)
** [[Loopback]]
** [[Radio devices|Radio]]
** [[Scanners]]
** [[Webcams]]
'''Digital Devices (DVB):'''
* [[ATSC Devices]]
* [[DMB-T/H Devices]]
* [[DVB-C Devices]]
* [[DVB-S Devices]]
* [[DVB-S2 Devices]]
* [[8-PSK Turbo Coded Devices]]
* [[DVB-T Devices]]
* [[ISDB-T Devices]]
* [[Pre-configured DVB Systems and Set Top Hardware]]''
'''Peripheral Components:'''
* [[Antenna]]s (Rooftop, Indoor, Satellite Dishes)
* [[DD receiver|Dolby Digital receiver]]
* [[DiSEqC related hardware]]
** Switches, attenuators, and amplifiers
* [[DVB Conditional Access Modules]]
* [[Remote Controllers]]
** [[Remote controllers-V4L|Remote controllers (V4L article)]]

|}
</div>

[[Category:LinuxTV]]

Main Page

2010-02-17T20:34:59Z

Js: Reverted edits by Manu (Talk) to last version by Nmarci

__NOTOC__
__NOEDITSECTION__

<div style="background-color:#6289AB; padding:0.3em; color:#ffffff; font-weight:bold; font-size:150%; text-align:center">
Welcome to the linuxtv.org V4L-DVB Wiki !
</div>
{|valign=top background=none
|valign=top|
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff">

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.

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.

-- [[LinuxTVWiki:People|The LinuxTV V4L-DVB wiki team]] / [[People behind V4L-DVB]]

</div>
|}

<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff">
{|valign=top cellpadding=0 cellspacing=5 width=100%
| [[Image:Exclaimation.png|75px]]
| '''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]].
|}
</div>

<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;">
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
== '''User Section:'''==
* [[Special:Allpages|The Wiki's Indexes]]
'''Getting Started:'''
* [[What is V4L or DVB?]]
* [[Supported Hardware]]
* [[How to Obtain, Build and Install V4L-DVB Device Drivers]]
** Driver List
'''Having Trouble?:'''
* [[FAQ & Troubleshooting]]
* [[Testing your DVB device]] (PCI, USB, ...)
* [[V4L Test Suite]]
* [[Testing reception quality]]
* [[Bug Report|Filing a Bug Report]]
'''Software Applications and Usage:'''
* ''Applications to watch and record TV''
** [[software#Standalone_Software_to_Watch_Digital_TV|Software to Watch Digital TV]]
** [[Software#Standalone_Software_to_Watch_Analogue_TV|Software to Watch Analogue TV]] ... also see [[V4L TV Viewing]]
** [[V4L capturing]] ... also see [[Transcode]]
* [[software#Media_Center_Software|Full Media Centers]]
* [[software#DVB_Utility_Suites_or_Standalone_Tools|Applications to show Videotext/Teletext/Closed Captioning]]
** [[Text capture]]
* [[software#DVB_Utility_Suites_or_Standalone_Tools|Tools for testing, tuning, streaming]]
* [[software#DVB_Utility_Suites_or_Standalone_Tools|Tools for unattended/headless recording]]
* [[Radio Listening Applications|Radio Listening]]
'''Tutorials, Howtos, Usage Info & Guides:'''
* Howto record [[multiple programs]] at once
* [[Post-processing]] of recorded material
* [[Further V4L and DVB Links]]
'''Examples of User Hardware and Software Configurations:'''
* [[Example setups]]
* [[Mailing List survey of devices in use]]
* [[Conditional Access Module Usage Examples]] (sorted by country)
* [[User Modifications to Supported Devices]]

=='''The Wiki - How Can I Help?'''==
* [[Help:Contents|Everything you need to know about editing wiki pages but were afraid to ask]]
** [http://www.mediawiki.org/wiki/Help:Moving_a_page Help: Renaming/Moving a Page]
* [[Wiki - Help Wanted List|A list of things that need to be tackled]]
* [[Wiki - New Device Copy & Paste Template|New Device Copy & Paste Template]]

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=32%|
=='''Technical Background:'''==
'''Systems:'''
* [[Analog TV]]
* [[Radio Data System (RDS)]]
* [[Digital TV|Digital TV (DTV)]]
** [[ATSC|ATSC Standards]]
** [[DVB Standards]]
** [[DMB-T/H|DMB-T/H Standard]]
** [[ISDB|ISDB Standards]]
* [[Modulation Scheme]]s used for Analog & DTV
* [[MPEG-2 Standard]]
** [[DSM-CC Object Carousel Protocol]]
* [[DiSEqC|DiSEqC Protocols]]
'''Hardware Component Related:'''
* [[List of Chipset Vendors|Sortable List of Chipset Vendors]]
* ''Anatomy of a V4L-DVB device''
** [[Anatomy of a V4L device]]
** [[Anatomy of a DVB device]]
** [[Tuner]]s
** [[Demodulator]]s
** [[Interface chipsets]]
** [[Radio devices|Radio Chipsets]]
** [[GPIO pins]]
** [[I²C Protocol]]
** [[Hardware or Software Decoder?]]
** [[Hardware vs software encoders]]
** [[Remote Controllers]]

== '''Developer Section:'''==
'''Repos:'''
* [http://linuxtv.org/hg/v4l-dvb Master V4L-DVB development repository]
* [http://linuxtv.org/hg/ A list of LinuxTV hosted V4L-DVB development repositories]
* [http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/mchehab/v4l-dvb.git;a=log Current git log]
* [[Maintaining Git trees]]
* [[Maintaining Mercurial (Hg) trees]]
'''Kernel Driver Development:'''
* [http://jungla.dit.upm.es/%7Ejmseyas/linux/kernel/hackers-docs.html Linux kernel development documentation index]
* ''Application Programming Interface (API):''
** [[Development: Linux Media Infrastructure API|Linux Media Infrastructure API]]
* ''Drivers:''
** [[Anatomy of a V4L driver]]
** [[Anatomy of a DVB driver]]
** [[Development: How to add support for a device|How to add support for a device]]
** [[Development: How to develop drivers for USB based devices|How to develop drivers for USB based devices]]
*** [[DVB via USB|General Information Regarding DVB via USB]]
*** [[Development: Reverse Engineering USB Webcams|Reverse Engineering USB Webcams]]
** [[Development: Hints for Refactoring Existing Drivers|Hints for Refactoring Existing Drivers]]
* ''Submitting your work:''
** [[Development: Coding Style|Coding Style]]
** [[Development: Code Review|Invitation for Code Review]]
** [[Development: How_to_submit_patches |How to submit patches]]
*** [[Development: Submitting Patches|Rules for submitting patches]]
*** [[Development: Linux Kernel patch submittal checklist|Linux Kernel patch submittal checklist]]
*** [[Development: Submitting Drivers|Rules for submitting drivers]]
* ''Development miscellanea:''
** [[Bus snooping/sniffing]]
** [[Development: How to extract a firmware|How to extract a firmware]]
** [[Development: The DVB Decoder Challenge|The DVB Decoder Challenge]]
** [[TODO - main tasks]]
** [[Libv4l Progress]]
'''Userspace Development:'''
* [[V4L2 Userspace Library]]

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=32%|
=='''Hardware Device Information:'''==
* [[List of Device Vendors|Sortable List of Device Vendors]]
'''Analogue Devices (V4L):'''
* ''Graphics cards with TV Tuner and/or Capture facilities:''
** [[ATI/AMD#ATI Graphic cards with_TV Tuners and/or Capture facilities|ATI/AMD based combo cards]]
** [[RivaTV|NVIDIA based combo cards]]
** [[3Dfx Interactive|3Dfx Voodoo3 3500 TV]]
* ''Video via PCI:''
** [[Bttv devices (bt848, bt878)]]
** [[cx18 devices (cx23418)]]
** [[cx88 devices (cx2388x)]]
** [[ivtv devices (cx23415, cx23416)]]
** [[Matrox Meteor II cards]] (not working)
** [[saa713x devices]]
** [[saa7146 devices]]
** [[zoran devices (zr36057, zr36067)|zr360x7 devices (zr36057, zr36067)]]
** [[zr3612x devices]]
* ''Video via PCI Express (PCIe):''
** [[nGene devices]] (not supported)
** [[saa7162 devices]] (will be supported)
* ''Video via USB:''
** [[DiBcom USB devices]]
** [[Em28xx devices]]
** [[OmniVision USB devices (OV511, etc)]]
** [[PixArt PAC7301/PAC7302]]
** [[Pvrusb2|pvrusb2 devices]]
** [[Rtl2831_devices]]
** [[Trident TM6000#TM6000 based Devices|TM60x0 based devices]]
** [[USBVision devices]]
* ''Other devices:''
** [[V4L IEEE1394 devices|IEEE1394 devices]] (aka FireWire or i.LINK)
** [[Loopback]]
** [[Radio devices|Radio]]
** [[Remote controllers-V4L|Remote controllers]]
** [[Scanners]]
** [[Webcams]]
'''Digital Devices (DVB):'''
* ''Some descriptive name for the section''
** [[ATSC Devices]]
** [[DMB-T/H Devices]]
** [[DVB-C Devices]]
** [[DVB-S Devices]]
** [[DVB-S2 Devices]]
** [[8-PSK Turbo Coded Devices]]
** [[DVB-T Devices]]
** [[ISDB-T Devices]]

* ''Pre-configured DVB Systems and Set Top Hardware:''
** [[Barebones and bundles]]
** [[Commercial solutions]]
*** [[VDR-based STBs]]
*** [[MythTV STBs]]
*** [[Enigma on the dbox2]]
*** [[Neutrino on the dbox2]]
*** [[Enigma on the Dreambox]]
** [[Streaming clients]]
* ''Peripheral Components:''
** [[DD receiver|Dolby Digital receiver]]
** [[DiSEqC related hardware]]
** [[DVB Conditional Access Modules]]
** [[Antenna]]s (Rooftop, Indoor, Satellite Dishes)
** [[Remote Controllers]]
** Switches, attenuators, and amplifiers

|}
</div>

[[Category:LinuxTV]]

Archived:Main Page-V4L

2009-05-13T21:37:02Z

Js: Reverted edits by Mazyy (Talk); changed back to last version by CityK

__NOTOC__
__NOEDITSECTION__

<div style="background-color:#006600; padding:0.3em; color:#ffffff; font-weight:bold; font-size:150%; text-align:center">
Welcome to the video4linux wiki (For DVB wiki, click [http://www.linuxtv.org/wiki here])
</div>

{|valign=top background=none
|valign=top|
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff">

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].

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.

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!

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!

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.

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.

Enjoy!

[[People behind V4L]]

'''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.
</div>
|}

<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff">
{|valign=top cellpadding=0 cellspacing=5 width=100%
| [[Image:Exclaimation.png|75px]]
| '''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]].
|}
</div>

<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;">
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=5%|
|valign=top bgcolor=#F7F9FB width=45%|

* '''User Section'''
** [[How to build from Mercurial|How to build drivers from Mercurial]]
** [[How to write good problem report |How to write a good problem report]]
*** [[Test Suite]]
** Software Applications:
*** [[TV Viewing]]
*** [[TV Recording]]
*** [[Streaming]]
*** [[Text capture]] (Teletext/Closed Captioning)
*** [[Radio Listening Applications|Radio Listening]]
** [[v4l Links]]

* '''Technical Background
** Systems:
*** [[Analog TV]]
*** [[Digital TV]]
*** [[Radio Data System (RDS)]]
** Hardware Related:
*** [[Anatomy of a v4l device]]
**** [[PCI interface chipsets used for v4l cards]]
**** [[GPIO pins]]
**** [[i2c Protocol]]
**** [[Hardware vs software encoders]]
**** [[Audio Decoders]]

* '''Developer Section'''
** Kernel Development:
*** [[Anatomy of a v4l driver]]
*** [[Development: How to add support for a device|How to add support for a device]]
*** [[Development: USB based video drivers|USB based video drivers]]
*** [[SubmittingPatches | Rules for submitting patches]]
*** [[Development: How_to_submit_patches |How to submit patches]]
*** [[Documentation/SubmittingDrivers | Rules for submitting drivers]]
*** [[Documentation/CodingStyle | Coding Style]]
*** [[Documentation index]]
*** [[TODO - main tasks]]
** Userspace Development:
*** [[V4L2UserspaceLibrary|V4L2 Userspace library]]

|valign=top bgcolor=#F7F9FB width=45%|
* '''Supported Hardware'''
** Graphics cards with TV Tuner and/or Capture facilities:
*** [[ATI/AMD#ATI Graphic cards with_TV Tuners and/or Capture facilities|ATI/AMD based combo cards]]
*** [[RivaTV|NVIDIA based combo cards]]
** TV cards and drivers:
*** [[v4l card vendors]]
*** [[List survey of cards in use now]]
*** [[Tuners: Supported Tuners|Supported Tuners]]
*** Video via PCI:
**** [[bttv devices (bt848, bt878)]]
***** [[bttv kernel options]] documentation
***** [[btaudio (bt878)]]
***** [[snd-bt87x (alsa bt878 driver)]]
**** [[cx88 devices (cx2388x) ]]
**** [[ivtv devices (cx23415, cx23416)]]
**** [[cx18 devices (cx23418)]]
**** [[Matrox Meteor II cards]] (not working)
**** [[saa713x devices]]
***** [[saa7134-alsa]]
**** [[saa7146 devices]]
**** [[zoran devices (zr36057, zr36067)]]
**** [[zoran devices (zr36120, zr36125)]]
*** Video via PCI Express:
**** [[nGene devices]] (not supported)
**** [[saa7162 devices]] (will be supported)
*** Video via USB:
**** [[Hauppauge PVRUSB2]] (not to be confused with the wintv-usb2)
**** [[DiBcom USB devices]]
**** Em2820
**** [[Em28xx devices]]
**** [[OmniVision USB devices (OV511, etc)]]
**** [[Trident TM6000#TM6000 based Devices|TM6000 based devices]]
**** [[USBVision devices]]
** Other devices:
*** [[Firewire devices|Firewire]]
*** [[Loopback]]
*** [[Radio devices|Radio]]
*** [[Remote controllers]]
*** [[Scanners]]
*** [[Webcams]]

|}
</div>

[http://linuxtv.org Category:LinuxTV]

Development: Submitting Drivers

2008-10-21T09:06:26Z

Js: Reverted edits by Kz1Lg2 (Talk); changed back to last version by Js

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.

Also read the [[SubmittingPatches|Documentation/SubmittingPatches]] document.

== Allocating Device Numbers ==
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.

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
have shipped to customers before.

== Who To Submit Drivers To ==
;Linux 2.0: No new drivers are accepted for this kernel tree

;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>

;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>.

;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>.

== What Criteria Determine Acceptance ==
;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.

;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.

: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.

;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.

;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.

;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.

;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.

== What Criteria Do Not Determine Acceptance ==

;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.

;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.

== Resources ==
;Linux kernel master tree: ftp.??.kernel.org:/pub/linux/kernel/...<br> where ?? is your country code, such as "us", "uk", "fr", etc.

;Linux kernel mailing list: linux-kernel@vger.kernel.org <br> [mail majordomo@vger.kernel.org to subscribe]

;Linux Device Drivers, Third Edition (covers 2.6.10): http://lwn.net/Kernel/LDD3/ (free version)

;Kernel traffic [http://www.kerneltraffic.org/kernel-traffic/]: Weekly summary of kernel list activity (much easier to read)

;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]

;KernelTrap [http://kerneltrap.org/]: Occasional Linux kernel articles and developer interviews

; KernelNewbies [http://kernelnewbies.org/]: Documentation and assistance for new kernel programmers

;Linux USB project [http://sourceforge.net/projects/linux-usb/]: Helpful for the development of USB based device drivers

Maintaining Mercurial (Hg) trees

2008-10-21T09:06:19Z

Js: Reverted edits by SreHz3 (Talk); changed back to last version by Mkrufky

== The history of VCS for v4l ==

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].

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].

== Notes for maintainers ==

(See also file README.HG in the sources)

Current V4L/DVB tree uses a modern SCM system that fits better into
kernel development model, called Mercurial (aka hg).

There are some tutorials, FAQs and other valuable informations at
http://selenic.com/mercurial

Mercurial is a distributed SCM, which means every developer gets his
own full copy of the repository (including the complete revision
history), and can work and commit locally without network connection.
The resulting changesets can then be exchanged between repositories and
finally published to the master repository in linuxtv.org. A list of
current available repositories is available at: http://linuxtv.org/hg

The master repository with stable patches is available at:
http://linuxtv.org/hg/v4l-dvb

Mercurial is organized with a master tag, called tip. This tag contains
the master repository that will be used by normal users and to generate
patches to kernel.

This file postulates some simple rules for maintaing hg trees, as stated below:

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;

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.

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.

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.

Every developer should follow the "rules of thumb" of kernel development stated at Linux source code, especially:

* Documentation/SubmittingPatches
* Documentation/SubmittingDrivers
* Documentation/CodingStyle

All commits should have a consistent message. On v4l-dvb, this is done by using:

make commit

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.

Files can be added, removed or renamed at hg repository. This should be done by using:

hg add <files>
hg remove <files>
hg rename <source> <dest>
hg addremove [<files>]

<b>Warning</b> hg addremove will add/removes all files, including object files. Be careful! You can remove wrongly added files with hg remove.

If the commit went wrong, hg allows you to undo the last commit, by using the command:

hg undo

This command will preserve the changes at the files. So, a new hg commit will redo the desired commit.

To push the change to the repository you need to run:

hg push <url>

To update from the master repository, it is needed to do:

make pull

After pulling from master, if there are some changes at local repository, hg will require to merge it. This is done by

hg update -m
make commit

For hg to work properly, these vars should be defined (replacing the names at the left):

HGUSER="Maintainer Name <maintainer-email@cvsmaintainersite.com>"

If you use a different login name at the repo, you may use:

CHANGE_LOG_LOGIN=my_log_name

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:

export CHANGE_LOG_LOGIN HGUSER

It is strongly recommended to have these lines at .bashrc or .profile.

All commit messages shall have a Developers Certificate of Origin version 1.1 at commit log, as postulated at kernel's source at:

Documentation/SubmittingPatches

This is done by using Signed-off-by: fields at hg commit message.

It is not acceptable to use fake signatures like:

Signed-off-by: Fake me <me@snakeoilcompany.com>

The email should be a valid one. The bottom signed-off-by should be the commiter.

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:

patch subject
From: Patch Developer <patchdeveloper@patchdevelopersite.com>

patch descriptions

Signed-off-by: Patch Developer <patchdeveloper@patchdevelopersite.com>
Signed-off-by: Cvs Maintainer <cvsmaintainer@cvsmaintainersite.com>

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.

From: line shouldn't be suppressed, since it will be used when
converting to -git as patch author.

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.

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:

CC: someotherkerneldeveloper@someplace

Please notice that this is manually handled by the -git maintainer, so unnecessary usage should be avoided.

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:

kernel-sync

Patches with such lines will not be submitted upstream.

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.

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:

#if 0 /* keep */
or
#if 1 /* keep */

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.

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.

== Some quotations about development ==

"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

"Anyone who has never made a mistake has never tried anything new." - Albert Einstein

Audio Decoders

2008-09-16T19:30:04Z

Js: Reverted edits by OpyGc0 (Talk); changed back to last version by Gmy

== TV Sound Standards ==
{| border=1 cellspacing=0 cellpadding=5
|TV-System
| Sound Carrier [MHz]
| Sound Modulation
| Color System
| Country
|-
|B/G
|5.5/5.7421875
| FM-Stereo
|PAL
|Germany
|-
|B/G
| 5.5/5.85
|FM-Mono/NICAM
|PAL
|Scandinavia,Spain
|-
|L
|6.5/5.85
|AM-Mono/NICAM
|SECAM-L
|France
|-
|I
|6.0/6.552
|FM-Mono/NICAM
|PAL
|UK
|-
|D/K
|6.5/6.2578125 D/K1
6.5/6.7421875 D/K2

6.5/5.85 D/K/NICAM
|FM-Stereo
FM-Stereo

FM-Mono/NICAM
|SECAM-East
|USSR
Peoples Rep. of China

Hungary
|-
|M
M-Korea
|4.5
4.5/4.724212
|FM-Mono
FM-Stereo
|NTSC
|USA
Korea
|-
|Satellite
|6.5
7.02/7.20
|FM-Mono
FM-Stereo
|PAL
|ASTRA
|}
==TV Sound Decoding ==
The TV sound needs to be decoded in order to receive an Audio Frequency (Sound_AF) signal.

There are various possibilities

* Sound_AF provided by the tuner <br> Some tuners have mono out /stereo out /radio out

* Sound_IF provided by the tuner, this needs an extra decoder
** discrete decoding module (e.g. NE41S fpr BTSC stereo)
** simple audio decoder chip (e.g. tda9820)
** DSP audio decoder chip (e.g. MSP3415)
*** all DSP audio chips provide Sound_AF
*** some can provide I2S signal
** Audio decoding function built into the PCI bridge chip (e.g. cx25840)

== Sound Routing ==

There are multiple sound sources on the TV card, as there is only one
output, there must be a switch to select from these:
* Sound_AF from tuner (mono/stereo/radio)
* Sound_AF from decoder chip
* Line In

There can be these switches (aka mux or crossbars)
* HEF4052: this selects from 4 inputs
* some DSP audio decoder chips have multiple inputs
* some PCI bridge chips have multiple input

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).

== Sound Output ==

Sound can be output to:
* Line out
** Line out connected to sound card
** Line out connected to active speakers
* Speaker or headphone out (some cards had a headphone amplifier)
* 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
* also see I2S above

Archived:How to write good problem report

2008-08-29T09:16:34Z

Js: Reverted edits by OrlR0u (Talk); changed back to last version by CarlFK

Good problem report should include

0. Note that you are using V4L CVS.

1. Name of card

2. lspci -vn

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

4. Television standard for your country.

5. Exact sequence of actions that causes your problem.

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]].

Talk:Pinnacle PCTV Hybrid Pro Card (310c)

2008-08-18T00:08:00Z

Js: restore content

== Faq ==

==== PCI allocation failed ====

PCI: Failed to allocate mem resource #0:1000000@38000000 for 0000:03:00.2

----

to solve that problem change following entry in setup-bus.c in the kernel sources:

old entry:
#define CARDBUS_MEM_SIZE (32*1024*1024)
new entry:
#define CARDBUS_MEM_SIZE (48*1024*1024)

and recompile the kernel.

<pre>
$ cat /proc/iomem
...
30000000-35ffffff : PCI Bus #02
30000000-32ffffff : PCI CardBus #03
36000000-360003ff : 0000:00:1f.1
39000000-3bffffff : PCI CardBus #03
39000000-39ffffff : 0000:03:00.0
3a000000-3affffff : 0000:03:00.1
3b000000-3bffffff : 0000:03:00.2 <- this one failed to allocate previously
3c000000-3effffff : PCI CardBus #07
41000000-43ffffff : PCI CardBus #07
...
</pre>

<pre>
$ lspci -vvv
03:00.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05)
Subsystem: Yuan Yuan Enterprise Co., Ltd. Unknown device 1788
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 10
Region 0: Memory at 39000000 (32-bit, non-prefetchable) [disabled] [size=16M]
Capabilities: [44] Vital Product Data
Capabilities: [4c] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

03:00.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05)
Subsystem: Yuan Yuan Enterprise Co., Ltd. Unknown device 1788
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 10
Region 0: Memory at 3a000000 (32-bit, non-prefetchable) [disabled] [size=16M]
Capabilities: [4c] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

03:00.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05)
Subsystem: Yuan Yuan Enterprise Co., Ltd. Unknown device 1788
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 10
NEW --> Region 0: Memory at 3b000000 (32-bit, non-prefetchable) [disabled] [size=16M]
Capabilities: [4c] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
</pre>

==== Windows Allocation ====

allocation in windows:
<pre>
Cardbus #1:
E0207000 - E0207FFF
FEBFE000 - FEBFEFFF
FABFE000 - FEBFDFFF
E/A FF00 - FFFF
E/A FD00 - FDFF
IRQ 10
000DF000 - 000DFFFF

Cardbus #2:
E0208000 - E0208FFF
FABFD000 - FABFDFFF
E4000000 - E7FFFFFF
E/A FC00 - FCFF
E/A FB00 - FBFF
IRQ 10
000DE000 - 000DEFFF

PCMCIA:
Function 0: IRQ 10, FB000000 - FBFFFFFF - dvb-t/analog TV tuner card
Function 1: IRQ 10, FC000000 - FCFFFFFF - Pinnacle PCTV 310c Audio AVStream Device
Function 2: IRQ 10, FD000000 - FDFFFFFF - TS capture device
</pre>

==== /proc/iomem ====

<pre>
30000000-33ffffff : PCI Bus #01
30000000-31ffffff : PCI CardBus #02
32000000-33ffffff : PCI CardBus #06
34000000-340003ff : 0000:00:1f.1
36000000-37ffffff : PCI CardBus #02
38000000-39ffffff : PCI CardBus #06
</pre>

<pre>
PCI: Bus 2, cardbus bridge: 0000:01:06.0
IO window: 00003000-000030ff
IO window: 00003400-000034ff
PREFETCH window: 30000000-31ffffff
MEM window: 36000000-37ffffff
PCI: Bus 6, cardbus bridge: 0000:01:06.1
IO window: 00003800-000038ff
IO window: 00003c00-00003cff
PREFETCH window: 32000000-33ffffff
MEM window: 38000000-39ffffff
PCI: Bridge: 0000:00:1e.0
IO window: 3000-3fff
MEM window: e0200000-e07fffff
PREFETCH window: 30000000-33ffffff
</pre>

==== lspci -vvv ====
<pre>
03:00.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05)
Subsystem: Yuan Yuan Enterprise Co., Ltd. Unknown device 1788
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (5000ns min, 13750ns max)
Interrupt: pin A routed to IRQ 10
Region 0: Memory at 36000000 (32-bit, non-prefetchable) [size=16M]
Capabilities: [44] Vital Product Data
Capabilities: [4c] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

03:00.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05)
Subsystem: Yuan Yuan Enterprise Co., Ltd. Unknown device 1788
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR+
Latency: 64 (1000ns min, 63750ns max)
Interrupt: pin A routed to IRQ 10
Region 0: Memory at 37000000 (32-bit, non-prefetchable) [size=16M]
Capabilities: [4c] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

03:00.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05)
Subsystem: Yuan Yuan Enterprise Co., Ltd. Unknown device 1788
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 10
Capabilities: [4c] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
</pre>

==== dmesg (Kernel 2.6.18.4) ====
<pre>
pccard: CardBus card inserted into slot 0
Linux video capture interface: v2.00
cx2388x v4l2 driver version 0.0.6 loaded
PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 18 (level, low) -> IRQ 201
CORE cx88[0]: subsystem: 12ab:1788, board: Pinnacle Hybrid PCTV [card=57,autodetected]
TV tuner 71 at 0xc2, Radio tuner -1 at 0x1fe
cx2388x alsa driver version 0.0.6 loaded
cx2388x cx88-mpeg Driver Manager version 0.0.6 loaded
tuner 0-0061: chip found @ 0xc2 (cx88[0])
Tuner: setting up tuner core extension for: Xceive 3028 Tuner
ERROR TUNER TYPE NOT SUPPORTED (0)
cx88[0]/0: found at 0000:03:00.0, rev: 5, irq: 201, latency: 0, mmio: 0x45000000
PCI: Setting latency timer of device 0000:03:00.0 to 64
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
Loading base firmware: xc3028_init0.i2c.fw
Switching to Analogue TV
cx88_gpio_write: 132 - 0
Loading default analogue TV settings: xc3028_BG_PAL_A2_A.i2c.fw
xc3028_set_std, Loading specific configuration for requested mode xc3028_MN_NTSCPAL_A2.i2c.fw
PCI: Enabling device 0000:03:00.1 (0000 -> 0002)
ACPI: PCI Interrupt 0000:03:00.1[A] -> GSI 18 (level, low) -> IRQ 201
PCI: Setting latency timer of device 0000:03:00.1 to 64
cx88[0]/1: CX88x/0: ALSA support for cx2388x boards
cx88[0]/2: cx2388x 8802 Driver Manager
PCI: Enabling device 0000:03:00.2 (0000 -> 0002)
ACPI: PCI Interrupt 0000:03:00.2[A] -> GSI 18 (level, low) -> IRQ 201
PCI: Setting latency timer of device 0000:03:00.2 to 64
cx88[0]/2: found at 0000:03:00.2, rev: 5, irq: 201, latency: 64, mmio: 0x47000000
</pre>

==== DVB-T Scanning ====

The zl10353 status register shows up that it locks onto a channel, but there's no IRQ coming in which signals MPEG data.

<pre>
============== SCAN ============
STATUS6: 6f
STATUS7: 33
STATUS8: 00
FE_HAS_CARRIER
FE_HAS_VITERBI
FE_HAS_LOCK
FE_HAS_SYNC
</pre>

<pre>
WARNING: filter timeout pid 0x0010
>>> tune to: 482000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_16:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
>>> tuning status == 0x00
>>> tuning status == 0x06
>>> tuning status == 0x1e
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x0010
>>> tune to: 578000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_16:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
>>> tuning status == 0x00
>>> tuning status == 0x1e
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x0010
</pre>

Talk:Pinnacle PCTV Hybrid Pro Card (310c)

2008-08-18T00:04:16Z

Js: Reverted edits by Bq9A2i (Talk); changed back to last version by TqfNbp

== Faq ==

==== PCI allocation failed ====

PCI: Failed to allocate mem resource #0:1000000@38000000 for 0000:03:00.2

----

to solve that problem change following entry in setup-bus.c in the kernel sources:

old entry:
#define CARDBUS_MEM_SIZE (32*1024*1024)
new entry:
#define CARDBUS_MEM_SIZE (48*1024*1024)

and recompile the kernel.

<pre>
$ cat /proc/iomem
...
30000000-35ffffff : PCI Bus #02
30000000-32ffffff : PCI CardBus #03
36000000-360003ff : 0000:00:1f.1
39000000-3bffffff : PCI CardBus #03
39000000-39ffffff : 0000:03:00.0
3a000000-3affffff : 0000:03:00.1
3b000000-3bffffff : 0000:03:00.2 <- this one failed to allocate previously
3c000000-3effffff : PCI CardBus #07
41000000-43ffffff : PCI CardBus #07
...
</pre>

<pre>
$ lspci -vvv
03:00.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05)
Subsystem: Yuan Yuan Enterprise Co., Ltd. Unknown device 1788
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap 66MHz- UDF- FastB2B ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 10
Region 0: Memory at 39000000 (32-bit, non-prefetchable) [disabled] [size=16M]
Capabilities: [44] Vital Product Data
Capabilities: [4c] Power Management version 2
Flags: PMEClk- DSI D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

03:00.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05)
Subsystem: Yuan Yuan Enterprise Co., Ltd. Unknown device 1788
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap 66MHz- UDF- FastB2B ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 10
Region 0: Memory at 3a000000 (32-bit, non-prefetchable) [disabled] [size=16M]
Capabilities: [4c] Power Management version 2
Flags: PMEClk- DSI D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

03:00.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05)
Subsystem: Yuan Yuan Enterprise Co., Ltd. Unknown device 1788
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap 66MHz- UDF- FastB2B ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 10
NEW --> Region 0: Memory at 3b000000 (32-bit, non-prefetchable) [disabled] [size=16M]
Capabilities: [4c] Power Management version 2
Flags: PMEClk- DSI D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
</pre>

==== Windows Allocation ====

allocation in windows:
<pre>
Cardbus #1:
E0207000 - E0207FFF
FEBFE000 - FEBFEFFF
FABFE000 - FEBFDFFF
E/A FF00 - FFFF
E/A FD00 - FDFF
IRQ 10
000DF000 - 000DFFFF

Cardbus #2:
E0208000 - E0208FFF
FABFD000 - FABFDFFF
E4000000 - E7FFFFFF
E/A FC00 - FCFF
E/A FB00 - FBFF
IRQ 10
000DE000 - 000DEFFF

PCMCIA:
Function 0: IRQ 10, FB000000 - FBFFFFFF - dvb-t/analog TV tuner card
Function 1: IRQ 10, FC000000 - FCFFFFFF - Pinnacle PCTV 310c Audio AVStream Device
Function 2: IRQ 10, FD000000 - FDFFFFFF - TS capture device
</pre>

==== /proc/iomem ====

<pre>
30000000-33ffffff : PCI Bus #01
30000000-31ffffff : PCI CardBus #02
32000000-33ffffff : PCI CardBus #06
34000000-340003ff : 0000:00:1f.1
36000000-37ffffff : PCI CardBus #02
38000000-39ffffff : PCI CardBus #06
</pre>

<pre>
PCI: Bus 2, cardbus bridge: 0000:01:06.0
IO window: 00003000-000030ff
IO window: 00003400-000034ff
PREFETCH window: 30000000-31ffffff
MEM window: 36000000-37ffffff
PCI: Bus 6, cardbus bridge: 0000:01:06.1
IO window: 00003800-000038ff
IO window: 00003c00-00003cff
PREFETCH window: 32000000-33ffffff
MEM window: 38000000-39ffffff
PCI: Bridge: 0000:00:1e.0
IO window: 3000-3fff
MEM window: e0200000-e07fffff
PREFETCH window: 30000000-33ffffff
</pre>

==== lspci -vvv ====
<pre>
03:00.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05)
Subsystem: Yuan Yuan Enterprise Co., Ltd. Unknown device 1788
Control: I/O- Mem BusMaster SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap 66MHz- UDF- FastB2B ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (5000ns min, 13750ns max)
Interrupt: pin A routed to IRQ 10
Region 0: Memory at 36000000 (32-bit, non-prefetchable) [size=16M]
Capabilities: [44] Vital Product Data
Capabilities: [4c] Power Management version 2
Flags: PMEClk- DSI D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

03:00.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05)
Subsystem: Yuan Yuan Enterprise Co., Ltd. Unknown device 1788
Control: I/O- Mem BusMaster SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap 66MHz- UDF- FastB2B ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR
Latency: 64 (1000ns min, 63750ns max)
Interrupt: pin A routed to IRQ 10
Region 0: Memory at 37000000 (32-bit, non-prefetchable) [size=16M]
Capabilities: [4c] Power Management version 2
Flags: PMEClk- DSI D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

03:00.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05)
Subsystem: Yuan Yuan Enterprise Co., Ltd. Unknown device 1788
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap 66MHz- UDF- FastB2B ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 10
Capabilities: [4c] Power Management version 2
Flags: PMEClk- DSI D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
</pre>

==== dmesg (Kernel 2.6.18.4) ====
<pre>
pccard: CardBus card inserted into slot 0
Linux video capture interface: v2.00
cx2388x v4l2 driver version 0.0.6 loaded
PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 18 (level, low) -> IRQ 201
CORE cx88[0]: subsystem: 12ab:1788, board: Pinnacle Hybrid PCTV [card=57,autodetected]
TV tuner 71 at 0xc2, Radio tuner -1 at 0x1fe
cx2388x alsa driver version 0.0.6 loaded
cx2388x cx88-mpeg Driver Manager version 0.0.6 loaded
tuner 0-0061: chip found @ 0xc2 (cx88[0])
Tuner: setting up tuner core extension for: Xceive 3028 Tuner
ERROR TUNER TYPE NOT SUPPORTED (0)
cx88[0]/0: found at 0000:03:00.0, rev: 5, irq: 201, latency: 0, mmio: 0x45000000
PCI: Setting latency timer of device 0000:03:00.0 to 64
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
Loading base firmware: xc3028_init0.i2c.fw
Switching to Analogue TV
cx88_gpio_write: 132 - 0
Loading default analogue TV settings: xc3028_BG_PAL_A2_A.i2c.fw
xc3028_set_std, Loading specific configuration for requested mode xc3028_MN_NTSCPAL_A2.i2c.fw
PCI: Enabling device 0000:03:00.1 (0000 -> 0002)
ACPI: PCI Interrupt 0000:03:00.1[A] -> GSI 18 (level, low) -> IRQ 201
PCI: Setting latency timer of device 0000:03:00.1 to 64
cx88[0]/1: CX88x/0: ALSA support for cx2388x boards
cx88[0]/2: cx2388x 8802 Driver Manager
PCI: Enabling device 0000:03:00.2 (0000 -> 0002)
ACPI: PCI Interrupt 0000:03:00.2[A] -> GSI 18 (level, low) -> IRQ 201
PCI: Setting latency timer of device 0000:03:00.2 to 64
cx88[0]/2: found at 0000:03:00.2, rev: 5, irq: 201, latency: 64, mmio: 0x47000000
</pre>

==== DVB-T Scanning ====

The zl10353 status register shows up that it locks onto a channel, but there's no IRQ coming in which signals MPEG data.

<pre>
============== SCAN ============
STATUS6: 6f
STATUS7: 33
STATUS8: 00
FE_HAS_CARRIER
FE_HAS_VITERBI
FE_HAS_LOCK
FE_HAS_SYNC
</pre>

<pre>
WARNING: filter timeout pid 0x0010
>>> tune to: 482000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_16:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
>>> tuning status == 0x00
>>> tuning status == 0x06
>>> tuning status == 0x1e
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x0010
>>> tune to: 578000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_16:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
>>> tuning status == 0x00
>>> tuning status == 0x1e
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x0010
</pre>

Development: Submitting Drivers

2008-08-18T00:02:25Z

Js: Reverted edits by VnpMav (Talk); changed back to last version by CityK

V4L capture script

2008-07-12T09:31:27Z

Js: Reverted edits by VxlPed (Talk); changed back to last version by Js

===Introduction===

An updated version of this script may be available at [http://www.fernmeldung.de/capture/ fernmelding.de].

===The capture script===

This script lets you encode to raw video, mpeg4, or H.264 according to your needs.

<pre>

#!/bin/sh

# Name: capture
PROG_VERSION="0.9.8"
# Datum: 15.03.2006

# Analoge Video-Aufzeichnung von Video4Linux-TV-Karte

# Benoetigt: mencoder
# Empfohlen: GNU time

# Quelle: http://www.fernmeldung.de/capture/

echo "---------------------------------------------------------------"
echo "capture $PROG_VERSION (http://www.fernmeldung.de/capture)"
echo "Aufzeichnung von analoger Video4Linux-TV-Karte"
echo "---------------------------------------------------------------"
echo "Winke fuer eine erfolgreiche Aufzeichnung:"
echo "- ntp-Daemonen u.ae. Zeitverstell-Programme beenden, da sonst"
echo " Sync-Probleme auftreten koennten"
echo "- Audio-Eingang (igain) auf 70 einstellen"
echo "- Ggf. Audio-Pegel der Quelle (z.B. DVB-Empfaenger) einstellen"
echo "---------------------------------------------------------------"

DVDx=720
DVDy=576
DVDxy=$DVDx"x"$DVDy
# 5000 + 192 = 5192kbit/s = 38,1 MB/Min.

HuffYUVx=768
HuffYUVy=576
HuffYUVxy=$HuffYUVx"x"$HuffYUVy
# 768x576 + MP2 = 650 MB/Min.

MPEG4x=576
MPEG4y=432
MPEG4xy=$MPEG4x"x"$MPEG4y
MPEG4bitrate=1200
# 1200+128=1328kbit/s=9,8 MB/Min.
# 1500+128=1628kbit/s=12,0 MB/Min.
# 1800+128=1928kbit/s=14,2 MB/Min.

x264x=384
x264y=288
x264xy=$x264x"x"$x264y

# Temp-Datei fuer time-Ausgabe:
# $$ = PID
TEMP_DATEI="/tmp/capture_time.$$.tmp"

echo -n "Name der Aufzeichnung [aufzeichnung]: "
read NAME

# NAME leer (zero) ?
if [ -z $NAME ]; then
NAME="aufzeichnung"
fi

# Bei Audio-Aufzeichnungsproblemen kann evtl. ein angehaengtes :forceaudio helfen
BEFEHL="mencoder tv:// -tv driver=v4l:norm=pal:input=1:fps=25:audiorate=48000"

echo -n "Format (d=DVD-"$DVDxy", h=HuffYUV-"$HuffYUVxy", x=x264-"$x264xy") [MPEG4-"$MPEG4xy"]: "
read FORMAT

case $FORMAT in
d) echo "Format: DVD / AC3 / "$DVDxy" (etwa 40 MB/Min.)"
AUFLOESUNG=$DVDxy
CODECS="DVD_AC3"
BEFEHL=$BEFEHL":width="$DVDx":height="$DVDy" -oac lavc -ovc lavc -of mpeg -mpegopts format=dvd -lavcopts vcodec=mpeg2video:vrc_buf_size=1835:vrc_maxrate=8000:vbitrate=5000:keyint=15:acodec=ac3:abitrate=192:aspect=4/3"
# (see mplayer homepage for encoding examples)
;;

h) echo "Format: HuffYUV / MP2 / "$HuffYUVxy" (etwa 650 MB/Min.)"
AUFLOESUNG=$HuffYUVxy
CODECS="HuffYUV_MP2"
BEFEHL=$BEFEHL":width="$HuffYUVx":height="$HuffYUVy" -oac lavc -ovc lavc -lavcopts vcodec=huffyuv:format=422p:acodec=mp2:abitrate=224"
;;

x) echo "Format: X264 / MP3 / $x264xy"
AUFLOESUNG=$x264xy
CODECS="x264_MP3"
BEFEHL=$BEFEHL":width="$x264x":height="$x264y" -ovc x264 -x264encopts bitrate=1000 -oac lavc -lavcopts acodec=mp2"
# vhq=1..4
;;

*) echo "Format: MPEG4 / MP3 / $MPEG4xy / $MPEG4bitrate kbit/s (9,8 MB/Min.)"
AUFLOESUNG=$MPEG4xy
CODECS="FMP4_MP3"
BEFEHL=$BEFEHL":width="$MPEG4x":height="$MPEG4y" -ovc lavc -lavcopts vcodec=mpeg4:mbd=2:vbitrate="$MPEG4bitrate" -ffourcc XVID -oac mp3lame -lameopts cbr:br=128"
;;
esac

echo -n "Deinterlacing (n=nein) [ja] ? "
read DI
if [ "$DI" != "n" ]; then
echo "Deinterlacing: ja"
DI=".deinterlaced"
BEFEHL="$BEFEHL -vf pp=lb"
else
echo "Deinterlacing: nein"
DI=""
fi

echo -n "Maximale Aufnahmedauer ([[hh:]mm:]ss) [unbegrenzt]: "
read DAUERMAX
if [ $DAUERMAX ]; then
echo "Aufnahmedauer: $DAUERMAX"
BEFEHL="$BEFEHL -endpos $DAUERMAX"
else
echo "Aufnahmedauer: unbegrenzt"
fi

echo "--------------------------------------------------------------"
echo "Fuehre aus: $BEFEHL"
echo "--------------------------------------------------------------"
echo "Die Aufzeichnung kann mit <Strg>-C korrekt beendet werden."
echo "Eingabe-Taste druecken, um mit der Aufzeichnung zu beginnen"
echo "<Strg>-C zum Abbruch"
read x

STARTZEIT=$(date +%Y.%m.%d_%H:%M)

DATEI=$NAME"."$STARTZEIT"."$AUFLOESUNG$DI"."$CODECS

BEFEHL="$BEFEHL -o $DATEI"

# Wo ist GNU time ?
TIMEBEFEHL=$(which time)

if [ $TIMEBEFEHL -a -x $TIMEBEFEHL ]; then

# quiet=keine Abbruchmeldung format %e = Realsekunden -o Ausgabedatei
$TIMEBEFEHL -o $TEMP_DATEI --quiet --format %e $BEFEHL

DAUERsec=$(cat $TEMP_DATEI)
rm $TEMP_DATEI

# Loeschen aller Zeichen vom Zeilenende bis zu einem Punkt
# und des Punktes selbst (also eine ganze Zahl machen):
DAUERsec=${DAUERsec%.*}

if [ $DAUERsec -lt 60 ]; then
DAUER=${DAUERsec}sec
else
DAUERmin=$[$DAUERsec/60]
DAUER=${DAUERmin}min
fi

ENDDATEI=$DATEI"."$DAUER".avi"
else
$BEFEHL
ENDDATEI=$DATEI".avi"
echo
echo "Hinweis: Konnte die Aufnahmedauer nicht ermitteln und dem Dateinamen zufuegen, da das Programm \"time\" nicht ausfuehrbar ist (Achtung: Es wird die Programmdatei time (GNU time) benoetigt, kein Shell-interner time-Befehl; pruefen mit \"which time\")."
echo "Falls gewuenscht, \"time\" ausfuehrbar machen."
echo
fi

mv $DATEI $ENDDATEI

echo "------------------------------------------------------"
echo "Datei: $ENDDATEI"
echo "------------------------------------------------------"

</pre>

Meye

2008-07-12T09:28:17Z

Js: Reverted edits by McrU2q (Talk); changed back to last version by UpooPoo

===Vaio Picturebook Motion Eye Camera Driver Readme===
From /usr/src/linux/Documentation/video4linux/meye.txt

* Copyright (C) 2001-2004 Stelian Pop <stelian@popies.net>
* Copyright (C) 2001-2002 Alcôve <www.alcove.com>
* Copyright (C) 2000 Andrew Tridgell <tridge@samba.org>

This driver enables the use of video4linux compatible applications with the
Motion Eye camera. This driver requires the "Sony Vaio Programmable I/O
Control Device" driver (which can be found in the "Character drivers"
section of the kernel configuration utility) to be compiled and installed
(using its "camera=1" parameter).

It can do at maximum 30 fps @ 320x240 or 15 fps @ 640x480.

Grabbing is supported in packed YUV colorspace only.

MJPEG hardware grabbing is supported via a private API (see below).

===Hardware supported===

This driver supports the 'second' version of the MotionEye camera :)

The first version was connected directly on the video bus of the Neomagic
video card and is unsupported.

The second one, made by Kawasaki Steel is fully supported by this
driver (PCI vendor/device is 0x136b/0xff01)

The third one, present in recent (more or less last year) Picturebooks
(C1M* models), is not supported. The manufacturer has given the specs
to the developers under a NDA (which allows the develoment of a GPL
driver however), but things are not moving very fast (see
http://r-engine.sourceforge.net/) (PCI vendor/device is 0x10cf/0x2011).

There is a forth model connected on the USB bus in TR1* Vaio laptops.
This camera is not supported at all by the current driver, in fact
little information if any is available for this camera
(USB vendor/device is 0x054c/0x0107).

===Driver options===

Several options can be passed to the meye driver using the standard
module argument syntax (<param>=<value> when passing the option to the
module or meye.<param>=<value> on the kernel boot line when meye is
statically linked into the kernel). Those options are:

forcev4l1: force use of V4L1 API instead of V4L2
gbuffers: number of capture buffers, default is 2 (32 max)
gbufsize: size of each capture buffer, default is 614400
video_nr: video device to register (0 = /dev/video0, etc)

===Module use===

In order to automatically load the meye module on use, you can put those lines
in your /etc/modprobe.conf file:

alias char-major-81 videodev
alias char-major-81-0 meye
options meye gbuffers=32

===Usage===

xawtv >= 3.49 (<http://bytesex.org/xawtv/>) for display and uncompressed video capture:

xawtv -c /dev/video0 -geometry 640x480

or

xawtv -c /dev/video0 -geometry 320x240

motioneye (<http://popies.net/meye/>) for getting ppm or jpg snapshots, mjpeg video

===Private API===

The driver supports frame grabbing with the video4linux API
(either v4l1 or v4l2), so all video4linux tools (like xawtv)
should work with this driver.

Besides the video4linux interface, the driver has a private interface
for accessing the Motion Eye extended parameters (camera sharpness,
agc, video framerate), the shapshot and the MJPEG capture facilities.

This interface consists of several ioctls (prototypes and structures
can be found in include/linux/meye.h):

MEYEIOC_G_PARAMS
MEYEIOC_S_PARAMS
Get and set the extended parameters of the motion eye camera.
The user should always query the current parameters with
MEYEIOC_G_PARAMS, change what he likes and then issue the
MEYEIOC_S_PARAMS call (checking for -EINVAL). The extended
parameters are described by the meye_params structure.

MEYEIOC_QBUF_CAPT
Queue a buffer for capture (the buffers must have been
obtained with a VIDIOCGMBUF call and mmap'ed by the
application). The argument to MEYEIOC_QBUF_CAPT is the
buffer number to queue (or -1 to end capture). The first
call to MEYEIOC_QBUF_CAPT starts the streaming capture.

MEYEIOC_SYNC
Takes as an argument the buffer number you want to sync.
This ioctl blocks until the buffer is filled and ready
for the application to use. It returns the buffer size.

MEYEIOC_STILLCAPT
MEYEIOC_STILLJCAPT
Takes a snapshot in an uncompressed or compressed jpeg format.
This ioctl blocks until the snapshot is done and returns (for
jpeg snapshot) the size of the image. The image data is
available from the first mmap'ed buffer.

Look at the 'motioneye' application code for an actual example.

===Bugs / Todo===

- the driver could be much cleaned up by removing the v4l1 support. However, this means all v4l1-only applications will stop working.

- 'motioneye' still uses the meye private v4l1 API extensions.

KNC1 DVB-S2 TV Station

2007-10-24T20:48:10Z

Js:

There are experimental drivers available for the device
(see http://jusst.de/hg/multiproto/).

TechnoTrend TT-budget S2-3200

2007-10-24T20:05:29Z

Js: simlify link

A [[DVB-S2]] [[DVB-S PCI Cards|PCI card]] from [[TechnoTrend]].

There are experimental drivers available for the device
(see http://jusst.de/hg/multiproto/).

==Overview==
This card is apparently also available/rebranded as the [[TechniSat SkyStar HD]].

===Components Used===
* [[STMicroelectronics]] STB6100 (tuner)
* [[STMicroelectronics]] [[STMicroelectronics STB0899|STB0899]] (demodulator)
* NXP/Philips SAA7146 (PCI bridge)

It also supports an add-on [[CI]] slot.

==External Links==
* [http://www.technotrend.de/2711/TT-budget__S2-3200.html TechnoTrend product page]

Archived:Main Page-V4L

2007-07-02T09:50:16Z

Js: Reverted edits by Erxiao (Talk); changed back to last version by Tmerle

__NOTOC__
__NOEDITSECTION__

<div style="background-color:#006600; padding:0.3em; color:#ffffff; font-weight:bold; font-size:150%; text-align:center">
Welcome to the video4linux wiki (For DVB wiki, click [http://www.linuxtv.org/wiki here])
</div>

{|valign=top background=none
|valign=top|
<div style="vertical-align:top; margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#ffffff">

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].

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.

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!

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!

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.

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.

Enjoy!

[[People behind V4L]]

'''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.
</div>
|}

<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;">
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=5%|
|valign=top bgcolor=#F7F9FB width=45%|
* '''Technical Background'''
** [[Video4linux APIs]]
** [http://www.ee.surrey.ac.uk/Contrib/WorldTV/ Analog TV]
** [[Digital TV]]
** [[PCI interface chipsets used for v4l cards]]
** [[GPIO pins]]
** [http://www.esacademy.com/faq/i2c/ i2c Protocol]
** [[Radio Data System (RDS)]]
* '''Developer Section'''
** [[How to write good problem report |How to write a good problem report]]
** [[How to add support for a new card]]
** [[How to build from mercurial|How to build from v4l mercurial]]
** [[How_to_submit_patches |How to submit patches]]
** [[Maintaining mercurial trees]]
** [[TODO - main tasks]]
** [[Anatomy of a v4l device]]
** [[Anatomy of a v4l driver]]
** '''Kernel Development'''
*** [[SubmittingPatches | Rules for submitting patches]]
*** [[Documentation/SubmittingDrivers | Rules for submitting drivers]]
*** [[Documentation/CodingStyle | Coding Style]]
*** [http://jungla.dit.upm.es/%7Ejmseyas/linux/kernel/hackers-docs.html Documentation index]
*** [http://linuxtv.org/hg/v4l-dvb Master v4l development repository]
*** [http://mcentral.de/hg/~mrec/v4l-dvb-experimental/ v4l-dvb experimental repository]
*** [http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/mchehab/v4l-dvb.git;a=log Current git log]
** '''Userspace Development'''
*** [[V4L2UserspaceLibrary | V4L2 Userspace library]]
* '''Applications'''
** [[TV Viewing]]
** [[TV Recording]]
** [[Streaming]]
** [[Text capture]] (Teletext/Closed Captioning)
* '''[[v4l Links]]'''
|valign=top bgcolor=#F7F9FB width=45%|
* '''Supported Hardware'''
** [[Tuners]]
** [[Audio Decoders]]
** [[Hardware vs software encoders]]
** [[v4l card vendors]]
** TV cards and drivers
*** Video via PCI
**** [[List survey of cards in use now]]
**** [[bttv devices (bt848, bt878)]]
***** [[btaudio (bt878)]]
**** [[Matrox Meteor II cards]] (not working)
**** [[Saa713x devices|saa713x devices (saa713x)]]
***** [[saa7134-alsa]]
**** [[saa7146 devices]]
**** [[cx88 devices (cx2388x) ]]
**** [[ivtv devices (cx23415, cx23416)]]
**** [[zoran devices (zr36057, zr36067)]]
**** [[zoran devices (zr36120, zr36125)]]
*** Video via PCI Express
**** [[saa7162 devices]] (not yet supported)
**** [[nGene devices]] (not supported)
*** Video via USB
**** [[USBVideo]] Request support for USB Video devices
**** [[Em2820]] (USB Analog only)
**** [[Em2880]] (USB Analog+DVB-T)
**** [[USBVision devices]]
**** [[DiBcom USB devices]]
**** [[OmniVision USB devices (OV511, etc)]]
** Graphics cards with TV tuner
*** [[ATI/AMD]]
*** [[NVIDIA]]
** Other devices
*** [[Radio]]s
*** [[Remote controllers]]
*** [[Webcams]]
*** [[Scanners]]
*** [[Loopback]]

|}
</div>

[http://linuxtv.org Category:LinuxTV]

MediaWiki:Usernameblacklist

2007-07-01T17:52:26Z

Js: New page: usernames used by vandal bot: * \b[A-Z][a-z0-9]{2}[A-Z][a-z0-9]{2}\b

usernames used by vandal bot:
* \b[A-Z][a-z0-9]{2}[A-Z][a-z0-9]{2}\b

DiBcom USB devices

2007-07-01T08:35:01Z

Js: Reverted edits by YmwGq0 (Talk); changed back to last version by Js

http://www.linuxtv.org/wiki/index.php?title=DVB_USB&oldid=1868

(Should be http://www.linuxtv.org/wiki/index.php/DVB_USB, but the wiki has been heavily spammed) [[User:MrJones|MrJones]] 20:48, 10 Sep 2005 (CEST)

Development: How to submit patches

2007-06-24T08:31:53Z

Js: Reverted edits by Ro0Nmx (Talk); changed back to last version by Js

=== Patch Preparation ===

Patches should be created against the v4l-dvb mercurial tree; see [[How to build from mercurial]].

For references on how to develop a driver, take a look at [http://jungla.dit.upm.es/%7Ejmseyas/linux/kernel/hackers-docs.html Index of Documentation for People Interested in Writing and/or Understanding the Linux Kernel].

Post your patches to the [https://www.redhat.com/mailman/listinfo/video4linux-list video4linux mailing list] for review and testing.

Follow the guidelines in [http://lxr.linux.no/source/Documentation/SubmittingPatches Documentation/SubmittingPatches] (cf. [http://linux.yyz.us/patch-format.html jgarzik's version]), including:
:* Verify best-practice [[Documentation/CodingStyle |kernel coding style]]
:* Use [PATCH] in the subject line to get attention
:* Explain what the patch does and what hardware it applies to
:* Document your work where appropriate, in the form of patches to Documentation/video4linux files
:* Add a '''Signed-off-by: Your name <name@yoursite.com>''' as a [[ SubmittingPatches#Developer.27s_Certificate_of_Origin_1.1|Developer's Certificate of Origin 1.1 ]]
:* Fix any problems and repeat until everyone is happy ;)
:* Send the patch inline, not as an attachment

Hint: [[ CheckList | There's a checklist for patch submission ]]

Subscription to the [https://www.redhat.com/mailman/listinfo/video4linux-list V4l mailing list] is recommended but not required.

The patch will be applied to the main mercurial tree. Once tested and integrated, patches are merged into a git tree by the v4l maintainer and periodically pulled by Linus.

AVerMedia Cardbus E500

2007-06-24T08:31:40Z

Js: Reverted edits by BpgTxl (Talk); changed back to last version by Js

I have an AverMedia Cardbus (E500) which works fine with Windows XP. In recent 2.6.11 kernels there is this line in drivers/media/video/saa7134/saa7134.h:

#define SAA7134_BOARD_AVERMEDIA_CARDBUS 46

but the corresponding entry in saa7134-cards.c didn't work for me, I couldn't tune in any channel.

To make is work, I did the following:

1. Got the (almost) latest kernel from www.kernel.org (2.6.12-rc1) with support for tda8290+75.

2. In saa7134-cards.c I replaced the the board config entry for this card with the following:

<pre>
[SAA7134_BOARD_AVERMEDIA_CARDBUS] = {
/* Kees.Blom@cwi.nl */
.name = "AVerMedia Cardbus TV (E500)",
.audio_clock = 0x187de7,
.tuner_type = TUNER_PHILIPS_TDA8290,
.inputs = {{
.name = name_tv,
.vmux = 1,
.amux = LINE2,
.tv = 1,
},{
.name = name_comp1,
.vmux = 3,
.amux = LINE2,
},{
.name = name_svideo,
.vmux = 8,
.amux = LINE2,
}},
.radio = {
.name = name_radio,
.amux = LINE1,
},
},
</pre>

3. Added this code in saa7134-cards.c, under the function saa7134_board_init1():
<pre>
case SAA7134_BOARD_AVERMEDIA_CARDBUS:
/* wake-up tuner chip */
saa_andorl(SAA7134_GPIO_GPMODE0 >> 2, 0x0FFFFFFFF, 0x0FFFFFFFF);
saa_andorl(SAA7134_GPIO_GPSTATUS0 >> 2, 0x0FFFFFFFF, 0x0FFFFFFFF);
break;
</pre>

4. With these compiled, installed and rebooted, I issued

modprobe saa7134 oss=1

This resulted in the following lines in /var/log/messages:

Mar 28 21:57:55 localhost kernel: Linux video capture interface: v1.00
Mar 28 21:57:55 localhost kernel: saa7130/34: v4l2 driver version 0.2.12 loaded
Mar 28 21:57:55 localhost kernel: ACPI: PCI interrupt 0000:07:00.0[A] -> GSI 11 (level, low) -> IRQ 11
Mar 28 21:57:55 localhost kernel: saa7134[0]: found at 0000:07:00.0, rev: 1, irq : 11, latency: 64, mmio: 0x21000000
Mar 28 21:57:55 localhost kernel: saa7134[0]: subsystem: 1461:d6ee, board: AVerMedia Cardbus TV/Radio [card=46,autodetected]
Mar 28 21:57:55 localhost kernel: saa7134[0]: board init: gpio is effffff
Mar 28 21:57:56 localhost kernel: tuner 0-004b: chip found @ 0x96 (saa7134[0])
Mar 28 21:57:56 localhost kernel: tuner 0-004b: tuner: type set to tda8290+75
Mar 28 21:57:56 localhost kernel: saa7134[0]: i2c eeprom 00: 61 14 ee d6 ff ff ff ff ff ff ff ff ff ff ff ff
Mar 28 21:57:56 localhost kernel: saa7134[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Mar 28 21:57:56 localhost kernel: saa7134[0]: i2c eeprom 20: ee df ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Mar 28 21:57:56 localhost kernel: saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Mar 28 21:57:56 localhost kernel: saa7134[0]: registered device video0 [v4l2]
Mar 28 21:57:56 localhost kernel: saa7134[0]: registered device vbi0
Mar 28 21:57:56 localhost kernel: saa7134[0]: registered device radio0
Mar 28 21:57:56 localhost kernel: saa7134[0]: registered device dsp2
Mar 28 21:57:56 localhost kernel: saa7134[0]: registered device mixer2

5. Video

At this point I could tune-in tv channels and see tv pictures with xawtv, tvtime and kdetv.

6. Audio

To get tv sound, I first typed in a terminal while tvtime was running (after killing artsd):

sox -tossdsp /dev/dsp2 -tossdsp /dev/dsp

However, this command is just a hack and sound terminates when changing channels in tvtime.

A better solution is to use Hartmut Hackman's code in CVS (as of 10 May 2005). I downloaded these files from linuxtv.org:

saa7134-oss.c,v 1.14 2005/05/18 22:45:16 hhackmann
saa7134-tvaudio.c,v 1.23 2005/05/18 22:46:17 hhackmann

and set

.amux = TV

After compiling and loading the module saa7134, the commands:

tvtime --mixer=/dev/mixer:vol&
sox -c 2 -s -w -r 32000 -t ossdsp /dev/dsp2 -t ossdsp -w -r 32000 /dev/dsp &

starts tvtime with sound and sound is now restored when changing channels.

The only flaw left is that, when changing channel, during ~1 sec. sound of the new channel is heard, followed by ~1 sec. of noise, whereafter sound is restored properly.

6. Problems left

* is the code to wake up the tuner chip correct? Isn't trying to set all bits high a little bit too much?
* so far, I haven't tested the S-Video and Composite inputs of this card.
'''Edit:'''Both S-Video and Composite inputs work fine, even before changes to saa7134-cards.c. I needed to pass the module option
modprobe saa7134 card=46 oss=1
because the card type was not auto detected.

This was done on a Dell Inspiron 4150 with Fedora Core 3 Installed.

-------
Kees Blom

It looks like that all the source changes are in the 2.6.15 kernel (and probably som lower versions).
//jostmart

AVerMedia Cardbus E500

2007-06-23T22:26:46Z

Js: Reverted edits by AnsMhb (Talk); changed back to last version by Js

Radio Listening Software

2007-06-23T19:24:33Z

Js: Reverted edits by ZvfXrb (Talk); changed back to last version by Js

== Radio applications ==

A number of v4l cards have a radio receiver/tuner.

The following applications control the tuner. 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.

* [http://whats.all.this.brouhaha.com/?p=199 radioshark] -- application to control the griffin radioshark
* [http://www.wh-hms.uni-ulm.de/~mfcn/gnomeradio gnomeradio] -- for Gnome, capable of recording
* [http://kradio.sourceforge.net/ kradio] for KDE
* [http://silicone.free.fr/xmms-FMRadio/ xmms-fmradio] -- plugin for [http://www.xmms.org/ XMMS], last version autumn 2004, Debian and Red Hat packages
* [http://gkrellm.luon.net/gkrellm-radio.phtml gkrellm-radio] -- minimalistic [http://gkrellm.net gkrellm] plugin to control radio tuners
* [http://foobazco.org/projects/gradio/ gradio] -- in Debian, but not currently active
* [http://linux.bytesex.org/xawtv/ radio] -- a curses-based radio application by Gerd Knorr, part of xawtv; see [http://dc.qut.edu.au/cgi-bin/man/man2html?1+radio man page] (most distros)
** [http://w3.misterhouse.net:81/mh/code/public/v4l_radio.pl radio script] part of the [http://w3.misterhouse.net:81/ MisterHouse] project
* [http://www.stanford.edu/~blp/fmtools/ fmtools] also for the command-line (most distros)
** [http://cajun.sourceforge.net/ cajun] for making your own car or home audio system
** [http://www.dashpc.com/ DashPC] for car radio and more from Linux Automotive
* [http://www.gnu.org/software/gnuradio/ gnuradio] -- the GNU software radio, testing phase; cf. [http://comsec.com/wiki?GnuRadio2.X wiki]
* [http://goodies.xfce.org/projects/panel-plugins/xfce4-radio-plugin/ xfce4-radio-plugin] -- plugin for the [http://www.xfce.org/ Xfce] panel

== User experiences ==

If you're a user, post your installation and user experiences here!

=== gradio ===

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

gradio -d /dev/radio2

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.

=== gnomeradio ===

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.

=== fmtools ===

The package contains two binaries, fm and fmscan. To pick up all stations even with very weak reception, I issued,

$ fmscan -d /dev/radio2 fmscan -d /dev/radio3 -t 18 -i 0.1
Scanning range: 87.9 - 107.9 MHz (0.2 MHz increments)...

Nice and clean. I added an antenna, but still got weak reception. This is very useful for testing the radio and finding the stations; does it support directing the sound to a file? I try various combinations and end up with this to get 100% volume:

$ fm -d /dev/radio3 89.9 65535
Radio tuned to 89.88 MHz at 100.00% volume

Weird. I don't see a way to record; do I need to use sox? I don't know if I'm getting any sound, as I don't have speakers on this box.

Sox is what gnomeradio uses to record and it thankfully sends commands it uses to standard out.

for wav file:

sox -c2 -w -r32000 -tossdsp /dev/audio -r 44100 -c 2 -w -twav /tmp/foo.wav

for mp3 or ogg:

sox -c2 -w -r32000 -tossdsp /dev/audio -r 44100 -c 2 -w -twav /tmp/fm_fifo &

and

lame -S -h -b 128 /tmp/fm_fifo /tmp/foo.mp3

or

oggenc -Q -b 128 -o /tmp/foo.ogg /tmp/fm_fifo

=== radio ===

The radio package has a single binary, radio. The man page says it looks for the kradio configuration file ~/.kde/share/config/kradiorc. Failing that, radio tries ~/.radio. I issue,

radio -c /dev/radio3

and get a blue and red curses screen, very cool. Arrow keys increase and decrease frequency in 0.05 intervals. I'm clearly not picking up any signal to speak of. I figure I have a lower-level issue with the tuner.

AVerMedia AVerTV GO 007 FM

2007-06-23T19:24:25Z

Js: Reverted edits by MlzGgz (Talk); changed back to last version by Bugboom

== Quick start ==

The *latest revision*(PCI ID 1461:f31f) of the Avermedia AVerTV GO 007 FM works "out of the box" in recent kernels. Earlier revisions WILL work, but you must currently use them once on Windows with the official drivers to load the internal EEPROM, and manually specify the card type as 57 and tuner as 54. Otherwise, to prepare the card to work, type in two lines:

modprobe saa7134-oss
sox -c 2 -sw -r 32000 -t ossdsp /dev/dsp1 -t ossdsp /dev/dsp

== Closer look ==
Using configuration tool DrakConf (''drakxtv'') in Mandriva Linux resulted in new line in /etc/modprobe.conf :

options saa7134 card=57 tuner=54 gbuffers=4

It seems that ''tuner'' value should be "61" instead, but it turned out this option did nothing wrong. Also commenting out this whole line has no visible effect, so I assume it may be skipped.

Command ''modprobe saa7134'' does the job with a trace in /var/log/messages as follows:

Feb 24 20:40:53 auriga kernel: saa7130/34: v4l2 driver version 0.2.14 loaded
Feb 24 20:40:53 auriga kernel: ACPI: PCI Interrupt 0000:00:05.0[A] -> GSI 16 (level, low) -> IRQ 17
Feb 24 20:40:53 auriga kernel: saa7133[0]: found at 0000:00:05.0, rev: 208, irq: 17, latency: 32, mmio: 0xdffff800
Feb 24 20:40:53 auriga kernel: saa7133[0]: subsystem: 1461:f31f, board: Avermedia AVerTV GO 007 FM [card=57,insmod option]
Feb 24 20:40:53 auriga kernel: saa7133[0]: board init: gpio is 803c5
Feb 24 20:40:53 auriga kernel: input: saa7134 IR (Avermedia AVerTV GO as /class/input/input7
Feb 24 20:40:53 auriga kernel: tuner 0-004b: chip found @ 0x96 (saa7133[0])
Feb 24 20:40:54 auriga kernel: tuner 0-004b: setting tuner address to 61
Feb 24 20:40:54 auriga kernel: tuner 0-004b: tuner: type set to tda8290+75
Feb 24 20:40:54 auriga kernel: saa7133[0]: i2c eeprom 00: 61 14 1f f3 ff ff ff ff ff ff ff ff ff ff ff ff
Feb 24 20:40:54 auriga kernel: saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Feb 24 20:40:54 auriga kernel: saa7133[0]: i2c eeprom 20: ff d2 fe ff ff ff ff ff ff ff ff ff ff ff ff ff
Feb 24 20:40:54 auriga kernel: saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Feb 24 20:40:54 auriga kernel: saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Feb 24 20:40:54 auriga kernel: saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Feb 24 20:40:54 auriga kernel: saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Feb 24 20:40:54 auriga kernel: saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Feb 24 20:40:55 auriga kernel: saa7133[0]: registered device video0 [v4l2]
Feb 24 20:40:55 auriga kernel: saa7133[0]: registered device vbi0
Feb 24 20:40:55 auriga kernel: saa7133[0]: registered device radio0

There's no sound yet, so the next command is ''modprobe saa7134-oss'', and the result is:

Feb 24 20:41:44 auriga kernel: saa7134 OSS driver for DMA sound loaded
Feb 24 20:41:44 auriga kernel: saa7133[0]: registered device dsp1
Feb 24 20:41:44 auriga kernel: saa7133[0]: registered device mixer1

There's also a ''saa7134-alsa'' module, but in my case it was useless, because the sound quality was much worse; ''modprobe saa7134-alsa'' gives the following output:

Feb 24 20:05:44 auriga kernel: saa7134 ALSA driver for DMA sound loaded
Feb 24 20:05:44 auriga kernel: saa7133[0]/alsa: saa7133[0] at 0xdffff800 irq 17 registered as card -1

It may work better some day, but for now I had to stick to ''saa7134-oss'' module. In a matter of fact ''modprobe saa7134'' may be totally skipped, because while probing for ''saa7134-oss'' or ''saa7134-alsa'' the main module will be automatically loaded in the background.

The hardware is now perfectly ready, but although you can watch TV, the sound is still not there. As found in [[AVerMedia Cardbus E500]] instructions I did the simple trick, which dumps the sound from TV card (/dev/dsp1) to the real sound card (/dev/dsp):

sox -c 2 -sw -r 32000 -t ossdsp /dev/dsp1 -t ossdsp /dev/dsp

See also [[saa7134-alsa]].

Now everything is in place and I can do basic things - watch and listen TV channels.

== Configuring for Revision PCI ID 1461:f31d ==

Place the following in /etc/modprobe.conf(or /etc/modprobe.d/options, or wherever your distribution keeps module parameters):
options saa7134 gbuffers=2 card=57 tuner=54

Note that you may wish to change gbuffers to a larger value, such as 8, or even 32. I'm not sure how this affects latency, though it may reduce dropped frames on heavily loaded systems...

Output from /var/log/messages(this may be useful if you wish to try to load the EEPROM manually if you don't have a Windows machine available!):
Mar 17 02:46:34 gaia kernel: [ 801.319037] saa7134 ALSA driver for DMA sound unloaded
Mar 17 02:46:49 gaia kernel: [ 816.608799] saa7130/34: v4l2 driver version 0.2.14 loaded
Mar 17 02:46:49 gaia kernel: [ 816.610412] ACPI: PCI Interrupt 0000:05:06.0[A] -> Link [APC1] -> GSI 16 (level, low) -> IRQ 74
Mar 17 02:46:49 gaia kernel: [ 816.610421] saa7133[0]: found at 0000:05:06.0, rev: 209, irq: 74, latency: 32, mmio: 0xd0000000
Mar 17 02:46:49 gaia kernel: [ 816.610431] saa7133[0]: subsystem: 1461:f31d, board: Avermedia AVerTV GO 007 FM [card=57,insmod option]
Mar 17 02:46:49 gaia kernel: [ 816.611004] saa7133[0]: board init: gpio is 8068d
Mar 17 02:46:49 gaia kernel: [ 816.659771] input: saa7134 IR (Avermedia AVerTV GO as /class/input/input4
Mar 17 02:46:50 gaia kernel: [ 816.892973] tuner 2-004b: chip found @ 0x96 (saa7133[0])
Mar 17 02:46:50 gaia kernel: [ 816.940965] tuner 2-004b: setting tuner address to 61
Mar 17 02:46:50 gaia kernel: [ 816.981032] tuner 2-004b: type set to tda8290+75a
Mar 17 02:46:50 gaia kernel: [ 817.084942] saa7133[0]: i2c eeprom 00: 61 14 1d f3 ff ff ff ff ff ff ff ff ff ff ff ff
Mar 17 02:46:50 gaia kernel: [ 817.084948] saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Mar 17 02:46:50 gaia kernel: [ 817.084954] saa7133[0]: i2c eeprom 20: ff d2 fe ff ff ff ff ff ff ff ff ff ff ff ff ff
Mar 17 02:46:50 gaia kernel: [ 817.084960] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Mar 17 02:46:50 gaia kernel: [ 817.084965] saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Mar 17 02:46:50 gaia kernel: [ 817.084971] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Mar 17 02:46:50 gaia kernel: [ 817.084976] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Mar 17 02:46:50 gaia kernel: [ 817.084982] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Mar 17 02:46:52 gaia kernel: [ 819.642929] saa7133[0]: registered device video0 [v4l2]
Mar 17 02:46:52 gaia kernel: [ 819.643478] saa7133[0]: registered device vbi0
Mar 17 02:46:52 gaia kernel: [ 819.643963] saa7133[0]: registered device radio0
Mar 17 02:46:53 gaia kernel: [ 819.702393] saa7134 ALSA driver for DMA sound loaded
Mar 17 02:46:53 gaia kernel: [ 819.702623] saa7133[0]/alsa: saa7133[0] at 0xd0000000 irq 74 registered as card -1

== MythTV and AC '97 Issues (SBLive) ==

With the equivalent [[Bona TV-PCI|Bona/Mentor TV-PCI]] card connected via the line input of a Creative Labs Sound Blaster Live! Platinum sound card, I had some issues getting MythTV to capture the audio. The tvtime application worked flawlessly without any of these procedures. I couldn't get the audio working for MythTV with the saa7134-alsa module and the sox workarounds.

On every boot-up, the card must be unmuted and the automute turned off. Some people had the same problems in [http://www.linuxquestions.org/questions/showthread.php?p=1850566#post1850566 similar reports] for the Avermedia card. Consider putting the following on a boot-up script.

v4lctl setattr automute off
v4lctl setattr mute off

For the Sound Blaster Live card, the AC '97 volume ''playback'' control (through a card mixer, such as alsamixer) is to be completely put to 0 (zero), or else you hear the audio being played back twice (loopback). The AC '97 volume ''capture'' control should be put as high as possible. This information can be found in the Linux kernel documentation in the Documentation/sound/alsa/SB-Live-mixer.txt file.

I also had issues with the audio captured with MythTV because I was hear crackling noises constantly. The reason was how loaded the system was, so I reduced the capture resolution and quality, as put audio at 32kHz.

[http://www.mythtvtalk.com/forum/viewtopic.php?t=4671 Discussion on MythTVtalk]

== Other Equivalent Cards ==

* [[Bona TV-PCI|Bona / Mentor TV-PCI]]