Skip to content

Hardware Oddity NVNet Receive Status

Mainkill1 edited this page Sep 27, 2026 · 1 revision

NVNet receive-status combinations

Evidence: original driver implementation correction, not a complete silicon characterization. The nxdk receive-status change excludes framing-only status from its hard-error mask while retaining CRC, overflow, and other hard errors. The old expression could accept a packet whenever the framing flag was present, including when another error flag was also set.

This establishes driver recovery policy and a real implementation correction. It does not mean every framing-damaged packet is valid or every status combination has been measured on hardware.

Proposed test: construct a receive-descriptor truth table covering framing-only, each hard error, and combinations. Capture packet length, descriptor ownership, buffer contents, driver action, and interrupt behavior separately.

See also NVNet Networking.

Clone this wiki locally