SAS-1.1: Checking Rx frame DATA OFFSET

Sheffield, Robert L robert.l.sheffield at intel.com
Tue Feb 22 12:27:09 PST 2005


* From the T10 Reflector (t10 at t10.org), posted by:
* "Sheffield, Robert L" <robert.l.sheffield at intel.com>
*
This is a multi-part message in MIME format.

------_=_NextPart_001_01C5191C.E2B1B8E6
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Question, suppose someone were to run a test case that has an SSP
transmitter open two connections through a wide port to an SSP device =
on
the other end, and while transmitting data frames to the destination,
transmits adjacent data frames (consecutive DATA OFFSET) at the same
time on both connections (illegal for a transmitter). Would the =
receiver
be required to detect the error and report an error?  (i.e., "the =
ST_TTS
state machine discards the frame ... and the device server terminates
the command with CHECK CONDITION status with the sense key set to
ABORTED COMMAND and the additional sense code set to DATA OFFSET =
ERROR")

Regards,=20
Bob Sheffield=20
Intel Corporation=20


------_=_NextPart_001_01C5191C.E2B1B8E6
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">

 SAS-1.1: Checking Rx frame DATA OFFSET Question, suppose someone were to run = a test case that has an SSP transmitter open two connections through a = wide port to an SSP device on the other end, and while transmitting = data frames to the destination, transmits adjacent data frames = (consecutive DATA OFFSET) at the same time on both connections = (illegal for a transmitter). Would the receiver be = required to detect the error and report an error?  = (i.e., ;the ST_TTS state machine discards the frame ... and the = device server terminates the command with CHECK CONDITION status with = the sense key set to ABORTED COMMAND and the additional sense code set = to DATA OFFSET ERROR;) Regards, 
Bob Sheffield 
Intel Corporation 
------_=_NextPart_001_01C5191C.E2B1B8E6--





More information about the T10 mailing list