[linux-usb-devel] Re: USB Mouse simulation using GadgetFS API, continued

2004-03-12 Thread David Brownell
Colleen Przybyla wrote: From user space, just stick to the file system API ... if for any reason that's not working, it's just a bug. It should keep you from being too wrong. In this case it sounds like you've strayed off the path of righteousness by some indeterminate amount. - Dave I'm tryi

[linux-usb-devel] RE: USB Mouse simulation using GadgetFS API, continued

2004-03-11 Thread Colleen Przybyla
> From user space, just stick to the file system API ... if for any > reason that's not working, it's just a bug. It should keep you from > being too wrong. In this case it sounds like you've strayed off the > path of righteousness by some indeterminate amount. > - Dave I'm trying to work my wa

[linux-usb-devel] Re: USB Mouse simulation using GadgetFS API, continued

2004-03-05 Thread David Brownell
Colleen Przybyla wrote: When ep_config is called from the simple_source_thread function, it correctly opens a new fd for this endpoint. Memcpy -ing the endpoint descriptor data returns a pointer to memory, as it should. However, when the function enters the status = write(fd, buf, (4+USB_DT_EN

[linux-usb-devel] RE: USB Mouse simulation using GadgetFS API, continued

2004-03-04 Thread Colleen Przybyla
>You probably hit the second case: no control request was >pending, since the previous write() completed the response. >("No process was expecting that response!") > >Try leaving debug messages on in gadgetfs for a while. Normally, >only "interesting" paths like faults (and some initialization >or

[linux-usb-devel] Re: USB Mouse simulation using GadgetFS API, continued

2004-02-27 Thread David Brownell
Colleen Przybyla wrote: Hello again, I had written previously in regards to getting an embedded PXA255 chip to work as a simulated USB mouse using the GadgetFS API. I have been able to properly alter the example usb.c code example from GadgetFS to initialize properly as a USB mouse. ... Good sta