Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
From: Ragnar Jonsson All, As discussed in today’s 802.3cy comment resolution meeting, George and I reviewed the following paragraph on page 66, lines 18-22: Alert, a four RS-FEC frame long sequence (alert_length), shall start four frames after the beginning of any eighth RS-FEC frame counting from the start of the QR cycle. The MASTER and SLAVE shall derive the tx_refresh_active
and tx_alert_start_next signals from the transmitted RS-FEC frames as shown in Table 165–4 and Table 165–5. When Slow Wake is active, alert can be transmitted in only a single QR cycle location, starting at RS-FEC frame 92. To help address comments 65, 134, and 135, we suggest changing the paragraph above to Alert is a four RS-FEC frame long sequence (alert_length). When SlowWakeRequest is not set, alert can be transmitted such that it ends at any eighth RS-FEC frame boundary, counting from the start of the QR cycle
(see Figure 165-11). When SlowWakeRequest is set, alert can only be transmitted in a single QR cycle location, starting at RS-FEC frame 92 for master and at RS-FEC frame 44 for slave (see Figure 165-12). The synchronization for the alert signaling is described
in tables 165-4 and 165-5. To address comment 135, I also suggest the following changes
Ragnar To unsubscribe from the STDS-802-3-B10GAUTO list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B10GAUTO&A=1 |