- ported all dibusb drivers to fit into the dvb-usb-frameword

- created dvb-pll-entries for the tuner used with the dibusb-drivers
- removed all traces of the dibusb driver
- adapted the dib3000-frontends to get along with the dvb-pll-changes

1 files changed, 32 insertions, 37 deletions

diff --git a/linux/Documentation/dvb/README.dvb-usb b/linux/Documentation/dvb/README.dvb-usb
index 9cf8ff4a2..5173cacd1 100644
--- a/linux/Documentation/dvb/README.dvb-usb
+++ b/linux/Documentation/dvb/README.dvb-usb
@@ -1,27 +1,26 @@
-Documentation for dvb-usb-lib module and its devices
+Documentation for dvb-usb-framework module and its devices
 
-Idea behind the dvb-usb-lib
-===========================
+Idea behind the dvb-usb-framework
+=================================
 
 In March 2005 I got the new Twinhan USB2.0 DVB-T device. They provided specs and a firmware.
 
 Quite keen I wanted to put the driver (with some quirks of course) into dibusb.
 After reading some specs and doing some USB snooping, it realized, that the
 dibusb-driver would be a complete mess afterwards. So I decided to do it in a
-different way: With the help of a dvb-usb-lib.
+different way: With the help of a dvb-usb-framework.
 
-The dvb-usb-lib basically contains generic functions which every particular DVB
-USB device would need to handle if it would be on its own.
+The framework provides generic functions (mostly kernel API calls), such as:
 
 - Transport Stream URB handling in conjunction with dvb-demux-feed-control
   (bulk and isoc (TODO) are supported)
 - registering the device for the DVB-API
 - registering an I2C-adapter if applicable
-- remote-control/input-device handling (TODO)
+- remote-control/input-device handling
 - firmware requesting and loading (currently just for the Cypress USB
   controller)
 - other functions/methods which can be shared by several drivers (such as
-  bulk-control-commands)
+  functions for bulk-control-commands)
 
 The source code of the particular DVB USB devices does just the communication
 with the device via the bus. The connection between the DVB-API-functionality
@@ -34,8 +33,8 @@ Objective is to migrate all the usb-devices (dibusb, cinergyT2, maybe the
 ttusb; flexcop-usb already benefits from the generic flexcop-device) to use
 the dvb-usb-lib.
 
-The following list is mix of dibusb-devices and real dvb-usb-devices. Sooner or
-later all device will be handled by dvb-usb. Then this line can be removed too.
+TODO: dynamic enabling and disabled of the pid-filter in regard to number of
+feeds requested.
 
 Supported devices USB1.1
 ========================
@@ -88,10 +87,10 @@ Others:
 
 Supported devices USB2.0-only
 =============================
-- Twinhan MagicBox II (3)
+- Twinhan MagicBox II
 	http://www.twinhan.com/product_terrestrial_7.asp
 
-- TwinhanDTV Alpha (3)
+- TwinhanDTV Alpha
 	http://www.twinhan.com/product_terrestrial_8.asp
 
 - Hanftek UMT-010
@@ -100,8 +99,11 @@ Supported devices USB2.0-only
 
 Supported devices USB2.0 and USB1.1
 =============================
-- Typhoon/Yakumo/HAMA DVB-T mobile USB2.0 (3)
+- Typhoon/Yakumo/HAMA/Yuan DVB-T mobile USB2.0
 	http://www.yakumo.de/produkte/index.php?pid=1&ag=DVB-T
+	http://www.yuan.com.tw/en/products/vdo_ub300.html
+	http://www.hama.de/portal/articleId*114663/action*2563
+	http://www.anubisline.com/english/articlec.asp?id=50502&catid=002
 
 - Artec T1 USB TVBOX (FX2) (2)
 
@@ -112,13 +114,13 @@ Supported devices USB2.0 and USB1.1
 
 - DiBcom USB2.0 DVB-T reference device (non-public)
 
-- AVerMedia AverTV DVB-T USB2.0
+- AVerMedia AverTV A800 DVB-T USB2.0
 
 1) It is working almost - work-in-progress.
 2) No test reports received yet.
-3) porting for dvb-usb done.
 
 0. History & News:
