How to get the Nebula, PCTV 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) Loading Modules
==================

In general you need to load the bttv driver, which will handle the gpio
and i2c communication for us. Next you need the common dvb-bt8xx device
driver and one frontend driver.

The bttv driver will HANG YOUR SYSTEM IF YOU DO NOT SPECIFY THE
COORECT  CARD ID! A list of possible card ids can be found inside
"bttv-cards.c" inside the bttv driver package.

Pay attention to failures to load these frontends. 
(E.g. dmesg, /var/log/messages).

2a) Nebula / Pinnacle PCTV
--------------------------

   $ modprobe bttv i2c_hw=1 card=0x68
   $ modprobe dvb-bt8xx
   
For Nebula cards use the "nxt6000" frontend driver:
   $ modprobe nxt6000

For Pinnacle PCTV cards use the "cx24110" frontend driver:
   $ modprobe cx24110

2b) TwinHan and Clones
--------------------------

   $ modprobe bttv i2c_hw=1 card=0x71
   $ modprobe dvb-bt8xx
   $ modprobe dst

The value 0x71 will override the PCI type detection for dvb-bt8xx,
which  is necessary for TwinHan cards.

If you're having an older card (blue color circuit) and card=0x71 locks
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 5. These values control the verbosity level.

debug takes values 0 and 1. You can either disable or enable debugging.

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 autodected values are determined bythe cards 'response
string' which you can see in your logs e.g.

dst_get_device_id: Recognise [DSTMCI]
