fadden, thanks for taking a looksy into the emulator. Great ideas for optimization BTW. I've been looking at your ideas plus this document (http://slack.net/~ant/nes-emu/6502.html) and wondering how much mhz I can squeeze out of her.
> How are you determining performance? Mhz is calculated by counting clock cycles per loop. Might be pessimistic, but I'm thinking the G1 hardware is just too slow. It's at 1/3 mhz right now, and even if I squeeze another 1/3rd out I'm still at .66Mhz. The last 1/3 would probably be more trouble than the time is worth (or impossible.) I'm leaning heavily towards waiting for the hardware to catch up. Do you know anything about the NDK? Would it allow me to do C language type operations to speed this up? i.e. get the JVM out of the way and go straight to the cpu / memory? > BTW, at some point you'll want to add support for a virtual keyboard. > Not all devices have physical keyboards, which makes it tough to get > things going. True - I could use the built in one correct? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
