SATA CONT discrepancy in SATA / SAS standards!!

Mark Overby MOverby at nvidia.com
Fri Apr 29 09:20:03 PDT 2005


* From the T10 Reflector (t10 at t10.org), posted by:
* "Mark Overby" <MOverby at nvidia.com>
*
This is a multi-part message in MIME format.

------_=_NextPart_001_01C54CD7.CE644364
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I don't see a conflict here.
=20
Under the SATA specification, once you correctly detect a CONT you
ignore anything until you receive another valid primitive (excluding
align). Under the SAS standard, you can send more than one CONT. If a
device following the SATA specification were to receive a CONT (a valid
primitive), then it would cycle back and start ignoring anything until
another valid primitive is received.
=20
Unexpected, maybe. Illegal, doubtful. (IMHO)
=20
We went around on this during ATA-ATAPI-7 as well.

  _____ =20

From: owner-t10 at t10.org on behalf of Shah, Amit M
Sent: Thu 4/28/2005 2:09 PM
To: Serial ATA II; t10 at t10.org
Cc: Beckett, Richard C; Carmichael, Rick; Devidas, Devicharan; Teo,
Daryl; Karthikeyan, Kishore K; Mak, Henry; Mak, Henry; Sheffield, =
Robert
L
Subject: SATA CONT discrepancy in SATA / SAS standards!!



Hi,

=20

I am a bit confused about the way SATA_CONT behavior is mentioned in
SATA as well as SAS specs. Both the behaviors sound conflicting to me
and I would really appreciate if somebody can throw some light on
clarifying the standards.

=20

The SATA specification (section 7.4.5 as attached below) mentions that
SATA CONT should expected only once during a CONT sequence. So if the
receiver detects=20

XRDY    XRDY    CONT    CONT     RD    RD    RD    SOF

then it would be a unexpected / invalid sequence as there were two
CONT's back to back.

=20

Now the SAS Specifications (section 7.2.4.4 as attached below) mentions
that there could be one or more SATA_CONTs in a CONT sequence. So if =
the
receiver detects=20

XRDY    XRDY    CONT    CONT     RD    RD    RD    SOF

then it would be a valid sequence as there were two CONT's back to =
back.

=20

I am wondering if two or more CONT's back to back are valid or not.

=20

Amit Shah

Intel Corporation

=20

>>>>>>>>>>>=20

The SATA specs Revision 1.0 29-August-2001

=20

7.4.5 Continue primitive

In order to accommodate EMI reductions, scrambling of data is
incorporated in Serial ATA as

described in Section 7.5. The scrambling of data is simple, with a
linear feedback shift register

(LFSR) used in generating the scrambling pattern being reset at each =
SOF
primitive, or rolling over

every 2048 Dwords. However, the scrambling of primitives is not as
effective or simple because of the

small number of control characters available. In order to accommodate
EMI reductions, repeated

primitives are eliminated through the use of the CONT primitive.

Any repetitive primitive may be implied to continue repeating through
the use of the CONT primitive.

The recipient of the CONT primitive shall ignore all data received =
after
the CONT primitive until the

reception of any primitive, excluding ALIGN. After transmitting the =
CONT
character, the transmitter

may send any sequence of data characters to the recipient provided that
no primitives are included.

The reception of a CONT primitive shall cause the last valid primitive
to be implied as repeated until

the reception of the next valid primitive.

=20

=20

The SAS specs Revision 9   18 March 2005

=20

7.2.4.4 Continued primitive sequence

Primitives that form continued primitive sequences (e.g., SATA_HOLD)
shall be transmitted two times, then be

followed by SATA_CONT, if needed, then be followed by vendor-specific
scrambled data dwords, if needed.

ALIGNs and NOTIFYs may be sent inside continued primitive sequences as
described in 7.2.4.1. After the

SATA_CONT, during the vendor-specific scrambled data dwords:

a) a SATA_CONT continues the continued primitive sequence; and

b) any other STP primitive, including the primitive that is being
continued, ends the continued primitive

sequence.

Receivers shall detect a continued primitive sequence after at least =
one
primitive is received. The primitive

may be followed by one or more of the same primitive. The primitive may
be followed by one or more

