Search results

The Pandora RAM is DDR-333 with a 32-bit data path. A typical low-end PC (Intel Atom) is DDR2-667 with a 64-bit data path. It's quite a large difference.

For those who want to try NiGHTS into dreams... http://hotfile.com/dl/126054899/6ca83f7/yabause-r2660.pnd.html This will also allow you to run games without the bios.

I really have no idea... I'm assuming that the CPU requirements for PSP emulation would be higher than for N64 or Saturn, but I don't know how much higher. There really aren't any existing PSP emulators that are working well enough to make such a comparison.

The problem with the Pandora is the slow memory rather than the Cortex-A8 clock. Running yabause on a 1GHz Intel Atom is quite a bit faster than on a 1GHz OMAP3530, due to the RAM and cache.

I have a fix for that, but NiGHTS runs way too slow for it to be useful. Also, it's worth mentioning that Bust-A-Move 2 Arcade Edition won't work if you rip the CD without the audio tracks.

You need to set the location of valid BIOS file in preferences. There's nothing really special needed to compile and run Yabause on the Pandora. It should work on any Linux system with x11+gtk+sdl. The dynarec will do ARMv7a or x86/x86-64.

The Nights issue is an actual bug, which doesn't occur using the interpreter. The rest of the things that have been reported are just limitations of Yabause. Also, Nights into Dreams requires the audio tracks.

...and people complain that Saturn emulation on the Pandora is slow.

I'll get back to mupen at some point. I played with it for awhile, but now one of the nubs broke and won't stay centered. :( Volvagia: Fast interpreter isn't fast. Emnasut: You don't need both the cartridge memory and the internal memory. Try setting the cartridge to 'None' and just use...

Yabause isn't perfect, and this game is known not to work. You might want to check the compatibility list at yabause.org. These games have CD audio, and won't work without the audio tracks.

Well, the register allocation situation is certainly better than N64, but still you've only got about 12 registers to work with (not counting stack, link, and global pointer). Take out another few for the cycle count, address generation, and memory map (although those are somewhat negotiable)...

The code is actually not alot different. Yes.

The register allocation and delay slot handling is largely the same. I made some changes to the constant propagation to handle the PC-relative loads, and there's a hack in the liveness analysis to handle the T bit separately. Code on the master and slave sh2s is compiled separately. It would...

I think you'd better get working on an upgraded Pandora with a faster CPU. :D

Now that I have a Pandora, I made a PND of Yabause (Saturn emulator). As expected, it is rather slow. Some games are playable if you overclock and don't mind using frameskip. PND is here: http://hotfile.com/dl/124843269/071b2b7/yabause-r2657.pnd.html Source code is here...

I didn't do anything fancy, it just counts 1 cycle per instruction. I think notaz underclocked it by half though (ie 16.9 million instructions per second). Is that sort of timing really necessary for anything newer than SNES? Checking after every instruction contributes to code bloat and L1...

http://code.google.com/p/mupen64plus/issues/detail?id=280 It never worked in the original glN64. I don't know what's wrong. Same... It somewhat works with rice, but it's glitchy.

64-bit signed multiply is broken. It's not a regression and doesn't affect PCSX. The loop preload bug and the dirty flag bug do affect PCSX, so you want those. Plus you probably want the liveness analysis and register allocation stuff for a small speedup.

Measuring CPU usage doesn't confirm this, may be a frameskip bug. I can confirm this is a dynarec bug. Are there any other non-working games that I should know about?

Thanks for the offer, but I doubt it'd make much difference at this point since Craig is out of boards. In addition to my pre-order, I bought a Pandora from another forum member, but the LCD cable was going bad and it soon became unusable. So that one went back for repair. Unfortunately the...