BCM ECD recovered from OpenBCM SDK and proven: 1E.4006 start, 1.A896 verdicts, 1.A897-9A per-pair meters -- meter-accurate on a 45m cable, healthy pairs report length

This commit is contained in:
flamingcow
2026-08-12 19:37:54 -07:00
parent c57816345f
commit ad9bc9fae4
3 changed files with 24 additions and 12 deletions
+1 -1
View File
@@ -68,6 +68,6 @@ Fallbacks if raw-L2 steering can't work: minimal bare-IPv4 framing steered by IP
## Open items
- **ECD register chapter** from FS — the one missing document for BCM cable length; the wider ask list is in modules/fs/.
- **BCM ECD works** (recipe recovered from the OpenBCM SDK, validated on the FS — modules/fs/): per-pair lengths meter-accurate against a known ~45 m cable. Remaining work is characterizing the link blip the run causes (length is a between-runs operation until then). The FS ECD-chapter ask is now confirmation, not unblocking.
- **Pre-FEC verification** on the Aquantia — counters documented (modules/fibergaga/); needs the graded-noise correlation run (open-questions.md §5).
- **X710 PTP path-delay length measurement**: viable fallback for linked-cable length (PTP-latch timestamps both ports, same oscillator, short-cable calibration); scoped but unbuilt — the committed `probe.go` is the *filter-all* variant (raw-frame probes, needs all-packet rx stamping, E810-only); the X710/X520 variant means PTP-shaped probes. Superseded for the product if PHY DSP length pans out.