SAS PHY working group teleconference agenda, Sept 16, 2 - 4 pm CDT

Alvin.Cox at seagate.com Alvin.Cox at seagate.com
Wed Sep 11 19:43:19 PDT 2002


* From the T10 Reflector (t10 at t10.org), posted by:
* Alvin.Cox at seagate.com
*
SAS PHY Teleconference Monday, September 16, 2:00 pm - 4:00 pm CDT

PARTICIPANT INFORMATION:
-----------------------
All Participants should use the following information to reach the
conference call:

Toll Free Dial in Number:  (866)279-4742
International Access/Caller Paid Dial In Number:  (309)229-0118

PARTICIPANT CODE:  3243413



Webex information:

Meeting Summary
     Meeting Name:  SAS PHY WG
     Scheduled Time: 9/16/2002 at 1:45PM (GMT -05:00) Central Time, USA &
Canada (DayLight Time).
     Meeting Number: 281981011
          Any meeting attendee can use this number to join the meeting, at
          https://seagate.webex.com/join/

     Password: commonmode


Agenda:

1.  LED driver requirements
Barry Olawsky presentation concerning system level impact of 15mA current,
3.6V max.

2.  Test Patterns
What should we do since scrambling of address affects data pattern to
achieve on-the-wire results?
Suggestion: Describe on-the-wire pattern and leave implementation to be
vendor specific. This may include special secret test set-up codes to
disable scrambling. Other ideas?

3.  Common mode specification
Update status.

4.  Test loads
Update status. posting due 9/20

5.  OOB transmition levels

Discuss possibility that both drives and expanders send OOB at SAS levels
rather than SATA levels. Would not be an issue dor SAS drives since the
connector is not compatible with SATA connectors. Risk to SATA drives? Not
doing so risk to SAS robust design for enterprise applications?

6.  Define conditions for "loss of signal"
Based on the impact to the system, what defines a loss of signal? One bit?
Voltage level loss? Etc.

7. Review what PHY group wants to count on the SMP REPORT PHY ERROR LOG.

List below made intially by PHY working group. Is this what we want? What
interactive errors stop counts on others?

PHY group suggested error report items in order of significance:

* Loss of signal
* OOB signal detected but can't negotiate OOB (expander log)
* Speed negotiation at each speed (count of successes for G1, G2, ?)
* Disparity error count
* Illegal character count
* CRC error count
* Loss of synchronization

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