Lines Matching +full:bus +full:- +full:id
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
120 varying sizes of SRAM. Each card contains a Bus Interface Unit (BIU)
121 as appropriate for the host bus (SBus or PCI). The BIUs allow access
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'
129 core and auxiliary logic which either is used to interface to a SCSI bus
130 (or to external bus drivers that connect to a SCSI bus), or to connect
131 to a Fibre Channel bus.
149 HBA has 8 dual-ranked 16 bit mailbox registers, mostly for out-of-band
160 mailboxes may be things like notification of SCSI Bus resets, or that the
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
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
221 and bus specific outer modules (machine dependent).
234 The platform/bus specific modules (and definitions) depend on each
236 module's use. Generally a platform module set is split into a bus
237 dependent module (where configuration is begun from and bus specific
242 For ease of bus specific access issues, a centralized soft state
244 soft state structure contains a machine/bus dependent vector (mdvec)
293 Typically a bus specific module for a platform (e.g., one that wants
303 it's more useful have a bus specific wrapper module that calls isp_intr.
306 Part of the isp_reset call may cause callbacks out to the bus dependent
309 Channel HBA). The reason this is considered 'bus dependent' is that
310 only the bus dependent module may have the information that says how
319 NVRAM from the QLogic card), then this bus specicic module will call the
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
364 of the Request Queue entry can contain a non-zero handle identifier so
384 interrupts. When some external event causes the SCSI bus to be reset,
411 the bus dependent DMA mapping function). If this entry completes the
453 supported Automatic Request sense will work- there is no particular provision
454 for disabling it's usage on a per-command basis.
459 architecture for dealing with Fibre Channel as just a 'fat' SCSI bus
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
532 for each possible local loop id the QLogic firmware for a Port Database
550 loop but we wish to retain a 'constant' Target ID (see 5.9.4), this
551 is indexed directly via the Target ID for the command (XS_TGT(xs)).
553 If there is a valid entry for this Target ID, the command is started
554 (with the stored 'Loop ID'). If not the command is completed with
567 for arbitrated loop is that the physical bus address for a loop member
575 disk# Loop ID Target ID
582 The driver uses 'Loop ID' when it forms requests to send a comamnd to
584 ID'. As you can see here, there is perfect correspondence between disk,
585 Loop ID and Target ID.
591 disk# Loop ID Target ID
599 Clearly, you don't want disk3 and disk4's "Target ID" to change while you're
605 disk# Loop ID Target ID
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