Lines Matching +full:layer +full:- +full:primary

54 PCI and SBus SCSI cards, and now also drove the QLogic 2100 FC-AL HBA.
56 After this, ports to non-NetBSD platforms became interesting as well.
65 mode support has been added, and 2300 support as well as an FC-IP stack
71 Normally you design via top-down methodologies and set an initial goal
76 as I perceive them to be now- not necessarily what they started as.
78 The primary design goal now is to have a driver that can run both the
90 as well as private loop and private loop, direct-attach topologies.
91 FC-IP support is also a goal.
96 Pure, raw, performance is not a primary goal of this design. This design,
103 Another primary aim, which almost need not be stated, is that the
119 The QLogic HBA cards all contain a tiny 16-bit RISC-like processor and
122 to a set of dual-ranked 16 bit incoming and outgoing mailbox registers
124 other portions of the card (e.g., Flash BIOS). The term 'dual-ranked'
149 HBA has 8 dual-ranked 16 bit mailbox registers, mostly for out-of-band
173 FC-AL as a 'fat' SCSI bus (a SCSI bus with more than 15 targets). All
175 to providing FC-4 services on top of a Class 3 connection are performed
186 Still- the HBA firmware does really nearly all of the tedious management
201 a SCSI HBA driver for any system is that of a 2 or 3 layer model where
203 SCSI tapes, and so on), possibly a middle services layer, and a bottom
204 layer that manages the transport of SCSI CDB's out a SCSI bus (or across
214 There are some additional basic assumptions that this driver makes- primarily
238 support functions reside) and relatively thin platform specific layer
347 also the place where any endian byte-swizzling will be done. At any
364 of the Request Queue entry can contain a non-zero handle identifier so
377 pointer to the completing command. This would then be the glue layer that
453 supported Automatic Request sense will work- there is no particular provision
454 for disabling it's usage on a per-command basis.
479 It starts with FW_CONFIG_WAIT, attempts to get an AL_PA (if on an FC-AL
480 loop instead of being connected as an N-port), waits to log into all
481 FC-AL loop entities and then hopefully transitions to FW_READY state.
489 5.9.2. Loop State Transitions- From Nil to Ready
500 (where "Loop" is taken to mean FC-AL or N- or F-port connections) states
531 be called which will then scan for any local (FC-AL) entries by asking
617 HBA - Host Bus Adapter
619 SCSI - Small Computer 
625 http://www.netbsd.org		-	NetBSD's Web Page
626 http://www.openbsd.org		-	OpenBSD's Web Page
627 https://www.freebsd.org		-	FreeBSD's Web Page
629 http://www.t10.org		-	ANSI SCSI Commitee's Web Page
631 http://www.t11.org		-	NCITS Device Interface Web Page