Sounds like the driver is polling in some sort of a tight loop and soaking up all of
the available CPU. In other words, it sounds like it's the "driver's fault", not
xmame.
Hmm..... the driver's fault. Not the butler's fault. *tee hee*
On Tue, 18 Sep 2001 21:28:06 +0000 (GMT)
[EMAIL PROTECTED] wrote:
>
> Thanks Tom for your answer, but im using the gamecon driver for parallel
> port console joysticks and is working but the prosessor goes to 100%
> everytime i use the joystick and the emus goes slow as hell.
>
>
> Tom H. Warkentin writes:
>
> > [EMAIL PROTECTED] wrote:
> >
> > > Does anybody tryed the psx joystick under linux, because i tryed and works
> > > but when i try to play any emulator the emu goes slow as hell.
> > > Does anybody knows if this is normal or how do i solve this problem??, and
> > > xmame doesnt detect it even when i sent the /dev/js1 or /dev/input/js1 in
> > > command line
> > > TIA.
> >
> > I have a DualShock 2 controller working well in Linux. I am using the xmame
> > i386 joystick driver for Linux. I have a USB adapter that supports both the
> > PSX controller and the N64 controller. Both worked great pretty much out of
> > the box with kernel 2.4.6. If the controller wasn't plugged in when you
> > rebooted, just pull out the USB connection and plug it back in (assuming you
> > are using a USB adapter). This should reload the appropriate drivers. Also,
> > I have to set the PSX controller to analog mode before it works (the analog
> > mode gets turned off when rebooting). I use the following little perl script
> > to see if the joystick is working:
> >
> > #!/usr/bin/env perl
> >
> > use FileHandle;
> >
> > $| = 1;
> >
> > my $fh = new FileHandle;
> >
> > print "Trying /dev/js0... ";
> > $fh->open( "/dev/js0" ) || die "error: $!\n";
> > $fh->close;
> > print "done\n";
> >
> > If you see "Trying /dev/js0... done", then it usually means that everything
> > is working great (Note: my /dev/js0 is a symlink to /dev/input/js0). Then
> > all you have to do is configure the joystick in xmame but hitting the <TAB>
> > key while the emulator is running and mapping the buttons appropriately in
> > the controller setup menu.
> >
> > BTW, I think someone here mentioned that when you use the -jdev command line
> > arg with xmame, don't specify the numbers of the joystick device. In other
> > words if you want to use /dev/input/js1, use "-jdef /dev/input/js" to tell
> > xmame to try all the /dev/input/jsN devices to find joysticks. Maybe you did
> > this already but if you didn't, then that is probably why it didn't work.
> >
> > - Tom
> >
> >
> >
> >
> > _______________________________________________
> > Xmame mailing list
> > [EMAIL PROTECTED]
> > http://toybox.twisted.org.uk/mailman/listinfo/xmame
>
>
>
>
> _______________________________________________
> Xmame mailing list
> [EMAIL PROTECTED]
> http://toybox.twisted.org.uk/mailman/listinfo/xmame
_______________________________________________
Xmame mailing list
[EMAIL PROTECTED]
http://toybox.twisted.org.uk/mailman/listinfo/xmame
