SAS - primitive after SOF

Goh, Han (Server Storage) Han.Goh at hp.com
Tue Jun 11 10:51:50 PDT 2002


* From the T10 Reflector (t10 at t10.org), posted by:
* "Goh, Han (Server Storage)" <Han.Goh at hp.com>
*
A primitive has a K28.5 control character which does not map
to any valid data dword. The last non-primitive dword 
received before EOF is the CRC.
 

-----------
Han Goh
Server Storage ASIC, ISS
(281) 518-5031   han.goh at hp.com



-----Original Message-----
From: Sriram Srinivasan [mailto:srirams at lsil.com]
Sent: Tuesday, June 11, 2002 10:48 AM
To: t10 at t10.org
Subject: RE: SAS - primitive after SOF


* From the T10 Reflector (t10 at t10.org), posted by:
* Sriram Srinivasan <srirams at lsil.com>
*
Rob:

  I understand that primitives are allowed in an SSP frame.  My question was 
specifically aimed at those immediately before or after an EOF or SOF 
respectively.  If it is NOT an error why mandate: [SOF DWORD .... DWORD EOF] 
?!? i.e. why disallow primitives before EOF or after SOF during 
transmission?
  
  So if I get [SOF DWORD1 ... DWORDN RRDY EOF]  how do I know that DWORDN 
was CRC for the frame?!?  What if I get 5 RRDYs between the CRC and the 
EOF?!?  How do I recognize the CRC?  I guess that is why the primitives are 
disallowed in those spots.  So if they are not allowed and I DO get a 
primitive in those positions what do I do?

  Should clause 7.13.6.3.1 "SSP_RF1:Frame_rcv state description" also 
describe this case (just as it describes receiving two SOF primitives 
without an intervening EOF primitive) as a protocol violation condition?
  
  thank you,
  \Sriram\
                                          -Khalil Gibran

 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
----------------------------------------------------------------------

*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org
*
* 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