1 -- porter's foreword --
\r
3 This is a Pandora port of Exophase's impressive GBA emulator, gpSP.
\r
4 Since nobody has released a functional port for more than a year after
\r
5 pandora's release, and the GINGE'd version doesn't do this emulator
\r
6 justice, I've decided to take this task. This version also includes
\r
7 my own tweaks from GP2X/Wiz version. In case anyone wonders, this
\r
8 release was done with author's consent.
\r
10 To use it, you'll first need to copy authentic GBA BIOS to gpSP
\r
11 appdata directory, which usually is <SD card>/pandora/appdata/gpsp/ .
\r
12 It must be named gba_bios.bin and should be 16kB in size.
\r
14 I've appended the original gpSP GP2X and PSP readme files as they
\r
15 contain lots of information that is still relevant for this version,
\r
16 as well as development history of this project.
\r
23 - Pandora port, using hardware scaler for video output.
\r
24 - Fixed a few portablility issues in ARM asm and sound code.
\r
25 - Tweaked timing to suit pandora's LCD refresh nicely.
\r
26 - Maybe fixed GBC/digital sound channel desync over time.
\r
27 - Some other not-that-relevant cleanups and tweaks.
\r
29 Source code should be available at:
\r
30 http://notaz.gp2x.de/cgi-bin/gitweb.cgi
\r
34 -- gameplaySP2X Gameboy Advance emulator for GP2X --
\r
36 gpSP2X is a version of my (Exophase)'s emulator originally for Sony PSP.
\r
37 A large amount of effort has been done to make it more optimized for the
\r
38 ARM CPU present in the GP2X, however it is still very much a work in
\r
41 See readme.txt for the PSP version readme, which contains a lot of
\r
42 information relevant to the GP2X version (note that some of it does
\r
49 - Fixed clock and scaling config saving.
\r
50 - Fixed occasional crash on first ROM load on 1.1 firmware.
\r
51 - Added LCD timing setup code, which can be controlled through
\r
52 'pollux_dpc_set' environment vatiable (see gpsp.gpe wrapper script).
\r
55 - Added portrait drawing modes. They eliminate tearing but are slightly
\r
57 - Added page scrolling in ROM browser with L/R.
\r
58 - 32MB ROM support fixed.
\r
60 0.9-2xb u4 (unofficial notaz release, done on Exophase's request)
\r
61 - Wiz port. No emulation related changes.
\r
62 - Wiz: dropped SDL for video and hitting hardware directly (GPH SDL can't
\r
63 be trusted, it doesn't do double buffering as of firmware 1.0).
\r
64 - Added new optimized software scaler with interpolation.
\r
65 - gpSP is now saving ROM dir on exit. Delete romdir.txt if you don't
\r
67 - gpSP now comes with wARM, new kernel module+lib for ARM cache control
\r
69 - gpSP no longer invalidates whole icache after recompilation, might
\r
70 cause minor speedup.
\r
72 0.9-2xb u3 (unofficial notaz release, released with permission):
\r
73 - Removed built-in CPU/LCD/RAM-Tweaker.
\r
74 - Improved usability of volume control.
\r
75 - Removed PSP-specific GUI options, adjusted help text.
\r
76 - Overclocking from menu now works, keep it at 200 if you don't want that
\r
77 (if you want to overclock using launcher, for example).
\r
78 - Fixed centering-on-first-run problem.
\r
79 - 3:2 scaled option now does what it says.
\r
81 0.9-2xb u2 (unofficial notaz release):
\r
82 - Replaced non-working mmuhack.o with proper one, added cache flush calls
\r
85 0.9-2xb u1 (unofficial notaz release):
\r
86 - Fixed a problen in thread synchronization which caused deadlock after
\r
90 -- IMPORTANT-- If you're overwriting an old version, be sure to delete the
\r
91 gpsp.cfg file first, or be prepared to have a bunch of weird button
\r
92 settings that would require fixing.
\r
94 - Fixed some bugs stunting compatability.
\r
95 - Optimized alpha blends in renderer.
\r
96 - Some more optimizations to dynarec output.
\r
97 - Savestates should work better now.
\r
98 - Cheat/misc menu won't crash the emulator.
\r
99 - Main button config window works (not all buttons are in yet)
\r
101 0.9-2Xa: (Exophase release)
\r
102 - Redid autoframeskip. Should work more reliably.
\r
103 - Rewrote dynamic recompiler from x86 source (arm_emit.h, arm_stub.S).
\r
104 Has some more sophisticated behavior than the last version, more is
\r
105 still to come... Should notice a slight speed improvement over the
\r
107 - Tweaked GUI to be a little more useable. Buttons are now mirroring the
\r
109 - Code unification + cleanup amongst versions.
\r
112 v9008: (zodttd release)
\r
113 - Updated the way autoframeskip works. Should be better now. Still has a max
\r
115 - Added a slight performance increase to the dynarec.
\r
116 - Added sync() to make sure files such as savestates and in-game saves are
\r
117 saved properly to the GP2X.
\r
119 v9006: (zodttd release)
\r
120 - Initial public release
\r
125 1. Place the "gpsp.gpe" and "game_config.txt" file in a directory on your SD
\r
126 card used with the GP2X.
\r
128 2. Place your GBA BIOS in the directory from step 1. This file must be named
\r
129 "gba_bios.bin" in all lowercase as shown, so rename it if needed.
\r
133 There are two commonly available BIOSes - one is the correct one used in
\r
134 production GBA's worldwide and the other is a prototype BIOS. The latter
\r
135 will not cause some games to not work correctly or crash. If you attempt
\r
136 to use this BIOS you will be presented with a warning before being
\r
137 allowed to continue. This screen will give you a checksum of the real
\r
138 BIOS image (see readme.txt for further information).
\r
140 3. Place your GBA games in the directory from step 1. These files should have
\r
141 a ".gba" or ".bin" file extension. Zip compressed games should be supported
\r
142 and are recognized with the ".zip" file extension. Note that 32MB ROMs will
\r
143 probably not run if zipped. 16MB and smaller should be OK.
\r
145 4. Done. Run gpsp.gpe.
\r
150 How to use gpSP on the GP2X:
\r
151 Buttons are mapped as follows (GBA/ingame buttons can be changed in the menu):
\r
153 GP2X--------------------GBA
\r
161 GP2X--------------------------------gpSP
\r
165 VOL MIDDLE (UP + DOWN) -> menu
\r
166 PUSH STICK -> fps display toggle (second number is
\r
167 frames actually drawn)
\r
171 X -> cancel/exit menu
\r
172 A -> escape (up one director level in the
\r
175 When gpSP is started, you are presented with the option to overclock your
\r
176 GP2X. Use the L/R TRIG to change the CPU clockspeed and press START to
\r
177 continue. You may also change RAM timings here - experiment with what
\r
178 works well. Note that going too high on overclocking or low on RAM
\r
179 timings can cause the game to crash or the GP2X to outright freeze up.
\r
181 If you do not want to overclock, press START without using L/R.
\r
182 You will now be presented with a menu to choose a game. Press the IN-MENU
\r
183 "SELECT" button shown above to pick a game to load.
\r
185 If you would like to test gpSP for the GP2X with a homebrew (free public
\r
186 domain) game, a game by Russ Prince works very well with gpSP. It is called
\r
187 Bust-A-Move and is a remake of the classic game it's named after.
\r
190 How to build from source:
\r
192 The makefile included in the source is geared towards the Open2x toolchain.
\r
193 If you use Open2x and installed it in the way recommended then it should
\r
194 work okay, assuming you also have up to date HW-SDL (and have
\r
195 arm-linux-sdl-config installed in the right place). The makefile is in the
\r
196 gp2x directory, so go there first then just type make to build gpsp.gpe.
\r
197 Might need a little tweaking if your setup is different. If you need help
\r
198 you can ask me, but I'll probably nag you about why you want to build it in
\r
204 Q) Help! This game doesn't work. Am I using a bad version of the ROM?
\r
206 A) First, make sure you're using the correct BIOS version. If you aren't
\r
207 gpSP should tell you. Other than that, there are some games that are
\r
208 known to not work now (and will probably work later), and perhaps
\r
209 many more games that I don't know about that don't work. I haven't
\r
210 launched a full scale compatability test at this version, so it might
\r
211 take a while before the compatability levels are high.
\r
214 Q) Why is this version slower than the PSP version?
\r
216 A) gpSP is still a work in progress. It might be possible to obtain more
\r
217 speed from both this version and the PSP one too (and others in the
\r
218 future). With that in mind, know that even a very agressively overclocked
\r
219 GP2X is still less powerful than a PSP, generally speaking. Still, I
\r
220 have a lot of ideas. It's unlikely that the GP2X version will ever be as
\r
221 fast/faster than the PSP version for anyone but anything's possible.
\r
224 Q) How high does my GP2X have to overclock to enjoy gpSP?
\r
226 A) That depends on you. Higher overclocking will mean less frames skipped
\r
227 on autoframeskip, or less frameskip needed if on manual. Or it can
\r
228 make the difference between whether or not virtual 60fps can be reached.
\r
229 For some games no GP2X in the world will be able to run them fullspeed,
\r
230 with any amount of frameskip. A few might run well with no overclocking
\r
231 and a generous level of frameskip (probably manual). If you don't care
\r
232 about battery life (or you're plugged into an outlet) you should push
\r
233 it as high as you can while still maintaining stability, because
\r
234 chances are high that whatever you play will benefit from it. Right now
\r
235 you'll probably want 260MHz if you can achieve it, but with a lot of
\r
236 luck this number will lower slightly in the future (and is just a vague
\r
237 ballpark figure anyway). I don't want to scare anyone off from using the
\r
238 emulator, you should give it a try and see how it plays for you
\r
239 regardless of how high you can overclock. Just note that this is far
\r
240 from a locked smooth experience for everyone on every game.
\r
243 Q) GBA has an ARM processor, GP2X has an ARM processor. GP2X is more
\r
244 powerful than GBA. This emulator should run great without overclocking,
\r
245 so therefore you're doing it wrong.
\r
247 A) That's not a question, but I'll field it anyway. Two things: first,
\r
248 "virtualization", or running the GBA code "natively" on the GP2X is
\r
249 probably not possible, at least not with the way I want to do things.
\r
250 For reasons why go read my blog (see below). So yes, you actually
\r
251 do need more than 16.7MHz of ARM9 power to emulate the GBA's CPU.
\r
252 Second: there is a whole lot of work behind emulating the pretty 2D
\r
253 graphics on the GBA, something it can do in hardware a lot better than
\r
255 End result: GBA emulation on GP2X isn't as easy as you think it is.
\r
258 Q) What are you working on now? When will you release the next version?
\r
260 A) See the gpSP development blog:
\r
262 http://gpsp-dev.blogspot.com/
\r
264 Note that I don't give release dates, ever, unless I'm right on the verge
\r
265 of releasing. Be grateful that I've decided to be much more open about
\r
266 the development of the emulator now.
\r
269 Q) Thanks to your blog I heard that you made some improvement. Can I have
\r
270 a copy of the new code?
\r
272 A) No. Builds in transition often have a lot of problems, and I like for
\r
273 releases to be relatively substantial. I can probably be bribed out of
\r
274 them with donations though. :P
\r
277 Q) Why do the menu suck so much? Why do half the options not work or not
\r
280 A) Sorry, the menu still hasn't been modified very much to fit the GP2X
\r
281 version instead of the PSP version.. hopefully this will improve in the
\r
285 Q) Who's in charge of the GP2X version anyway?
\r
287 A) Originally, zodttd was. I, Exophase, have basically usurped control of it
\r
288 now to encourage zodttd to work more on his PS1 emulator (that and I'm
\r
289 possessive of gpSP and get nervous when people work on it too heavily).
\r
290 zodttd will most likely still be around to work on things though.
\r
293 Q) I'm a super nice person and would like to donate some of my hard earned
\r
294 money to this one-off GBA emulator. Where do I send my money to?
\r
296 A) Exophase: exophase@gmail.com on PayPal
\r
297 zodttd: https://www.paypal.com/cgi-bin/webscr?cmd=_xclick&business=heirloomer
\r
298 %40pobox%2ecom&item_number=1&no_shipping=1&no_note=1&tax=0&cy_code=USD&bn=
\r
299 PP%2dDonationsBF&charset=UTF%2d8
\r
300 ^ Click there for donating on PayPal (remove whitespace/linebreaks).
\r
302 GP2X people have already donated a lot more to me than PSP people have,
\r
303 even though there's an order of magnitude or two less users. And they've
\r
304 donated far more to zodttd than they have to me. So I'm not going to ask
\r
307 However I won't lie: donating ups the chances of me actually working on the
\r
308 next version (for which I have a lot of ideas, but not necessarily time to
\r
309 dedicate to.. that time might need more incentive to be allotted from other
\r
310 things). This could change depending on my employment situation, but right
\r
311 now I feel guilty doing anything that doesn't help guarantee that I'll be
\r
312 able to buy food a year from now.
\r
315 Q) Tell me all of your personal information.
\r
317 A) Again not a question, but why not. I'm Exophase, real name: Gilead Kutnick,
\r
318 male, 23 years old, current residence Bloomington, IN; straight/single/not
\r
319 actively looking, almost have an MS in Computer Science (do have a BS
\r
320 underneath it), likes PSP more than GP2X, will not write a Nintendo DS
\r
321 emulator for either, am currently looking for a job for after I graduate.
\r
324 Q) You said you're looking for a job.
\r
326 A) Yes. If you have one or know someone who needs a low level oriented
\r
327 programmer then I'm up for grabs. And this is my resume:
\r
328 http://exophase.devzero.co.uk/resume.pdf
\r
333 Original codebase: Exophase (exophase@gmail.com)
\r
334 Foundation gp2x code: zodttd
\r
335 GP2X dynarec/stubs + current code maintainance: Exophase
\r
339 -- gameplaySP Gameboy Advance emulator for Playstation Portable --
\r
344 v0.91 (minor cleanup release)
\r
346 NOTE: I don't usually do minor releases but I rewrote a ton of
\r
347 things in gpSP 0.9, much of it during the last few days, and although
\r
348 I spent a lot of time debugging a few bugs inevitably crept in.
\r
350 # Fixed some issues in the new memory handlers that crept up, hopefully
\r
351 should fix the problems between 0.8 and 0.9.
\r
352 # Fixed a bug introduced in 0.9 that could cause crashes when selecting
\r
353 things in the menu (I hope, at least).
\r
354 # Fixed a bug with a certain invalid opcode causing a jump to be scanned
\r
355 when there isn't one (fixes Sabre Wulf).
\r
356 # Removed 2048 option for audio buffer.
\r
358 v0.9 (yes, it's still beta)
\r
360 NOTE: As some of you may be aware I'm pretty much tired of these
\r
361 unofficial releases by people (okay, mostly single person) who
\r
362 don't wish to follow my wishes. I'm in the process of asking this
\r
363 person to stop, in his own language. However, I want to make
\r
364 something clear. Look at the last six new features in this
\r
365 changelog. I added these TODAY. I could have done them at any
\r
366 time. But I didn't, because I spent many (dozens, quite possibly
\r
367 hundreds) hours debugging games that people want to play. I have
\r
368 always believed that this is far more important than spending time
\r
369 on new features. Frankly, I'm tired of my emulator being hacked on
\r
370 by other people, and if it doesn't stop I'm going to make this
\r
371 project closed source.
\r
373 Since I know this information is most visible when updated on the
\r
374 major sites, note that it is the news posters I am especially
\r
375 talking to. Next time you upload unofficial releases of my
\r
376 emulator (without even knowing what's changed) bear in mind that
\r
377 you're only encouraging me to stop working on this. If you want
\r
378 to pick sides between me and unofficial devs, be my guest. I'll
\r
379 let you decide by the contents of this release who's doing more
\r
382 Oh, and if you downloaded a version of gpSP that has more than
\r
383 "gpSP" in its name then you're using one of their versions. Shame
\r
384 on them for not even removing this threatening message, and shame
\r
385 on you. Unless you're using a port I endorse (GP2X, Dreamcast, etc),
\r
386 in which case everything's good.
\r
389 # Fixed stereo output being reversed.
\r
390 # Fixed a bug causing misaligned errors on 8bit writes to the gbc
\r
391 audio channel 3 wave data (fixes various Super Robot Wars games)
\r
392 # Fixed DMA with garbage in their upper 4 bits (fixes a crash in
\r
394 # Added double buffering to the rendering, removes line artifacts.
\r
395 Big thanks to Brunni for the idea.
\r
396 # Fixed a bug preventing some SRAM based games from saving (fixes
\r
398 # Fixed a bug causing part of EWRAM to potentially get corrupted if
\r
399 code segments loaded in EWRAM cross 32KB boundaries (fixes
\r
401 # Fixed a bug causing games using movs pc in user mode (very bad
\r
402 behavior) to crash. Fixes Colin McRae Rally 2.0.
\r
403 # Improved timing a bit more. Fixes GTA Advance.
\r
404 # Fixed a sprite clipping bug (fixes crash in third boss of Zelda:
\r
406 # Increased translation buffer size significantly (fixes Donkey Kong:
\r
408 # Fixed a dynarec bug causing add pc, reg to not work in Thumb code
\r
409 (fixes crash in DBZ:LoZ, seems to fix crashes in battle in Golden
\r
410 Sun, probably fixes other games)
\r
411 # Made sprites using tiles < 512 not display in modes 3-5 (fixes
\r
412 a couple minor graphical bugs)
\r
413 # Removed abort on instruction 0x00000000 hack, was breaking a
\r
414 certain bugged up game (Scurge)
\r
415 # Fixed bug in flags generating variable logical shifts (fixes
\r
417 # Fixed unaligned 16bit reads (fixes DBZ:LoZ in game)
\r
418 # Redid contiguous block flag modification checking AGAIN and
\r
419 hopefully got it right this time (fixes Mario vs. Donkey Kong)
\r
420 # Redid ldm/stm instructions, fixing some cases (along with the
\r
421 timing improvements fixes Mario & Luigi)
\r
422 # Fixed 14bit EEPROM addressing (hopefully fixes saving in a lot
\r
424 # Completely redid memory handlers, accurately emulates open and
\r
425 BIOS reads now. Fixes Zelda: Minish Cap (roll bug, last dungeon),
\r
426 Rayman, MMBN 1 (last dungeon), probably others.
\r
427 # Fixed a minor graphical glitch on the edges of the screen
\r
428 (thanks Brunni and hlide for the help!)
\r
429 # Fixed crash on loading savestates from files of games not currently
\r
430 loaded, but be sure you have the exact file you loaded it from or
\r
432 @ New memory handlers should provide performance boost for games
\r
433 that access VRAM significantly (ie 3D games)
\r
434 @ Added dead flag elimination checking for logical shifts, probably
\r
435 doesn't make a noticeable difference but should have been there
\r
437 + Added rapidfire to the button mappings.
\r
438 + Added auto frameskip. Removed fractional frameskip (don't think
\r
439 it's very useful with auto anyway). Select auto in the graphics/
\r
440 sound menu to activate it; frameskip value will act as the
\r
441 maximum (auto is by default on). Thanks again to Brunni for some
\r
442 help with this. Frameskip options are game specific.
\r
443 + Added vsync to the rendering. Only occurs when frames aren't
\r
444 skipped. Seems to reduce tearing at least some of the time.
\r
445 + Added non-filtered video option.
\r
446 + Cheat support (Gameshark/Pro Action Replay v1-v3 only), still
\r
447 in early stages, doesn't support everything; codes may cause
\r
448 the game to crash, haven't determined yet if the codes are bad
\r
449 or the implementation is. See cheat section for more information.
\r
450 + Added ability to change audio buffer size. Does not take affect
\r
451 until you restart the game.
\r
452 + Added analog config options.
\r
453 + Added ability to set analog sensitivity and turn off analog.
\r
454 + Added ability to change the clock speed. This is a game specific
\r
455 option. Try lower speeds w/auto frameskip to save battery life.
\r
456 + Fixed savestate speed on crappy Sony sticks.
\r
458 (legend: # bug fix, + feature addition, @ optimization)
\r
460 v0.8 - ("unlocked" beta)
\r
462 NOTE 1: It has come to my attention that there are actually BIOSes
\r
463 out there that are being used that cause some games to not work.
\r
464 The BIOS md5sum listed here is for the BIOS actually in GBAs and
\r
465 is as accurate as you'll get, (if you have a GBA and a flashcart
\r
466 you can dump it yourself, see http://wiki.pocketheaven.com/GBA_BIOS)
\r
468 NOTE 2: Since I know this is as far as a lot of people here I have a
\r
469 little request. Please, please, (I'd italicize this if I could)
\r
470 please stop constantly asking me when the next release will be,
\r
471 what it'll have, etc. And while you're at it, please stop asking me
\r
472 to implement wi-fi multiplayer, cheat support, or fix all of your
\r
473 games. Some things will happen in due time, other things might not
\r
474 ever happen. I devote about as much time as I can to this emulator
\r
475 and I carefully include as much as I can in releases to try to
\r
476 minimize the number of people who will nag me next time (erm, I
\r
477 mean, to make the most people happy), so I don't release every other
\r
478 day or anything like that. Sorry that I can't release once a week,
\r
479 but I'm a lot busier now than I was when I was first developing this
\r
480 emulator. Good thing I got the first version out before that, wasn't
\r
483 Congratulations, you made it this far! Now read the rest of the this
\r
487 # Fixed bug in dead flag elimination, "alt" version no longer needed.
\r
488 # Fixed EEPROM saves being saved as 32kb instead of 512bytes/8kb
\r
489 + 32MB ROM support has been added. ROMS are "demand loaded" as
\r
490 necessary and page swapped out; there might be a small loading lag,
\r
491 but I have yet to ever really notice anything.
\r
492 NOTE: 32MB ROM support only works for unzipped ROMs.
\r
493 + Save states have been added. See the save state menu for save/load
\r
495 + Support for the real-time clock (RTC) chip in Pokemon cartridegs
\r
496 and other games. The implementation is based off of VBA's, whatever
\r
497 notes on gbadev I could find, and some of my own reverse engineering
\r
498 of what the games do... it might not be totally correct. Also,
\r
499 setting the time does not work.
\r
500 + Per-game configuration. Currently this only saves frameskip and
\r
501 frameskip variation options.
\r
502 + Removed the flash type option from the menu and instead added it
\r
503 to game_config.txt. Hopefully got everything - let me know if you
\r
504 find something that isn't there. It's pretty easy to add them if you
\r
506 + Added a display in the upper left-hand corner to indicate when
\r
507 fast-forward is on.
\r
508 + Added button bindings for save/load state.
\r
509 @ Found a fix of StrmnNrmn proportion: far too much unnecessary mutex
\r
510 synchronization was going on. Removing the two offending lines of
\r
511 code gave a massive speed boost for free. Enjoy.
\r
513 v0.7 - (beta than ever)
\r
515 # Fixed a dynarec bug involving flags generating functions in
\r
516 contiguous conditional blocks. Fixes music in Super Mario
\r
518 # Fixed a dynarec bug where Thumb mov imm instructions wouldn't
\r
519 set flags. Fixes Zelda: Minish Cap, Megaman Battle Network,
\r
520 probably others. Comes at a slight speed cost.
\r
521 # Fixed a MIPS dynarec bug where some delay slots might not
\r
522 get filled rarely, causing chaos. Don't know if it improves
\r
524 # Improved self-modifying code detection. Makes Golden Sun,
\r
525 Golden Sun 2, and Madden 2007 sorta work but excrutiatingly
\r
526 slowly. Looking for a game-specific workaround for this - if you
\r
527 want to play these games you'll have to wait for now :(
\r
528 # Fixed a bug causing the interrupt disable flag to go down
\r
529 when SWIs are entered, causing crashes/resets. Fixes
\r
530 Super Mario Advance 2-4.
\r
531 # Fixed menu crashing when strings with certain characters are
\r
532 printed (for instance going to the menu after loading the
\r
534 # Accidentally forgot to render win0 + win1 + objwin when all
\r
535 active at the same time, many weeks ago. Added that, should fix
\r
536 some parts in games that had frozen screens.
\r
537 # Fixed some issues with gpsp.cfg needing to be present and
\r
538 corrupting, hopefully. At the very least sanity checks are
\r
539 performed on the config file.
\r
540 # Made it so assigning the frameskip button to something besides
\r
541 triangle actually worked as expected.
\r
542 # Fixed ability to restart current game if nothing is loaded
\r
544 # Added interrupt on cpsr modification support to the dynarec
\r
545 (fixes backgrounds in Castlevania: Harmony of Dissonance)
\r
546 # Added open addressing for ldm/stm instructions (fixes
\r
547 Super Mario Advance 3)
\r
548 # Improved cycle accuracy a little. Don't know of anything this
\r
549 fixes, but games with idle loops will run a little better w/o
\r
550 idle loop elimination (but should still be added when possible)
\r
551 # Fixed some bugs causing sound to play sometimes when it shouldn't.
\r
552 @ Added dead flag elimination for Thumb code. May possibly have
\r
553 noticeable performance increases (Thumb emited coded size can
\r
554 have a reduction of 20% or more)
\r
555 @ Added code generation for divide SWI. May have a small speed
\r
556 increase in some games.
\r
557 + Added analog nub support (special thanks to psp298 for the
\r
559 + Added fractional frameskip. Go below 0 to get them. A frameskip
\r
560 of 1/2 for instance means render 2 out of every 3 frames, 2/3
\r
561 means render 3 out of every 4 frames, etc. Possibly useful for
\r
562 games that are not quite fast enough at fs0 but fullspeed at
\r
565 v0.6 - (still beta quality, look out for new bugs)
\r
567 NOTE: Please include gpsp.cfg with EBOOT.PBP, this shouldn't be
\r
568 necessary but I think it is right now.
\r
570 # Fixed a nasty bug that shouldn't have made it into the initial
\r
571 release; a lot of games that TECM.. erm.. crash won't anymore.
\r
572 NOTE: This doesn't mean that no game will ever crash, freeze,
\r
573 otherwise not work.
\r
574 # Fixed some crashes in the GUI and the ability to "go up" past
\r
575 ms0:/PSP. Made the "go up" button square like it was supposed to
\r
576 be (instead of cross).
\r
577 + There's now a menu that you can access, by default press right
\r
578 while holding down triangle for the frameskip bar.
\r
579 + Menu option: resize screen aspect ratio, the default is now
\r
580 "scaled 3:2" which makes it look more like a normal GBA. You
\r
581 can use "fullscreen" (what it was like before) or "unscaled 3:2"
\r
582 (tiny but pixel for pixel like a GBA)
\r
583 + Menu option: You can now load new games while the current one
\r
585 + Menu option: You can now restart the currently running game.
\r
586 + Menu option: Frameskip variation - this defaults to "uniform"
\r
587 whereas it defaulted to "random" last release. Basically, turn
\r
588 it on random if you find that frameskip causes flickering
\r
589 animations to make things disappear. Other than that it will
\r
590 generally look better on uniform.
\r
591 + GUI and file loading now have "auto repeat" on the buttons so
\r
592 they're not such a pain to navigate.
\r
593 + Menu option: Added support for 128KB flash ROM, some games
\r
594 require it (Pokemon Firered/Leaf Green, Super Mario Advance 4),
\r
595 turn it on before running the game to make sure it works.
\r
596 NOTE: There are some versions of these ROMs that have been
\r
597 hacked to get around their 128KB flash, and may not even work
\r
598 properly at all. Look out for them, these games should save
\r
599 128KB save files after you set the setting to it, IF they use
\r
601 + Menu option: Added ability to make the .sav files only update
\r
602 when you exit the emulator, use with extreme caution (in other
\r
603 words, it's not a good idea to use something like this in beta
\r
604 quality software if you care about your saves). Does NOT update
\r
605 if you exit through the home button, don't use the home button
\r
606 if you can help it.
\r
607 + Zip support thanks to SiberianSTAR. It will load the first file
\r
608 with the extension .gba or .bin that it finds.
\r
609 + Menu options are saved to gpsp.cfg. Note that it does not save
\r
610 frameskip options or flash ROM options because these are very
\r
611 per game particular.
\r
612 + The emulator will now try to save backup files to something
\r
613 more matching the backup size than a fixed 64KB.
\r
614 @ Loading ROMs and the auto save of the .sav files is MUCH faster
\r
615 now. Thanks for the heads up on how to improve this from pollux!
\r
616 @ While coding for the screen resize code I found that SDL just
\r
617 wasn't cutting it and had to code for the GU myself. Turns out
\r
618 the new code is faster (but because it is render code any
\r
619 improvement will be diminished to nothing as frameskip is
\r
620 increased). Special thanks to Zx-81 for the tips on this one
\r
621 and for his GU code in the PSPVBA source as an example.
\r
622 @ Added some games to game_config.txt. Note that not all versions
\r
623 of these ROMs will work with these options, try to use the USA
\r
624 version if possible.
\r
626 8-19-2006 v0.5 - Initial release (public beta quality)
\r
631 gameplaySP (gpSP for short) is a GBA emulator written completely from
\r
632 scratch. It is still pretty young (only having started a 3 months prior
\r
633 to the first release) and thus rather immature, but it does a decent
\r
634 job of playing a number of games, and is being improved upon somewhat
\r
635 regularly. It is currently somewhat minimalistic, in the sourcecode,
\r
636 presentation, and features. Its number one focus is to deliver a GBA
\r
637 gaming experience in the most playable way that PSP can manage, with
\r
638 frills being secondary (although still a consideration, at least for
\r
641 Having said that, optimization was the important way in achieving this
\r
642 goal, with overall compatability being a near second. Because of this
\r
643 some games may not run at the favor of running more games significantly
\r
644 better. Of course, the compatability will improve with time. The
\r
645 compatability in the current version (0.8) is perhaps around 80%
\r
646 (assuming the correct BIOS image is used).
\r
648 Many games will run at their best out of the box, but some games will
\r
649 run very slowly unless idle loops are taken care of. There is a supplied
\r
650 ROM database, game_config.txt, that gives idle loop targets and other
\r
651 settings that may help a game to run better (or at all) on a per-game
\r
652 basis. Currently (as of version 0.8) a few dozen games are on this list,
\r
653 mostly only USA versions. This list will continue to be updated; there's
\r
654 no real telling exactly how many of the ~2500 GBA games will need to
\r
657 gpSP currently requires an authentic GBA BIOS image file to run. It will
\r
658 make no effort to run without one present; this file is 16kb and should
\r
659 be called gba_bios.bin and present in the same location as the EBOOT.PBP
\r
660 file. Please do not ask me where to obtain this, you'll have to look
\r
661 online or grab it from a GBA. Note that it is not legal to have this file
\r
662 unless you own a GBA, and even then it's rather gray area.
\r
668 gpSP mostly emulates the core Gameboy Advance system. As of right now it
\r
669 does not emulate any special hardware present on various GBA cartridges.
\r
674 GBA CPU: All ARM7TDMI ARM and Thumb mode opcodes except block memory w/
\r
675 s-bit (probably aren't used in GBA games)
\r
676 Video: Modes 0, 1, 2 almost completely, basic 3-5 support, sprites,
\r
677 windows/OBJ windows
\r
678 Interrupts: HBlank, VBlank, all timers, all DMA channels, keypad
\r
679 DMA: Immediate, HBlank, VBlank, sound timer triggered
\r
680 Sound: Both DirectSound channels and all 4 GBC audio channels
\r
681 Input: Basic GBA input delivered through PSP controls
\r
682 Cartridges: Currently supports ROMs up to 32MB in size (the maximum for
\r
683 GBA) with the technique of ROM page swapping to fit within PSP's RAM.
\r
684 Backup: 32/64kb SRAM, 64/128kb flash, 512bit/8kb EEPROM
\r
685 RTC: The real-time clock present in cartridges such as most of the
\r
686 Pokemon games and some others.
\r
691 Video: No mosaic, bitmap modes lack color effects (alpha, fades),
\r
692 there might be some minor inaccuracies in blending...
\r
693 Cycle accuracy: Very cycle innacurate; CPU is effectively somewhat
\r
694 overclocked, meaning games with rampant idle loops will probably run
\r
695 rather poorly. DMA transfers effectively happen for free (0 cycle).
\r
696 Please do NOT use gpSP as a first source for developing GBA homebrew,
\r
697 try No$GBA instead.
\r
700 Additional features it has:
\r
701 - The ability to attempt to run games at faster than GBA speed (sometimes
\r
702 they can end up a lot faster, other times not so much)
\r
703 - Savestates: the ability to save a game's state to a file and resume
\r
704 playing where you left off later.
\r
705 - Mild cheat support
\r
708 Features that it doesn't have (please don't ask me to implement these!)
\r
709 - Wi-fi multiplayer
\r
714 The default control scheme is very simple. If you don't like it you can
\r
715 change it in the configuration menu.
\r
717 At the ROM selection screen:
\r
719 Up/down: navigate current selection window.
\r
720 Left/right: switch between file window and directory window.
\r
721 Circle/start: select current entry.
\r
722 Square: go one directory up.
\r
726 Up/down/left/right: GBA d-pad
\r
727 Circle: GBA A button
\r
728 Cross: GBA B button
\r
729 Square/start: GBA start button
\r
730 Select: GBA select button
\r
731 Left trigger: GBA left trigger
\r
732 Right trigger: GBA right trigger
\r
733 Triangle: Adjust frameksip
\r
735 In frameskip adjustment:
\r
737 Hold down triangle to keep up, press up/down to increase/decrease
\r
738 frameskip, respectively. Press down at 0 to change to auto, and up
\r
739 at auto to change to 0.
\r
743 Up/down: navigate current menu.
\r
744 Left/right: change value in current menu selection (if a value is present)
\r
745 Circle/start: select current entry (see help for entry to see what this means)
\r
746 Square: exit the current menu.
\r
751 The purpose behind frameskip is to cause the emulator to not render every
\r
752 frame of graphics to make the emulation closer to fullspeed. Many games will
\r
753 run fullspeed without skipping any frames, however, some (particularly more
\r
754 graphically demanding ones) will require this.
\r
756 Frameskip can be set to two forms, either auto or manual. Auto will attempt
\r
757 to skip only as many frames as necessary to make the game full speed, and
\r
758 will not skip more than 4 in a row no matter what speed the game runs at
\r
759 (at this point the benefits of frameskip yield diminishing returns).
\r
761 It is recommended that you keep frameskip on auto, but manual is maintained
\r
762 as an option if you want it and works as follows:
\r
764 Manual frameskip will only render one out of every (n + 1) frames, where n
\r
765 is the current frameskip value (so 0 will render everything). Increasing
\r
766 the frameskip can improve speed, especially with very graphically
\r
772 Currently, gpSP supports some functionality of Gameshark/Pro Action Replay
\r
773 cheat codes. To use these, you must first make a file with the same name
\r
774 as the ROM you want the cheat code to apply to, but with the extension .cht.
\r
775 Put this file in the same directory as the ROM. To make it use a normal
\r
776 text editor like notepad or wordpad if you're on Windows.
\r
778 To write a code, write the type of model it is, gameshark_v1, gameshark_v3,
\r
779 PAR_v1, or PAR_v3. gameshark_v1/PAR_v1 and gameshark_v3/PAR_v3 respectively
\r
780 are interchangeable, but v1 and v3 are not! So if you don't know which
\r
781 version it is, try both to see if it'll work.
\r
783 Then, after that, put a space and put the name you'd like to give the cheat.
\r
785 On the next several lines, put each cheat code pair, which should look like
\r
790 Then put a blank line when you're done with that code, and start a new code
\r
791 immediately after it. Here's an example of what a cheat file should look
\r
795 gameshark_v3 MarioInfHP
\r
798 gameshark_v3 MarioMaxHP
\r
801 gameshark_v3 InfHlthBat
\r
807 gameshark_v3 StopTimer
\r
811 After you have written the .cht file, you have to enable the cheats
\r
812 individually in the game menu. Go to the Cheats/Misc menu, and you will
\r
813 see the cheats; turn them on here. You may turn them on and off as you
\r
814 please, but note that some cheats may still hold after you turn them off,
\r
815 due to the nature of the system. Restart to completely get rid of them.
\r
819 This is still very work in progress! I basically added this in only 1.5
\r
820 or so hours, and I don't have a lot of time right now to work on it
\r
821 before releasing. So I'll probably improve it later.
\r
823 Not all of gameshark's features are supported, especially for v3. Only
\r
824 basic cheats will work, more or less.
\r
826 Cheats may be unstable and may crash your game. If you're having problems
\r
827 turn the cheats off.
\r
829 Really, there's no guarantee that ANY cheats will work; I tried a few and
\r
830 some seem to work, others are questionable. Try for yourself, but don't
\r
831 expect anything to actually work right now. Do expect this feature to
\r
832 improve in future versions.
\r
836 -- Frequently Asked Questions --
\r
838 Q) How do I run this on my PSP?
\r
840 A) Provided is an EBOOT.PBP which will run as is on a 1.0 firmware
\r
841 PSP or custom firmware that can run unsigned EBOOTs. On 1.5 firmwares
\r
842 you must use a kxploit tool to run it (try SeiPSPtool). On 2.0
\r
843 firmwares and higher further exploits must be used - see
\r
844 http://pspupdates.qj.net/ for more information. Note that I have NOT
\r
845 tested this emulator on any firmware version besides 1.5, and it's
\r
846 very possible that it doesn't run well, or at all on higher versions.
\r
847 Therefore I strongly recommend you downgrade if possible, and use
\r
848 Devhook to run games that require > 1.5 version firmwares.
\r
850 Be sure to include in the same directory as the EBOOT.PBP file the
\r
851 game_config.txt file included and the gba_bios.bin file which you
\r
852 must provide yourself.
\r
854 gpSP does not run on PSPs with version 2.71 or higher firmware yet,
\r
855 nor does any other homebrew executable.
\r
858 Q) What is a BIOS image file? Why do I need it to run gpSP? Other GBA
\r
859 emulators don't require this...
\r
861 A) The GBA BIOS image file is a copy of a ROM on the GBA system that
\r
862 has code for starting up the GBA (it shows the logo), verifying the
\r
863 game, and most importantly, providing utility functions for the games
\r
864 to use. It is the latter that gpSP needs the BIOS present for. It's
\r
865 possible to replace all of these functions with equivilent code, but
\r
866 this will take time - in the future gpSP may not require a BIOS image.
\r
869 Q) I can't find this BIOS image.. please send it to me.
\r
871 A) Sorry, but you're on your own. I won't send you a BIOS or tell you
\r
872 where to get one (unless you want to rip it from a GBA yourself, in
\r
873 which case I'll just give you the same link at the top). I can't do
\r
874 this because it's not legal to send it around and I don't want to
\r
875 get a reputation for illegally distributing BIOS images.
\r
878 Q) How do I know I have the right BIOS?
\r
880 A) If you have md5sum you can check if it has this hash:
\r
881 a860e8c0b6d573d191e4ec7db1b1e4f6
\r
882 That BIOS should work fine. I think that some others work fine too,
\r
883 although I haven't confirmed this with absolute certainty. It's also
\r
884 theoretically possible to use custom (and free) BIOS replacements,
\r
885 but I don't know of any publically availablone ones.
\r
887 As far as I'm aware there are two BIOSes floating around, I doubt
\r
888 you'll get one that isn't one of those two. There's a very easy way
\r
889 to determine which one you have - just look at the very first byte in
\r
890 a hex editor. The correct BIOS begins with 0x18, the buggy BIOS begins
\r
894 Q) My favorite game won't run.
\r
896 A) There probably isn't anything you can do about this, although a
\r
897 change to game_config.txt might help. gpSP is still an emulator in
\r
898 its infancy so the compatability is not superb. I don't have time
\r
899 to test too many games so I'm releasing it as a public beta to get
\r
900 a feel for some things that don't work. The next version could
\r
901 perhaps fix it, or it might never run. There are always other
\r
902 emulators of course, please try one.
\r
904 However, before nagging me there is one thing I recommend you try,
\r
905 and that is to add the option "iwram_stack_optimize = no" for the
\r
906 game in game_config.txt. See the file itself for more information
\r
907 on how to do this. If this fixes your game (and it's not already
\r
908 in the game_config.txt) please tell me about it.
\r
911 Q) My favorite game is very slow.
\r
913 A) Emulating GBA takes a number of resources and getting it done well
\r
914 on PSP is no simple task by any means. Some games are just going to
\r
915 overwhelm the emulator completely. Of course, there is one special
\r
916 case of game (a lot of early generation games fall under this
\r
917 category) that can be made much faster by a simple addition to the
\r
918 game_config.txt file. Wait for a new version of this file or the
\r
919 next version of the emulator and the game may be improved.
\r
921 That aside, there are still numerous optimizations that can be done,
\r
922 and I sure you future versions will be faster (I just can't tell you
\r
925 Also, a lot of games will be sped up considerably by adding an
\r
926 idle_loop_eliminate_target line for it in game_config.txt. There
\r
927 are some more obscurer options there that can improve speed too. If
\r
928 the game is VERY slow there might be something wrong with its
\r
929 emulation that can be improved. For instance, if you can't get a game
\r
930 to run fullspeed on any frameskip you should e-mail me about it.
\r
933 Q) Some games run fullspeed but the sound is messed up. Why?
\r
935 A) At least 9 out of 10 times it means the game isn't really running
\r
936 full speed, but just that you can't notice the difference. Increasing
\r
937 frameskip will almost always improve sound quality in these
\r
938 situations, to a certain point (after around frameskip 3 you
\r
939 probably won't be seeing many more returns if it isn't already
\r
940 fullspeed). The rest of the time it means there's a bug somewhere else
\r
941 in the emulator, probably in the CPU core. Chances are that all you
\r
942 can do is wait for it to be fixed in a later release.
\r
945 Q) The emulator crashed!
\r
947 A) Most games that don't run will probably take the emulator down with
\r
948 it, or it could be an emulator bug completely unrelated to the game
\r
949 (but unlikely). Press home and wait for the next version.
\r
951 There is some information that comes up when the game crashes. This
\r
952 information may be slightly useful to me, but chances are it
\r
953 usually won't be all that interesting.
\r
955 These days games are more likely to exit with a "bad crash" error.
\r
956 This number is possibly useful to me, but to debug a game I'll have
\r
957 to reproduce the crash anyway. When this happens it's probably due to
\r
958 a bug in the CPU core that hasn't been fixed yet.
\r
961 Q) Why won't my game save?
\r
963 A) The game might need 128KB flash turned on and might not be listed in
\r
964 game_config.txt. See game_config.txt for more information regarding
\r
965 this. Be sure to include game_config.txt with the EBOOT.PBP file.
\r
967 Other games might simply have bugs in the save support. For now, use
\r
968 savestates as an alternative if you can't save.
\r
971 Q) How do I change sound quality?
\r
973 A) Right now, you can't. For those wondering, sound is locked at 44.1KHz
\r
974 (sounds a bit high? It is, but it's currently necessary to play
\r
975 everything correctly). I don't have any plans to allow changing this
\r
976 right now, because I don't think there's really much reason to be
\r
977 able to (it'd be a tiny speed boost at best and I don't think SDL even
\r
978 allows for anything besides this sampling rate on PSP)
\r
981 Q) What is this emulator's name?
\r
983 A) Um.. what? It's gameplaySP, isn't it? You call it gpSP for short.
\r
984 Somehow the name can't have the acronyms gbSP, gbapSP, or really
\r
985 just about anything else you feel like giving it. Oh, and if you
\r
986 really want to make me happy get the capitalization right too.
\r
987 That's gpSP, not gPSP, GPsp.. you get the idea.
\r
990 Q) Does gpSP run Gameboy/Gameboy Color games? Will it later?
\r
992 A) No. Even though GBA can run these games it uses separate hardware
\r
993 that proper GBA games have no access to (save for the audio chip),
\r
994 and thus there's no point including it in a GBA emulator (it
\r
995 doesn't help run GBA games). I recommend using a GB/GBC emulator
\r
996 like Rin for playing these games. It'll probably give you a lot
\r
997 more options anyway. gpSP will never actually emulate GB/GBC
\r
998 games. You'd may as well be waiting for it to emulate PS2 games...
\r
999 (that was an analogy. gpSP won't ever emulate PS2 games. >_>)
\r
1002 Q) Other emulators use the PSP's graphical hardware to accelerate the
\r
1003 video emulation. Is this possible for gpSP?
\r
1005 A) I'm honestly not too sure at this point. It's definitely a rather
\r
1006 complicated procedure, and I don't think it'll be possible to
\r
1007 accurately accelerate alpha blending. On the other hand, affine
\r
1008 transformations could perhaps receive a speed boost this way. Any
\r
1009 solution would have to be hybrid hardware/software, which might be
\r
1010 possible due to the nature of the PSP's VRAM. Maybe someone will
\r
1011 be willing to help me think of possibilities here?
\r
1013 But don't bother of you're just going to tell me to render a list
\r
1017 Q) Other emulators use the PSP's second CPU to offload the sound
\r
1018 emulation. Is this possible for gpSP?
\r
1020 A) Yes, but it wouldn't improve it nearly as much as say, SNES9x TYL.
\r
1021 This is because most of the processing that goes into sound on a GBA
\r
1022 game is done in the CPU, not in dedicated audio hardware. It could
\r
1023 help a little, but probably not a lot. Maybe enough to be worthwhile.
\r
1024 It might also be possible to split the video rendering to the main
\r
1025 CPU and the main emulation to the secondary one, but there are a lot
\r
1026 of coherency issues involved.
\r
1029 Q) I heard gpSP can only load games 16MB or smaller in size. Is this
\r
1030 true? What about zipped games?
\r
1032 A) As of version 0.8 gpSP can play 32MB ROMs. However, they must be
\r
1033 unzipped. The reason for this is that parts of the ROM are constantly
\r
1034 loaded to memory as needed, and for this to be as fast as possible the
\r
1035 ROM has to be present on the memory stick in raw format.
\r
1037 You might be wondering, why not just have gpSP unzip the ROM to a file
\r
1038 then delete the file when it is done? The reason why is because this
\r
1039 would impose a "hidden" requirement of 32MB on the user that very
\r
1040 likely may not be there. Furthermore, there are only a few 32MB games
\r
1041 that anyone actually wants to play. If you only have one 32MB game on
\r
1042 your memstick then it'd actually require signifnicantly more free space
\r
1043 to hold both the ROM and the 32MB raw file. With 2 32MB ROMs you only
\r
1044 gain a around 10-25MB of free space, depending on how effective the
\r
1048 Q) Savestates? From other emulators??
\r
1050 A) See the savestates option in main menu. gpSP will probably never
\r
1051 support savestates from other emulators, there's just too much in the
\r
1052 way of emulator specific data in them.
\r
1054 Savestates are currently 506,943 bytes. They would be a little smaller
\r
1055 without the snapshot, but I find that very useful and it wouldn't help
\r
1056 size immensely. Compression would help, but I wanted the size to be
\r
1057 constant so you knew exactly how much you could hold and to improve
\r
1061 Q) What's with the zip support?
\r
1063 A) I hear stories that some games work unzipped and not zipped, so you
\r
1064 might want to try unzipping them if it gives you problems. You also
\r
1065 might want to try making fresh zips with WinRAR - users have
\r
1066 reported some higher success rates doing this.
\r
1069 Q) What's with the config file? Should I make it read only?
\r
1071 A) There was a bug in version 0.6 that caused the config file to not
\r
1072 get updated or get corrupted sometimes. Hopefully this is fixed now,
\r
1073 but if it DOES get corrupted making it read only can prevent this
\r
1074 from happening in the future.
\r
1077 Q) So when WILL the next version be released?
\r
1079 A) Sorry, but I almost never announce release dates. Furthermore, I'll
\r
1080 probably be pretty hush hush on internal development, just to keep
\r
1081 people from nagging me about it and building too much suspense.
\r
1084 Q) I don't like this emulator. Are there other alternatives?
\r
1086 A) Yes. Try PSPVBA by Zx-81 (http://zx81.dcemu.co.uk/). Overall I doubt
\r
1087 the compatability is significantly higher than gpSP's anymore, but
\r
1088 I'm sure there are some games it runs that gpSP doesn't.
\r
1091 Q) I heard there was a version of gpSP for PCs. Is that true?
\r
1093 A) I developed this emulator internally on PC. It might have a speed
\r
1094 advantage over other PC GBA emulators, although the PSP version has
\r
1095 more sophisticated optimizations. Most people have fast enough
\r
1096 computers to run better GBA emulators for PC and gpSP lacks some
\r
1097 important features (screen resizing) that the PSP version kinda
\r
1098 hides. Even though gpSP spent a majority of its development
\r
1099 gestation as a PC app it was always developed with the PSP in mind,
\r
1100 so the PC version will probably not see the light of the day unless
\r
1101 I get overwhelming demand for it. It is, however, possible to
\r
1102 build it from the source. But I request that you don't distribute
\r
1103 such builds. If you happen to find one, bear in mind that I don't
\r
1104 offer any support for it, and as far as I'm concerned it won't
\r
1108 Q) I hear there's a version of gpSP for other platforms too, like
\r
1109 Dreamcast. And I hear they're slow! What gives?
\r
1111 These are ports, done by other people (or maybe myself?). This is
\r
1112 possible because gpSP is open source and its base version is fairly
\r
1113 portable, but to run fast enough on anything but platforms quite a
\r
1114 bit faster than PSP it at least needs a CPU specific dynarec backend.
\r
1116 I don't (necessarily) maintain all builds of gpSP, so you'll have to
\r
1117 contact the authors of these ports for more information. That
\r
1118 notwithstanding, I try to get as involved in other ports of gpSP as
\r
1122 Q) I want to modify gpSP. How can I do this, and am I at liberty to do
\r
1125 A) Yes, you are, under the terms of the GPL (see the included
\r
1126 COPYING.DOC). You can download the sourcecode from whereever you
\r
1127 downloaded this; if you can't find it please e-mail me and I'll give
\r
1128 you a link to it. I would vastly appreciate it if you contacted me first
\r
1129 before forking my project, especially if you're just looking to gain
\r
1130 recognition without adding much to it. It's better to keep all changes
\r
1131 tidy in one branch of development.
\r
1133 I would like to stress this a little more seriously (hopefully those
\r
1134 interested are reading this). Although you are legally entitled to
\r
1135 release your own forks of gpSP it would be much more benficial to me,
\r
1136 to you, and to the users of this program if you instead tried working
\r
1137 with me to get your changes incorporated into the next version. I
\r
1138 really don't feel like competing with other builds of my source
\r
1139 anymore, so please do me a big favor and send me an e-mail if you want
\r
1140 to work with gpSP.
\r
1143 Q) How do I build gpSP?
\r
1145 A) make will build it. You need to have SDL for PSP installed, as well
\r
1146 as the standard PSP toolchain/PSPSDK and zlib. gpSP isn't much of a
\r
1147 "build it yourself" program so please don't bother me much about how to
\r
1148 build it unless you have a good reason for wanting to do so.
\r
1151 Q) What is with the version numbers?
\r
1153 A) Anything less than 1.0 means beta. Beta means that I still have major
\r
1154 plans for working on it, and that I don't fully back it as being
\r
1155 stable or reliable software. Of course, if it does hit 1.0, that doesn't
\r
1156 mean it'll be perfect. It just means I'll have spent a lot of cumulative
\r
1157 time working things out. The closer it gets to 0.9, the happier I am with
\r
1163 A) Very appreciated. exophase@gmail.com on PayPal. <3
\r
1166 Q) How can I contact you?
\r
1168 A) exophase@gmail.com, Exophase on AIM, exophase@adelphia.net on MSN. I
\r
1169 welcome IMs, but if you nag me a lot you'll make me sad inside. And
\r
1170 don't ask me for ROMs or the GBA BIOS. I figured this was common sense
\r
1171 but apparently not.
\r
1176 Exophase: main developer
\r
1177 siberianSTAR: zip support
\r
1178 psp298: analog nub code
\r
1180 Beta testers for 0.7:
\r
1187 Beta testers for 0.8:
\r
1193 Beta testers for 0.9:
\r
1194 RunawayPrisoner (my right hand man)
\r
1195 Veskgar (my left hand man)
\r
1198 -- Special thanks --
\r
1200 Quasar84: He's helped me in so many ways with this. We both kinda learned
\r
1201 GBA together, he did little demos for me and I got them emulated. It was
\r
1202 great trying out your more advanced code for your own projects once you
\r
1203 got to them, it was equally rewarding to see your work and to be able to
\r
1204 run it at the same time. Least of all I wouldn't have been able to do any
\r
1205 of this without your constant support and presence. I really owe this
\r
1208 gladius: You are an amazing GBA coder. I wouldn't have been able to get
\r
1209 through some tough parts without your help. Its been good talking about
\r
1210 ideas with you.. I'm sure you're glad to see that there's finally a GBA
\r
1211 emulator with dynarec ;)
\r
1214 Many, many others of course, probably too many to name, and I don't want
\r
1215 to make anyone feel bad by putting others above them (well, except those
\r
1216 two, heh) so if you think you should be on here, you probably should be!
\r
1217 Just pretend you are for now, and maybe I'll put you here next time.
\r
notaz.gp2x.de / gpsp.git / blob