SATA_CONTs, each of which may be followed by vendor-specific data
dwords. Receivers shall ignore invalid

dwords before, during, or after the SATA_CONT(s). Receivers do not =
count
the number of times the continued

primitive, the SATA_CONTs, or the vendor-specific data dwords are
received (i.e., receivers are simply in the

state of receiving the primitive).

Expanders forwarding dwords may or may not detect an incoming sequence
of the same primitive and convert

it into a continued primitive sequence.

=20

Table 64 in the SAS Specs also mentions that the SATA_CONT has a
primitive sequence type "Single".

=20

=20


------_=_NextPart_001_01C54CD7.CE644364
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


<html                                                                   =
                                                                        =
                                                      >

<head>

<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">



<style>
<!--
                       =20
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{
	font-family:Arial;
	color:windowtext;}

div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
<DIV id=3DidOWAReplyText68743 dir=3Dltr>
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>I don't see =
a conflict=20
here.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Under the SATA =
specification, once you=20
correctly detect a CONT you ignore anything until you receive another =
valid=20
primitive (excluding align). Under the SAS standard, you can send more =
than one=20
CONT. If a device following the SATA specification were to receive a =
CONT (a=20
valid primitive), then it would cycle back and start ignoring anything =
until=20
another valid primitive is received.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Unexpected, maybe. Illegal, =
doubtful.=20
(IMHO)</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>We went around on this =
during ATA-ATAPI-7=20
as well.</FONT></DIV></DIV>
<DIV dir=3Dltr><BR>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> owner-t10 at t10.org on behalf =
of Shah, Amit=20
M<BR><B>Sent:</B> Thu 4/28/2005 2:09 PM<BR><B>To:</B> Serial ATA II;=20
t10 at t10.org<BR><B>Cc:</B> Beckett, Richard C; Carmichael, Rick; =
Devidas,=20
Devicharan; Teo, Daryl; Karthikeyan, Kishore K; Mak, Henry; Mak, Henry; =

