2 .\" Copyright (c) 2004 Tom Rhodes
3 .\" All rights reserved.
5 .\" Redistribution and use in source and binary forms, with or without
6 .\" modification, are permitted provided that the following conditions
8 .\" 1. Redistributions of source code must retain the above copyright
9 .\" notice, this list of conditions and the following disclaimer.
10 .\" 2. Redistributions in binary form must reproduce the above copyright
11 .\" notice, this list of conditions and the following disclaimer in the
12 .\" documentation and/or other materials provided with the distribution.
14 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
15 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
16 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
17 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
18 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
19 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
20 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
21 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
22 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
23 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .Dd September 18, 2005
33 .Nd Qlogic FEPS and FAS366 SCSI driver
40 driver provides support for the
44 controller chips found in a wide variety of systems and peripheral boards.
61 driver should be used in place of the
64 .Sh IMPLEMENTATION NOTES
65 During the boot sequence, the
68 searches the linked list for LUN info by LUN ID.
69 At this point the driver will attach on that instance,
70 and then attempt to attach every sub-device.
72 There are at least 4 variations of the
73 configuration 3 register.
74 A second config register must be loaded to inquire the chip revision,
77 function will not set the defaults correctly.
79 The drive attach routine attempts to set the appropriate
80 bit to put the chip into Fast
82 mode so that it does not
83 have to be figured out each time.
84 This will then be stored in the
86 registers for later use.
90 driver makes use of the
94 engine which contains three independent
95 channels designed to interface with
99 an AM7990 Ethernet controller;
100 and certain types of parallel port hardware.
101 As such this driver may eventually replace the
103 driver for network hardware.
105 The following driver specific error messages
108 .It "esp: cannot map %d segments"
109 The device was unable to map segments while mapping the
114 .It "unknown variant %d, devices not attached"
115 An unknown version of the card was found and devices will
117 .It "Unhandled function code %d"
118 The device returned a function code which the driver is
119 unable to handle, most likely during negotiation.
120 .It "esp:%d:%d: selection failed %d left in FIFO"
121 The target left the command phase prematurely.
122 If a command did not reach the device then it will
123 be reported as shown above.
124 .It "invalid state: %d"
125 The device has reached an invalid state.
135 .Pa http://www.qlc.com/
137 .Pa http://www.sun.com/
142 driver was written for
148 driver was then ported to
151 .An Scott Long Aq scottl@FreeBSD.org .
153 This manual page was written by
154 .An Tom Rhodes Aq trhodes@FreeBSD.org
155 instead of porting the original from
160 driver includes the sbus front-end but lacks the
163 Thus it can only support the
171 machines at this time.
173 This driver should eventually replace the
175 driver, but that requires porting the
177 front-end mentioned above.