Commit 8abe58ae authored by Uwe Bugla's avatar Uwe Bugla Committed by Linus Torvalds

V4L/DVB (3538): Bt8xx documentation update

Signed-off-by: default avatarUwe Bugla <uwe.bugla@gmx.de>
Signed-off-by: default avatarManu Abraham <manu@linuxtv.org>
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@infradead.org>
parent a8733ca5
How to get the Nebula, PCTV, FusionHDTV Lite and Twinhan DST cards working How to get the bt8xx cards working
========================================================================== ==================================
This class of cards has a bt878a as the PCI interface, and 1) General information
require the bttv driver. ======================
Please pay close attention to the warning about the bttv module This class of cards has a bt878a as the PCI interface, and require the bttv driver
options below for the DST card. for accessing the i2c bus and the gpio pins of the bt8xx chipset.
Please see Documentation/dvb/cards.txt => o Cards based on the Conexant Bt8xx PCI bridge:
1) General informations Compiling kernel please enable:
======================= a.)"Device drivers" => "Multimedia devices" => "Video For Linux" => "BT848 Video For Linux"
b.)"Device drivers" => "Multimedia devices" => "Digital Video Broadcasting Devices"
These drivers require the bttv driver to provide the means to access => "DVB for Linux" "DVB Core Support" "Bt8xx based PCI Cards"
the i2c bus and the gpio pins of the bt8xx chipset.
Because of this, you need to enable
"Device drivers" => "Multimedia devices"
=> "Video For Linux" => "BT848 Video For Linux"
Furthermore you need to enable
"Device drivers" => "Multimedia devices" => "Digital Video Broadcasting Devices"
=> "DVB for Linux" "DVB Core Support" "BT8xx based PCI cards"
2) Loading Modules 2) Loading Modules
================== ==================
In general you need to load the bttv driver, which will handle the gpio and In default cases bttv is loaded automatically.
i2c communication for us, plus the common dvb-bt8xx device driver. To load the backend either place dvb-bt8xx in etc/modules, or apply manually:
The frontends for Nebula (nxt6000), Pinnacle PCTV (cx24110), TwinHan (dst),
FusionHDTV DVB-T Lite (mt352) and FusionHDTV5 Lite (lgdt330x) are loaded
automatically by the dvb-bt8xx device driver.
3a) Nebula / Pinnacle PCTV / FusionHDTV Lite
---------------------------------------------
$ modprobe bttv (normally bttv is being loaded automatically by kmod)
$ modprobe dvb-bt8xx
(or just place dvb-bt8xx in /etc/modules for automatic loading)
3b) TwinHan and Clones
--------------------------
$ modprobe bttv card=0x71 $ modprobe dvb-bt8xx
$ modprobe dvb-bt8xx
$ modprobe dst
The value 0x71 will override the PCI type detection for dvb-bt8xx, All frontends will be loaded automatically.
which is necessary for TwinHan cards. Omission of this parameter might result People running udev please see Documentation/dvb/udev.txt.
in a system lockup.
If you're having an older card (blue color PCB) and card=0x71 locks up In the following cases overriding the PCI type detection for dvb-bt8xx might be necessary:
your machine, try using 0x68, too. If that does not work, ask on the
mailing list.
The DST module takes a couple of useful parameters. 2a) Running TwinHan and Clones
------------------------------
verbose takes values 0 to 4. These values control the verbosity level, $ modprobe bttv card=113
and can be used to debug also. $ modprobe dvb-bt8xx
$ modprobe dst
verbose=0 means complete disabling of messages Useful parameters for verbosity level and debugging the dst module:
1 only error messages are displayed
2 notifications are also displayed
3 informational messages are also displayed
4 debug setting
dst_addons takes values 0 and 0x20. A value of 0 means it is a FTA card. verbose=0: messages are disabled
0x20 means it has a Conditional Access slot. 1: only error messages are displayed
2: notifications are displayed
3: other useful messages are displayed
4: debug setting
dst_addons=0: card is a free to air (FTA) card only
0x20: card has a conditional access slot for scrambled channels
The autodetected values are determined by the cards 'response string' The autodetected values are determined by the cards' "response string".
which you can see in your logs e.g. In your logs see f. ex.: dst_get_device_id: Recognize [DSTMCI].
For bug reports please send in a complete log with verbose=4 activated.
Please also see Documentation/dvb/ci.txt.
dst_get_device_id: Recognise [DSTMCI] 2b) Running multiple cards
If you need to sent in bug reports on the dst, please do send in a complete
log with the verbose=4 module parameter. For general usage, the default setting
of verbose=1 is ideal.
4) Multiple cards
-------------------------- --------------------------
If you happen to be running multiple cards, it would be advisable to load Examples of card ID's:
the bttv module with the card id. This would help to solve any module loading
problems that you might face.
For example, if you have a Twinhan and Clones card along with a FusionHDTV5 Lite
$ modprobe bttv card=0x71 card=0x87 Pinnacle PCTV Sat: 94
Nebula Electronics Digi TV: 104
Here the order of the card id is important and should be the same as that of the pcHDTV HD-2000 TV: 112
physical order of the cards. Here card=0x71 represents the Twinhan and clones Twinhan DST and clones: 113
and card=0x87 represents Fusion HDTV5 Lite. These arguments can also be Avermedia AverTV DVB-T 771: 123
specified in decimal, rather than hex: Avermedia AverTV DVB-T 761: 124
DViCO FusionHDTV DVB-T Lite: 128
DViCO FusionHDTV 5 Lite: 135
Notice: The order of the card ID should be uprising:
Example:
$ modprobe bttv card=113 card=135 $ modprobe bttv card=113 card=135
$ modprobe dvb-bt8xx
Some examples of card-id's For a full list of card ID's please see Documentation/video4linux/CARDLIST.bttv.
In case of further problems send questions to the mailing list: www.linuxdvb.org.
Pinnacle Sat 0x5e (94)
Nebula Digi TV 0x68 (104)
PC HDTV 0x70 (112)
Twinhan 0x71 (113)
FusionHDTV DVB-T Lite 0x80 (128)
FusionHDTV5 Lite 0x87 (135)
For a full list of card-id's, see the V4L Documentation within the kernel
source: linux/Documentation/video4linux/CARDLIST.bttv
If you have problems with this please do ask on the mailing list.
--
Authors: Richard Walker, Authors: Richard Walker,
Jamie Honan, Jamie Honan,
Michael Hunold, Michael Hunold,
Manu Abraham, Manu Abraham,
Uwe Bugla,
Michael Krufky Michael Krufky
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment