aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/dvb/bt8xx.txt
diff options
context:
space:
mode:
authorMichael Krufky <mkrufky@m1k.net>2005-11-09 00:35:35 -0500
committerLinus Torvalds <torvalds@g5.osdl.org>2005-11-09 10:56:03 -0500
commit2cbeddc976645262dbe036d6ec0825f96af70da3 (patch)
treec9916c7e66a1abcaafc788af4e6c0aee8cc1b5e2 /Documentation/dvb/bt8xx.txt
parent28fdd7599cb9c6c620caf13bcaea41e2532cb5fd (diff)
[PATCH] dvb: Updated documentation for FusionHDTV Lite cards
- Updated documentation for FusionHDTV Lite cards. We must differentiate the bt8xx based "Lite" cards from the cx2388x based "Gold" cards. - Provide location of CARDLIST.bttv Documentation, rather than instructing users to look at bttv.h - Include card decimal id numbers. These are valid for module arguments, and might be easier for some people to remember, rather than hex. Signed-off-by: Michael Krufky <mkrufky@m1k.net> Cc: Johannes Stezenbach <js@linuxtv.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'Documentation/dvb/bt8xx.txt')
-rw-r--r--Documentation/dvb/bt8xx.txt41
1 files changed, 23 insertions, 18 deletions
diff --git a/Documentation/dvb/bt8xx.txt b/Documentation/dvb/bt8xx.txt
index ac3af17f2b6f..df6c05453cb5 100644
--- a/Documentation/dvb/bt8xx.txt
+++ b/Documentation/dvb/bt8xx.txt
@@ -1,5 +1,5 @@
1How to get the Nebula, PCTV and Twinhan DST cards working 1How to get the Nebula, PCTV, FusionHDTV Lite and Twinhan DST cards working
2========================================================= 2==========================================================================
3 3
4This class of cards has a bt878a as the PCI interface, and 4This class of cards has a bt878a as the PCI interface, and
5require the bttv driver. 5require the bttv driver.
@@ -26,11 +26,12 @@ Furthermore you need to enable
26 26
27In general you need to load the bttv driver, which will handle the gpio and 27In general you need to load the bttv driver, which will handle the gpio and
28i2c communication for us, plus the common dvb-bt8xx device driver. 28i2c communication for us, plus the common dvb-bt8xx device driver.
29The frontends for Nebula (nxt6000), Pinnacle PCTV (cx24110) and 29The frontends for Nebula (nxt6000), Pinnacle PCTV (cx24110), TwinHan (dst),
30TwinHan (dst) are loaded automatically by the dvb-bt8xx device driver. 30FusionHDTV DVB-T Lite (mt352) and FusionHDTV5 Lite (lgdt330x) are loaded
31automatically by the dvb-bt8xx device driver.
31 32
323a) Nebula / Pinnacle PCTV 333a) Nebula / Pinnacle PCTV / FusionHDTV Lite
33-------------------------- 34---------------------------------------------
34 35
35 $ modprobe bttv (normally bttv is being loaded automatically by kmod) 36 $ modprobe bttv (normally bttv is being loaded automatically by kmod)
36 $ modprobe dvb-bt8xx 37 $ modprobe dvb-bt8xx
@@ -67,8 +68,8 @@ verbose=0 means complete disabling of messages
67dst_addons takes values 0 and 0x20. A value of 0 means it is a FTA card. 68dst_addons takes values 0 and 0x20. A value of 0 means it is a FTA card.
680x20 means it has a Conditional Access slot. 690x20 means it has a Conditional Access slot.
69 70
70The autodected values are determined bythe cards 'response 71The autodetected values are determined by the cards 'response string'
71string' which you can see in your logs e.g. 72which you can see in your logs e.g.
72 73
73dst_get_device_id: Recognise [DSTMCI] 74dst_get_device_id: Recognise [DSTMCI]
74 75
@@ -84,25 +85,29 @@ If you happen to be running multiple cards, it would be advisable to load
84the bttv module with the card id. This would help to solve any module loading 85the bttv module with the card id. This would help to solve any module loading
85problems that you might face. 86problems that you might face.
86 87
87for example, if you happen to have a Twinhan and clones alongwith a FusionHDTV5 88For example, if you have a Twinhan and Clones card along with a FusionHDTV5 Lite
88card
89 89
90 $ modprobe bttv card=0x71 card=0x87 90 $ modprobe bttv card=0x71 card=0x87
91 91
92Here the order of the card id is important and should be the same as that of the 92Here the order of the card id is important and should be the same as that of the
93physical order of the cards. Here card=0x71 represents the Twinhan and clones 93physical order of the cards. Here card=0x71 represents the Twinhan and clones
94and card=0x87 represents Fusion HDTV5. 94and card=0x87 represents Fusion HDTV5 Lite. These arguments can also be
95specified in decimal, rather than hex:
96
97 $ modprobe bttv card=113 card=135
95 98
96Some examples of card-id's 99Some examples of card-id's
97 100
98Pinnacle Sat 0x5e 101Pinnacle Sat 0x5e (94)
99Nebula Digi TV 0x68 102Nebula Digi TV 0x68 (104)
100PC HDTV 0x70 103PC HDTV 0x70 (112)
101Twinhan 0x71 104Twinhan 0x71 (113)
102Fusion HDTV5 0x87 105FusionHDTV DVB-T Lite 0x80 (128)
106FusionHDTV5 Lite 0x87 (135)
107
108For a full list of card-id's, see the V4L Documentation within the kernel
109source: linux/Documentation/video4linux/CARDLIST.bttv
103 110
104For a full list of card-id's, you can see the exported card-id's from
105bttv-cards.c in linux-2.6.x/drivers/media/video/bttv.h
106If you have problems with this please do ask on the mailing list. 111If you have problems with this please do ask on the mailing list.
107 112
108-- 113--