forums.ps2dev.org

Look at PSPLink.

Is there a way to install a CA root certificate in the PSP for use in the browser or with sceHTTPS* connections?

PSP_POWER_TICK_DISPLAY

Will only reset the screen dim/off timer. The suspend timer will still fire.

I thought even official games used hardcoded paths for custom memory stick data?

Seeing that NOTHING cross platform will ever compile for the PSP without extensive modification, it seems redundant to leave the fopen calls as such. You might as well convert everything to sce* while porting.

Davee wrote:No, it's still a fix.

If its only the hash then its probably software calculated in the pre-IPL like DAX said before, meaning the exploit if unpatched would still work if the hash is correct.

Hook the sceCtrl* syscalls to disable them in games. vshCtrl* for XMB.
For kernel buttons like volume, note etc and plugins you need to hook the kernel versions of the sceCtrl* functions.

jimparis wrote:An easy fix is still a fix

That means it can be cracked if its dumped.

You have to manage with 8 channels.

Do you think they simply added the IPL block hash as an easy fix for the exploit or that they have fixed the exploit and added the hash as an extra security measure?

Because prior to Pandora we relied on the weak security of 1.50OFW to boot CFW which doesn't work on the Slim onwards. The Pandora IPL block was used only in 3.52M33-something onwards.

No one mixes audio in real time games. That's why you need a sound card with lots of channels. Just play each on a different channel.

I completely disagree. How can you play games over ad-hoc Wifi then? TCP is a reliable protocol. You don't have to lose a single thing. Games send updates of the game state, not button presses. And much much less frequently than button sampling rate. There is no way you can play something like Tekk...

Application layer wifi is not suitable for sending keypresses in the first place. You will lose something.

Why the hell would anyone use newlib for a kernel module? Just compiling an empty module with it produces 84KiB of bloat.

You should really only be using sceDisplayVblankStart() within your rendering loop when you're making a proper application. Its not required for sceCtrlReadBuffer* functions because they already delay internally to keep up with the sampling rate. There's no need for a separate loop for reading butto...

20000ms is a little high. You'll miss some button presses. Use sceDisplayWaitVblankStart().

Add a sceDisplayWaitVblankStart() inside the loop. The syscon sends control packets at 60Hz anyway. Use this instead of latch. prevButtons = 0; while (1) { sceCtrlReadBufferPositive(&newButtons, 1) if ((prevButtons^newButtons) &...

I mean only have a kernel module and make it inject user mode code where required. What you're trying to do is much easier done with a PC like in XLink Kai. Having it entirely on the PSP seems pointless since you need to be within range of an access point and there is sure to be a laptop/PC with WiFi.

Don't think there's anything you can do, seeing that other devs use user modules for VSH hooks. You don't technically need a "module" if you can allocate space and put relocated code there.

If the function uses syscalls internally then I'm guessing it won't work.

What happens if you just get the function address and make an appropriate jump into it after disabling memory protection (So that it can return back to a kernel address, or does protection not apply when the source was a kernel address? I don't know.) If its a syscall, then the address of the functi...

I have no idea. Post some code. Depending on what you're doing you might need to disable interrupts or something. Actually you should always disable interrupts to be 100% thread safe. Don't see why reading is a problem when you can just set a pointer to any address and read away.

The syscall related functions from the M33 SDK are basically Tyranid's. You can get the source & headers from RemoteJoy and just statically link them into your modules.

And for the record I'm no expert in any of this.

That's massive. It could be hanging anywhere. Can't be bothered to look through everything.

Post the complete code.

All fake batteries are shit. Buy an original and use TM IPL to boot to NAND.

Looks like you're compiling for 1.50 and not 3.xx.

Declare prototype Call it in module_stop()