Repository navigation
Hardware Oddity NVNet Receive Status
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.
DSP tooling guide and navigation updated November 2, 2026 for experimental PR #384, source 8f51d237. Capture/replay usage and limits.
The earlier wiki-wide review was published November 1, 2026. Emulator source: b7140848. Reviewed wiki content: 1d2b671. Current status · Release availability · Publication process.
- Home
- Current status
- Stable versus main
- Implemented mechanisms
- Controls and defaults
- Measured results and limits
- Complete change register
- System
- CPU and vCPU
- Memory and DMA
- Graphics / NV2A
- APU and audio
- Timing and timers
- Platform and I/O
- Hardware observations
- Fidelity boundaries
- Methodology
- PGR2 routes
- Debugging lag / hot paths
- Tools and commands
- DSP capture, replay and fuzzing
- HLE readiness and public XISO proof
- Concurrent DSP shadow and OpenAL proof
- DSP HLE operation inventory
- DSP HLE fix examples and testing
- Development
- Upstream shortlist
- Wiki maintenance
- Research / retired work
- Optimization catalog
- Hot-path shortcuts
- Researched experiments
- Unproven proposal directory
- PR lessons
- September26 snapshot
Repository · PRs · Issues