[linux-dvb] Patch for /Documentation/dvb/bt8xx.txt, Revision 1

Uwe Bugla uwe.bugla at gmx.de
Mon Mar 27 15:59:29 CEST 2006

- rewrote document from scratch
- reduced the card ID reference to one proven exception (TwinHan)
- added cross references (=>)
- added a date to show actual status of development
- short, precise, compact info now
- no more endless author list

Applies against: Kernel 2.6.16
Signed-off-by: Uwe Bugla <uwe.bugla at gmx.de>

--- /Documentation/dvb/bt8xx.txt Wed Mar 23 19:37:00 2006
+++ /Documentation/dvb/bt8xx.txt Mon Mar 27 12:51:00 2006
@@ -1,118 +1,47 @@
-How to get the Nebula, PCTV, FusionHDTV Lite and Twinhan DST cards working
-This class of cards has a bt878a as the PCI interface, and
-require the bttv driver.
-Please pay close attention to the warning about the bttv module
-options below for the DST card.
-1) General informations
-These drivers require the bttv driver to provide the means to access
-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
-  => "DVB for Linux" "DVB Core Support" "BT8xx based PCI cards"
+How to get the bt8xx cards working
+1) General information
+The bttv driver accesses the i2c bus and the gpio pins of the bt8xx chipset
+- Card types? => Documentation/dvb/cards.txt => o Cards based on the
Conexant Bt8xx PCI bridge:
+- Creating device nodes? => Documentation/dvb/udev.txt
+Compiling kernel:
+a.)"Device drivers" => "Multimedia devices" => "Video For Linux" => "BT848
Video For Linux"
+b.)"Device drivers" => "Multimedia devices" => "Digital Video Broadcasting
+	=> "DVB for Linux" "DVB Core Support" "Bt8xx based PCI Cards"
 2) Loading Modules
-In general you need to load the bttv driver, which will handle the gpio and
-i2c communication for us, plus the common dvb-bt8xx device driver.
-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
+Default cases: bttv and all frontends are loaded automatically
+Load backend: a) put dvb-bt8xx in etc/modules or b) apply manually:
+	$ modprobe dvb-bt8xx
+Exception TwinHan and Clones: overriding autodetection might be necessary
+a) standalone:
-   $ modprobe bttv card=0x71
-   $ modprobe dvb-bt8xx
-   $ modprobe dst
+	$ modprobe bttv card=113
+	$ modprobe dvb-bt8xx
+	$ modprobe dst
-The value 0x71 will override the PCI type detection for dvb-bt8xx,
-which  is necessary for TwinHan cards. Omission of this parameter might
-in a system lockup.
-If you're having an older card (blue color PCB) and card=0x71 locks up
-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.
-verbose takes values 0 to 4. These values control the verbosity level,
-and can be used to debug also.
-verbose=0 means complete disabling of messages
-	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.
-0x20 means it has a Conditional Access slot.
-The autodetected values are determined by the cards 'response string'
-which you can see in your logs e.g.
-dst_get_device_id: Recognise [DSTMCI]
-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
-of verbose=1 is ideal.
-4) Multiple cards
-If you happen to be running multiple cards, it would be advisable to load
-the bttv module with the card id. This would help to solve any module
-problems that you might face.
-For example, if you have a Twinhan and Clones card along with a FusionHDTV5
-	$ modprobe bttv card=0x71 card=0x87
-Here the order of the card id is important and should be the same as that
of the
-physical order of the cards. Here card=0x71 represents the Twinhan and
-and card=0x87 represents Fusion HDTV5 Lite. These arguments can also be
-specified in decimal, rather than hex:
-	$ modprobe bttv card=113 card=135
-Some examples of card-id's
-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,
-	 Jamie Honan,
-	 Michael Hunold,
-	 Manu Abraham,
-	 Michael Krufky
+Parameters for dst:
+verbose=1:		only error messages
+	2:		notifications
+	3:		other useful messages
+	4:		debug setting
+dst_addons=0x20:	card owns conditional access slot for scrambled channels
+- Unscramble channels? => Documentation/dvb/ci.txt
+b) >= 2 cards in a box: Card ID order should be uprising: Example:
+	$ modprobe bttv card=113 card=135
+- Card ID list? => Documentation/video4linux/CARDLIST.bttv
+- Questions? Suscribe to mailing list: www.linuxdvb.org
+Uwe Bugla, March 27th, 2006

Bis zu 70% Ihrer Onlinekosten sparen: GMX SmartSurfer!
Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer

More information about the linux-dvb mailing list