- white space changes :)

- acknowledgements

1 files changed, 21 insertions, 16 deletions

diff --git a/linux/Documentation/dvb/README.flexcop b/linux/Documentation/dvb/README.flexcop
index 2d73446fb..8036faa1e 100644
--- a/linux/Documentation/dvb/README.flexcop
+++ b/linux/Documentation/dvb/README.flexcop
@@ -30,9 +30,9 @@ We should proceed as follows (as long as no one complains):
 0) Think before start writing code!
 
 1) rewriting the skystar2.c with the help of the flexcop register descriptions
-and splitting up the files to a pci-bus-part and a flexcop-part. 
+and splitting up the files to a pci-bus-part and a flexcop-part.
 The new driver will be called b2c2-flexcop-pci.ko/b2c2-flexcop-usb.ko for the
-device-specific part and b2c2-flexcop.ko for the common flexcop-functions. 
+device-specific part and b2c2-flexcop.ko for the common flexcop-functions.
 
 2) Search for errors in the leftover of flexcop-pci.c (compare with pluto2.c
 and other pci drivers)
@@ -44,7 +44,7 @@ done')
 a wider tester audience.
 
 5) creating an usb-bus-part using the already written flexcop code for the pci
-card. 
+card.
 
 Idea: create a kernel-object for the flexcop and export all important
 functions. This option saves kernel-memory, but maybe a lot of functions have
@@ -67,7 +67,7 @@ What seems to be ready?
 1) Rewriting
 1a) i2c is cut off from the flexcop-pci.c and seems to work
 1b) moved tuner and demod stuff from flexcop-pci.c to flexcop-tuner-fe.c
-1c) moved lnb and diseqc stuff from flexcop-pci.c to flexcop-tuner-fe.c 
+1c) moved lnb and diseqc stuff from flexcop-pci.c to flexcop-tuner-fe.c
 1e) eeprom (reading MAC address)
 1d) sram (no dynamic sll size detection (commented out) (using default as JJ told me))
 1f) misc. register accesses for reading parameters (e.g. resetting, revision)
@@ -92,7 +92,7 @@ What to do in the near future?
 5c) feeding of ISOC data to the software demux (format of the isochronous data
 and speed optimization, no real error)
 
-Testing changes 
+Testing changes
 ---------------
 
 O             = item is working
@@ -105,19 +105,19 @@ N             = item does not apply here
 item   | mt352 | nxt2002 | stv0299 | mt312 | mt352 | nxt2002 | stv0299 | mt312
 -------+-------+---------+---------+-------+-------+---------+---------+-------
 1a)    | O     |         |         |       | N     | N       | N       | N
-1b)    | O     |         |         |       |       |         | O       |  
-1c)    | N     | N       |         |       | N     | N       | O       |  
+1b)    | O     |         |         |       |       |         | O       |
+1c)    | N     | N       |         |       | N     | N       | O       |
 1d)    |                 O                 |                 O
-1e)    |                 O                 |                 O            
-1f)    |                                   P                                 
+1e)    |                 O                 |                 O
+1f)    |                                   P
 1g)    |                                   O
-1h)    |                 P                 |                              
-1i)    |                 O                 |                 N 
+1h)    |                 P                 |
+1i)    |                 O                 |                 N
 1j)    |                 O                 |                 N
 1l)    |                 O                 |                 N
 2)     |                 O                 |                 N
 5a)    |                 N                 |                 O
-5b)*   |                 N                 |                
+5b)*   |                 N                 |
 5c)*   |                 N                 |
 
 * - not done yet
@@ -133,7 +133,7 @@ DMA usage currently:
   address. When the second address is full, the IRQ is triggered again, and
   the flexcop writes to first address again, and so on.
   The buffersize of each address is currently 640*188 bytes.
-  
+
   Problem is, when using hw-pid-filtering and doing some low-bandwidth
   operation (like scanning) the buffers won't be filled enough to trigger
   the IRQ. That's why:
@@ -177,7 +177,7 @@ Debugging
 Everything which is identical in the following table, can be put into a common
 flexcop-module.
 
-                  PCI                  USB          
+                  PCI                  USB
 -------------------------------------------------------------------------------
 Different:
 Register access:  accessing IO memory  USB control message
@@ -235,7 +235,7 @@ flexcop-module. (within the flexcop_device-struct)
 Initialization process
 ======================
 
-b2c2-flexcop.ko is loaded 
+b2c2-flexcop.ko is loaded
 b2c2-flexcop-<bus>.ko is loaded
 
 suppose a device is found:
@@ -274,6 +274,11 @@ Acknowledgements (just for the rewriting part)
 Bjarne Steinsbo thought a lot in the first place of the pci part for this code
 sharing idea.
 
-Andreas Oberritter for providing a recent PCI initialization template (pluto2.c).
+Andreas Oberritter for providing a recent PCI initialization template
+(pluto2.c).
+
+Boleslaw Ciesielski for pointing out a problem with firmware loader.
+
+Vadim Catana for correcting the USB transfer.
 
 comments, critics and ideas to linux-dvb@linuxtv.org or patrick.boettcher@desy.de