sc(4) [netbsd man page]

SC(4)							   BSD Kernel Interfaces Manual 						     SC(4)

NAME

     sc -- Sun Sun-2 SCSI bus host adaptor driver

SYNOPSIS

   sun2
     sc0 at mbmem0 addr 0x80000 ipl 2
     sc1 at mbmem0 addr 0x84000 ipl 2

   sun2 and sun4
     sc0 at vme0 addr 0x200000 irq 2 vec 0x40

DESCRIPTION

     The sc driver provides support for the Sun Microsystems "Sun-2" SCSI Bus Controller chipset found on various VME boards (Sun part #s
     501-1045, 501-1138, 501-1149, and 501-1167) and on the "Sun-2 SCSI/Serial" (Sun part # 501-1006) Multibus board.

     All versions of this driver can be configured with a flags directive in the config(1) file.  The values are bits in a bitfield, and are
     interpreted as follows:

	   0x0ff    Set bit (1<<target) to disable SCSI parity checking
	   0x100    Set this bit to disable DMA interrupts (poll)
	   0x200    Set this bit to disable DMA entirely (use PIO)

     For example: "flags 0x1ff" would disable DMA interrupts, and disable parity checking for targets 0-7.  The "target" is the SCSI ID number of
     a particular device on a particular SCSI bus.

SEE ALSO

     cd(4), ch(4), intro(4), scsi(4), sd(4), st(4)

AUTHORS

     Matt Fredette <fredette@NetBSD.org>,
     David Jones,
     Gordon Ross <gwr@NetBSD.org>,
     Adam Glass <glass@NetBSD.org>,
     Jason R. Thorpe <thorpej@NetBSD.org>.

BUGS

     This SCSI chipset is rumored to have bugs in its handling of SCSI parity, therefore it is recommended that you disable parity on all SCSI
     devices connected to this controller, and configure it with a 0x0ff value for its flags directive in the config(1) file.

     This chipset has no support for raising the ATN signal, so there is no way to ever schedule a MSG_OUT phase on the bus.  Currently, the
     driver will ultimately reset the bus if this phase is ever requested by the upper layer SCSI driver.

     This chipset has no support for SCSI disconnect/reselect.	This means that slow devices, such as tape drives, can hog, or "lock up" the SCSI
     bus.

     This driver has not been tested in combination with non-SCSI devices behind Emulex or Adaptec bridges, which are common in Sun 2s and in Sun
     Shoebox-type configurations.  These devices pre-date the SCSI-I spec, and might not behave the way the chipset code currently expects.

BSD
								   June 28, 2001							       BSD

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