1 of 18
`
` CROSSROADS EXHIBIT 2308
`Oracle Corp., et al v. Crossroads Systems, Inc.
` IPR2014-01207 and IPR2014-1209
`
`CROSSROADS EXHIBIT 2308
`NetApp Inc. v. Crossroads Systems, Inc.
`IPR2015-00776
`
`

`

`fiesnviff'.
`‘ Vcrrazano Soflwan: Dcvelo-yncnt
`I96 7:08 PM
`
`
`
`
`
`1%.:sz
`-4: — —-1L,
`
`
`
`
`
`Verrazano Software Development
`
`Confidential Document
`
`1
`
`Infinity CommSlor, LLC
`
`ATTORNEYS'
`EYES ONLY
`
`CRDS 421958
`
`2 of 18
`
`CRDS-T 00285
`
`2 of 18
`
`

`

`4V"!-
`.ted:09/lO/96 7:08 PM
`
`
`
`
`
`
`i2fimabumito: ,2“ .ii ”'1‘!
`
`
`
`1. introduction
`
`This document gives an overview of the methods, processes, and requirements involved in the software
`development effort for the Verrazano Bridge. It is meant as an overview intended to provide the basic
`gurdelmes for development, and as such is subject to change as the implementation evolves.
`
`2. Overview
`
`2.1 Product Hardware Description
`The target hardware is an embedded system centered around the Intel i960RP processor. Incorporated on
`the i960 bus are program memory, flash memory, a serial UART. and a lObaseT Ethernet controller. The
`primary PCI bus from the i960RP will have an HP Tachyon Fibre Channel controller, using the Interphase
`TPI PCl interface, and 32th DRAM for data buffering. This DRAM will interface to the PCI bus via a
`custom interface designed in house. The secondary PCI bus will have the Symbios 53C875 PCl SCSI
`controller.
`
`
`Specific details of the hardware architecture and desi-p» can be foundto the Verrazano Requirements
`Document andin (hardwareflea-5'27 Ti: 'ir‘v“ . «f»
`51-3
`, 7]
`
`2.2 Prototype Description
`To accelerate software development and to allow for software development to be overlapped with hardware
`development, a PC based prototype platform will be used. Functionally, the PC will be used for the PCI
`bus and system memory. The host processor will not be used except for limited debugging purposes. The
`processor used will be the Intel Cyclone board with the i960!)( Squall module. This will have 2MB of
`DRAM for program memory. The PLX 9060 PCI bridge on the Cyclone will allow for "'
`‘acing the 960
`processor to the FC and SCSl devices over the PCI bus. The Fibre Channel interface w.
`he Interphase
`Tachyon based PCl adapter. The SCSI interface will be the Symbios SYM53C875 PCI ac..,~rer. Serial
`communication, flash memory. and other basic functionality is provided by the Cyclone board.
`This provides an architecturally similar platform using essentially identical core components for
`development. Porting to the Verrazano hardware platform will require changes limited to the PCI bridge,
`memory and device mapping, and serial and other peripheral interfaces The core driver and bridge code
`will remain unchanged.
`
`2.3 Design Philosophy
`0
`‘C' Code base
`
`0 Modular design
`-
`Pass-though, event driven architecture
`0
`Use Existing 05. Drivers. Protocol Stacks as possible
`Design for performance. future portability, maintainability
`
`Confidential Document
`
`2
`
`Infutity CommStor, LLC
`
`ATTORNEYS '
`EYES ONLY
`
`CRDS 40957
`
`-
`30f18
`
`CRDS-T 00286
`
`3 of 18
`
`

`

`Vertazano Software
`
`'Uted'09/l0/96 7:08 PM
`-
`Develoment
`’
`_
`v‘f—h
`was?
`r"? x
`t‘.=‘§«—'—_J.
`.' .
`.
`.-
`51-21: f .
`_‘ 1::131;
`"‘
`.,»_
`-‘=-,
`‘2
`-
`:-"_V
`
`3. Core Software Modules
`
`3. 1 Boot Code
`
`At system boot. code will, be required to initialize the hard» are, perform basic system testing. and load the
`runtime code. The expectation is that this will consist in large part of modules available from Intel
`(mon960) and the runtime OS (currently VxWorks). Portions of this code will be modified and extended to
`support hardware specific characteristics which are TBD.
`
`Requirements:
`0
`Initialize hardware
`
`-
`-
`-
`
`Run boot diagnostics
`Set Processor, PCI address mapping
`Initialize and start VxWorks, core software
`
`3.2 Diagnostics
`In addition to the power on self test code executed at boot time. further diagnostics will be required for
`manufacturing test. field diagnosis. and returned unit test. These tests should be more extensive than the
`POST, and should include tests for all major subsystems of the Verrazano board. Diagnostics should be
`accessible from the serial console. TELNET via Ethernet. and SNMP via Ethernet. Future extensions
`should include accessrbility via SCSI and Fibre Channel via FCJP.
`
`Requirements:
`-
`One base test suite is desired. covering:
`- Manufacturing Test
`a
`Field Test
`0
`Retum Unit Test
`Processor test
`
`Memory test
`PCl test
`
`‘
`Buffer memory test
`Tachyon test - internal l00pbaclt. electrical (GLM) wrap, external loopback
`Symbios test - internal loopback, external loopback
`Ethernet adapter test - internal loopbaclc external loopback
`
`3.3 Kernel
`
`Currently VxWorks from Wind River Systems is the targeted runtime 08. Future ports may be targeted for
`lx Works.
`
`Confidential Document
`
`3
`
`Infinity CommStor. LLC
`
`RTTORNEYS ’
`EYES ONLY
`
`CRDS 40955
`
`4of18
`
`CRDS-T 00287
`
`4 of 18
`
`

`

` . _ _ I . ' 10/96 7:08PM
`
`
`
`
`
`
`' Writ
`i W: 9-.
`.
`i
`3.
`'.
`i
`_
`.
`-
`\ new i“.
`
`,
`
`3.4 FC Driver
`
`The Fibre Channel driver will be based on the current ICS FC DDK. Modifications may be made to the
`initialization and FC—4 layers. The interfaces to this code will be defined in section 4.2 of this document.
`
`The FC driver provides the following functionality:
`0 Manage logins and logouts
`- Manage FC-4 exchanges
`- Activation of new exchange for each FCP command
`0 Manage FCP comma.nd(exchange) through all phases for that command
`0
`Provide means for FC—4 to do process login for an FCP attached device
`0
`Receive all FC-4 data commands
`. Manage exchanges
`- Activation and Deactivation of exchanges
`.
`assigmnent of XJD
`- Manage sequences
`.
`Initiation and termination of sequences
`0
`SEQJD assignment
`a Managing sequence initiative
`0 Manage EE credit
`-
`All FC-2 functionality
`
`3.5 SCSI Driver
`
`The SCSI driver will consist of two parts. The SCSI state machines will be implemented in the Symbios
`SCRIPTS language, which runs on the 875 internal processor. This code will interface with a higher layer
`interface running on the i960 processor. The interfaces to this code will be defined in section 4.3 of this
`document.
`
`The SCSI dnver provides the following functionality:
`0
`Provtde SCSI initiator support with a single SCSI ID
`0 Manage Commands and Messages to targets
`- Manage DMA to/from buffer memory
`Provide SCSI target support
`-
`Respond to multiple target IDs
`0
`Process Commands and Messages
`0 Manage DMA to/from buffer memory
`0 Manage all SCSI bus phases and transitions
`0 Manage Synchronous, wide. and fast negotiation
`
`0
`
`Confidential Document
`
`4
`
`Infinity CommStor. LLC
`
`ATTORNEYS '
`E YES ONLY
`
`CRDS 409
`
`53
`
`5of18
`
`CRDS-T 00288
`
`5 of 18
`
`

`

`
`
`Verrazano Software Develmment
`..p?l"
`.._ www-
`
`
`
`_...- - ‘1}—
`3"“ ti.
`.
`‘
`
`taxman—7“"
`
`
`
`3me? R)51,505 = or;
`-
`g
`' “ 41—min e
`’é.
`
`
`3.6 Bridge Code
`The Bridge code provides for the conversion and transport of data and commands between PCP and SCSI
`devices. This code should be event driven. of a pass-though design and use a store and forward method of
`data transport. Major functionality is defined below. Additional operational characteristics are outlined in
`the Venazano Requirements Document.
`
`Requirements:
`.
`Process incoming CDBs from FC4 and SCSI layers
`Manage command and data transfer between FCP and SCSI drivers
`Manage data buffers and internal command structures
`Manage FC4 interface
`Translate protocols from FCP to SCSI~2
`Translate address information between FC and SCSI devices
`
`3.6.1 Architectural Overview
`
`Figure 3.ldiagrams the core processes and program flow within the bridge. Three areas of functionality are
`dragrammed. for PC? and SCSI processes. These are:
`
`0
`0
`0
`
`Event handling '
`Bndge processing
`Request handling
`
`Event handlers process incoming requests from the FCP or SCSI interfaces and route these requests to the
`appropriate bn'dge module. The bridge modules handle the creation and management of buffer queues,
`address translation, and protocol translation. The request handlers initiate transfers on the PCP or SCSI
`interface as required by the other modules. Further description of these modules and their «moments is
`provided in the following sections.
`
`Confidential Document
`
`5
`
`Infinity CommStor. LLC
`
`ATTORNEYS '
`EYES ONLY
`
`CRDS 40951
`
`-~
`
`60f18
`
`CRDS-T 00289
`
`6 of 18
`
`

`

