Lines Matching refs:Channel

7 for, and current theory of operation for the joint Fibre Channel/SCSI
16 The reader is expected to understand the basics of SCSI and Fibre Channel
49 looking into implementing Fibre Channel mass storage at NAS. At this time
79 SCSI and Fibre Channel SCSI prototocols on multiple OS platforms with
86 The intended support targets for Fibre Channel HBAs is the 2100, 2200
89 Fibre Channel support should include complete fabric and public loop
93 For both SCSI and Fibre Channel, simultaneous target/initiator mode support
131 to a Fibre Channel bus.
155 Channel chipsets.
170 4.3 Fibre Channel SCSI out of SCSI
174 of the things that you really need to do with Fibre Channel with respect
178 distinguish addressing a Fibre Channel disk from addressing a plain
187 of Fibre Channel login state. The corollary to this sometimes is the
189 Channel disk is not working well.
205 Fibre Channel) to a SCSI device. It's assumed that each SCSI command is
284 based upon whether this is a SCSI HBA or a Fibre Channel HBA (which is
308 queues (as well as a Fibre Channel scratch area if this is a Fibre
309 Channel HBA).  The reason this is considered 'bus dependent' is that
338 Channel loop state would preclude successful starting of the command).
385 or when a Fibre Channel loop changes state (e.g., a LIP is observed),
456 5.9 Fibre Channel Specifics
458 Fibre Channel presents an interesting challenge here. The QLogic firmware
459 architecture for dealing with Fibre Channel as just a 'fat' SCSI bus
465 Part of the initialization (isp_init) for Fibre Channel HBAs involves
540 to process commands to send to Fibre Channel devices.
542 5.9.3 Fibre Channel variants of Initiator Mode Code Flow
544 The code flow in isp_start for Fibre Channel devices is the same as it is
563 5.9.4 "Target" in Fibre Channel is a fixed virtual construct
632 					(Fibre Channel Specs)