Orange Pi5 kernel

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