Sheffield, Robert L<BR><B>Subject:</B> SATA CONT discrepancy in SATA / =
SAS=20
standards!!<BR></FONT><BR></DIV>
<DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi,</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I am a bit confused about =
the way=20
SATA_CONT behavior is mentioned in SATA as well as SAS specs. Both the =
behaviors=20
sound conflicting to me and I would really appreciate if somebody can =
throw some=20
light on clarifying the standards.</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The SATA specification =
(section=20
7.4.5 as attached below) mentions that SATA CONT should expected only =
once=20
during a CONT sequence. So if the receiver detects </SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">XRDY&nbsp;&nbsp;&nbsp;=20
XRDY&nbsp;&nbsp;&nbsp; CONT&nbsp;&nbsp;&nbsp; =
CONT&nbsp;&nbsp;&nbsp;&nbsp;=20
RD</SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;=20
RD&nbsp;&nbsp;&nbsp; RD&nbsp;&nbsp;&nbsp; SOF</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">then it would be a =
<B><FONT=20
color=3Dred><SPAN style=3D"FONT-WEIGHT: bold; COLOR: red">unexpected / =
invalid=20
sequence</SPAN></FONT></B> as there were two CONT&#8217;s back to=20
back.</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Now the SAS =
Specifications (section=20
7.2.4.4 as attached below) mentions that there could be one or more =
SATA_CONTs=20
in a CONT sequence. So if the receiver detects </SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">XRDY&nbsp;&nbsp;&nbsp;=20
XRDY&nbsp;&nbsp;&nbsp; CONT&nbsp;&nbsp;&nbsp; =
CONT&nbsp;&nbsp;&nbsp;&nbsp;=20
RD</SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;=20
RD&nbsp;&nbsp;&nbsp; RD&nbsp;&nbsp;&nbsp; SOF</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">then it would be a =
<B><FONT=20
color=3Dred><SPAN style=3D"FONT-WEIGHT: bold; COLOR: red">valid=20
sequence</SPAN></FONT></B> as there were two CONT&#8217;s back to=20
back.</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I am wondering if two or =
more CONT&#8217;s=20
back to back are valid or not.</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Amit =
Shah</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Intel =
Corporation</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">>>>>>>>>>>>&nbsp;</SPAN></FONT><=
/P>
<P class=3DMsoNormal><B><U><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">The =
SATA specs=20
Revision 1.0 29-August-2001</SPAN></FONT></U></B></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><B><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">7.4.5 =
Continue=20
primitive</SPAN></FONT></B><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">In order to accommodate =
EMI=20
reductions, scrambling of data is incorporated in Serial ATA=20
as</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">described in Section 7.5. =
The=20
scrambling of data is simple, with a linear feedback shift=20
register</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">(LFSR) used in generating =
the=20
scrambling pattern being reset at each SOF primitive, or rolling=20
over</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">every 2048 Dwords. =
However, the=20
scrambling of primitives is not as effective or simple because of=20
the</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">small number of control =
characters=20
available. In order to accommodate EMI reductions, =
repeated</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">primitives are eliminated =
through=20
the use of the CONT primitive.</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Any repetitive primitive =
may be=20
implied to continue repeating through the use of the CONT=20
primitive.</SPAN></FONT></P>
<P class=3DMsoNormal><B><FONT face=3DArial color=3Dred size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: red; FONT-FAMILY: =
Arial">The=20
recipient of the CONT primitive shall ignore all data received after =
the CONT=20
primitive until the</SPAN></FONT></B></P>
<P class=3DMsoNormal><B><FONT face=3DArial color=3Dred size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: red; FONT-FAMILY: =
Arial">reception=20
of any primitive, excluding ALIGN</SPAN></FONT></B><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">. After transmitting the =
CONT=20
character, the transmitter</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">may send any sequence of =
data=20
characters to the recipient provided that no primitives are=20
included.</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The reception of a CONT =
primitive=20
shall cause the last valid primitive to be implied as repeated=20
until</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">the reception of the next =
valid=20
primitive.</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><B><U><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">The =
SAS specs=20
Revision 9&nbsp;&nbsp; 18 March 2005</SPAN></FONT></U></B></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><B><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">7.2.4.4 Continued=20
primitive sequence</SPAN></FONT></B></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Primitives that form =
continued=20
primitive sequences (e.g., SATA_HOLD) shall be transmitted two times, =
then=20
be</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">followed by SATA_CONT, if =
needed,=20
then be followed by vendor-specific scrambled data dwords, if=20
needed.</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">ALIGNs and NOTIFYs may be =
sent=20
inside continued primitive sequences as described in 7.2.4.1. After=20
the</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">SATA_CONT, during the=20
vendor-specific scrambled data dwords:</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">a) a SATA_CONT continues =
the=20
continued primitive sequence; and</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">b) any other STP =
primitive,=20
including the primitive that is being continued, ends the continued=20
primitive</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">sequence.</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Receivers shall detect a =
continued=20
primitive sequence after at least one primitive is received. The=20
primitive</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">may be followed by one or =
more of=20
the same primitive. <B><FONT color=3Dred><SPAN=20
style=3D"FONT-WEIGHT: bold; COLOR: red">The primitive may be followed =
by one or=20
more</SPAN></FONT></B></SPAN></FONT></P>
<P class=3DMsoNormal><B><FONT face=3DArial color=3Dred size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: red; FONT-FAMILY: =
Arial">SATA_CONTs,=20
each of which may be followed by vendor-specific data=20
dwords</SPAN></FONT></B><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">. Receivers shall ignore=20
invalid</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">dwords before, during, or =
after the=20
SATA_CONT(s). Receivers do not count the number of times the=20
continued</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">primitive, the =
SATA_CONTs, or the=20
vendor-specific data dwords are received (i.e., receivers are simply in =

the</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">state of receiving the=20
primitive).</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Expanders forwarding =
dwords may or=20
may not detect an incoming sequence of the same primitive and=20
convert</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">it into a continued =
primitive=20
sequence.</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><B><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">Table=20
64</SPAN></FONT></B><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"> in the SAS Specs also =
mentions that=20
the SATA_CONT has a primitive sequence type =
&#8220;Single&#8221;.</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV></DIV>

</body>

</html>

------_=_NextPart_001_01C54CD7.CE644364--





More information about the T10 mailing list