patch-1.3.29 linux/Documentation/scsi.txt

• Lines: 31
• Date: Fri Sep 22 08:04:12 1995
• Orig file: v1.3.28/linux/Documentation/scsi.txt
• Orig date: Thu Jan 1 02:00:00 1970

diff -u --recursive --new-file v1.3.28/linux/Documentation/scsi.txt linux/Documentation/scsi.txt
@@ -0,0 +1,30 @@
+
+	The scsi support in the linux kernel can be modularized in a
+number of different ways depending upon the needs of the end user.  To
+understand  your options, we should first define a few terms.
+
+	The scsi-core contains the core of scsi support.  Without it
+you can do nothing with any of the other scsi drivers.  The scsi core
+support can be a module (scsi_mod.o), or it can be build into the kernel.
+If the core is a module, it must be the first scsi module loaded, and
+if you unload the modules, it will have to be the last one unloaded.
+
+	The individual upper and lower level drivers can be loaded in any
+order once the scsi core is present in the kernel (either compiled in
+or loaded as a module).  The disk driver (sd_mod.o), cdrom driver (sr_mod.o),
+tape driver (st.o) and scsi generics driver (sg.o) represent the upper level
+drivers to support the various assorted devices which can be controlled.
+You can for example load the tape driver to use the tape drive, and then
+unload it once you have no further need for the driver (and release the
+associated memory).
+
+	The lower level drivers are the ones that support the
+individual cards that are supported for the hardware platform that you
+are running under.  Examples are aha1542.o to drive Adaptec 1542
+cards.  Rather than list the drivers which *can* be modularized, it is
+easier to list the ones which cannot, since the list only contains a
+few entries.  The drivers which have NOT been modularized are:
+
+	NCR5380 boards of one kind or another including PAS16,
+		Trantor T128/128F/228, 
+