| 
     
      
      
      From: <li...@ze...> - 2006-04-02 21:02:31
      
     
   | 
* On 2006-03-28 Stephan Meyer <ste...@we...> wrote : > > > > Summarizing: I want the normal windows driver to handle my mouse, but > > > > still be able to talk to the other endpoints using libusb. What would > > > > be the best way to handle this with libusb-win32 ? > > > > Solution 1): Add feature reports to your mouse. So that you can use > > > Windows' HidD_SetFeature() and HidD_GetFeature() API functions > > > to send vendor specific commands to your device (I haven't done this > > > on my own, so I don't know if this solution actually works). > > > > I will still need one bulk OUT enpoint though, for the purpose of > > firmware uploading. > > You don't need the extra endpoint. You can use feature reports for > this as well. Thank you all for your help; Instead of using the provided library from atmel, I have now created my own USB client stack, and successfully implemented the get_feature and set_feature requests. Both configuration and upgrading of firmware works as a charm. -- :wq ^X^Cy^K^X^C^C^C^C  |