Ah... 1Time user, I think I will fall in love with you ! go go !!! :P
Well, here is my round for "B_man55".
1/ You treat "TYL" of piece of $#@!... Dont worry yoyo and I really appreciated it.
2/ You know NOTHING about coding and you admit it...
So if you know nothing... Why do you write sentences like :
[ It won't work, garuan-damn-tee it. ]
So you dont know how to code, but you know what will be the result of the coding ??? Hum... then I would say :
1/ You are the dumbest guy I ever seen on earth.
2/ You are a genious, you have the vision in the ether and I should shut up...
Well, I let people here decide which options I should choose.
Now lets get more constructive and more technical shall we ?
Personnal opinion about a PS emu on a PSP :
1/ Same CPU, same instruction set... (expert on MIPS , correct me here)
2/ PS cpu run at 33 Mhz if I am correct.
3/ PSP and PS graphics chip are close technically (= send a list of GU commands)
4/ Audio chip should be easy to emulate.(PS expert correct me here also)
5/ No special matrix, 3d geometry processing if I remember correctly...
Conclusion :
I believe that if the CPU emulation is written correctly, it would be possible to make a PS emu running at full speed.
(sound on ME, GU translation code taking around 5~10% of PSP CPU time,
remain 300 Mhz to emulate 33 Mhz)
If the CPU emulation is done in C the standard way (= emulate a MIPS over a MIPS), you are going to be slow like hell... Because 33 Mhz is too fast to be emulated on a 333 Mhz machine.
If you use MMU and memory protection mecanism, virtual memory and stuff like this, it may be possible to use CPU exception to do the memory mapping and run most of the code natively. Or you have enough memory on the PSP to store "translated" code and cache it.(and the funny part is that it is as powerfull as a dynarec, without the need for a dynarec :P)
Any develloper opinion here ?
Bookmarks