dev/isp/DriverManual.txt

8 for, and current theory of operation for the joint Fibre Channel/SCSI
17 The reader is expected to understand the basics of SCSI and Fibre Channel
50 looking into implementing Fibre Channel mass storage at NAS. At this time
80 SCSI and Fibre Channel SCSI prototocols on multiple OS platforms with
87 The intended support targets for Fibre Channel HBAs is the 2100, 2200
90 Fibre Channel support should include complete fabric and public loop
94 For both SCSI and Fibre Channel, simultaneous target/initiator mode support
132 to a Fibre Channel bus.
156 Channel chipsets.
171 4.3 Fibre Channel SCSI out of SCSI
175 of the things that you really need to do with Fibre Channel with respect
179 distinguish addressing a Fibre Channel disk from addressing a plain
188 of Fibre Channel login state. The corollary to this sometimes is the
190 Channel disk is not working well.
206 Fibre Channel) to a SCSI device. It's assumed that each SCSI command is
285 based upon whether this is a SCSI HBA or a Fibre Channel HBA (which is
309 queues (as well as a Fibre Channel scratch area if this is a Fibre
310 Channel HBA).  The reason this is considered 'bus dependent' is that
339 Channel loop state would preclude successful starting of the command).
386 or when a Fibre Channel loop changes state (e.g., a LIP is observed),
457 5.9 Fibre Channel Specifics
459 Fibre Channel presents an interesting challenge here. The QLogic firmware
460 architecture for dealing with Fibre Channel as just a 'fat' SCSI bus
466 Part of the initialization (isp_init) for Fibre Channel HBAs involves
541 to process commands to send to Fibre Channel devices.
543 5.9.3 Fibre Channel variants of Initiator Mode Code Flow
545 The code flow in isp_start for Fibre Channel devices is the same as it is
564 5.9.4 "Target" in Fibre Channel is a fixed virtual construct
633 					(Fibre Channel Specs)