Skip to main content
How Can We Help?
< All Topics
Print

Experiment: PSPLink Native Windows vs WSL2 Qualification

Posted
Updated
ByJstar269

Experiment ID: EXP-PSPLINK-TRANSPORT-20260806-A · State: ACCEPTANCE ELIGIBLE (WSL2 leg) / TRANSPORT FAILED (native Windows leg) · Classification: methodology finding

Question

Which transport conditions must be true before a PSPLink session can support semantic hardware experiments?

Fixture and environment

Same physical PSP, cable, PSP-side package, and matched PSPLink source build were compared across native Windows and WSL2/usbipd Linux. Public prior art includes PSPDEV debugging, PSPLink Windows guidance, and psplinkusb.

Procedure and transport qualification

  • Native Windows enumerated Sony 054c:01c9, opened/configured/claimed the interface, then timed out with libusb -7 on the first four-byte HostFS EP2 write.
  • The same PSP/package through usbipd to WSL2/Linux returned 4 for that write, completed EP81 protocol traffic, and reached a real host0:/> shell.
  • Only after the handshake, remote shell round trip, and repeated source-owned smoke probes should semantic records be accepted.

Interpretation

The A/B isolates the tested failure to the native Windows host/backend/path in that environment, while stopping short of claiming PSPLink generally fails on Windows or that one specific library is proven as root cause.

Acceptance and capture integrity

Transport states are not a Boolean. Use HOSTFS_HANDSHAKE_PASS, SHELL_REMOTE_PASS, SMOKE_QUALIFIED, TRANSPORT_WEDGED, CAPTURE_MISSING, and CAPTURE_CORRUPT. Stale-tail or truncated HostFS output is not semantic evidence.

Claims not supported

  • No universal Windows failure claim.
  • No semantic PASS/FAIL when transport or capture is invalid.
  • No private host paths, device identifiers, or raw captures.

Implementation and replication

Record exact PSPLink source/build identity, host backend, driver, model/firmware/CFW, first EP2 result, and remote shell result. A contributor can reproduce the A/B without any retail game data. Report only environment metadata and scalar handshake outcomes.

Related: FIND-PSPLINK-TRANSPORT-001 · CONFLICT-PSPLINK-TRANSPORT-001 · PSPLink synthesis.

Publication safety: methodology aggregate only; no private paths/captures. Last reviewed: 2026-08-11.

Current source anchor — Wave 4

The public transport protocol was checked against docs/HARDWARE_ORACLE.md at main 04daf156. This documents the qualification boundary, not a claim that the runtime implements every host path.

Table of Contents