It's also possible that whoever built the build people are testing on the RasPi did something like use an old compiler or may have even had compiler level optimization disabled entirely or perhaps set for "generic ARM" which will generate pretty crap code for an ARM1176JZF.įWIW, I'm not really fond of the SoC used on the RasPi, but it should perform OK. GCC's ARM backend is decent, but it's not as good as its x86 backend. Presumably, ARM Linux MAME is being built with GCC. If somebody wanted to hack on MAME to make it run better on ARM 1176, substantial improvements are probably possible, but I'd suspect most of the work in the "MAME on ARM" department is going to be focused on Cortex-A these days for use on modern smartphones, Beagle/Panda, etc.Īlso, it'll depend on what compiler you use some.
Note that CPU ISA makes a huge difference in the performance of MAME: some backends run much faster on AMD64 than IA-32 even on the exact same CPU due to things such as number of explicitly named registers. Even if there's no inline assembly, some of the "performance tricks" in the code may only work well on x86 and may actually hurt on ARM (there are other "tricks" that can go the other way, of course). MAME is also generally only hacked on by people looking to use it on x86 type CPUs. I will have to give it quite a bit more thought and figure it out before ordering graphics etc.
Galaga mame os x problems full#
I am still unsure which direction I want to take the cabinet, but am currently leaning more towards a full sized cabinet than the original coffee table idea. The other good news about transitioning into phase II of this project is that I have two joysticks, buttons, wire, etc on order for the cabinet. When I get home tonight my next round of work will center around making this look more acceptable. I think this is due to missing files from unzipping the ROMs.
Yes the menu is working and it launches the ROMs, but it doesn't give a preview or artwork or anything in the right hand pane for the ROM. I ended up having to manually add it to advMENU's config. After compiling and installing advMENU I had a bear of a time getting it to recognize that I had advMAME installed as an emulator. Back out to the internet with a wget command yielded advMenu's src. Luckily there are MAME front ends that I can utilize that will facilitate launching games etc. advMAME galaga, this is not very user friendly at all and would be a huge hassle once I have this in an arcade cabinet (since this computer will run without a keyboard). If you've played with advMAME or a command line based MAME emulator at all then you know launching a game involves something like. I was able to resolve the stutter and lag issues with Galaga this way and both Galaga and 1942 run flawlessly at this point: I had read about people overclocking these little boards with pretty good success, so back into the config files! I settled so far on a 200MHZ overclock (up from the stock 700MHZ to 900MHZ) on the processor and a 100MHZ overclock on the memory (up to 600MHZ). Unfortunately, the first run of this ROM was VERY slow and the audio was stuttering something fierce. After wgetting advanceMAME src and compiling it, I was able to run advMAME and was able to get the Galaga ROM running with minimal issue (after setting up a proper config etc): This little computer was consistently averaging 2.3 mbps from most of the locations I was downloading from online. As an aside, I was very impressed with the network transfer speed as well. A quick check of the GCC and compiler environments and another pleasant surprise they were already in place with all the required dependencies for me to be off and running. The next order of business was getting a MAME emulator up and running on this ARM platform. Upon first boot the RPI booted into a setup program:Īfter setting my environment variables, disabling graphical interface start-up, running updates, and rebooting I was presented with a fully functional Debian powered beast. I am quite surprised with how quick this little credit card sized computer is. When I got home from work today and began work on the project again, I was pleasantly surprised to see that the RPI would actually boot from the card: So it looked like the img of Debian for Raspberry Pi didn't properly transfer to my SD card, when in fact it was just taking forever.
0 kommentar(er)
