Today Dertyp at PSX-Scene (linked above) reports that http://twitter.com/KaKaRoToKS has dumped the PS3 LV1 syscalls, and plans to update his payload soon to allow other developers to dump the calls.
To quote: For Those Of You Who Are Asking What This Is:
level-1 syscalls are used to call hypervisor functions. On a PS3 the hypervisor is known as as "lv1? (level1) since it is the lowest level that runs directly on top of the hardware. The operating system is executed on top of this and is known as "lv2? (level2).
The two common operating systems are GameOS which PS3 games run on, and OtherOS which is usually used to run linux. Since both OSes run on top of the same lv1 hypervisor, they use the same set of hypercalls which has been partially documented here.
KaKaRoToKS Recent Tweets:
FINALLY able to dump (over eth) all lv1 calls!! Will push it soon!
To everyone misunderstanding: no lv1 access, all I did was be able to dump the "call trace" of lv1 hypercalls. same as payload_dump_syscalls
Released the hypercall tracer payload! Also merged syscall tracer, and a payload that traces hypercalls+syscalls.
Adding a payload to trace all sc calls (syscalls and hypercalls). Use carefully, this generates race conditions easily!!
Add a payload to trace all read/writes to the vuart by showing the hypercall and the data buffers sent/received
And Finally What Does These All Mean To Us Right Now!
This is work-in-progress, once KaKaRoToKS has finished his poking around the dumps, and detailing the info on his GIT, I will update this thread, even after he is done, it will take some time for various PS3 developers to study all this new information, before it will help out the "end-user" but it is another big step forward in the daily forever-changing and growing-fast PS3 Scene World!
For any one who asks/wants to ask "What does this mean?" This means we know a lot more cool information about the PS3. Its like reading a muscle magazine per-say... we learned information, we want to apply information, but our ability to do so might be dampened by what little muscle we have so far. We will gain more muscle, and the information will be useful to us (in the near future hopefully), but we still aren't there yet.
For all you non-techies: For now, this will not do anything for you, but it's another layer in the 'archeology' of the PS3's operating system. Once the complete system has been mapped, then we can start creating a proper firmware.
me and my mate in oz have been working on the ps3 scene since the JB, and we have managed to get a custom update to work.
We are just seeing if we can make a custom update that can load FW 3.50 with the jailbreak glich as many would call it to allow us to edit the ps3update.pup file and use data from 3.41 but have 3.50 info without the update that stops the JB. So we should have a solution in the next cpl of weeks
Originally Posted by bgrewar
me and my mate in oz have been working on the ps3 scene since the JB, and we have managed to get a custom update to work. We are just seeing if we can make a custom update that can load FW 3.50 with the jailbreak glich as many would call it to allow us to edit the ps3update.pup file and use data from 3.41 but have 3.50 info without the update that stops the JB. So we should have a soultion in the nxt cpl of weeks :P
We have manage to allow the backup manager to be installed over this process already stoping the need to load a pkg file
Last edited by bgrewar; 11-22-2010 at 09:35 AMReason: Automerged Doublepost