theater/cabletest
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Sharpen MCIA open question from mlx5_ifc.h register format; drop offline-rig and instrumentation-flow framing

Browse Source
This commit is contained in:
flamingcow
2026-08-12 21:37:02 -07:00
parent 65b1e18004
commit 4e5ba0bccf
4 changed files with 17 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/open-questions.md
+3 -3
View File
@@ -6,9 +6,9 @@ The genuinely open, thinking-worthy problems — nothing here is resolved. Analy
The decisive unknown for product diagnostics coverage ([nics/connectx-5/](nics/connectx-5/README.md)):
- Does firmware MCIA accept **arbitrary I2C device addresses**? The BCM bridge sits at 0x56; kernel paths only ever use 0x50/0x51.
- Can the BCM SMI **read data phase** (raw 2-byte read, no offset write) be framed through MCIA's offset model?
- If no to either: product diagnostics via the Marvell/Aquantia modules only, X520 kept as an offline BCM rig.
- Does firmware MCIA accept **arbitrary I2C device addresses**? The register format allows it (8-bit field, per-access status — verified in `mlx5_ifc.h`); firmware acceptance is the unknown.
- Does the BCM bridge **tolerate an offset write before its SMI read phase**? MCIA has no raw-read encoding, so this module-side property is the whole question — and it is testable on the X520 before the card arrives.
- If no to either: product diagnostics via the Marvell/Aquantia modules only.
## 2. ECD run disturbance