Hauppauge WinTV-HVR-4000: Difference between revisions

From LinuxTVWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
For DVB-S/S2 there is an experimental drivers repository from Steven Toth (see http://www.linuxtv.org/hg/~stoth/hvr4000). Analog video and remote control works also with this driver (*).
For DVB-S there is an experimental drivers repository from Steven Toth (see http://www.linuxtv.org/hg/~stoth/hvr4000-dvbs). Analog video and remote control works also with this driver (*).


Currently, no support for simultaneous operation of both DVB-T and DVB-S is implemented. Default operation mode preferes DVB-S.
Currently, no support for simultaneous operation of both DVB-T and DVB-S is implemented. Default operation mode prefers DVB-S.


Guess Note : Using HVR3000 as example the DVB-T and DVB-S use the same demux on the card, so only one will ever be available. The above I expect to be the same for the HVR4000, ie not a linuxtv issue. It is suggested to create symbolic links to access the frontends for some apps (see HVR3000 in this wiki), but you need to ensure your appilication does not attempt to access both DVB-T and DVB-S at the same time.
Guess Note : Using HVR3000 as example the DVB-T and DVB-S use the same demux on the card, so only one will ever be available. The above I expect to be the same for the HVR4000, ie not a linuxtv issue. It is suggested to create symbolic links to access the frontends for some apps (see HVR3000 in this wiki), but you need to ensure your application does not attempt to access both DVB-T and DVB-S at the same time.


(*) Work in progress patches to enable features of this card have been merged into the hvr4000 repository, yet a patch is available without DVB-S2 support for v4l-dvb hg is available here: http://dev.kewl.org/hvr4000/
(*) Work in progress patches to enable features of this card have been merged into the hvr4000-dvbs repository, yet an updated patchset is available for v4l-dvb hg here: http://dev.kewl.org/hvr4000/

This patchset also adds two hacks which will allow DVB-S2 reception (command line) for experimental purposes, also it allows the selection of which DVB frontend to load, DVB-T or DVB-S/S2.


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

Revision as of 10:56, 7 December 2007

For DVB-S there is an experimental drivers repository from Steven Toth (see http://www.linuxtv.org/hg/~stoth/hvr4000-dvbs). Analog video and remote control works also with this driver (*).

Currently, no support for simultaneous operation of both DVB-T and DVB-S is implemented. Default operation mode prefers DVB-S.

Guess Note : Using HVR3000 as example the DVB-T and DVB-S use the same demux on the card, so only one will ever be available. The above I expect to be the same for the HVR4000, ie not a linuxtv issue. It is suggested to create symbolic links to access the frontends for some apps (see HVR3000 in this wiki), but you need to ensure your application does not attempt to access both DVB-T and DVB-S at the same time.

(*) Work in progress patches to enable features of this card have been merged into the hvr4000-dvbs repository, yet an updated patchset is available for v4l-dvb hg here: http://dev.kewl.org/hvr4000/

This patchset also adds two hacks which will allow DVB-S2 reception (command line) for experimental purposes, also it allows the selection of which DVB frontend to load, DVB-T or DVB-S/S2.

DVB-T

For DVB-T a special option for the module cx88xx is needed: card=56

The card is automatically detected as card 57. Therefore, using OpenSuSE (and probably also other distros) add the line

options cx88xx card=56

in /etc/modprobe.conf.local (or /etc/conf.modules or similar).


For Ubuntu make a file /etc/modprobe.d/cx88xx.modprobe with the following contents:

options cx88xx card=53

(Yes, on my system I need to use "card=53" - not "card=56" - to get DVB-T to work)