Another question I have, regarding this matter is if the different Hypervisor modes have some disadvantages. I heard the TEST FW cannot run Blu-Ray movies. This should be on account of the Hypervisor mode since the software is pretty identical (like stated in the article).

The next question I, a noob in this scene with low ASM knowledge, have is wether I can just load the firmware.pup in IDA and start to explore the FW's functions or not.

Recently I stumbled over the Backup Loader article and I would like to know if this loader needs to read some data from the game files in order to launch the backup or if it already can load all backups. Also which format can the Backup Loader read yet?

Well I joined this forum yesterday and read many interesting articles.
But one major question did leave;
What tasks needs to be done in order to let a retail PS3 FW run our own applications.

Well you should read more carefully next time. Retail units are configured in a way that they only run signed code. Unless this security is broken or someone gets access to the signing key (which Sony guards very strictly I am sure) there is no chance for running "your applications". At least not directly from PS3 XMB - you can run whatever you want from Linux (or any other OS) installed on PS3 but that is constricted by hypervisor (i.e. no access to RSX, only 6 out of 8 SPUs)

And the question is? Because you cannot sign binaries, you cannot run them. Because you don't have signing (encryption) key, you cannot write those flags (read something about encryption).

Originally Posted by xhugox

Another question I have, regarding this matter is if the different Hypervisor modes have some disadvantages.
I heard the TEST FW cannot run Blu-Ray movies. This should be on account of the Hypervisor mode since the software is pretty identical (like stated in the article).

The limitation is purely in software - i.e. appropriate functions are just disabled. It has nothing to do with hypervisor.

Originally Posted by xhugox

The next question I, a noob in this scene with low ASM knowledge, have is wether I can just load the firmware.pup in IDA and start to explore the FW's functions or not.

No because the files encrypted and guess what - nobody besides Sony has decryption keys. These are stored in every PS3 but as you read the aforementioned article about CELL security, you should understand there is no easy way to get them.

Originally Posted by xhugox

Recently I stumbled over the Backup Loader article and I would like to know if this loader needs to read some data from the game files in order to launch the backup or if it already can load all backups. Also which format can the Backup Loader read yet?

Read above for some (there's more) reasons this is not (yet) possible.

Would just like to make it clear that the backup loader does in fact work fine, however, it only works on a Development Console, not a retail unit!

You're right - I was however referring to retail units which most of us have. And before someone asks (and doesn't deduce it from the above) - because we cannot sign the binary with retail keys it is impossible to use this loader on retail machines...

So installing a Test firmware on a retail console wont help? Is the hardware different on a Development Console?

Development Console= Retail Console with test firmware?

Correct, it won't help for the time being as it will only show you the Debug menu options but they won't function.

The hardware is identical, it's only the software that differs. This is covered in the 'PS3 Development News' sideblock articles on the main page, as well as detailing the detection bit flags that the PS3 Devs feel (based on their research) is a reason why we can't just install fully functioning Debug Firmware on a Retail PS3 console.

So just to clarify this; We can only run unsigned code on a full debug console.
A retail PS3 with a debug FW does not run unsigned.

It's stated in about 20 other threads, but to answer once more: correct. A Retail PS3 with Debug Firmware only show the menu options, they don't function and it cannot run unsigned code. Only real Debug consoles can.