~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/scsi/qlogicfas.rst

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

Diff markup

Differences between /Documentation/scsi/qlogicfas.rst (Version linux-6.12-rc7) and /Documentation/scsi/qlogicfas.rst (Version linux-5.19.17)


  1 .. SPDX-License-Identifier: GPL-2.0                 1 .. SPDX-License-Identifier: GPL-2.0
  2                                                     2 
  3 =================================                   3 =================================
  4 Qlogic FASXXX Family Driver Notes                   4 Qlogic FASXXX Family Driver Notes
  5 =================================                   5 =================================
  6                                                     6 
  7 This driver supports the Qlogic FASXXX family       7 This driver supports the Qlogic FASXXX family of chips.  This driver
  8 only works with the ISA, VLB, and PCMCIA versi      8 only works with the ISA, VLB, and PCMCIA versions of the Qlogic
  9 FastSCSI!  cards as well as any other card bas      9 FastSCSI!  cards as well as any other card based on the FASXX chip
 10 (including the Control Concepts SCSI/IDE/SIO/P     10 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
 11                                                    11 
 12 This driver does NOT support the PCI version.      12 This driver does NOT support the PCI version.  Support for these PCI
 13 Qlogic boards:                                     13 Qlogic boards:
 14                                                    14 
 15         * IQ-PCI                                   15         * IQ-PCI
 16         * IQ-PCI-10                                16         * IQ-PCI-10
 17         * IQ-PCI-D                                 17         * IQ-PCI-D
 18                                                    18 
 19 is provided by the qla1280 driver.                 19 is provided by the qla1280 driver.
 20                                                    20 
 21 Nor does it support the PCI-Basic, which is su     21 Nor does it support the PCI-Basic, which is supported by the
 22 'am53c974' driver.                                 22 'am53c974' driver.
 23                                                    23 
 24 PCMCIA Support                                     24 PCMCIA Support
 25 ==============                                     25 ==============
 26                                                    26 
 27 This currently only works if the card is enabl     27 This currently only works if the card is enabled first from DOS.  This
 28 means you will have to load your socket and ca     28 means you will have to load your socket and card services, and
 29 QL41DOS.SYS and QL40ENBL.SYS.  These are a min     29 QL41DOS.SYS and QL40ENBL.SYS.  These are a minimum, but loading the
 30 rest of the modules won't interfere with the o     30 rest of the modules won't interfere with the operation.  The next
 31 thing to do is load the kernel without resetti     31 thing to do is load the kernel without resetting the hardware, which
 32 can be a simple ctrl-alt-delete with a boot fl     32 can be a simple ctrl-alt-delete with a boot floppy, or by using
 33 loadlin with the kernel image accessible from      33 loadlin with the kernel image accessible from DOS.  If you are using
 34 the Linux PCMCIA driver, you will have to adju     34 the Linux PCMCIA driver, you will have to adjust it or otherwise stop
 35 it from configuring the card.                      35 it from configuring the card.
 36                                                    36 
 37 I am working with the PCMCIA group to make it      37 I am working with the PCMCIA group to make it more flexible, but that
 38 may take a while.                                  38 may take a while.
 39                                                    39 
 40 All Cards                                          40 All Cards
 41 =========                                          41 =========
 42                                                    42 
 43 The top of the qlogic.c file has a number of d     43 The top of the qlogic.c file has a number of defines that controls
 44 configuration.  As shipped, it provides a bala     44 configuration.  As shipped, it provides a balance between speed and
 45 function.  If there are any problems, try sett     45 function.  If there are any problems, try setting SLOW_CABLE to 1, and
 46 then try changing USE_IRQ and TURBO_PDMA to ze     46 then try changing USE_IRQ and TURBO_PDMA to zero.  If you are familiar
 47 with SCSI, there are other settings which can      47 with SCSI, there are other settings which can tune the bus.
 48                                                    48 
 49 It may be a good idea to enable RESET_AT_START     49 It may be a good idea to enable RESET_AT_START, especially if the
 50 devices may not have been just powered up, or      50 devices may not have been just powered up, or if you are restarting
 51 after a crash, since they may be busy trying t     51 after a crash, since they may be busy trying to complete the last
 52 command or something.  It comes up faster if t     52 command or something.  It comes up faster if this is set to zero, and
 53 if you have reliable hardware and connections      53 if you have reliable hardware and connections it may be more useful to
 54 not reset things.                                  54 not reset things.
 55                                                    55 
 56 Some Troubleshooting Tips                          56 Some Troubleshooting Tips
 57 =========================                          57 =========================
 58                                                    58 
 59 Make sure it works properly under DOS.  You sh     59 Make sure it works properly under DOS.  You should also do an initial FDISK
 60 on a new drive if you want partitions.             60 on a new drive if you want partitions.
 61                                                    61 
 62 Don't enable all the speedups first.  If anyth     62 Don't enable all the speedups first.  If anything is wrong, they will make
 63 any problem worse.                                 63 any problem worse.
 64                                                    64 
 65 Important                                          65 Important
 66 =========                                          66 =========
 67                                                    67 
 68 The best way to test if your cables, terminati     68 The best way to test if your cables, termination, etc. are good is to
 69 copy a very big file (e.g. a doublespace conta     69 copy a very big file (e.g. a doublespace container file, or a very
 70 large executable or archive).  It should be at     70 large executable or archive).  It should be at least 5 megabytes, but
 71 you can do multiple tests on smaller files.  T     71 you can do multiple tests on smaller files.  Then do a COMP to verify
 72 that the file copied properly.  (Turn off all      72 that the file copied properly.  (Turn off all caching when doing these
 73 tests, otherwise you will test your RAM and no     73 tests, otherwise you will test your RAM and not the files).  Then do
 74 10 COMPs, comparing the same file on the SCSI      74 10 COMPs, comparing the same file on the SCSI hard drive, i.e. "COMP
 75 realbig.doc realbig.doc".  Then do it after th     75 realbig.doc realbig.doc".  Then do it after the computer gets warm.
 76                                                    76 
 77 I noticed my system which seems to work 100% w     77 I noticed my system which seems to work 100% would fail this test if
 78 the computer was left on for a few hours.  It      78 the computer was left on for a few hours.  It was worse with longer
 79 cables, and more devices on the SCSI bus.  Wha     79 cables, and more devices on the SCSI bus.  What seems to happen is
 80 that it gets a false ACK causing an extra byte     80 that it gets a false ACK causing an extra byte to be inserted into the
 81 stream (and this is not detected).  This can b     81 stream (and this is not detected).  This can be caused by bad
 82 termination (the ACK can be reflected), or by      82 termination (the ACK can be reflected), or by noise when the chips
 83 work less well because of the heat, or when ca     83 work less well because of the heat, or when cables get too long for
 84 the speed.                                         84 the speed.
 85                                                    85 
 86 Remember, if it doesn't work under DOS, it pro     86 Remember, if it doesn't work under DOS, it probably won't work under
 87 Linux.                                             87 Linux.
                                                      

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php