patch-2.1.46 linux/drivers/scsi/README.in2000

• Lines: 37
• Date: Thu Jul 17 20:24:38 1997
• Orig file: v2.1.45/linux/drivers/scsi/README.in2000
• Orig date: Mon Oct 14 23:39:48 1996

diff -u --recursive --new-file v2.1.45/linux/drivers/scsi/README.in2000 linux/drivers/scsi/README.in2000
@@ -1,4 +1,16 @@
 
+UPDATE NEWS: version 1.31 - 6 Jul 97
+
+   Fixed a bug that caused incorrect SCSI status bytes to be
+   returned from commands sent to LUN's greater than 0. This
+   means that CDROM changers work now! Fixed a bug in the
+   handling of command-line arguments when loaded as a module.
+   Also put all the header data in in2000.h where it belongs.
+   There are no longer any differences between this driver in
+   the 2.1.xx source tree and the 2.0.xx tree, as of 2.0.31
+   and 2.1.45 (or is it .46?) - this makes things much easier
+   for me...
+
 UPDATE NEWS: version 1.30 - 14 Oct 96
 
    Fixed a bug in the code that sets the transfer direction
@@ -105,15 +117,10 @@
 There's also a define called 'DEFAULT_SX_PER'; this sets the data
 transfer speed for the asynchronous mode. I've put it at 500 ns
 despite the fact that the card could handle settings of 376 or
-252, because I'm not really sure if certain devices or maybe bad
-cables might have trouble at higher speeds. I couldn't find any
-info in my various SCSI references that talk about this in language
-I could understand, so decided to compromise with 500. This is still
-faster than the old driver was set at (I think). Can someone explain
-the significance of the bus transfer speed setting? Do devices on
-the bus ever care what it is? Is cable quality a factor here?
-Regardless, you can choose your own default through the command-
-line with the 'period' keyword.
+252, because higher speeds may be a problem with poor quality
+cables or improper termination; 500 ns is a compromise. You can
+choose your own default through the command-line with the
+'period' keyword.
 
 
 ------------------------------------------------