| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame^] | 1 | How to get the Nebula, PCTV and Twinhan DST cards working |
| 2 | ========================================================= |
| 3 | |
| 4 | This class of cards has a bt878a as the PCI interface, and |
| 5 | require the bttv driver. |
| 6 | |
| 7 | Please pay close attention to the warning about the bttv module |
| 8 | options below for the DST card. |
| 9 | |
| 10 | 1) General informations |
| 11 | ======================= |
| 12 | |
| 13 | These drivers require the bttv driver to provide the means to access |
| 14 | the i2c bus and the gpio pins of the bt8xx chipset. |
| 15 | |
| 16 | Because of this, you need to enable |
| 17 | "Device drivers" => "Multimedia devices" |
| 18 | => "Video For Linux" => "BT848 Video For Linux" |
| 19 | |
| 20 | 2) Loading Modules |
| 21 | ================== |
| 22 | |
| 23 | 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 |
| 25 | and one frontend driver. |
| 26 | |
| 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 | |
| 37 | 3a) Nebula / Pinnacle PCTV |
| 38 | -------------------------- |
| 39 | |
| 40 | $ modprobe bttv i2c_hw=1 card=0x68 |
| 41 | $ modprobe dvb-bt8xx |
| 42 | |
| 43 | For Nebula cards use the "nxt6000" frontend driver: |
| 44 | $ modprobe nxt6000 |
| 45 | |
| 46 | For Pinnacle PCTV cards use the "cx24110" frontend driver: |
| 47 | $ modprobe cx24110 |
| 48 | |
| 49 | 3b) TwinHan |
| 50 | ----------- |
| 51 | |
| 52 | $ modprobe bttv i2c_hw=1 card=0x71 |
| 53 | $ modprobe dvb-bt8xx |
| 54 | $ modprobe dst |
| 55 | |
| 56 | The value 0x71 will override the PCI type detection for dvb-bt8xx, which |
| 57 | is necessary for TwinHan cards.# |
| 58 | |
| 59 | If you're having an older card (blue color circuit) and card=0x71 locks your |
| 60 | machine, try using 0x68, too. If that does not work, ask on the DVB mailing list. |
| 61 | |
| 62 | The DST module takes a couple of useful parameters, in case the |
| 63 | dst drivers fails to detect your type of card correctly. |
| 64 | |
| 65 | dst_type takes values 0 (satellite), 1 (terrestial TV), 2 (cable). |
| 66 | |
| 67 | dst_type_flags takes bit combined values: |
| 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 | |
| 72 | 2 = TS 204. If your card tunes OK, but the picture is terrible, seemingly |
| 73 | breaking up in one half continually, and crc fails a lot, then |
| 74 | this is worth a try (or trying to turn off) |
| 75 | |
| 76 | 4 = has symdiv. Some cards, mostly without new tuner packets, require |
| 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. |
| 82 | |
| 83 | dst_check_ci: recognize DST-MOT |
| 84 | |
| 85 | or |
| 86 | |
| 87 | dst_check_ci: unable to recognize DSTXCI or STXCI |
| 88 | |
| 89 | -- |
| 90 | Authors: Richard Walker, Jamie Honan, Michael Hunold |