Lines Matching +full:port +full:- +full:mapping +full:- +full:mode
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.
90 as well as private loop and private loop, direct-attach topologies.
91 FC-IP support is also a goal.
93 For both SCSI and Fibre Channel, simultaneous target/initiator mode support
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'
146 of asynchronous events (e.g., incoming commands in target mode).
149 HBA has 8 dual-ranked 16 bit mailbox registers, mostly for out-of-band
151 of 64 byte fixed size Queue Entries to receive normal initiator mode
152 I/O commands (or continue target mode requests). The request queue may
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
214 There are some additional basic assumptions that this driver makes- primarily
300 Configuration at this point usually involves mapping in board registers
305 After mapping and interrupt registry is done, isp_reset is called.
307 module to perform allocation and/or mapping of Request and Response
311 one could perform I/O mapping and dependent (e.g., on a Solaris system)
314 interrupt driven mode.
325 5.4 Initiator Mode Command Code Flow
343 function to make sure any DMA mapping for this command is done.
345 Now, DMA mapping here is possibly a misnomer, as more than just
346 DMA mapping can be done in this bus dependent function. This is
347 also the place where any endian byte-swizzling will be done. At any
350 entries than there are currently available. If the mapping and other
364 of the Request Queue entry can contain a non-zero handle identifier so
394 5.6 Target Mode Code Flow
398 The QLogic cards, when operating in target mode, follow a code flow that is
399 essentially the inverse of that for intiator mode describe above. In this
403 This is passed to possibly external target mode handler. This driver
405 things open enough that a completely different target mode handler
408 The external target mode handler then turns around forms up a response
410 Queue and handled very much like an initiator mode command (i.e., calling
411 the bus dependent DMA mapping function). If this entry completes the
415 target mode handler will respond to that, and so on until the command
418 Because almost no platform provides basic SCSI Subsystem target mode
453 supported Automatic Request sense will work- there is no particular provision
454 for disabling it's usage on a per-command basis.
467 and Port WWNs as well as topology preferences. After this occurs,
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
515 to LOOP_LIP_RCVD. This should be followed by a "Port Database Changed"
531 be called which will then scan for any local (FC-AL) entries by asking
532 for each possible local loop id the QLogic firmware for a Port Database
542 5.9.3 Fibre Channel variants of Initiator Mode Code Flow
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