esp(4) [debian man page]
ESP(4) BSD Kernel Interfaces Manual ESP(4) NAME
esp -- Qlogic FEPS and FAS366 SCSI driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device scbus device esp HARDWARE
The esp driver provides support for the Qlogic FAS216 and FAS408 SCSI controller chips found in a wide variety of systems and peripheral boards. This includes the Qlogic SCSI cards found in most Sun Ultra 1e and Ultra 2 machines. For Qlogic PCI SCSI host adapters, the isp(4) driver should be used in place of the esp driver. IMPLEMENTATION NOTES
During the boot sequence, the esp driver searches the linked list for LUN info by LUN ID. At this point the driver will attach on that instance, and then attempt to attach every sub-device. There are at least 4 variations of the configuration 3 register. A second config register must be loaded to inquire the chip revision, oth- erwise the ncr53c9x_reset() function will not set the defaults correctly. The drive attach routine attempts to set the appropriate bit to put the chip into Fast SCSI mode so that it does not have to be figured out each time. This will then be stored in the NCR registers for later use. The esp driver makes use of the LSI 64854 DMA engine which contains three independent channels designed to interface with an NCR539X SCSI controller; an AM7990 Ethernet controller; and certain types of parallel port hardware. As such this driver may eventually replace the amd(4) driver for network hardware. DIAGNOSTICS
The following driver specific error messages may be reported: esp: cannot map %d segments The device was unable to map segments while mapping the SCSI devices in DMA mode. unknown variant %d, devices not attached An unknown version of the card was found and devices will not be attached. Unhandled function code %d The device returned a function code which the driver is unable to handle, most likely during negotiation. esp:%d:%d: selection failed %d left in FIFO The target left the command phase prematurely. If a command did not reach the device then it will be reported as shown above. invalid state: %d The device has reached an invalid state. SEE ALSO
amd(4), isp(4), scbus(4), camcontrol(8) http://www.qlc.com/ http://www.sun.com/ HISTORY
The esp driver was written for NetBSD by Eric S. Hvozda. The esp driver was then ported to FreeBSD 5.3 by Scott Long <scottl@FreeBSD.org>. AUTHORS
This manual page was written by Tom Rhodes <trhodes@FreeBSD.org> instead of porting the original from NetBSD. BUGS
The esp driver includes the sbus front-end but lacks the PCI front-end. Thus it can only support the FEPS/FAS366 SCSI found in Sun Ultra 1e and Ultra 2 machines at this time. This driver should eventually replace the amd(4) driver, but that requires porting the PCI front-end mentioned above. BSD
September 18, 2005 BSD
Check Out this Related Man Page
ISP(4) BSD Kernel Interfaces Manual ISP(4) NAME
isp -- Qlogic based SCSI and FibreChannel SCSI Host Adapters SYNOPSIS
isp* at pci? dev? function? (PCI) isp* at sbus? slot ? offset ? (SBus) scsibus* at isp? DESCRIPTION
This driver provides access to SCSI or FibreChannel devices. SCSI features include support for Ultra SCSI and wide mode transactions for SCSI, and LVD (for the ISP1080 and ISP1280), Fibre Channel support uses FCP SCSI profile for FibreChannel. and uses Class 3 connections only. Support is available for Public and Pri- vate loops. Command tagging is supported for all (in fact, FibreChannel requires tagging). CONFIGURATION
An optional flags 0x80 appended to the above isp* declarations will disable the download of driver firmware, which means you use whatever firmware is running on the card. If no firmware is running on the card, the driver cannot operate the card. An optional flags 0x40 appended to the above isp* declarations (can be OR'd in with the other config flags option) will keep the driver from looking at device or bus NVRAM settings (this is in case NVRAM is just wrong and you have the card in a platform where it is inconvenient to change NVRAM settings on the card). HARDWARE
Supported cards include: ISP1000 SBus Fast Wide, Ultra Fast Wide cards, Single Ended or Differential cards. PTI SBS440 Performance Technology ISP1000 variants. ISP1020 Qlogic 1020 Fast Wide and Differential Fast Wide PCI cards. ISP1040 Qlogic 1040 Ultra Wide and Differential Ultra Wide PCI cards. PTI SBS450 Performance Technology ISP1040 variants. Qlogic 1240 Qlogic 1240 Dual Bus Ultra Wide and Differential Ultra Wide PCI cards. Qlogic 1080 Qlogic 1280 LVD Ultra2 Wide PCI cards. Qlogic 1280 Qlogic 1280 Dual Bus LVD Ultra2 Wide PCI cards. Qlogic 2100 Qlogic 2100 and 2100A Copper and Optical Fibre Channel Arbitrated Loop Qlogic 2102 Qlogic Dual Loop 2100A Optical Fibre Channel Arbitrated Loop PCI cards. Qlogic 2200 Qlogic 2200 Copper and Optical Fibre Channel Arbitrated Loop PCI cards. Qlogic 2202 Qlogic 2200 Dual Bus Optical Fibre Channel Arbitrated Loop PCI cards. Qlogic 2204 Qlogic 2200 Quad Bus Optical Fibre Channel Arbitrated Loop PCI cards. Qlogic 2300 Qlogic 2300 2-Gigabit Optical Fibre Channel PCI cards. Qlogic 2312 Qlogic 2300 2-Gigabit Dual Channel Optical Fibre Channel PCI cards. PTI SBS470 Performance Technology ISP2100 variants. Antares P-0033 Antares Microsystems ISP2100 variants. Qlogic 2400 Qlogic 2400 4-Gigabit Optical Fibre Channel PCI cards. Qlogic 2500 Qlogic 2500 8-Gigabit Optical Fibre Channel PCI cards. SEE ALSO
cd(4), intro(4), scsi(4), sd(4), st(4) AUTHORS
The isp driver was written by Matthew Jacob for NASA/Ames Research Center. BUGS
The driver currently ignores some NVRAM settings. The driver currently doesn't do error recovery for timed out commands very gracefully. Sometimes, when booting, the driver gets stuck waiting for the Fibre Channel firmware to tell it that the loop port database is ready. In this case you'll see an announcement that the loop state has a value of 0x1. To unwedge the system, unplug and replug the fibre channel con- nection, or otherwise cause a LIP (Loop Initialization Primitive sequence) - this will kick the firmware into getting unstuck. BSD
June 24, 2009 BSD