Iso module: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 23: | Line 23: | ||
| me_iso_spu_module || PS2 | | me_iso_spu_module || PS2 | ||
|- | |- | ||
| sb_iso_spu_module || | | sb_iso_spu_module || southbridge | ||
|- | |- | ||
| sc_iso || syscon | | sc_iso || syscon | ||
Revision as of 17:03, 6 December 2011
Isolated modules are used for de-/encryption, rehashing etc.
Commonly found in CoreOS and service packages like Remarry Bluray Drive.
They are SPU .self binaries which can be called whenever needed: e.g. decrypting and hashcheck EID0/EID5 for Target ID inside IDPS when called upon by lv1 (HyperVisor) to set up restrictions for Retail or Debug etc.
Known isolated modules:
| Module | Remarks |
|---|---|
| aim_spu_module | EID0/EID5 |
| fdm_spu_module | 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 | PS2, bluray |