(Last update Jan. 30, 2006)

1. Page 10, paragraph 6: “Wide ports provide on (one) of SAS’s key…”
2. Page 10, paragraph 7: “…which PHY is used.  The (This) provides a…”
3. Page 10, Figure 1-5 some of the drivers are missing the "circles" on the negative signal lines
4. Page 13, paragraph 6: “Figure 1-9 on page 16 shows the SAS structure…”  The text that follows this particular reference makes more sense to me if one changes the reference to read: “Figure (1-8) on page (14) shows the SAS structure…”  Also, I noticed that the previous text-embedded reference was to Figure 1-7, and the following text-embedded reference is to Figure 1-9.
5. Page 14, Figure 1-8: Moved the "PHY [1..n PHYs per port]" text from each of the PHYs to immediately under the Port layer to clarify the relationship between Port and PHY..
6. Page 26, topic 2.2.5, item 4: “Data out (in) frames received.”  Data from the target comes IN to the Initiator.
7. Page 53, last paragraph: “In the example shown in Figure 4-14 on page 49, Host 1 is attempting…”  The text that follows this particular reference makes more sense to me if one changes the reference to read: “… in Figure (4-17) on page (54), Host 1 is attempting…”  Also, I noticed that the previous text-embedded reference was to Figure 4-16, and the following text-embedded reference is to Figure 4-18.
8. Page 55, Figure 4-18: The OPEN associated with the host in the upper right should be labeled "Host 2" rather than "Host 1".
9. Page 85, last sentence: Change "This field is not be changeable" to "This field is not changeable."
10. Page 111, paragraph 3: “…of a single command, just a (as) multiple…”
11. Page 112, paragraph 6:  Please consider adding the following thoughts to the Additional CDB Length topic to “re-mind” the students, if they have forgotten “the rest of the story.”  For CDB’s that are “variable,” those in Group Code = 3, the number of bytes over 16 are the bytes in the ADDITIONAL CDB BYTES Field.     (or some wording similar to that)
12. Page 117, Table 7-2: SAS-1 restricted allowed status values to only those shown in the table. This precluded support for SCSI Linking. The SAS-2 draft does not contain these restrictions. The following not has been added prior to the table - NOTE: Other status byte values were reserved by the SAS-1 standard. This restriction will be removed in SAS-2 (see Table 6-2 on page 78 for a complete list of status values)
13. Page 138, Figure 9-7: The frame associated with item 5 should be labeled "Response (Command)"
14. Page 143, Figures 9-13 & 9-14: Updated to show ACK/NAK Balance and clarify frames. You can download a corrected page by clicking on this link. Open Now
15. Pages 155-161: The SSP traces in Chapter 10 have a number of editing and functional errors. A pdf file containing a set of corrected traces in book format can be viewed by clicking on the following link. Open Now
16. Page 291, Figure 18-6: There is an extra "OPEN ADR Frame" at the top left.
17. Page 402, Figure 26-12: The OPEN associated with the host in the upper right should be labeled "Host 2" rather than "Host 1".
18. Page 424, Transition SL_CC1 to SL_CC2: Neither the text nor the standard is very explicit about what happens to the transmitted OPEN address frame. The overriding OPEN takes precedence and the transmitted OPEN must be resent (i.e., the original OPEN is discarded).
19. Page 490, Figure 33-1: In block SP4:OOB_COMSAS, the 'COMSAS Transmitted' and 'COMSAS Detected' labels are reversed. The labels should be swapped to correct the figure.
20. Page 535, 1st paragraph last sentence: Grammar is awkward. Change to read " Normally, this would apply to expander PHYs, discrete SAS to SATA bridges and HBAs designed to directly connect to SATA devices.