SAS - primitive after SOF

Elliott, Robert (Server Storage) Elliott at hp.com
Mon Jun 10 18:08:51 PDT 2002


* From the T10 Reflector (t10 at t10.org), posted by:
* "Elliott, Robert (Server Storage)" <Elliott at hp.com>
*

> -----Original Message-----
> From: Sriram Srinivasan [mailto:srirams at lsil.com] 
> Sent: Monday, June 10, 2002 4:36 PM
> Subject: SAS - primitive after SOF
>
> In sas-r00a.pdf clause 7.13.6.7.1 SSP_T1:Transmit state 
> description states:
>   
> "On an indication that a SOF/frame/EOF is to be transmitted 
> the transmit state shall transmit an SOF in the dword before 
> the first dword of the frame and an EOF in first dword after 
> the last dword of the frame. 
> If during the transmission of a frame an indication that a 
> primitive is to be transmitted occurs the transmit state may 
> transmit the indicated primitive by inserting 
> the primitive between the frames  dwords."
>   
> If the receiving device gets a primitive immediately after 
> an SOF or immediately before an EOF, is it supposed to 
> indicate a protocol error to the port layer?  

No error - primitives are allowed inside SSP frames.  This is
mainly for ALIGN, RRDY, ACK, and NAK.

The SSP_RF states are the ones that receive frames (there are
some typos where SSP_FR is used, but they're the same).

> Or should the primitive(s) just be processed as usual and 
> the frame accepted?

Yes.

>  Sriram Srinivasan                       Sriram.Srinivasan at lsil.com
>  ASIC Design Engineer, LSI Logic,
>  2001 Danfield Ct., 				Phone: 970-206-5847
>  Fort Collins, CO 80525				FAX  : 
> 970-206-5244

--
Rob Elliott, elliott at hp.com
Industry Standard Server Storage Advanced Technology
Hewlett-Packard

*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org




More information about the T10 mailing list