--- dvb-kernel/README.bt8xx	2003/10/13 04:01:31	1.2
+++ dvb-kernel/README.bt8xx	2003/10/28 22:53:10	1.3
@@ -9,13 +9,13 @@ require the bttv driver.
 Please pay close attention to the warning about the bttv module
 options below for the DST card.
 
-For 2.4, make sure you are using an uptodate kernel 2.4.21 and above.
+For 2.4, make sure you are using an uptodate kernel 2.4.23 and above.
 For 2.6, shuffle down to the 2.6 section below. 2.6 is recommended
 because of it's multimedia latency support, and ease of build.
 
 2.4
 ===
-For 2.4, make sure you are using an uptodate kernel 2.4.21 and above.
+For 2.4, make sure you are using an uptodate kernel 2.4.23 and above.
 This is the *only* way to go when you are experimenting with 
 bleeding-edge stuff like DVB and Dxr3.  Do the usual to build your kernel.  
 (remember to enable the V4L functionality)  I'd recommend you install and 
@@ -25,7 +25,7 @@ Download http://bytesex.org/patches/2.4.
 apply this to your kernel source tree.  For example:
 
   $ cd /usr/src
-  $ patch -p0 < ~/11-v4l2-api-2.4.21-rc4.diff
+  $ patch -p0 < ~/11-v4l2-api-2.4.xxxx-rc4.diff
 
 This will patch your kernel to include support for VideoForLinux 2.
 
@@ -36,6 +36,7 @@ You need to use 'dvb-kernel', along with
 
 Download http://bytesex.org/bttv/bttv-0.9.12.tar.gz or above and unpack it.
 This is the first version that will not hang your card.
+You may find this in the http://bytesex.org/snapshots directory.
 
 Using this version of
 
@@ -90,6 +91,39 @@ FOR THE DST!
 Pay attention to failures to load these frontends. 
 (E.g. dmesg, /var/log/messages).
 
+For DST cards, you can also use card type 0x71 for bttv module params, 
+providing the bttv version supports this. (The ones from bytesex/snapshots do).
+
+If you use this value, 0x71, it will override the PCI type detection
+for dvb-bt8xx.
+
+The DST module takes a couple of useful parameters, in case the
+dst drivers fails to detect your type of card correctly.
+
+dst_type takes values 0 (satellite), 1 (terrestial TV), 2 (cable).
+
+dst_type_flags takes bit combined values:
+1 = new tuner type packets. You can use this if your card is detected
+    and you have debug and you continually see the tuner packets not
+    working (make sure not a basic problem like dish alignment etc.)
+
+2 = TS 204. If your card tunes OK, but the picture is terrible, seemingly
+    breaking up in one half continually, and crc fails a lot, then
+    this is worth a try (or trying to turn off)
+
+4 = has symdiv. Some cards, mostly without new tuner packets, require
+    a symbol division algorithm. Doesn't apply to terrestial TV.
+
+You can also specify a value to have the autodetected values turned off
+(e.g. 0). The autodected values are determined bythe cards 'response
+string' which you can see in your logs e.g.
+
+dst_check_ci: recognize DST-MOT
+
+or 
+
+dst_check_ci: unable to recognize DSTXCI or STXCI
+
 Cheers,
 Richard Walker,