Lines Matching +full:solid +full:- +full:state

13 serve as a solid basis for attempting to understand where the driver
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.
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
187 of Fibre Channel login state. The corollary to this sometimes is the
214 There are some additional basic assumptions that this driver makes- primarily
242 For ease of bus specific access issues, a centralized soft state
244 soft state structure contains a machine/bus dependent vector (mdvec)
283 This soft state structure also contains different parameter information
338 Channel loop state would preclude successful starting of the command).
347 also the place where any endian byte-swizzling will be done. At any
361 In order to keep track of commands that are in progress, the soft state
364 of the Request Queue entry can contain a non-zero handle identifier so
375 storage within the soft state structure. Skipping over a lot of details,
385 or when a Fibre Channel loop changes state (e.g., a LIP is observed),
453 supported Automatic Request sense will work- there is no particular provision
454 for disabling it's usage on a per-command basis.
463 5.9.1 Firmware State
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.
483 Clearly, no command should be attempted prior to FW_READY state is
489 5.9.2. Loop State Transitions- From Nil to Ready
491 Once the firmware has transitioned to a ready state, then the state of the
499 In order to manage this state an eight level staging of current "Loop"
500 (where "Loop" is taken to mean FC-AL or N- or F-port connections) states
514 state to LOOP_NIL. The first 'LIP Received' asynchronous event sets state
516 asynchronous event which will set the state to LOOP_PDB_RCVD. Each of
520 After the state of LOOP_PDB_RCVD is reached, the internal core function
527 QLogic firmware log into (at LOOP_SYNCING_PDB state level)).
529 After this has occurred, the state LOOP_FSCAN_DONE is set, and then the
531 be called which will then scan for any local (FC-AL) entries by asking
538 then perform the PLOGI/PRLI functions for fabric devices. The next state
548 state structure is a distillation of the existing population of both
558 do firmware and loop state management (as described above) at this
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