PS3 Backward Compatibility
The inherited OPL support targets hardware backward-compatible PS3 models. Current RiptOPL changes still need testing on the specific console, firmware, entry point and game source.
Supported hardware scope
| PS3 models | Mainboard | PS2 hardware |
|---|---|---|
| CECHA / CECHB | COK-001 | EE + GS hardware |
| CECHC / CECHE | COK-002 / COK-002W | GS hardware; EE emulated by the PS3 |
Identify the CECH model on the console label; drive capacity alone is unreliable after upgrades. See PS3 Developer Wiki's compatibility table and COK board references. Later non-BC models use a different software-emulation path; this guide does not claim RiptOPL support for them.
Inherited storage modes
Upstream OPL documents USB, SMB and CFW-dependent HDD modes for BC PS3. These are inherited support paths, not a current RiptOPL hardware test matrix. A source working on PS2 does not establish that its exFAT, VMC, GSM or networking implementation works in the PS3's PS2 environment.
Do not format a PS3 system disk as a PS2 APA drive. The internal-HDD instructions for an ordinary PS2 are not a PS3 installation procedure. Use the documentation for your actual PS3 firmware and PS2 execution environment.
Getting an entry point
You need a working way to launch a PS2 ELF on the BC console. Upstream mentions Swap Magic and recommends CFW with Cobra; HDD mode requires CFW. Consult that firmware/launcher project's current instructions rather than assuming every disc exploit or ODE exposes the same devices. See upstream OPL's PS3 notes.
Validation and bug reports
MMCE, MX4SIO, iLink, UDPFS/UDPBD, HTTP, Neutrino and RA are not established PS3 compatibility claims here. Start with the native OPL core and a known-working setup. A report should name CECH model, firmware/Cobra version, ELF entry point, exact RiptOPL commit/flavour, source, game and failure stage. Compare the same setup against a known-good build. See report details.