Visible to Intel only — GUID: gtl1605490956362
Ixiasoft
1. About the Low Latency 50G Ethernet IP Core
2. Getting Started
3. Low Latency 50G Ethernet Intel® FPGA IP Parameters
4. Functional Description
5. Interfaces and Signal Descriptions
6. IP Core Register Descriptions
7. Document Revision History for the Low Latency 50G Ethernet Intel® FPGA IP User Guide: Stratix® 10 Devices
6.6.1. AN/LT Sequencer Config
6.6.2. AN/LT Sequencer Status
6.6.3. Auto Negotiation Config Register 1
6.6.4. Auto Negotiation Config Register 2
6.6.5. Auto Negotiation Status Register
6.6.6. Auto Negotiation Config Register 3
6.6.7. Auto Negotiation Config Register 4
6.6.8. Auto Negotiation Config Register 5
6.6.9. Auto Negotiation Config Register 6
6.6.10. Auto Negotiation Status Register 1
6.6.11. Auto Negotiation Status Register 2
6.6.12. Auto Negotiation Status Register 3
6.6.13. Auto Negotiation Status Register 4
6.6.14. Auto Negotiation Status Register 5
6.6.15. Link Training Config Register 1
6.6.16. Link Training Config Register 2
6.6.17. Link Training Status Register 1
6.6.18. Link Training Config Register for Lane 0
6.6.19. Link Training Frame Contents for Lane 0
6.6.20. Local Transceiver TX EQ 1 Settings for Lane 0
6.6.21. Local Transceiver TX EQ 2 Settings for Lane 0
6.6.22. Local Link Training Parameters
6.6.23. Link Training Config Register for Lane 1
6.6.24. Link Training Frame Contents for Lane 1
6.6.25. Local Transceiver TX EQ 1 Settings for Lane 1
6.6.26. Local Transceiver TX EQ 2 Settings for Lane 1
6.6.27. Link Training Config Register for Lane 2
6.6.28. Link Training Frame Contents for Lane 2
6.6.29. Local Transceiver TX EQ 1 Settings for Lane 2
6.6.30. Local Transceiver TX EQ 2 Settings for Lane 2
6.6.31. Link Training Config Register for Lane 3
6.6.32. Link Training Frame Contents for Lane 3
6.6.33. Local Transceiver TX EQ 1 Settings for Lane 3
6.6.34. Local Transceiver TX EQ 2 Settings for Lane 3
Visible to Intel only — GUID: gtl1605490956362
Ixiasoft
4.3. RX MAC Datapath
The RX MAC receives Ethernet frames and forwards the payload with relevant header bytes to the client after performing some MAC functions on header bytes. The RX MAC processes all incoming valid frames.
Figure 9. Flow of Client Frame With Preamble Pass-Through Turned On This figure uses the following notational conventions:
- <p> = payload size, which is arbitrarily large.
- <s> = number of padding bytes (0–46).
Figure 10. Flow of Client Frame With Preamble Pass-Through Turned Off This figure uses the following notational conventions:
- <p> = payload size, which is arbitrarily large.
- <s> = number of padding bytes (0–46).