+  2005-04-17 - all dibusb devices ported to make use of the dvb-usb-framework
   2005-04-02 - re-enabled and improved remote control code.
   2005-03-31 - ported the Yakumo/Hama/Typhoon DVB-T USB2.0 device to dvb-usb.
   2005-03-30 - first commit of the dvb-usb-module based on the dibusb-source. First device is a new driver for the
@@ -180,36 +182,26 @@ Supported devices USB2.0 and USB1.1
   2004-05-11 - start writing the driver
 
 1. How to use?
-NOTE: This driver was developed using Linux 2.6.6.,
-it is working with 2.6.7 and above.
-
-Linux 2.4.x support is not planned, but patches are very welcome.
-
-NOTE: I'm using Debian testing, so the following explaination (especially
-the hotplug-path) needn't match your system, but probably it will :).
-
-The driver is included in the kernel since Linux 2.6.10.
-
 1.1. Firmware
 
-The USB driver needs to download a firmware to start working.
+Most of the USB drivers need to download a firmware to start working.
 
-for USB1.1 (AN2135) you need: dvb-dibusb-5.0.0.11.fw
-for USB2.0 HanfTek: dvb-dibusb-umt-2.fw
-for USB2.0 DiBcom: dvb-dibusb-6.0.0.5.fw
-for USB2.0 AVerMedia AverTV DVB-T USB2: dvb-dibusb-avertv-usb2-1.fw
+for USB1.1 (AN2135) you need: dvb-usb-dibusb-5.0.0.11.fw
+for USB2.0 HanfTek: dvb-usb-umt-010-02.fw
+for USB2.0 DiBcom: dvb-usb-dibusb-6.0.0.8.fw
+for USB2.0 AVerMedia AverTV DVB-T USB2: dvb-usb-avertv-a800-01.fw
 for USB2.0 TwinhanDTV Alpha/MagicBox II: dvb-usb-vp7045-01.fw
 
 The files can be found on http://www.linuxtv.org/download/firmware/ .
 
-We do not have the permission to publish the following firmware-files.
+We do not have the permission (yet) to publish the following firmware-files.
 You'll need to extract them from the windows drivers.
 
-You should be able to use "get_dvb_firmware dibusb" to get the firmware:
+You should be able to use "get_dvb_firmware dvb-usb" to get the firmware:
 
-for USB1.1 (AN2235) (a few Artec T1 devices): dvb-dibusb-an2235-1.fw
-for USB2.0 Hauppauge: dvb-dibusb-nova-t-1.fw
-for USB2.0 ADSTech/Kworld USB2.0: dvb-dibusb-adstech-usb2-1.fw
+for USB1.1 (AN2235) (a few Artec T1 devices): dvb-usb-dibusb-an2235-01.fw
+for USB2.0 Hauppauge: dvb-usb-nova-t-usb2-01.fw
+for USB2.0 ADSTech/Kworld USB2.0: dvb-usb-adstech-usb2-01.fw
 for USB2.0 Yakumo/Typhoon/Hama: dvb-usb-dtt200u-01.fw
 
 1.2. Compiling
@@ -218,6 +210,9 @@ Since the driver is in the linux kernel, activating the driver in
 your favorite config-environment should sufficient. I recommend
 to compile the driver as module. Hotplug does the rest.
 
+If you use dvb-kernel enter the build-2.6 directory run 'make' and 'insmod.sh
+load' afterwards.
+
 1.3. Loading the drivers
 
 Hotplug is able to load the driver, when it is needed (because you plugged
@@ -288,14 +283,14 @@ Patches, comments and suggestions are very very welcome.
 
    Bernd Wagner for helping with huge bug reports and discussions.
 
-   Gunnar Wittich and Joachim von Caron for their trust for giving me
+   Gunnar Wittich and Joachim von Caron for their trust for providing
     root-shells on their machines to implement support for new devices.
 
    Glen Harris for bringing up, that there is a new dibusb-device and Jiun-Kuei
     Jung from AVerMedia who kindly provided a special firmware to get the device
     up and running in Linux.
 
-   Jennifer Chen, Jeff and Jack from Twinhan for kindly supporting me by
+   Jennifer Chen, Jeff and Jack from Twinhan for kindly supporting by
 	writing the vp7045-driver.
 
    Some guys on the linux-dvb mailing list for encouraging me