Support and General Use > Plugins/Viewers
NES plugin - a proposal
criznach:
--- Quote from: ComposerDude on October 09, 2007, 12:32:22 PM ---Enjoy your coffee, fellow travellers, and peace out.
ComposerDude
--- End quote ---
I'm cool with that. I'm totally new to rockbox but not c/c++ and oldschool development. So this caught my eye as both a way to get involved in some rockbox coding, and another cool thing that rockbox can do.
I think as far as getting something to the community to use, the InfoNes port is pretty far along. The games that i've tried have the same quirks that they do on the windows port, but may run a bit slower even with frame skip turned on.
If you or anyone else want to continue to work on FCEU or TuxNes for Rockbox, I'd be interested in that too. I looked at FCEU for several evenings and even created a stripped down makefile, started looking at platform problems, etc. But the next day I discovered an already running InfoNes port and haven't touched it again. :) That doesn't mean I won't ever again!
I guess I'm still kinda distracted by all the shiny bells and whistles of rockbox.
stateq2:
Yeah, I'm not dead yet either :) I have had to do just about the same things you have, ComposerDude (school, work, etc).
Anyway, I haven't made much progress with the plugin, but once I get started, I really think that progress will come rapidly. Free time is rare when trying desperately to raise your GPA ;) However, I will start working on it during the weekends.
So, in summary, I'm still VERY interested in seeing project get finished properly (GPL code), so I'm going to work on it every free chance I get.
ComposerDude:
Oh, GPA's...
Definitely feel you there. Thankfully, I had viral pneumonia, so they excused the poor GPA from last semester.
Finding time to work on anything else is a miracle.
LambdaCalculus:
I'm sticking by this project, no matter what. Lack of time be damned, I'll work on it in whatever spurts of time I can get!
criznach:
Are you guys looking more at an interpretive core, like FCEU, or a dynamic compilation core like TuxNES? The dynamic compilation core might be hell to implement across multiple targets. I've been digging into the source for InfoNES and FCEU and looking at their approaches. One potential bottleneck for both seems to be memory reads and writes. Any thoughts on how to optimize that in an interpretive core? The read/write functions in InfoNES are inlined, but they are quite large, and I'm not sure they're really being inlined without looking at a disassembly.
Later,
Chris.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version