PS3 Question about Cobra

[StarmanX32]

Hi,

I've looked through the Cobra stage2 source and saw that Cobra creates the syscall 6 (LV2 Peek), 7 (LV2 Poke), 9 (LV1 Poke), 10 (LV1 Call), 15 (LV2 Function call) and overwrites LV1 Peek (which is syscall 8), so my question is why does Cobra create these syscalls (except for syscall 8 to create its own syscall functions) when they're already being created by the custom firmware itself? For example, PASTA Standard DEX by Joonie86 does have all these functions without Cobra. Are there any differences between the one created by the CFW and the one created by Cobra?

Sorry if this question might sound dumb, I'm just curious :p

 

[aldostools]

If the CFW has these syscalls hardcoded, then the syscalls in the payload are redundant.

Cobra payload originally was designed to be loaded from an USB dongle on a modified FW that acted like OFW when the dongle was removed. Therefore the payload needed to create the CFW syscalls. When Cobra payload was made public and integrated into Rebug, new syscalls were added by habib like syscalls 10 and 15. The syscalls already existing in the CFW are only overwritten.

Almost all CFW creators opted to leave the hardcoded syscalls when Cobra is disabled, instead of emulate an OFW like the original Cobra CFW.

 

[StarmanX32]

If the CFW has these syscalls hardcoded, then the syscalls in the payload are redundant.

Cobra payload originally was designed to be loaded from an USB dongle on a modified FW that acted like OFW when the dongle was removed. Therefore the payload needed to create the CFW syscalls. When Cobra payload was made public and integrated into Rebug, new syscalls were added by habib like syscalls 10 and 15. The syscalls already existing in the CFW are only overwritten.

Almost all CFW creators opted to leave the hardcoded syscalls when Cobra is disabled, instead of emulate an OFW like the original Cobra CFW.

Great explanation, thanks aldo.