Program Vender Id: Difference between revisions

From PS3 Developer wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 28: Line 28:


Note: first byte is territory value, last byte is guest_os_id.
Note: first byte is territory value, last byte is guest_os_id.
{| class="wikitable sortable"
|-
! Guest OS ID !! Description
|-
| 0x0000 || None
|-
| 0x0001 || PME
|-
| 0x0002 || Lv2
|-
| 0x0003 || PS2Emu
|-
| 0x0004 || Linux
|-
|}


{{Development}}<noinclude>[[Category:Main]]</noinclude>
{{Development}}<noinclude>[[Category:Main]]</noinclude>

Revision as of 01:05, 28 June 2019

Located at SELF offset 0x78.

For some reason it was named vendor_id there.

In geohot's makeself it was used as: set_u32(&(output_self_info_header.i_magic), 0x01000002);.

Not directly related to Authority ID, but seems to have many simularities with it (vendorid=2nd-9th bytes of authid), seems also related to SM ; LPAR's and their order suggests hierarchy/permission from high (can do everything) to low (lesser abilities).

VendorID count filetype
0x00000000 ? lv0 / lv1 only before SDK 060
0x33000077 ? *ldr / lv0 / lv1 only on SDK 060
0xFF000000 16 lv1.self's
0x07000001 180 iso spu self's
0x05000002 17 lv2_kernel.self's
0x02000003 45 ps2_emu self's
0x01000002 6147 CoreOs / dev_flash files / Games

Note: first byte is territory value, last byte is guest_os_id.

Guest OS ID Description
0x0000 None
0x0001 PME
0x0002 Lv2
0x0003 PS2Emu
0x0004 Linux