Main > Linux

current status of gentoo linux / advmame

<< < (5/16) > >>

Major Rock Hardy:
elvis, whammoed-

are you using fb in your latest projects?  or did you get tired of fighting it and switch to svgalib?  I'm beginning to think I'm going to do that since other emulators I want to run will support svgalib but I don't know of any that support fb...

Thanks,
Rock

whammoed:
The only reason I switched to svgalib was to get lower pclocks.

elvis:
I use SVGALib.  It was the first method I tried, and it worked, so I've used it ever since on all of my projects and never bothered to test FBDev out of sheer laziness. :)

From what I can see, SVGALib supports more chipsets too.  Not that it matters for most ATi/Nvidia owning people.

Major Rock Hardy:
K, thanks you two...

so I'm going about the SVGA path and I've run into a wierd message..

I downloaded svgalib-1.9.19 and advancemame-0.102.0... now, following desmatic's patch instructions on easymamecab, here are the results:

me@persephone /usr/src/svgalib-1.9.19 $ sudo patch -p1 < ../advancemame-0.102.0/contrib/mame/svgalib/svgalib-1.9.19-force.diff
patching file src/timing.c
patching file src/timing.h
me@persephone /usr/src/svgalib-1.9.19 $ sudo patch -p1 < ../advancemame-0.102.0/contrib/mame/svgalib/svgalib-1.9.19-radeon.diff
patching file src/drivers/r128.c
patch unexpectedly ends in middle of line
Hunk #4 succeeded at 862 with fuzz 1.

...
any thoughts about my fuzzy hunk?  :o

thanks,
Rock

whammoed:
I got errors when the radeon files were patching too.  I ignored them without issue and I am using a radeon.

Navigation

[0] Message Index

[#] Next page

[*] Previous page