Lines Matching +full:platform +full:- +full:specific
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.
62 Operating System Platform differences segregated and to a minimum.
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.
80 as little OS platform support code as possible.
90 as well as private loop and private loop, direct-attach topologies.
91 FC-IP support is also a goal.
99 driver that is specifically designed for a single platform and a single
104 implementation of platform differences must not clutter up the common
105 code with platform specific defines. Instead, some reasonable layering
106 semantics are defined such that platform specifics can be kept in the
107 platform specific code.
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
161 Fabric Name server has sent a change notification, or even that a specific
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
183 binding of entities it's queried from the name server to specific 'target'
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
220 The driver is split into a core (machine independent) module and platform
221 and bus specific outer modules (machine dependent).
234 The platform/bus specific modules (and definitions) depend on each
235 platform, and they provide both definitions and functions for the core
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
238 support functions reside) and relatively thin platform specific layer
239 which serves as the interconnect with the rest of this platform's SCSI
242 For ease of bus specific access issues, a centralized soft state
266 XS_T Platform SCSI transaction type (i.e., command for HBA)
276 MEMZERO(dst, src) platform zeroing function
293 Typically a bus specific module for a platform (e.g., one that wants
294 to configure a PCI card) is entered via that platform's configuration
297 dependent vector as well as any other platform specific information that
303 it's more useful have a bus specific wrapper module that calls isp_intr.
313 of interrupts should this platform be able to finish configuration in
320 platform dependent module that takes the appropriate steps to 'register'
321 this HBA with this platform's SCSI subsystem. Examining either the
328 itself with this platform's SCSI subsystem. One assumed action for this
329 is the registry of a function that the SCSI subsystem for this platform
332 The platform specific module function that receives this will do whatever
335 a complete marshalling/demarshalling of this platform's SCSI command
347 also the place where any endian byte-swizzling will be done. At any
356 left to the machine dependent platform function which called isp_start. In
364 of the Request Queue entry can contain a non-zero handle identifier so
378 informs the SCSI subsystem for this platform that a command is complete.
388 Each platform module has to provide an isp_async entry point that will
418 Because almost no platform provides basic SCSI Subsystem target mode
432 The platform dependent code may also therefore assume that if it is
435 to the platform dependent code to worry about avoiding any lock nesting
444 masking could be dropped. It's now up to each platform to figure out how
451 The driver core or platform dependent architecture issues that are specific
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
547 Maintained within the fibre channel specific portion of the driver soft
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