Main > Linux
current status of gentoo linux / advmame
Major Rock Hardy:
--- Quote from: whammoed on January 11, 2006, 12:00:48 pm ---Are you able to change the 49 way mode with software in linux or are you just doing it manually with the button combos?
--- End quote ---
well, before striking out on this whole linux adventure, I secured an agreement w/ Randy that I will develop a version of the GPWiz49.exe windows program (the one that changes the board mode) - for linux. He's going to provide me with the codes that I need to send down the USB cable to the boards to change their mode automagically. I did a bit of searching and I found this:
http://lwn.net/Kernel/LDD3/
... which should help a great deal. There's a whole chapter on USB. I'm a big fan of O'Reilly books.
Looking at some of the advmame docs, it appears that the joystick mode of the original game is available from within advmame, so I'd basically write a script with a case statement in it. I'm sure that is an oversimplification, but that's what I have in mind currently.
whammoed:
Nice. Reminds me we need a way to control the ledwiz in linux too. Wonder if anyone is working on that?
Major Rock Hardy:
I'm not sure... shouldn't be too hard. For my cab, I am thinking of hooking up something like this:
http://www.noritake-elec.com/7000.htm
so it would show the joystick mode (if applicable - if not, spinner, TB, whatever), what buttons are used and their functions, etc. I know, I'm nuts, but I think it would be slick.
MotorHedJr:
Hi Major Rock and Elvis,
Major Rock -- Thanks for the permissions link.
Fellas:
The last thing I wanted to do with my AdvMAME Linux PC before I swapped it w/ my AdvMAME DOS PC was to create a bootsplash theme w/ a nice progress bar --That (and USB compatibility) were the two main reasons I wanted to switch to Linux.
Do you guys have (or intend to have) a bootsplash on your cabinets?
So after some research:
http://gentoo-wiki.com/HOWTO_fbsplash
It explains recompiling your kernel to add framebuffer support:
Device Drivers > Graphics support:
[*] Support for frame buffer devices
<*> VESA VGA graphics support
VESA driver type (vesafb-tng) --->
(HRESxVRES@FREQ) VESA default mode
# pick resolution@freq of your own here !
# 8pp is the only one supported for this time
# Ex: (1024x768@72)
that's what should be in the kernel...
my kernel shows:
Device Drivers > Graphics support:
[*] Support for frame buffer devices
<*> VESA VGA graphics support
VESA driver type (vesafb-tng) --->
( )vesafb
(X)vesafb-tng
What's up w/ the 'X' option? -- No matter I do I cannot put a 'M' or '*' in either option... Have you seen this before? I'm using an MSI HM4M-V mobo w/ a Matrox g400 video card... Anyway I re-complied the kernel (trying both options w/ the 'X') and it broke everything AdvMAME, SVGAhelper, startx... etc.
Man, what a bummer... I can rebuild everything (I took careful notes) but before I try anything w/ a boot splash again I wanted to check and see if this was even possible:
Can you run SVGAlib w/ FB support?
Could my kernel (2.6.12-r6) be broken for FB?
Why does X hate FB?
Thanks for any help -- you guys have been great...
MH Jr.
elvis:
1) The "X" means it's compiled direct into the kernel, and always loaded into memory. An "M" means it is a module, and needs to be loaded via startup scripts or manually after boot. I prefer having items loaded into the kernel direct. Modules are a waste of time, especially on a custom-built system.
2) You shouldn't use the VESA Framebuffer. It won't work with AdvanceMAME. You need to use the FrameBuffer driver specific to your video card (there should be ATI and Nvidia framebuffer drivers in the kernel).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version