Prior Art and Sources

Status: MAINTAINED SOURCE INDEX · Evidence class: IMPLEMENTATION FACT / PRIOR ART · Last reviewed: 2026-08-17

Claims on this site should be traceable to a public source, a source-owned fixture, or a clearly labeled hardware record. This page keeps the public source lineage compact so readers can distinguish implementation evidence, comparative prior art, and measured PSP behavior.

How to read a source card

Each card states what the source is useful for, what it does not establish, and how to pin a revision. A source can be primary for one claim and secondary for another.

PSP development and platform sources

  • PSPSDK / generated docs — open SDK headers, libraries, samples, NID prototypes, PRX/export tooling. Useful for public API shape and build metadata. Not Sony’s internal SDK and not a complete hardware oracle.
  • PSPAutotests — source-owned behavioral tests and expected values. Useful for reproducible test intent and regression ideas. A comment or emulator-only expectation is not a hardware measurement by itself.
  • PSP Developer Wiki — community-maintained platform, format, and hardware notes. Treat unsourced or conflicting wording as a lead, not final authority.
  • YAPSPD — historical hardware/software reference. Historical terminology and current model/firmware claims need re-verification.

Reverse-engineering and instruction references

  • PSP Reverse Engineering HQ — public Ghidra/Allegrex/RE workflow and tool pointers. Useful for workflow, not a measurement authority; do not publish user-supplied commercial binaries.
  • DavidGF VFPU documentation — community VFPU reference with test-oriented explanations; still separate documented behavior, emulator agreement, and hardware results.

Comparative implementations

  • PPSSPP — open PSP emulator. Useful for differential/reference comparisons; agreement does not prove real-PSP behavior.
  • JPCSP — open Java PSP emulator. Useful as an independent implementation and historical comparison; emulators are not hardware authority.
  • PSPLinkUSB — PSP USB homebrew/debugging toolkit. Useful for transport and debug workflow; valid transport does not make a probe result valid.

Compiler and toolchain provenance

  • PSPDEV and release history — open toolchain distribution and release metadata.
  • Nakagawa Recomp — current public implementation/test reference at reviewed main head 4eda0c4f97ba0f74b7d0668411185624076d17be. Use file/revision links for current implementation claims; do not infer PSP facts from one runtime.

Citation and novelty guardrails

Cite the smallest useful unit: source file and revision, issue or experiment ID, specification section, or measured record. Record whether a source is primary, near-primary, secondary, or historical. When sources disagree, preserve the disagreement and state the smallest supported conclusion.

Historical research notes are context and must be re-verified against current source before publication. Private archives, retail assets, keys, traces, and derived restricted bytes are never source cards.

Cite the smallest useful unit: source file and revision, issue or experiment ID, specification section, or measured record. Record whether a source is primary, near-primary, secondary, or historical. Use bounded novelty labels only when the survey scope supports them; never use ‘first ever’ without an exhaustive survey.

When sources disagree, preserve the disagreement in the Contradictions Registry and state the smallest supported conclusion. Link readers through Hardware Replication and Replication Wanted when a source gap needs a new experiment.