1*4882a593Smuzhiyun.. SPDX-License-Identifier: GPL-2.0 2*4882a593Smuzhiyun 3*4882a593Smuzhiyun================================= 4*4882a593SmuzhiyunQlogic FASXXX Family Driver Notes 5*4882a593Smuzhiyun================================= 6*4882a593Smuzhiyun 7*4882a593SmuzhiyunThis driver supports the Qlogic FASXXX family of chips. This driver 8*4882a593Smuzhiyunonly works with the ISA, VLB, and PCMCIA versions of the Qlogic 9*4882a593SmuzhiyunFastSCSI! cards as well as any other card based on the FASXX chip 10*4882a593Smuzhiyun(including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards). 11*4882a593Smuzhiyun 12*4882a593SmuzhiyunThis driver does NOT support the PCI version. Support for these PCI 13*4882a593SmuzhiyunQlogic boards: 14*4882a593Smuzhiyun 15*4882a593Smuzhiyun * IQ-PCI 16*4882a593Smuzhiyun * IQ-PCI-10 17*4882a593Smuzhiyun * IQ-PCI-D 18*4882a593Smuzhiyun 19*4882a593Smuzhiyunis provided by the qla1280 driver. 20*4882a593Smuzhiyun 21*4882a593SmuzhiyunNor does it support the PCI-Basic, which is supported by the 22*4882a593Smuzhiyun'am53c974' driver. 23*4882a593Smuzhiyun 24*4882a593SmuzhiyunPCMCIA Support 25*4882a593Smuzhiyun============== 26*4882a593Smuzhiyun 27*4882a593SmuzhiyunThis currently only works if the card is enabled first from DOS. This 28*4882a593Smuzhiyunmeans you will have to load your socket and card services, and 29*4882a593SmuzhiyunQL41DOS.SYS and QL40ENBL.SYS. These are a minimum, but loading the 30*4882a593Smuzhiyunrest of the modules won't interfere with the operation. The next 31*4882a593Smuzhiyunthing to do is load the kernel without resetting the hardware, which 32*4882a593Smuzhiyuncan be a simple ctrl-alt-delete with a boot floppy, or by using 33*4882a593Smuzhiyunloadlin with the kernel image accessible from DOS. If you are using 34*4882a593Smuzhiyunthe Linux PCMCIA driver, you will have to adjust it or otherwise stop 35*4882a593Smuzhiyunit from configuring the card. 36*4882a593Smuzhiyun 37*4882a593SmuzhiyunI am working with the PCMCIA group to make it more flexible, but that 38*4882a593Smuzhiyunmay take a while. 39*4882a593Smuzhiyun 40*4882a593SmuzhiyunAll Cards 41*4882a593Smuzhiyun========= 42*4882a593Smuzhiyun 43*4882a593SmuzhiyunThe top of the qlogic.c file has a number of defines that controls 44*4882a593Smuzhiyunconfiguration. As shipped, it provides a balance between speed and 45*4882a593Smuzhiyunfunction. If there are any problems, try setting SLOW_CABLE to 1, and 46*4882a593Smuzhiyunthen try changing USE_IRQ and TURBO_PDMA to zero. If you are familiar 47*4882a593Smuzhiyunwith SCSI, there are other settings which can tune the bus. 48*4882a593Smuzhiyun 49*4882a593SmuzhiyunIt may be a good idea to enable RESET_AT_START, especially if the 50*4882a593Smuzhiyundevices may not have been just powered up, or if you are restarting 51*4882a593Smuzhiyunafter a crash, since they may be busy trying to complete the last 52*4882a593Smuzhiyuncommand or something. It comes up faster if this is set to zero, and 53*4882a593Smuzhiyunif you have reliable hardware and connections it may be more useful to 54*4882a593Smuzhiyunnot reset things. 55*4882a593Smuzhiyun 56*4882a593SmuzhiyunSome Troubleshooting Tips 57*4882a593Smuzhiyun========================= 58*4882a593Smuzhiyun 59*4882a593SmuzhiyunMake sure it works properly under DOS. You should also do an initial FDISK 60*4882a593Smuzhiyunon a new drive if you want partitions. 61*4882a593Smuzhiyun 62*4882a593SmuzhiyunDon't enable all the speedups first. If anything is wrong, they will make 63*4882a593Smuzhiyunany problem worse. 64*4882a593Smuzhiyun 65*4882a593SmuzhiyunImportant 66*4882a593Smuzhiyun========= 67*4882a593Smuzhiyun 68*4882a593SmuzhiyunThe best way to test if your cables, termination, etc. are good is to 69*4882a593Smuzhiyuncopy a very big file (e.g. a doublespace container file, or a very 70*4882a593Smuzhiyunlarge executable or archive). It should be at least 5 megabytes, but 71*4882a593Smuzhiyunyou can do multiple tests on smaller files. Then do a COMP to verify 72*4882a593Smuzhiyunthat the file copied properly. (Turn off all caching when doing these 73*4882a593Smuzhiyuntests, otherwise you will test your RAM and not the files). Then do 74*4882a593Smuzhiyun10 COMPs, comparing the same file on the SCSI hard drive, i.e. "COMP 75*4882a593Smuzhiyunrealbig.doc realbig.doc". Then do it after the computer gets warm. 76*4882a593Smuzhiyun 77*4882a593SmuzhiyunI noticed my system which seems to work 100% would fail this test if 78*4882a593Smuzhiyunthe computer was left on for a few hours. It was worse with longer 79*4882a593Smuzhiyuncables, and more devices on the SCSI bus. What seems to happen is 80*4882a593Smuzhiyunthat it gets a false ACK causing an extra byte to be inserted into the 81*4882a593Smuzhiyunstream (and this is not detected). This can be caused by bad 82*4882a593Smuzhiyuntermination (the ACK can be reflected), or by noise when the chips 83*4882a593Smuzhiyunwork less well because of the heat, or when cables get too long for 84*4882a593Smuzhiyunthe speed. 85*4882a593Smuzhiyun 86*4882a593SmuzhiyunRemember, if it doesn't work under DOS, it probably won't work under 87*4882a593SmuzhiyunLinux. 88