`
`
`rcP RECEIVE EVENT
`
`SCSI ascewE Event
`
`
`I E
`
`
`
`SCSI sums.
`FCP_STATUS.
`roam” h
`Data In
`
`
`FCP SEND REQUEST
`SCSI SEND REQUEST
`
`
`
`
`
`
`:—-——_L—._..
`
`I
`rcpw '
`
`Figure 3.1- Core processes and flow
`
`Confidential Document
`
`6
`
`Infinity CommStor. LLC
`
`ATTORNEYS '
`EYES DNLY
`
`CRDS 40949
`
`7of18
`
`CRDS-T 00290
`
`7 of 18
`
`

`

`“0/96 7:08 PM
` Verrazano SoftwareDevelo ment
`V
`‘ L-
`—.
`~
`I
`
`
`Figure 3.1 Illustrates control flow for management commands. Management commands are those ,
`commands that are processed by the bridge directly. and not passed through to the alternate interface. This
`capability is to be provided to support diagnostics, configuration. and imband management through the PCP
`and SCSI interfaces. Similar interfaces to the Management Command Service will be provided for out of
`band management. via the Ethernet and serial interfaces.
`
`[—5071
`_l__
`
`I i
`
`I i
`
`re» macaw: EVENT R
`I WW
`Hound
`
`scsa neczrve even
`
`
`
`l
`'
`
`.
`rep
`:
`eon-mm
`:
`Bridge
`=_____J
`
`5"“
`
`lWComm
`
`Rom
`
`l
`
`I
`
`1
`
`scs:
`W
`Map
`
`SCSI SEND REQUEST
`
`_....__.____._fi
`
`FCP SEND REGUESY
`
`
`
`
`lx l i
`
`'
`
`Figure 3.2 - Management Commands Control Flow
`
`Confidential Document
`
`7
`
`Infinity CommStor. LLC
`
`ATTORNEYS’
`EYES ONLY
`
`80f18
`
`BROS W947
`
`CRDS-T 00291
`
`8 of 18
`
`

`

