Re: [Flightgear-devel] Re: [Flightgear-users] Slackware, USB, CH yoke
Andy Ross wrote: I've never looked at the kernel source. Presumably this would be a trivial fix, no? As always, write it and see.. :) A keyboard can be interrogated. A mouse outputs constant data and/or can be interrogated. A standard joystick does.. nothing. It can look like it's there when it's not, and it can look like it isn't when it is. And there are more than a few different formats of joystick, do you plan to load every possible driver, checking all the time, and then dump the ones not in use? What if they have TWO joysticks? Pick the one that moves? What if they hit the other one while picking up the one they want? How does your own software propose to reliably determine something that approaches near indeterminability? Trying to do this automatically will cause as many problems as it fixes. The USB can probably be done though, since it should have an ID string. You need to hurry up and write it, what is taking you so long? As always, everything seems quite 'trivial' to those who haven't actually tried to do it. Hurry up and build a running robot too while you're at it.. Alan ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: [Flightgear-users] Slackware, USB, CH yoke
Andy Ross writes: As always, everything seems quite 'trivial' to those who haven't actually tried to do it. Hurry up and build a running robot too while you're at it.. Plonk. Does anyone with a real clue have an answer for this? Sorry, not me. I was waiting until after I get finished up the flight simulator to start work on my running robot ... although my master's degree project involved parallel algorithms for pre-calculating paths for a 7 degree of freedom robotic arm and simulating the proposed motion. Does that count for anything? http://www.flightgear.org/~curt/research/ Curt. -- Curtis Olson HumanFIRST Program FlightGear Project Twin Citiescurt 'at' me.umn.edu curt 'at' flightgear.org Minnesota http://www.flightgear.org/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: [Flightgear-users] Slackware, USB, CH yoke
Jon Stockill wrote: There's no driver loaded - try modprobe hid;modprobe joydev as root, then see if js_demo shows the yoke working correctly. This misfeature annoys me to no end. Has anyone investigated why the kernel input modules understand keyboards and mice just fine, but don't have the sense to load joydev automatically when a joystick is plugged in? I've never looked at the kernel source. Presumably this would be a trivial fix, no? Sometimes it seems like we're the only major user of the joystick driver, and the kernel folks don't care about it... Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: [Flightgear-users] Slackware, USB, CH yoke
On Wed, Dec 17, 2003 at 09:59:51AM -0800, Andy Ross wrote: Alan King wrote: A keyboard can be interrogated. A mouse outputs constant data and/or can be interrogated. A standard joystick does.. nothing. A standard joystick* looks like an HID device, just like a mouse or [...] [* i.e. a USB one, like the ones you buy in stores these days and like A standard joystick port, old analog PC style (those that use the ns558.o) can also detect the number of axes connected, but not the number of buttons. It works by charging a capacitor through a resistor (RC circuit) and couting the time it takes. That time is dependent on the resistor, which in this case would be the potentiometer inside the connected joystick. If no joystick is present, the capacitor will never load, and this is what the software uses to determine whether a joystick is present. (this has given me some headaches with my homebuilt yoke... i had a loose wire so the driver never loaded :( :))) Regards, Manuel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
