On Tuesday 05 October 2004 6:29 am, Colleen Przybyla wrote: > Hello, > > I recently used the GadgetFS sample code as a template to create a USB wheel > mouse.
I'm glad to hear that ... folk haven't talked much about using GadgetFS. I think that's because it's not a drop-in solution; someone has to write code to use it! > I am now looking in to adding force feedback capabilities to this > simulation - when a certain place is triggered on the host computer, the > Linux 'gadget' should vibrate (like a cell phone vibrator). I have a couple > of questions, if anyone could offer any insight I would be much > appreciative. Google searches seem to turn up conflicting information. > > First, is the GadgetFS API compatible with a force-feedback PID device? The API should have no problems with any USB device protocol, at least for ones fitting into the types of configuration it supports. It just passes bits through, and the protocol is in the bits. Though if you need control-OUT transfers, you might hit a glitch in the implementation: those are in the API/design, but I recall an issue that'd prevent them from working in all cases. > Second, given the task, am I correct in thinking this is a possible > solution? Can I trigger a PID device from a certain movement on the host > computer? The host can send data whenever it wants, including when it senses some movement. As I understand it, the PID devices just need a HID report sent on some interrupt-OUT endpoint. > Third, in terms of PID devices - I've been reviewing the USB.org PID > documentation, and even so, I'm somewhat confused. With the host-based USB > system, I can't seem to determine which calls are made to the GadgetFS API > during enumeration. Enumeration is covered by the standard USB 2.0 spec; it's basically a set of descriptor fetches, as needed by the host side USB stack. Nothing PID-specific there ... though the host side driver that's bound to the device at the end of enumeration is likely going to know things about PID/HID class support. > I have more of an idea how these report descriptors > should be answered, but even that is not solid. Is there anyone available > that could give a somewhat nutshell 'what has to happen and when' for a PID > device? I assume that my existing HID mouse code would need to have a > couple of additional descriptors in order to enumerate properly as a PID > force-feedback mouse. Maybe the folk who did the force feedback drivers on Linux, or in their absence the drivers they wrote, can answer some of those questions. I don't know HID, or PID, myself. - Dave > I would greatly appreciate any insight that anyone could offer, thank you in > advance!! > > Regards, > > Colleen > > > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > [EMAIL PROTECTED] > To unsubscribe, use the last form field at: > https://lists.sourceforge.net/lists/listinfo/linux-usb-devel > ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
