|
From: Krakora, R. V <rob...@de...> - 2007-08-16 19:17:21
|
Carl: In my mind, running the driver provided with libusb-win32 as a filter driver and changing configurations and/or selecting alternate interfaces is really dangerous as the "real" driver may have pipes open to the configuration and/or on the interface which is being switched from possibly causing some real problems since the "real" driver does not know that the configuration and or interface has been yanked out from under it. Best Regards, Rob Krakora Software Engineer Delphi Electronics & Safety e-mail: rob...@de... phone: 765-451-8574 -----Original Message----- From: lib...@li... [mailto:lib...@li...] On Behalf Of lib...@li... Sent: Thursday, August 16, 2007 3:11 PM To: lib...@li... Subject: Libusb-win32-devel Digest, Vol 15, Issue 12 Send Libusb-win32-devel mailing list submissions to lib...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel or, via email, send a message with subject or body 'help' to lib...@li... You can reach the person managing the list at lib...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Libusb-win32-devel digest..." Today's Topics: 1. Re: lots of bugs (Carl Kenner) (Xiaofan Chen) (Krakora, Robert V) 2. Re: lots of bugs (Carl Kenner) (Xiaofan Chen) (Xiaofan Chen) 3. Re: lots of bugs (Carl Kenner) (Xiaofan Chen) (Xiaofan Chen) 4. Re: lots of bugs (Carl Kenner) (Carl Kenner) 5. Re: lots of bugs (Carl Kenner) (Stephan Meyer) ---------------------------------------------------------------------- Message: 1 Date: Wed, 15 Aug 2007 15:18:00 -0400 From: "Krakora, Robert V" <rob...@de...> Subject: Re: [Libusb-win32-devel] lots of bugs (Carl Kenner) (Xiaofan Chen) To: <lib...@li...> Message-ID: =09 <3C7...@US... Auto.net> =09 Content-Type: text/plain; charset=3D"us-ascii" Xiaofan: I ported libhid myself and it took very little effort. I extended the API to not only allow the selection of an interface, but also the selection of a configuration. It works very well for me and is more straight forward than Microsofts HID API. If you want my port, I can zip it up and send it to you or upload it to an FTP site. Best Regards, Rob Krakora Software Engineer Delphi Electronics & Safety e-mail: rob...@de... phone: 765-451-8574 -----Original Message----- From: lib...@li... [mailto:lib...@li...] On Behalf Of lib...@li... Sent: Wednesday, August 15, 2007 3:07 PM To: lib...@li... Subject: Libusb-win32-devel Digest, Vol 15, Issue 11 Send Libusb-win32-devel mailing list submissions to lib...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel or, via email, send a message with subject or body 'help' to lib...@li... You can reach the person managing the list at lib...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Libusb-win32-devel digest..." Today's Topics: 1. Re: lots of bugs (Carl Kenner) (Xiaofan Chen) 2. Re: lots of bugs (Carl Kenner) (Xiaofan Chen) 3. Re: lots of bugs (Carl Kenner) (Carl Kenner) ---------------------------------------------------------------------- Message: 1 Date: Wed, 15 Aug 2007 07:11:34 +0800 From: "Xiaofan Chen" <xia...@gm...> Subject: Re: [Libusb-win32-devel] lots of bugs (Carl Kenner) To: lib...@li... Message-ID: <a27...@ma...> Content-Type: text/plain; charset=3DISO-8859-1 On 8/14/07, Krakora, Robert V <rob...@de...> wrote: > I ported libhid to Windows as it uses libusb on which libusb-win32 is > based. It takes care of claiming the interface for interrupt endpoints > and has an API call to retrieve data from interrupt endpoints. I added > an extra parameter to one of the API functions so that the configuration > as well as the interface could be selected. Previously, I was using the > Windows HID API which was quite confusing to use. Here is the link to > libhid: > Thanks for the info. Where can I get this Windows port of libhid? I am monitoring the libhid list and have not heard this. Regards, Xiaofan ------------------------------ Message: 2 Date: Wed, 15 Aug 2007 07:59:55 +0800 From: "Xiaofan Chen" <xia...@gm...> Subject: Re: [Libusb-win32-devel] lots of bugs (Carl Kenner) To: lib...@li... Message-ID: <a27...@ma...> Content-Type: text/plain; charset=3DISO-8859-1 On 8/15/07, Carl Kenner <car...@gm...> wrote: > OK, I tried it without setting the configuration or claiming the > interface, and it didn't work on my Vista computer with the Device > Driver. I then tried it without claiming the interface, but still > setting the configuration and it worked. Kind of strange. Which version of libusb are you using? Still I have no Vista... > The problem is that setting the configuration is the call that crashed > it on the filter driver on XP. > > So is there some way of knowing beforehand whether a call to > SetConfiguration is going to freeze my program and force the user to > reboot, or not? I am not so sure here. But the HID driver can be the issue. That is why I asked Stephan to add the native Windows HID backend to libusb-win32. When I first started with libusb-win32 with PICkit 2, the same BSOD happened. It turned out that I could not use the libusb-win32 filter driver since it is an HID device but has a second configuration. Xiaofan ------------------------------ Message: 3 Date: Wed, 15 Aug 2007 15:10:23 +0930 From: "Carl Kenner" <car...@gm...> Subject: Re: [Libusb-win32-devel] lots of bugs (Carl Kenner) To: lib...@li... Message-ID: <fab...@ma...> Content-Type: text/plain; charset=3DISO-8859-1 I'm using the latest version you can download. I reckon I'm going to try this: Open the device try reading the feature report if that fails then call usb_setconfiguration try reading the feature report again end if every frame try reading the input report using usb control messages close the device But on this vista computer, reading the feature report without setting the configuration always fails. Hopefully with the filter driver, reading the feature report will work the first time, so it will never call usb_setconfiguration and thus never lock up the computer forcing them to reboot. But I haven't tested that yet. On 15/08/07, Xiaofan Chen <xia...@gm...> wrote: > On 8/15/07, Carl Kenner <car...@gm...> wrote: > > OK, I tried it without setting the configuration or claiming the > > interface, and it didn't work on my Vista computer with the Device > > Driver. I then tried it without claiming the interface, but still > > setting the configuration and it worked. > > Kind of strange. Which version of libusb are you using? > Still I have no Vista... > > > The problem is that setting the configuration is the call that crashed > > it on the filter driver on XP. > > > > So is there some way of knowing beforehand whether a call to > > SetConfiguration is going to freeze my program and force the user to > > reboot, or not? > > I am not so sure here. But the HID driver can be the issue. That > is why I asked Stephan to add the native Windows HID backend > to libusb-win32. > > When I first started with libusb-win32 with PICkit 2, the same BSOD > happened. It turned out that I could not use the libusb-win32 filter > driver since it is an HID device but has a second configuration. > > Xiaofan > > ------------------------------------------------------------------------ - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > ------------------------------ ------------------------------------------------------------------------ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ------------------------------ _______________________________________________ Libusb-win32-devel mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel End of Libusb-win32-devel Digest, Vol 15, Issue 11 ************************************************** ************************************************************************ **************** Note: If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you.=20 ************************************************************************ **************** ------------------------------ Message: 2 Date: Thu, 16 Aug 2007 07:29:17 +0800 From: "Xiaofan Chen" <xia...@gm...> Subject: Re: [Libusb-win32-devel] lots of bugs (Carl Kenner) (Xiaofan Chen) To: lib...@li... Message-ID: <a27...@ma...> Content-Type: text/plain; charset=3DISO-8859-1 On 8/16/07, Krakora, Robert V <rob...@de...> wrote: > > Xiaofan: > > I ported libhid myself and it took very little effort. I extended the > API to not only allow the selection of an interface, but also the > selection of a configuration. It works very well for me and is more > straight forward than Microsofts HID API. If you want my port, I can > zip it up and send it to you or upload it to an FTP site. > Yes. Please send it to me. Because of some Gmail madness, please add a no-meaning extension to the zip file (libhidwin32.zip.gmailsucks or similar). ;-) Thanks a lot in advance. Regards, Xiaofan ------------------------------ Message: 3 Date: Thu, 16 Aug 2007 07:32:15 +0800 From: "Xiaofan Chen" <xia...@gm...> Subject: Re: [Libusb-win32-devel] lots of bugs (Carl Kenner) (Xiaofan Chen) To: lib...@li... Message-ID: <a27...@ma...> Content-Type: text/plain; charset=3DISO-8859-1 On 8/16/07, Xiaofan Chen <xia...@gm...> wrote: > On 8/16/07, Krakora, Robert V <rob...@de...> wrote: > > > > Xiaofan: > > > > I ported libhid myself and it took very little effort. I extended the > > API to not only allow the selection of an interface, but also the > > selection of a configuration. It works very well for me and is more > > straight forward than Microsofts HID API. If you want my port, I can > > zip it up and send it to you or upload it to an FTP site. > > > > Yes. Please send it to me. > > Because of some Gmail madness, please add a no-meaning extension > to the zip file (libhidwin32.zip.gmailsucks or similar). ;-) > I just read from the libhid list that people are requesting the Windows port of libhid. So maybe it is a good idea to put it to an FTP site so other people can get it as well. Xiaofan ------------------------------ Message: 4 Date: Thu, 16 Aug 2007 22:27:42 +0930 From: "Carl Kenner" <car...@gm...> Subject: Re: [Libusb-win32-devel] lots of bugs (Carl Kenner) To: lib...@li... Message-ID: <fab...@ma...> Content-Type: text/plain; charset=3DISO-8859-1 My program suddenly stopped working. Can anyone tell me what error number 116 is? (My program isn't written in C) On 15/08/07, Carl Kenner <car...@gm...> wrote: > I'm using the latest version you can download. > > I reckon I'm going to try this: > Open the device > try reading the feature report > if that fails then > call usb_setconfiguration > try reading the feature report again > end if > > every frame try reading the input report using usb control messages > > close the device > > But on this vista computer, reading the feature report without setting > the configuration always fails. Hopefully with the filter driver, > reading the feature report will work the first time, so it will never > call usb_setconfiguration and thus never lock up the computer forcing > them to reboot. But I haven't tested that yet. > > On 15/08/07, Xiaofan Chen <xia...@gm...> wrote: > > On 8/15/07, Carl Kenner <car...@gm...> wrote: > > > OK, I tried it without setting the configuration or claiming the > > > interface, and it didn't work on my Vista computer with the Device > > > Driver. I then tried it without claiming the interface, but still > > > setting the configuration and it worked. > > > > Kind of strange. Which version of libusb are you using? > > Still I have no Vista... > > > > > The problem is that setting the configuration is the call that crashed > > > it on the filter driver on XP. > > > > > > So is there some way of knowing beforehand whether a call to > > > SetConfiguration is going to freeze my program and force the user to > > > reboot, or not? > > > > I am not so sure here. But the HID driver can be the issue. That > > is why I asked Stephan to add the native Windows HID backend > > to libusb-win32. > > > > When I first started with libusb-win32 with PICkit 2, the same BSOD > > happened. It turned out that I could not use the libusb-win32 filter > > driver since it is an HID device but has a second configuration. > > > > Xiaofan > > > > ------------------------------------------------------------------------ - > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Libusb-win32-devel mailing list > > Lib...@li... > > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > > > ------------------------------ Message: 5 Date: Thu, 16 Aug 2007 15:26:42 +0200 From: Stephan Meyer <Ste...@ia...> Subject: Re: [Libusb-win32-devel] lots of bugs (Carl Kenner) To: lib...@li... Message-ID: =09 <OF3...@re...> Content-Type: text/plain; charset=3D"US-ASCII" > My program suddenly stopped working. > Can anyone tell me what error number 116 is? > (My program isn't written in C) #define ETIMEDOUT 116 >=20 > On 15/08/07, Carl Kenner <car...@gm...> wrote: > > I'm using the latest version you can download. > > > > I reckon I'm going to try this: > > Open the device > > try reading the feature report > > if that fails then > > call usb_setconfiguration > > try reading the feature report again > > end if > > > > every frame try reading the input report using usb control messages > > > > close the device > > > > But on this vista computer, reading the feature report without setting > > the configuration always fails. Hopefully with the filter driver, > > reading the feature report will work the first time, so it will never > > call usb_setconfiguration and thus never lock up the computer forcing > > them to reboot. But I haven't tested that yet. > > > > On 15/08/07, Xiaofan Chen <xia...@gm...> wrote: > > > On 8/15/07, Carl Kenner <car...@gm...> wrote: > > > > OK, I tried it without setting the configuration or claiming the > > > > interface, and it didn't work on my Vista computer with the Device > > > > Driver. I then tried it without claiming the interface, but still > > > > setting the configuration and it worked. > > > > > > Kind of strange. Which version of libusb are you using? > > > Still I have no Vista... > > > > > > > The problem is that setting the configuration is the call that=20 crashed > > > > it on the filter driver on XP. > > > > > > > > So is there some way of knowing beforehand whether a call to > > > > SetConfiguration is going to freeze my program and force the user=20 to > > > > reboot, or not? > > > > > > I am not so sure here. But the HID driver can be the issue. That > > > is why I asked Stephan to add the native Windows HID backend > > > to libusb-win32. > > > > > > When I first started with libusb-win32 with PICkit 2, the same BSOD > > > happened. It turned out that I could not use the libusb-win32 filter > > > driver since it is an HID device but has a second configuration. > > > > > > Xiaofan > > > > > >=20 ------------------------------------------------------------------------ - > > > This SF.net email is sponsored by: Splunk Inc. > > > Still grepping through log files to find problems? Stop. > > > Now Search log events and configuration files using AJAX and a=20 browser. > > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > _______________________________________________ > > > Libusb-win32-devel mailing list > > > Lib...@li... > > > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > > > > > >=20 >=20 ------------------------------------------------------------------------ - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel ------------------------------ ------------------------------------------------------------------------ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ------------------------------ _______________________________________________ Libusb-win32-devel mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel End of Libusb-win32-devel Digest, Vol 15, Issue 12 ************************************************** ***************************************************************************= ************* Note: If the reader of this message is not the intended recipient, or an= employee or agent responsible for delivering this message to the intended= recipient, you are hereby notified that any dissemination, distribution or= copying of this communication is strictly prohibited. If you have received= this communication in error, please notify us immediately by replying to= the message and deleting it from your computer. Thank you.=20 ***************************************************************************= ************* |