Iso module: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
| Line 45: | Line 45: | ||
|- | |- | ||
| SacModule.spu.isoself || | | SacModule.spu.isoself || | ||
|- | |||
|} | |||
=== Stop Codes === | |||
{| class="wikitable" | |||
|- | |||
! Stop Code !! Module !! Remark | |||
|- | |||
| - || - || - | |||
|- | |- | ||
|} | |} | ||
Revision as of 18:31, 11 December 2011
Explaination
Isolated modules are used for de-/encryption, rehashing etc.
Commonly found in CoreOS, dev_flash, embedded sony selfs and service packages like Remarry Bluray Drive.
They are SPU .self binaries which can be called whenever needed: e.g. decrypting and hashcheck EID0 for Target ID inside IDPS when called upon by lv1 (HyperVisor) to set up restrictions for Retail/CEX or Debug/DEX etc.
Known isolated modules
| Module | Remarks |
|---|---|
| aim_spu_module | EID0 (section 0x00 and 0x0A) |
| fdm_spu_module | EID2, Remarry Bluray Drive |
| manu_info_spu_module.self | |
| mc_iso_spu_module | PS2 |
| me_iso_for_ps2emu.self | PS2 |
| me_iso_spu_module | PS2 |
| sb_iso_spu_module | southbridge |
| sc_iso | syscon |
| spu_pkg_rvk_verifier.self | |
| spu_token_processor.self | systemtokens, QA Flagging |
| spu_utoken_processor.self | usertokens |
| sv_iso_for_ps2emu.self | PS2 |
| sv_iso_spu_module | EID4, PS2, bluray |
| AacsModule.spu.isoself | theoretically EID3 |
| CprmModule.spu.isoself | theoretically EID3 |
| CssModule.spu.isoself | |
| SacModule.spu.isoself |
Stop Codes
| Stop Code | Module | Remark |
|---|---|---|
| - | - | - |