diff options
author | <jgarzik@pretzel.yyz.us> | 2005-05-26 13:03:24 -0400 |
---|---|---|
committer | Jeff Garzik <jgarzik@pobox.com> | 2005-05-26 13:03:24 -0400 |
commit | 8973a585aec125beb2a3de50bb491004299f53d5 (patch) | |
tree | 3f069a9c7eff2c916e02427fd9800ce2b55a4a90 /Documentation/dvb/bt8xx.txt | |
parent | 907f4678c114a125fe4584758681c31bf3d627da (diff) | |
parent | bef9c558841604116704e10b3d9ff3dbf4939423 (diff) |
Automatic merge of rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git branch HEAD
Diffstat (limited to 'Documentation/dvb/bt8xx.txt')
-rw-r--r-- | Documentation/dvb/bt8xx.txt | 69 |
1 files changed, 24 insertions, 45 deletions
diff --git a/Documentation/dvb/bt8xx.txt b/Documentation/dvb/bt8xx.txt index e3cacf4f2345..d64430bf4bb6 100644 --- a/Documentation/dvb/bt8xx.txt +++ b/Documentation/dvb/bt8xx.txt | |||
@@ -17,74 +17,53 @@ Because of this, you need to enable | |||
17 | "Device drivers" => "Multimedia devices" | 17 | "Device drivers" => "Multimedia devices" |
18 | => "Video For Linux" => "BT848 Video For Linux" | 18 | => "Video For Linux" => "BT848 Video For Linux" |
19 | 19 | ||
20 | Furthermore you need to enable | ||
21 | "Device drivers" => "Multimedia devices" => "Digital Video Broadcasting Devices" | ||
22 | => "DVB for Linux" "DVB Core Support" "Nebula/Pinnacle PCTV/TwinHan PCI Cards" | ||
23 | |||
20 | 2) Loading Modules | 24 | 2) Loading Modules |
21 | ================== | 25 | ================== |
22 | 26 | ||
23 | In general you need to load the bttv driver, which will handle the gpio and | 27 | In general you need to load the bttv driver, which will handle the gpio and |
24 | i2c communication for us. Next you need the common dvb-bt8xx device driver | 28 | i2c communication for us, plus the common dvb-bt8xx device driver. |
25 | and one frontend driver. | 29 | The frontends for Nebula (nxt6000), Pinnacle PCTV (cx24110) and |
26 | 30 | TwinHan (dst) are loaded automatically by the dvb-bt8xx device driver. | |
27 | The bttv driver will HANG YOUR SYSTEM IF YOU DO NOT SPECIFY THE CORRECT | ||
28 | CARD ID! | ||
29 | |||
30 | (If you don't get your card running and you suspect that the card id you're | ||
31 | using is wrong, have a look at "bttv-cards.c" for a list of possible card | ||
32 | ids.) | ||
33 | |||
34 | Pay attention to failures when you load the frontend drivers | ||
35 | (e.g. dmesg, /var/log/messages). | ||
36 | 31 | ||
37 | 3a) Nebula / Pinnacle PCTV | 32 | 3a) Nebula / Pinnacle PCTV |
38 | -------------------------- | 33 | -------------------------- |
39 | 34 | ||
40 | $ modprobe bttv i2c_hw=1 card=0x68 | 35 | $ modprobe bttv (normally bttv is being loaded automatically by kmod) |
41 | $ modprobe dvb-bt8xx | 36 | $ modprobe dvb-bt8xx (or just place dvb-bt8xx in /etc/modules for automatic loading) |
42 | |||
43 | For Nebula cards use the "nxt6000" frontend driver: | ||
44 | $ modprobe nxt6000 | ||
45 | 37 | ||
46 | For Pinnacle PCTV cards use the "cx24110" frontend driver: | ||
47 | $ modprobe cx24110 | ||
48 | 38 | ||
49 | 3b) TwinHan | 39 | 3b) TwinHan and Clones |
50 | ----------- | 40 | -------------------------- |
51 | 41 | ||
52 | $ modprobe bttv i2c_hw=1 card=0x71 | 42 | $ modprobe bttv i2c_hw=1 card=0x71 |
53 | $ modprobe dvb-bt8xx | 43 | $ modprobe dvb-bt8xx |
54 | $ modprobe dst | 44 | $ modprobe dst |
55 | 45 | ||
56 | The value 0x71 will override the PCI type detection for dvb-bt8xx, which | 46 | The value 0x71 will override the PCI type detection for dvb-bt8xx, |
57 | is necessary for TwinHan cards.# | 47 | which is necessary for TwinHan cards. |
58 | 48 | ||
59 | If you're having an older card (blue color circuit) and card=0x71 locks your | 49 | If you're having an older card (blue color circuit) and card=0x71 locks |
60 | machine, try using 0x68, too. If that does not work, ask on the DVB mailing list. | 50 | your machine, try using 0x68, too. If that does not work, ask on the |
51 | mailing list. | ||
61 | 52 | ||
62 | The DST module takes a couple of useful parameters, in case the | 53 | The DST module takes a couple of useful parameters. |
63 | dst drivers fails to detect your type of card correctly. | ||
64 | 54 | ||
65 | dst_type takes values 0 (satellite), 1 (terrestial TV), 2 (cable). | 55 | verbose takes values 0 to 5. These values control the verbosity level. |
66 | 56 | ||
67 | dst_type_flags takes bit combined values: | 57 | debug takes values 0 and 1. You can either disable or enable debugging. |
68 | 1 = new tuner type packets. You can use this if your card is detected | ||
69 | and you have debug and you continually see the tuner packets not | ||
70 | working (make sure not a basic problem like dish alignment etc.) | ||
71 | 58 | ||
72 | 2 = TS 204. If your card tunes OK, but the picture is terrible, seemingly | 59 | dst_addons takes values 0 and 0x20. A value of 0 means it is a FTA card. |
73 | breaking up in one half continually, and crc fails a lot, then | 60 | 0x20 means it has a Conditional Access slot. |
74 | this is worth a try (or trying to turn off) | ||
75 | 61 | ||
76 | 4 = has symdiv. Some cards, mostly without new tuner packets, require | 62 | The autodected values are determined bythe cards 'response |
77 | a symbol division algorithm. Doesn't apply to terrestial TV. | ||
78 | |||
79 | You can also specify a value to have the autodetected values turned off | ||
80 | (e.g. 0). The autodected values are determined bythe cards 'response | ||
81 | string' which you can see in your logs e.g. | 63 | string' which you can see in your logs e.g. |
82 | 64 | ||
83 | dst_check_ci: recognize DST-MOT | 65 | dst_get_device_id: Recognise [DSTMCI] |
84 | |||
85 | or | ||
86 | 66 | ||
87 | dst_check_ci: unable to recognize DSTXCI or STXCI | ||
88 | 67 | ||
89 | -- | 68 | -- |
90 | Authors: Richard Walker, Jamie Honan, Michael Hunold | 69 | Authors: Richard Walker, Jamie Honan, Michael Hunold, Manu Abraham |