`Von-3390 Software Develoment
`“"1???" ‘.
`
`'
`
`~——’-
`
`,g':. 3.;
`
`ate-in,
`
`ted 09/10/96 7:08 PM
`
`
`27'3“ “9;:-
`‘
`‘
`
`'
`"
`
`'
`
`‘
`
`Certain other cases exist to the nonnal flow of execution. Chief among these is the case where an
`FCP__CMND Write is received. In order to reduce inactive time on the SCSI bus. data is pro-fetched. This
`is exhibited in Figure 3.3. The bridge module snoops the command, andfifnecessaxy, allocates buffers and
`requests data from the PCP device before generating the SCSI command. Subsequent data transfers and
`status phases for this command proceed normally.
`
`0l
`
`btwnrv
`'CP_C\Q WM
`
`l
`!
`l w
`i w m
`l
`5
`I
`t
`an AM
`I
`l
`SCSI
`Pool-ch Dela
`Duo in lull-v
`(‘C'flwfi
`
`FC’ SEW WS'
`
`
`
`Figure 3.3 - FCP Write with pre‘fetclt
`
`Confidential Document
`
`8
`
`Infinity CommStor, LLC
`
`ATTORNEYS '
`EYES ONLY
`
`CRDS 190945
`
`90f18
`
`CRDS-T 00292
`
`9 of 18
`
`

