The short answer
ps2tek is a community reference for PlayStation 2 internals. Use it to understand a subsystem, register or transfer described in a runtime log or code change; use project documentation for build commands and game reports for compatibility evidence.
Start with the question you are investigating
A hardware reference is most useful when you already have a concrete observation: an instruction, device call, register address or transfer that needs explaining. Begin with ps2tek's overview and memory map, then move to the subsystem named by that observation.
Do not treat the manual as a linear setup tutorial. It describes console behavior, while a recompiler's source describes how that project models it. Reading the two together helps distinguish expected hardware behavior from an implementation limitation.
Sources: ps2tek hardware reference ↗
A map of the main subsystems
These are starting points for reading, not diagnoses for a particular game. Similar symptoms can originate in different subsystems.
| Subsystem | Hardware question | Connection to a port |
|---|---|---|
| Emotion Engine (EE) | What does the main CPU instruction or address mean? | Read alongside the translated code and discovered entry points. |
| Input/Output Processor (IOP) | Which supporting device or service is involved? | Separate main-CPU translation from the runtime's IOP and library behavior. |
| Vector units (VU) | What vector program or transfer is being processed? | Review exploration coverage and the project's recorded/runtime vector paths. |
| Graphics Synthesizer (GS) | Which rendering state or register affects this operation? | Compare hardware behavior with the project's WebGPU implementation. |
| DMA, GIF and VIF | How does data move between processors and graphics units? | Investigate transfers and ordering as well as the code that produces data. |
Sources: ps2tek hardware reference ↗ · Reviewed PS2 Web Recomp README ↗
Keep the investigation reproducible
- Record the source commit, game release, native or browser runtime and exact point reached. These define the observation you are trying to explain.
- Keep a short relevant log excerpt and exploration screenshot. Identify the named operation before selecting a hardware chapter.
- Compare the hardware reference with the project's implementation and original issue or pull request. A manual entry alone does not show which code path ran.
- Report the observed behavior, expected behavior, source section and unknowns separately. Remove private paths and keep game data out of public reports.
What this reference can and cannot establish
ps2tek describes itself as incomplete. Treat it as a useful community reference, not a complete official specification. For a precise claim, cite the relevant section and check the implementation or additional primary evidence.
A hardware explanation does not establish that a game boots, renders correctly or completes. The compatibility records on this site retain the reporter, source, furthest documented stage and missing test details for that reason.
Sources: ps2tek hardware reference ↗
Common questions
Is ps2tek official Sony documentation?
It is a community-authored hardware reference. Its own introduction states that the documentation is incomplete.
Should I read the entire manual before building?
Start with the setup tutorial for a local build. Return to the hardware reference when a concrete runtime or implementation question requires it.
Does understanding a subsystem prove a game's compatibility?
No. Compatibility needs observations for a specific game release, environment and project version. Hardware documentation explains behavior; it does not replace those observations.