|Thread Links||Date Links|
|Thread Prev||Thread Next||Thread Index||Date Prev||Date Next||Date Index|
Thanks for your kindly help.
In your reply, the ALERT pattern will be generated only as the defined in 220.127.116.11. And the old ALERT signal(0xFF00) will be replaced.
But if we want to shorten the EEE wake up time, the signal(0xFF00) seems better than the defined in 18.104.22.168.
I apologize for the delay in responding.
I believe that you have highlighted a mistake in the draft specification. As this is currently under Sponsor Ballot review, I will submit a comment to fix the mistake. In particular:
Annex 83A.3.2a contradicts Clause 22.214.171.124 – I think that Annex 83.3.2a,, 2nd paragraph should change:
If the EEE capability includes XLAUI/CAUI shutdown (see 78.5.2) then when aui_tx_mode (see 83.5.11) is ALERT, the transmit direction sublayer sends a repeating pattern, as defined in 126.96.36.199 which is transmitted across the XLAUI/CAUI. When aui_tx_mode is QUIET, the transmit direction XLAUI/CAUI transmitter sends a repeating pattern, as defined in 188.8.131.52, and then is disabled as specified in 83A.184.108.40.206. Similarly when the received aui_tx_mode is set to ALERT, the receive direction sublayer sends a repeating pattern, as defined in 220.127.116.11 which is transmitted across the XLAUI/CAUI. When the received aui_tx_mode is QUIET, the receive direction XLAUI/CAUI transmitter sends a repeating pattern, as defined in 18.104.22.168, and then is disabled as specified in 83A.22.214.171.124.
Similarly, Clauses 84 and 85 need to be changed to remove some confusion. Change Clause 84.2 and Clause 85.2, second paragraph to:
The tx_mode parameter takes on one of up to six values: DATA, SLEEP, QUIET, FW, ALERT or BYPASS. When tx_mode = QUIET, transmission is disabled. Note: if Clause 74 FEC or a physical instance of XLAUI/CAUI is in use, only the values DATA, QUIET and ALERT may be passed through to the PMD (see 126.96.36.199, 83.5.11).
Also change Clause 84.7.2 and Clause 85.7.2 to:
If the optional Energy Efficient Ethernet (EEE) capability with the deep sleep mode option is supported (see Clause 78) then when tx_mode is ALERT, the transmitter equalizer taps shall be set to the preset state specified in 188.8.131.52.3.1. When tx_mode is QUIET, the transmitter shall be disabled as specified in 84.7.6. For all other states of tx_mode, the driver coefficients are restored to their states resolved during training.
I hope that resolves your difficulty. I will submit comments against the draft to make those changes.
I have EEE questions of 802.3bj D3.0 as following.
As the following figure(new plotted),
Question1:Does alert/quiet signal follow Figure 83-7/83-8(in 802.3bj D3.0) in XLAUI(point A,B)?
Does ALERT pattern replace repeating 16-bit pattern with Figure 83-7 method?
Question2:Does alert/quiet signal follow Figure 83-7/83-8(in 802.3bj D3.0) in 40GBASE-CR4(point E,F)?
I found following two descriptions(a)(b) in 802.3bj D3.0.
– If the optional Energy Efficient Ethernet (EEE) capability with the deep sleep mode option is supported (see Clause 78) then when tx_mode is set to ALERT, the adjacent PMA sends a repeating 16-bit pattern, hexadecimal 0xFF00, to the PMD, which the PMD transmits.
– When the value of tx_mode is ALERT, the PMA inserts the PMA alert signal defined in 184.108.40.206.
The description(a) seems that ALERT pattern is repeating 16bit pattern.
But description(b) seems that ALERT pattern is generated from Figure 83-7.
I am confused about these two descriptions.
Thanks for your kindly help.