`

`
`
`
`
`3.6.2 Buffer Management
`
`System memory is available both in the 960 local memory space or in PCI memory space. Hardware
`performance dictates that highest performance is available when a device requiring memory ‘reads from
`nearest RAM‘. Accordingly, DMA read lists for the Tachyon will be located in PCl buffer memory, and
`Tachyon wn'te lists in program memory. Interrupt structures and Bridge command structures will reside in
`program memory. Although these lists will be read by the Tachyon and Symbios part, it is likely that more
`read operations will be performed by the 960.0n the CD8 elements. Data buffering will be in the PCI
`buffer memory.
`
`Pn‘mary Data elements:
`
`Data buffers
`
`- Allocated sequentially
`0 2K each
`
`- ln 2MB PCI Buffer memory
`0 Memory is shared with Tachyon DMA lists, so less than 1024 buffers available
`
`Bridge command elements
`- Allocated in program memory
`0 Number allocated limits the number of outstanding [0 requests
`0 512 Allocated
`
`0 Max 480 targets (Wide SCSI targets times LUNS)
`- Average queue depth per target very near 1
`- About 96 bytes per, total allocation 49,152 Bytes
`
`Confidential Document
`
`9
`
`Infinity CommStor, LLC
`
`ATTORNEYS '
`EYES ONLY
`
`CRDS 40943
`
`100f18
`
`CRDS-‘I' 00293
`
`10 of 18
`
`

`

`Ye
`
`3.6.3 Protocol Translation
`
`Protocol translation is performed by the core bridge code. This involves the translation of a CD8
`(Command Descriptor Block) being convened between SCSX and FCP. Generally, the structure of the CD13
`15 the same in both cases. Changes to the CD8 may have to be made to the LUN field when LUN
`addressing is required. The structure of the FCP_CMND and CD8 is shown in Table 3.land Table 3.2.
`
`Table 3.1 - FCP__CNMD Information Unit
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Table 3.2 - SCSI Command Descriptor Block
`
`
`
`Confidential Document
`
`l0
`
`Infinity CommStor, LLC
`
`ATTORNEYS '
`
`EYES ONLY
`
`11of18
`
`CRDS 40941
`
`CRDS—T 00294
`
`11 of 18
`
`

`

`’
`‘
`-
`PM
`
`
`._.,._,.‘.
`,.
`.
`‘
`.
`:.
`.»
`-=:1(m-
`
`3.6.4 Address Translation
`
`By default, the bridge will address in 'Direct Addressing Mode' with the mapping shown inTable 3.3 and
`Table 3.4. Configuration will allow for FC AI._PA to be changed, however, the LUN value will map
`directly to the SCSI LUN. Configuration will also allow for specific SCSI target addresses to be disabled.
`This reduces the range of available addresses, but allows for attaching other devices to the SCSI bus.
`
`Table 3.3- Default Direct Address Map, FCP->SCSI (Narrow)
`
`errazano ALJ’A
`FC Address
`
`
`
`
`__
`
`SCSI Address
`:
`.
`SCSI Tar et 0 LUN 0
`
`
`
`
`
`
`
`
`
`
`—_
`
`
`_ SCSI Tar er 7 Unavailable (Brid-e lnitiatorID
`
`
`
`
`Confidential Document
`
`1|
`
`Infinity CommStor, LLC
`
`QTTDRNEYS'
`EYES ONLY
`
`CRDS 48939
`
`12 of 18
`
`CRDS-‘I' 00295
`
`12 of 18
`
`

`

`-2‘43th
`
`lo ment
`Verrazano Software Deve
`
`
`-.,.:,.
`tun,
`
` I:
`
` .— if???” I" (.
`sienna {fift-
`-'
`‘ewaqac . -
`=
`_
`-
`
`
`
`Optionally, Ordered Addressing niode can be enabled. This mode will perform discovery on eéch side of
`the bridge. and use the resulting data to build an address map between the busses. This results in an ordered
`list of addresses with no apparent gaps between devices. Although this provides automatic configuration,
`no allowance is given for hot plugging devices or any dynamic change of addressing. Example tables are
`shown in Table 3.5 and Table 3.6.
`
`Table 3.5 - Ordered Address Map, FC->SCSI
`
`FC Address
`
`errazano ALJ’A
`
`
`
`
`
`
`
`SCSI Address
`1“ discovered SCSI BUS=TARGETiUN
`2 ' discovered SCSI BUS=TARGETILUN
`3" discovered SCSI BUSITARGETILUN
`
`discovered BUS:SCSI TARGETILUN
`
`
`
`
`
`
`
`
`
`
`
`
`
`Table 3.6 - Ordered Address Map. SCSI->FC
`SCSI Address
`
`
`
`
`
`
`
`I" discovered FC AL_PA, LUN 0
`Taret 0, LUN 0
`2 ' discovered FC AL_PA, LUN 0
`Taret l. LUN 0
`3 ' discovered EC AL_PA, LUN O
`Tar_et 2, LUN 0
`——
`Tar et N. LUN N
`' discovered FC AL_PA. LUN O
`
`A maxrmum of 480 translation elements are required for each direction. This is the maximum number of
`logical units that can be addressed. This is determined by using the maximum number of usable SCSI
`targets times the number ofLUNS. Wide SCSI allows 16 SCSI IDs, one of which must be used as the
`bridge initiator ID. Each target can address 32 LU‘Ns.
`
`Each FC->SCSI entry is 7 words. Each SCSI->FC element is 8 words. Thus, the total required memory for
`address tables is 7200 bytes. These tables will reside in local 960 memory.
`
`3. 7 Ethernet Driver
`
`WindRiver currently has plans to supply the Epilogue driver for the AMD LANCE Ethernet chip.
`It is expected that this can be modified to support the PC—NET chip in LANCE compatibility mode. Further
`investigation is ongoing.
`
`Confidential Document
`
`12
`
`Infinity CornrnStor, LLC
`
`ATTORNEYS '
`EYES ONLY
`
`CRDS 49937
`
`13 of18
`
`CRDS-T 00296
`
`13 of 18
`
`

`

` 'fitfug'fifl‘fii‘rj'ffifi
`
`..
`
`.,
`
`,.
`
`" reg: ‘
`
`3.8 Configuration
`Verrazano will require configuration for various reasons. The prototype device will anew
`configuration though the serial interface. Ethernet via TELNET will be implemented in the first release.
`Subsequent releases will support SNMP and potentially HTTP, FC and SCSI interfaces.
`
`3.8.1 Configurable Optlons
`A number of configurable parameters are required. They are listed below, and grouped into major
`categories.
`
`3.8.1. 1 FCP Options
`0
`Use/Set Hard Address (AL_PA)
`0
`Participate if Hard Address unavailable
`0
`Override World Wide Address (IEEE)
`
`3.8.1.2 SCSI Options
`0
`Set ID for SCSI Initiator
`
`-
`-
`I
`0
`-
`
`Use multiple SCSI response IDs
`Set IDs for SCSI Target response
`Set general SCSI parameters (fast/disconnect/sync negotiation/etc.)
`Set SCSI Narrowaide
`Use CDB LUN field
`
`3.8. 1.3 Bridge Option:
`0
`Use Direct Address Method
`
`0
`
`c
`
`0
`-
`0
`
`Specify/Enter Address Map
`-
`. Use default Address Map
`Use Ordered Address Method
`
`Perform FCI’ Discovery
`.
`Perform SCSI Discovery
`0
`Use Target Addressing (LUN 0 Only)
`-
`FCP Target Addressing
`-
`SCSI Target Addressing
`Set Management Command method (LUN 0, LUN FF. Group Code, Disable)
`Select FCP LUN format
`Set Buffer Memory parameters
`0 Data Buffer Size
`0
`Set Tachyon list parameters
`0
`Set Symbios list parameters
`
`3.8.1 .4 Miscellaneous
`0 Override Ethernet IEEE address
`0
`Link FC/Ethemet IEEE addresses
`
`0
`0
`
`Set default serial parameters
`Disable diagnostics
`
`Confidential Document
`
`13
`
`Infinity CommStor, LLC
`
`RTTD RNEYS '
`EYES ONLY
`
`14 of18
`
`CRDS 48935
`
`CRDS-T 00297
`
`14 of 18
`
`

`

`
`
`3.8.2 Serial Console
`
`The Serial Console will provide for:
`- Menu based configuration
`. Statistics reports
`- EEPROM Download
`
`0 Debugging VxWorks Interface
`
`3.8.3 Telnet
`
`Access to the same options and control given through the serial interface will be provided through
`Ethernet based TELNET. (future FC-IP)
`
`3.8.4 FTP
`
`Firmware download will be provided through Ethernet FTP.
`
`3.8.5 SNMP
`
`Ml'B based configuration and statistics via SNMP (Ethernet, future FC-IP)
`
`3.8.6 HTTP
`
`Configuration, management available via HTTP in future release.
`
`3.9 Management
`
`3.9.1 SNMP
`MIB-ll definition TBD
`
`3.9.2 HTTP
`
`TBD. in future release
`
`Confidential Document
`
`14
`
`Infinity CommStor, LLC
`
`ATTORNEY-9'
`EYES ONLY
`
`cans “3933
`
`15 of 18
`
`CRDS-T 00298
`
`15 of 18
`
`

`

`Venazano Software Develoiment U .7. ted:09/10/96 7:08 PM
`
`
`
`4. Software Interfaces
`
`4.1 Common Structures
`
`There is a general one to one correlation between SCSI and PCP commands in the bridge. Cases
`where this rs not so include management commands as well as commands with invalid addressing and
`potentially other errors. Thus, in order to simplify allocation and increase performance, it is desirable to
`combine PCP and SCSI command structures into one element.
`
`Bridge Command Structure: (24 words)
`QUEUE
`qlink;
`FCP_CMND
`FCP_Cornmand
`SCSI_CDB
`SCSI_Command
`WORD
`FCP__flags
`WORD
`SCSLflags
`WORD
`FCP~burst_length
`WORD
`FCP_relative_otfset
`WORD
`FCP_total_data
`WORD
`SCSI_total__data
`WORD
`correlation_id
`FQXID
`quid
`QUEUE
`data_q_ptr
`WORD
`data_length
`
`Queue pointer info
`FCP Command Information Unit
`SCSI Command descriptor Block
`Flags for FCP state information
`Flags to indicate phase information
`Burst size for PC? transfers
`FCP data relative offset
`Data size expected for FCP
`Data size expected for SCSI
`Correlation ID for FC4
`DJD, S_ID. OX_ID, RX_ID
`Pointer to data buffer queue entries
`number of allocated data blocks
`
`FCP->SCSI Address Translation Structure: (7 words)
`FCP_LUN
`FCP_LUN_VaIue;
`SCSLADDR
`SCSI__Value;
`
`LUN contents
`SCSI BUS:TARGET:LUN
`
`SCSI->FCP Address Translation Structure: (8 words)
`FCP_AL_PA
`NJORTJD
`FCP_LUN
`FCP_LUN_Value
`SCSI_ADDR
`SCSI_Value
`
`FC Address
`LUN Value
`SCSI BUS:TARGET:LUN
`
`4 words
`8 words
`4 words
`l word
`l word
`1 word
`1 word
`l word
`l word
`l word
`4 words
`4 words
`1 word
`
`6 words
`l word
`
`l word
`6 words
`l word
`
`Confidential Document
`
`15
`
`Infinity CommStor, LLC
`
`ATTORNEYS '
`EYES ONLY
`
`CRDS 40931
`
`16 of 18
`
`CRDS-T 00299
`
`16 of 18
`
`

`

`ted:09/0/96 7:08 Phi
`Vertazano'Software Development __
`.
`_
`~
`.
`.
`
`4.2 FOP-SBrIdge Interface
`The FC interface is essentially that of the FC DDK, with some extensions. Primary elements are
`shown below.
`
`fe4_send__req()
`fc4_process_login()
`fc4_process__logout0
`
`Send an FC-4 request.
`Do process login for FC»4's that require process login.
`Do process log out for FC~4's that require process log out.
`
`fc4__register()
`
`fc4_remove()
`
`fc4__tx_callback
`fc4_rx_callback
`fc4__t‘reeBut‘s
`fc4_REQ snucnrre {
`
`Register an FC-4 type to the FC-Z layer. Registers the callback routines for the
`given FC-4. Enables this FC-4 to start receiving unsolicited data for this FC-4
`type.
`Remove an FC-4 type that was previously registered to the FC-Z layer With the
`fc4_register0 function. Removes the information registered with fe4_register()
`and disables the ability to receive unsolicited data for this FC-4 type.
`Provides status of fc4 send request.
`Provide status and transfer PCP command received to bridge
`Free receive buffer elements
`
`fc4_type
`profile
`s_id
`d_id
`totaLsizc
`fcp_cmd
`fcp_status
`data_info
`fc4_context
`
`xtensions:
`FCP_EventHandler
`
`ISR, DMA service routine
`
`3 E
`
`4.3 SCSI->Bridge Interface
`The interface between the SCSI driver module and Bridge code will be generally consistent with that
`specrfied by the SCSI-3 SIP specification (ANSI drafi X3TlO Project 856D R10).
`
`All functions will be passed a pointer to the current Bridge Command Structure.
`
`Primary functions are as follows:
`SCSLEventHandler
`SCSI_Command__ln
`SCSl_Command_Out
`SCSI_Data_ln
`SCSl_Data_0ut
`SCSLStatuan
`SCSl_Status_Out
`SCSl_Messagc_ln
`SCSl_Message_Out
`
`ISR, DMA service
`Initiate SCSI command to target device
`Process target command from initiator
`Process DMA Data In to buffer memory
`Process DMA Data Out from buffer memory
`Process SCSI Status message (Initiator Role)
`Process SCSI Status message (Target Role)
`Process other message (Initiator Role)
`Process other message (Target Role)
`
`Confidential Document
`
`16
`
`infinity CommStor, LLC
`
`RTTD RNEYS '
`EYES ONLY
`
`17 of18
`
`CRDS 40929
`
`CRDS—T 00300
`
`17 of 18
`
`

`

`
`Verrazano Software Develo
`i
`W)rj"?;'___
`
`
`
`
`
`
`4.4 Protocol Stacks
`The mitial release of Ven-azano will use off the shelf protocol stacks. Some modification may be
`necessary depending on code availability. Desired elements are:
`
`TCP/IP
`SNMP
`TELNET
`FTP
`
`HTTP (future)
`
`0OOOO
`
`Vendors provrding stacks are currently being researched and include:
`-
`US Software
`EBS lnc.
`Pacific SoftWorks
`Epilogue
`XLNT
`
`Accelerated Technology
`
`This code may have large up-front and royalty requiremens. A large body of public domain software is also
`available. Switching to Infinity generated code is a possible future cost reduction.
`
`Confidential Document
`
`l7
`
`Infinity CommStor, LLC
`
`ATTORNEYS '
`
`EYES ONLY
`
`180f18
`
`CRDS 49926
`
`CRDS-‘I' 00301
`
`18 of 18
`
`