Menu
▾
▴
libusb-win32-devel
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(27) |
Dec
(9) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(2) |
Feb
(19) |
Mar
(13) |
Apr
(15) |
May
(11) |
Jun
(17) |
Jul
(31) |
Aug
(45) |
Sep
(10) |
Oct
(40) |
Nov
(39) |
Dec
(45) |
| 2005 |
Jan
(113) |
Feb
(45) |
Mar
(38) |
Apr
(53) |
May
(11) |
Jun
(42) |
Jul
(56) |
Aug
(50) |
Sep
(32) |
Oct
(32) |
Nov
(47) |
Dec
(22) |
| 2006 |
Jan
(19) |
Feb
(32) |
Mar
(40) |
Apr
(40) |
May
(41) |
Jun
(44) |
Jul
(37) |
Aug
(51) |
Sep
(30) |
Oct
(30) |
Nov
(51) |
Dec
(20) |
| 2007 |
Jan
(7) |
Feb
(20) |
Mar
(17) |
Apr
(67) |
May
(13) |
Jun
(73) |
Jul
(16) |
Aug
(58) |
Sep
(29) |
Oct
(5) |
Nov
(74) |
Dec
(9) |
| 2008 |
Jan
(17) |
Feb
(12) |
Mar
(65) |
Apr
(22) |
May
(40) |
Jun
(32) |
Jul
(11) |
Aug
(8) |
Sep
(3) |
Oct
(41) |
Nov
(34) |
Dec
(12) |
| 2009 |
Jan
(44) |
Feb
(33) |
Mar
(16) |
Apr
(109) |
May
(11) |
Jun
(22) |
Jul
(21) |
Aug
(37) |
Sep
(5) |
Oct
(23) |
Nov
(7) |
Dec
(7) |
| 2010 |
Jan
(36) |
Feb
(40) |
Mar
(35) |
Apr
(45) |
May
(42) |
Jun
(104) |
Jul
(135) |
Aug
(50) |
Sep
(65) |
Oct
(110) |
Nov
(129) |
Dec
(75) |
| 2011 |
Jan
(105) |
Feb
(48) |
Mar
(93) |
Apr
(166) |
May
(169) |
Jun
(188) |
Jul
(106) |
Aug
(33) |
Sep
(85) |
Oct
(46) |
Nov
(102) |
Dec
(105) |
| 2012 |
Jan
(81) |
Feb
(115) |
Mar
(56) |
Apr
(93) |
May
(56) |
Jun
(77) |
Jul
(88) |
Aug
(52) |
Sep
(72) |
Oct
(16) |
Nov
(70) |
Dec
(70) |
| 2013 |
Jan
(23) |
Feb
(85) |
Mar
(38) |
Apr
(48) |
May
(40) |
Jun
(49) |
Jul
(33) |
Aug
(28) |
Sep
(66) |
Oct
(28) |
Nov
(28) |
Dec
(16) |
| 2014 |
Jan
(33) |
Feb
(58) |
Mar
(17) |
Apr
(50) |
May
(16) |
Jun
(24) |
Jul
(19) |
Aug
(32) |
Sep
(10) |
Oct
(10) |
Nov
(4) |
Dec
(10) |
| 2015 |
Jan
(11) |
Feb
(2) |
Mar
(4) |
Apr
(14) |
May
(1) |
Jun
(6) |
Jul
(16) |
Aug
(29) |
Sep
(6) |
Oct
(26) |
Nov
(10) |
Dec
|
| 2016 |
Jan
|
Feb
(20) |
Mar
(6) |
Apr
|
May
(3) |
Jun
(3) |
Jul
|
Aug
(16) |
Sep
(6) |
Oct
|
Nov
(15) |
Dec
|
| 2017 |
Jan
(1) |
Feb
(2) |
Mar
(4) |
Apr
|
May
(1) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2018 |
Jan
|
Feb
(8) |
Mar
(10) |
Apr
(16) |
May
|
Jun
(15) |
Jul
|
Aug
(3) |
Sep
(19) |
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(3) |
Aug
|
Sep
(6) |
Oct
(2) |
Nov
(4) |
Dec
|
| 2022 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
(5) |
Feb
(1) |
Mar
|
Apr
(3) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
(3) |
Mar
(1) |
Apr
(1) |
May
(11) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
(3) |
Dec
|
|
From: Thomas S. <th...@th...> - 2007-08-30 19:17:58
|
Does libusb-win32 support isochronous transfers? |
|
From: Spiro T. <an-...@sp...> - 2007-08-30 16:31:56
|
Hello, * On Thu, Aug 30, 2007 at 07:54:14PM +0800 Xiaofan Chen wrote: > On 8/30/07, Bachelier, Georges <geo...@at...> wrote: > > We provide the libUsb-Win32 driver and DLL to our customers within our > > software package (Atmel – In-System Programming application). One of our > > customers is asking for an XP 64-bit version of libUsb. Is there anything > > available or planned? > > According to the forum archive, XP 64bit is supported but not Vista 64bit. Unless someone is willing to contribute his Verisign (or similar) key to sign a 64 bit driver, it is unlikely that this will change soon. That is, this holds true as long as there is no new implementation that utilizes the built-in driver winusb.sys. Citing Stephan in Message-Id: <206...@we...>: * On Mon, Jun 25, 2007 at 09:03:58PM +0200 Stephan Meyer wrote: > > The current version (0.1.12.1) works without any problems > on vista-32bit but NOT on vista-64bit. > Furture versions of the DLL will use vista's built-in winusb.sys > driver and will therefore work on both platforms. If you're > interrested in a pre-pre-alpha version then grab the latest sources > from the SVN and try it out. > http://libusb-win32.svn.sourceforge.net/viewvc/libusb-win32/trunk/libusb1/ So, you might want to help Stephan in getting the new version done in order to get the Vista 64-bit version. Regards, Spiro. -- Spiro R. Trikaliotis http://opencbm.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/ |
|
From: Christian Z. <za...@tr...> - 2007-08-30 13:17:47
|
Hi, I need some advice on debugging libusb-win32. I get a segmentation fault in usb_submit_async(). There isn't too much code in that function, any hints on what the problem could be or how I can approach this? Also, is it likely that this is a bug outside of libusb, with wrong parameters or maybe the specific usb driver? I'm using libusb-win32. 0.1.12.1 filter and ObexFTP to access my mobile phone (download at http://triq.net/obexftp/obex-win32.zip ) This is from gdb: Program received signal SIGSEGV, Segmentation fault. 0x6e602da4 in usb_submit_async () from C:\WINDOWS\system32\libusb0.dll #0 0x6e602da4 in usb_submit_async () from C:\WINDOWS\system32\libusb0.dll #1 0x6e6043d2 in usb_reap_async () from C:\WINDOWS\system32\libusb0.dll #2 0x003f4988 in libopenobex-1!OBEX_FreeInterfaces () #3 0x003f26a3 in libopenobex-1!OBEX_FreeInterfaces () #4 0x003f3952 in libopenobex-1!OBEX_FreeInterfaces () #5 0x003f53c9 in libopenobex-1!OBEX_FreeInterfaces () #6 0x003f19b8 in libopenobex-1!OBEX_Request () #7 0x1000227a in cli_sync_request () from libobexftp-0.dll #8 0x100027f0 in obexftp_connect_src () from libobexftp-0.dll #9 0x00401b2a in cli_connect_uuid () #10 0x00401bcd in cli_connect () #11 0x004027cf in main () regards, Christian |
|
From: Xiaofan C. <xia...@gm...> - 2007-08-30 11:54:17
|
On 8/30/07, Bachelier, Georges <geo...@at...> wrote: > We provide the libUsb-Win32 driver and DLL to our customers within our > software package (Atmel =96 In-System Programming application). One of ou= r > customers is asking for an XP 64-bit version of libUsb. Is there anything > available or planned? > According to the forum archive, XP 64bit is supported but not Vista 64bit. ---------- Forwarded message ---------- From: Stephan Meyer Date: Mar 20, 2007 8:15 PM Subject: Re: [Libusb-win32-devel] Windows 2000 and Vista support (was: usb_claim_interface returns error code -22 on Windows) To: lib...@li... > * On Tue, Mar 20, 2007 at 11:02:10AM +0100 Stephan Meyer wrote: > > > > OS version: Windows 2K 5.00.2195 SP4 > > > libUsb: 0.1.10.1 > > > Peripheral Manager: our HID device status is OK > > > Task Manager: libusbd-nt.exe is running > > > > > > I have installed the 0.1.12.0 version to check if it could > > > fix the problem, but the things go even worse: the filter driver > > > service starts then stops after a few seconds. This has been tested > > > on a Windows XP machine with the same behavior: the service starts an= d > > > stops. > > > > Please do not use the old version any more. It's outdated. > > This reminds me: What is the state of libusb-win32 for Windows 2000? I > found that the latest release does not even install with the DDK > (3790.1830) in the Windows 2000 build environment. Does it mean that > Windows 2000 is not supported anymore? Windows 2000 is fully supported, even Win98SE. I just installed the 0.1.12.= 1 release (compiled with mingw) on win2k-sp4 (vmplayer install) and it works like a charm. Don't use the DDK's Win2k build environment, use the XP or the Server 2003 build environment even if you want to compile for Win2k. > > What about Vista 64 bit? As far as I see, the driver is not signed, > thus, it should refuse to install there. (I do not have Vista, so, I > cannot check for myself). You are right, Vista-64bit won't let you install unsigned drivers. This means that this platform is currently not supported. To resolve this issue, future versions of libusb-win32 will use Vistas built-in kernel driver winusb.sys. > > Do you plan to support 64 bit Windows at all? XP-64bit and Server-2003-64bit are supported. Use the files libusb0_x64.dll and libusb0_x64.sys on these systems. |
|
From: Bachelier, G. <geo...@at...> - 2007-08-30 06:17:49
|
Hi there! =20 We provide the libUsb-Win32 driver and DLL to our customers within our software package (Atmel - In-System Programming application). One of our customers is asking for an XP 64-bit version of libUsb. Is there anything available or planned? =20 Thanks in advance for your time, =20 Georges =20 |
|
From: Krakora, R. V <rob...@de...> - 2007-08-23 18:22:23
|
00000000 0.00000000 LIBUSB-DRIVER - release_all_interfaces(): releasing all interfaces bound to file object 0x893113e0=09 00000001 0.01598108 =09 00000002 0.01598862 =09 00000003 0.01599673 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000004 0.01600343 LIBUSB-DRIVER - transfer(): direction in 00000005 0.01601069 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000006 0.01601712 LIBUSB-DRIVER - transfer(): size 768=09 00000007 0.01602410 LIBUSB-DRIVER - transfer(): sequence 2609=09 00000008 0.01602829 =09 00000009 0.31996021 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2609: 14 bytes transmitted=09 00000010 0.34018961 =09 00000011 0.34019464 =09 00000012 0.34019938 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000013 0.34020358 LIBUSB-DRIVER - transfer(): direction in 00000014 0.34020832 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000015 0.34021336 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000016 0.34021783 LIBUSB-DRIVER - transfer(): size 48960=09 00000017 0.34022230 LIBUSB-DRIVER - transfer(): sequence 2610=09 00000018 0.34022507 =09 00000019 0.34116319 =09 00000020 0.34116739 =09 00000021 0.34117213 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000022 0.34117603 LIBUSB-DRIVER - transfer(): direction in 00000023 0.34118050 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000024 0.34118471 LIBUSB-DRIVER - transfer(): size 768=09 00000025 0.34118891 LIBUSB-DRIVER - transfer(): sequence 2611=09 00000026 0.34119198 =09 00000027 0.81540585 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2610: 44980 bytes transmitted=09 00000028 0.81547290 =09 00000029 0.81547683 =09 00000030 0.81548131 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000031 0.81548548 LIBUSB-DRIVER - transfer(): direction in 00000032 0.81549025 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000033 0.81549442 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000034 0.81549859 LIBUSB-DRIVER - transfer(): size 48960=09 00000035 0.81550282 LIBUSB-DRIVER - transfer(): sequence 2612=09 00000036 0.81550586 =09 00000037 1.81585515 =09 00000038 1.81586289 =09 00000039 1.81587207 LIBUSB-DRIVER - abort_endpoint(): endpoint 0x81=09 00000040 1.81587934 LIBUSB-DRIVER - abort_endpoint(): timeout 5000=09 00000041 1.81600678 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2612: 6704 bytes transmitted=09 00000042 1.81706142 =09 00000043 1.81706834 =09 00000044 1.81707621 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000045 1.81708229 LIBUSB-DRIVER - transfer(): direction in 00000046 1.81708932 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000047 1.81709599 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000048 1.81710279 LIBUSB-DRIVER - transfer(): size 48960=09 00000049 1.81710970 LIBUSB-DRIVER - transfer(): sequence 2613=09 00000050 1.81711388 =09 00000051 2.60454035 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2611: 26 bytes transmitted=09 00000052 2.60456824 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2613: 44980 bytes transmitted=09 00000053 2.60466504 =09 00000054 2.60467172 =09 00000055 2.60467911 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000056 2.60468531 LIBUSB-DRIVER - transfer(): direction in 00000057 2.60469222 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000058 2.60469913 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000059 2.60470581 LIBUSB-DRIVER - transfer(): size 48960=09 00000060 2.60471296 LIBUSB-DRIVER - transfer(): sequence 2614=09 00000061 2.60471702 =09 00000062 2.60711432 =09 00000063 2.60712123 =09 00000064 2.60712886 LIBUSB-DRIVER - vendor_class_request(): type: class=09 00000065 2.60713673 LIBUSB-DRIVER - vendor_class_request(): recipient: interface=09 00000066 2.60714459 LIBUSB-DRIVER - vendor_class_request(): request: 0x09=09 00000067 2.60715199 LIBUSB-DRIVER - vendor_class_request(): value: 0x020e=09 00000068 2.60715938 LIBUSB-DRIVER - vendor_class_request(): index: 0x0002=09 00000069 2.60716629 LIBUSB-DRIVER - vendor_class_request(): size: 9=09 00000070 2.60717320 LIBUSB-DRIVER - vendor_class_request(): direction: out=09 00000071 2.60718060 LIBUSB-DRIVER - vendor_class_request(): timeout: 10000=09 00000072 2.60793233 LIBUSB-DRIVER - vendor_class_request(): 9 bytes transmitted=09 00000073 2.62935853 =09 00000074 2.62936640 =09 00000075 2.62937403 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000076 2.62938094 LIBUSB-DRIVER - transfer(): direction in 00000077 2.62938786 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000078 2.62939429 LIBUSB-DRIVER - transfer(): size 768=09 00000079 2.62940097 LIBUSB-DRIVER - transfer(): sequence 2615=09 00000080 2.62940502 =09 00000081 3.60495734 =09 00000082 3.60496545 =09 00000083 3.60497475 LIBUSB-DRIVER - abort_endpoint(): endpoint 0x81=09 00000084 3.60498190 LIBUSB-DRIVER - abort_endpoint(): timeout 5000=09 00000085 3.60510635 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2614: 44984 bytes transmitted=09 00000086 3.60613394 =09 00000087 3.60614109 =09 00000088 3.60614848 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000089 3.60615468 LIBUSB-DRIVER - transfer(): direction in 00000090 3.60616207 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000091 3.60616899 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000092 3.60617542 LIBUSB-DRIVER - transfer(): size 48960=09 00000093 3.60618210 LIBUSB-DRIVER - transfer(): sequence 2616=09 00000094 3.60618591 =09 00000095 3.88746095 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2616: 44980 bytes transmitted=09 00000096 3.88756514 =09 00000097 3.88757181 =09 00000098 3.88757968 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000099 3.88758636 LIBUSB-DRIVER - transfer(): direction in 00000100 3.88759327 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000101 3.88760018 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000102 3.88760734 LIBUSB-DRIVER - transfer(): size 48960=09 00000103 3.88761401 LIBUSB-DRIVER - transfer(): sequence 2617=09 00000104 3.88761806 =09 00000105 3.98933458 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2615: 14 bytes transmitted=09 00000106 4.01124620 =09 00000107 4.01125431 =09 00000108 4.01126242 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000109 4.01126862 LIBUSB-DRIVER - transfer(): direction in 00000110 4.01127625 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000111 4.01128244 LIBUSB-DRIVER - transfer(): size 768=09 00000112 4.01128912 LIBUSB-DRIVER - transfer(): sequence 2618=09 00000113 4.01129293 =09 00000114 4.51166248 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2618: 14 bytes transmitted=09 00000115 4.51168633 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2617: 40928 bytes transmitted=09 00000116 4.51177073 =09 00000117 4.51177645 =09 00000118 4.51178312 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000119 4.51178980 LIBUSB-DRIVER - transfer(): direction in 00000120 4.51179647 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000121 4.51180363 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000122 4.51181078 LIBUSB-DRIVER - transfer(): size 48960=09 00000123 4.51181746 LIBUSB-DRIVER - transfer(): sequence 2619=09 00000124 4.51182079 =09 00000125 4.53372335 =09 00000126 4.53373146 =09 00000127 4.53373957 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000128 4.53374577 LIBUSB-DRIVER - transfer(): direction in 00000129 4.53375292 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000130 4.53375959 LIBUSB-DRIVER - transfer(): size 768=09 00000131 4.53376675 LIBUSB-DRIVER - transfer(): sequence 2620=09 00000132 4.53377056 =09 00000133 4.91146231 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2619: 44980 bytes transmitted=09 00000134 4.91158628 =09 00000135 4.91159296 =09 00000136 4.91159964 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000137 4.91160631 LIBUSB-DRIVER - transfer(): direction in 00000138 4.91161299 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000139 4.91161966 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000140 4.91162634 LIBUSB-DRIVER - transfer(): size 48960=09 00000141 4.91163445 LIBUSB-DRIVER - transfer(): sequence 2621=09 00000142 4.91163778 =09 00000143 5.06278038 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2620: 14 bytes transmitted=09 00000144 5.06280756 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2621: 20112 bytes transmitted=09 00000145 5.06290102 =09 00000146 5.06290674 =09 00000147 5.06291389 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000148 5.06292057 LIBUSB-DRIVER - transfer(): direction in 00000149 5.06293678 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000150 5.06294394 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000151 5.06295061 LIBUSB-DRIVER - transfer(): size 48960=09 00000152 5.06295729 LIBUSB-DRIVER - transfer(): sequence 2622=09 00000153 5.06296158 =09 00000154 5.08451986 =09 00000155 5.08452892 =09 00000156 5.08453798 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000157 5.08454418 LIBUSB-DRIVER - transfer(): direction in 00000158 5.08455133 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000159 5.08455801 LIBUSB-DRIVER - transfer(): size 768=09 00000160 5.08456516 LIBUSB-DRIVER - transfer(): sequence 2623=09 00000161 5.08456945 =09 00000162 5.55953789 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2623: 14 bytes transmitted=09 00000163 5.55956650 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2622: 38452 bytes transmitted=09 00000164 5.55966282 =09 00000165 5.55966854 =09 00000166 5.55967522 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000167 5.55968189 LIBUSB-DRIVER - transfer(): direction in 00000168 5.55968952 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000169 5.55969667 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000170 5.55970335 LIBUSB-DRIVER - transfer(): size 48960=09 00000171 5.55971003 LIBUSB-DRIVER - transfer(): sequence 2624=09 00000172 5.55971432 =09 00000173 5.58062077 =09 00000174 5.58062887 =09 00000175 5.58063698 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000176 5.58064318 LIBUSB-DRIVER - transfer(): direction in 00000177 5.58065128 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000178 5.58065748 LIBUSB-DRIVER - transfer(): size 768=09 00000179 5.58066416 LIBUSB-DRIVER - transfer(): sequence 2625=09 00000180 5.58066797 =09 00000181 5.93547487 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2624: 44984 bytes transmitted=09 00000182 5.93558121 =09 00000183 5.93558693 =09 00000184 5.93559408 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000185 5.93560028 LIBUSB-DRIVER - transfer(): direction in 00000186 5.93560791 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000187 5.93561459 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000188 5.93562078 LIBUSB-DRIVER - transfer(): size 48960=09 00000189 5.93562794 LIBUSB-DRIVER - transfer(): sequence 2626=09 00000190 5.93563128 =09 00000191 6.13879347 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2625: 14 bytes transmitted=09 00000192 6.13881874 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2626: 24344 bytes transmitted=09 00000193 6.13890314 =09 00000194 6.13890839 =09 00000195 6.13891506 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000196 6.13892078 LIBUSB-DRIVER - transfer(): direction in 00000197 6.13892841 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000198 6.13893557 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000199 6.13894176 LIBUSB-DRIVER - transfer(): size 48960=09 00000200 6.13894892 LIBUSB-DRIVER - transfer(): sequence 2627=09 00000201 6.13895226 =09 00000202 6.16164923 =09 00000203 6.16165733 =09 00000204 6.16166544 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000205 6.16167116 LIBUSB-DRIVER - transfer(): direction in 00000206 6.16167879 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000207 6.16168690 LIBUSB-DRIVER - transfer(): size 768=09 00000208 6.16169357 LIBUSB-DRIVER - transfer(): sequence 2628=09 00000209 6.16169786 =09 00000210 6.63666248 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2628: 14 bytes transmitted=09 00000211 6.63669062 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2627: 33516 bytes transmitted=09 00000212 6.63678885 =09 00000213 6.63679457 =09 00000214 6.63680220 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000215 6.63680840 LIBUSB-DRIVER - transfer(): direction in 00000216 6.63681555 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000217 6.63682222 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000218 6.63682938 LIBUSB-DRIVER - transfer(): size 48960=09 00000219 6.63683605 LIBUSB-DRIVER - transfer(): sequence 2629=09 00000220 6.63684034 =09 00000221 6.65778685 =09 00000222 6.65779495 =09 00000223 6.65780258 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000224 6.65780926 LIBUSB-DRIVER - transfer(): direction in 00000225 6.65781641 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000226 6.65782261 LIBUSB-DRIVER - transfer(): size 768=09 00000227 6.65782928 LIBUSB-DRIVER - transfer(): sequence 2630=09 00000228 6.65783405 =09 00000229 6.95948124 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2629: 44980 bytes transmitted=09 00000230 6.95959854 =09 00000231 6.95960474 =09 00000232 6.95961189 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000233 6.95961857 LIBUSB-DRIVER - transfer(): direction in 00000234 6.95962524 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000235 6.95963192 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000236 6.95963907 LIBUSB-DRIVER - transfer(): size 48960=09 00000237 6.95964670 LIBUSB-DRIVER - transfer(): sequence 2631=09 00000238 6.95965004 =09 00000239 7.15952826 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2630: 14 bytes transmitted=09 00000240 7.15955591 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2631: 33696 bytes transmitted=09 00000241 7.15965080 =09 00000242 7.15965700 =09 00000243 7.15967321 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000244 7.15967989 LIBUSB-DRIVER - transfer(): direction in 00000245 7.15968657 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000246 7.15969324 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000247 7.15969992 LIBUSB-DRIVER - transfer(): size 48960=09 00000248 7.15970707 LIBUSB-DRIVER - transfer(): sequence 2632=09 00000249 7.15971088 =09 00000250 7.18124533 =09 00000251 7.18125343 =09 00000252 7.18126154 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000253 7.18126822 LIBUSB-DRIVER - transfer(): direction in 00000254 7.18127489 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000255 7.18128157 LIBUSB-DRIVER - transfer(): size 768=09 00000256 7.18128824 LIBUSB-DRIVER - transfer(): sequence 2633=09 00000257 7.18129206 =09 00000258 7.65766001 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2633: 14 bytes transmitted=09 00000259 7.65768719 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2632: 43392 bytes transmitted=09 00000260 7.65779448 =09 00000261 7.65780115 =09 00000262 7.65780783 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000263 7.65781403 LIBUSB-DRIVER - transfer(): direction in 00000264 7.65782118 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000265 7.65782785 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000266 7.65783453 LIBUSB-DRIVER - transfer(): size 48960=09 00000267 7.65784121 LIBUSB-DRIVER - transfer(): sequence 2634=09 00000268 7.65784550 =09 00000269 7.67446709 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2634: 528 bytes transmitted=09 00000270 7.67459154 =09 00000271 7.67459726 =09 00000272 7.67460442 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000273 7.67461061 LIBUSB-DRIVER - transfer(): direction in 00000274 7.67461777 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000275 7.67462444 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000276 7.67463112 LIBUSB-DRIVER - transfer(): size 48960=09 00000277 7.67463779 LIBUSB-DRIVER - transfer(): sequence 2635=09 00000278 7.67464256 =09 00000279 7.67931747 =09 00000280 7.67932463 =09 00000281 7.67933226 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000282 7.67934036 LIBUSB-DRIVER - transfer(): direction in 00000283 7.67934704 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000284 7.67935371 LIBUSB-DRIVER - transfer(): size 768=09 00000285 7.67936039 LIBUSB-DRIVER - transfer(): sequence 2636=09 00000286 7.67936420 =09 00000287 7.98346806 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2635: 42516 bytes transmitted=09 00000288 7.98357773 =09 00000289 7.98358345 =09 00000290 7.98359013 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000291 7.98359680 LIBUSB-DRIVER - transfer(): direction in 00000292 7.98360443 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000293 7.98361111 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000294 7.98361826 LIBUSB-DRIVER - transfer(): size 48960=09 00000295 7.98362494 LIBUSB-DRIVER - transfer(): sequence 2637=09 00000296 7.98362923 =09 00000297 8.16053200 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2636: 14 bytes transmitted=09 00000298 8.17737198 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2637: 32984 bytes transmitted=09 00000299 8.17745495 =09 00000300 8.17746258 =09 00000301 8.17746925 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000302 8.17747688 LIBUSB-DRIVER - transfer(): direction in 00000303 8.17748356 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000304 8.17749119 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000305 8.17749786 LIBUSB-DRIVER - transfer(): size 48960=09 00000306 8.17750454 LIBUSB-DRIVER - transfer(): sequence 2638=09 00000307 8.17750835 =09 00000308 8.18219090 =09 00000309 8.18219662 =09 00000310 8.18220329 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000311 8.18220997 LIBUSB-DRIVER - transfer(): direction in 00000312 8.18221664 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000313 8.18222332 LIBUSB-DRIVER - transfer(): size 768=09 00000314 8.18223000 LIBUSB-DRIVER - transfer(): sequence 2639=09 00000315 8.18223381 =09 00000316 8.65740967 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2639: 14 bytes transmitted=09 00000317 8.65743732 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2638: 43748 bytes transmitted=09 00000318 8.65753269 =09 00000319 8.65753841 =09 00000320 8.65754604 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000321 8.65755272 LIBUSB-DRIVER - transfer(): direction in 00000322 8.65755939 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000323 8.65756607 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000324 8.65757275 LIBUSB-DRIVER - transfer(): size 48960=09 00000325 8.65758038 LIBUSB-DRIVER - transfer(): sequence 2640=09 00000326 8.65758419 =09 00000327 8.67932129 =09 00000328 8.67932987 =09 00000329 8.67933750 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000330 8.67934418 LIBUSB-DRIVER - transfer(): direction in 00000331 8.67935085 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000332 8.67935753 LIBUSB-DRIVER - transfer(): size 768=09 00000333 8.67936420 LIBUSB-DRIVER - transfer(): sequence 2641=09 00000334 8.67936802 =09 00000335 9.00748348 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2640: 4056 bytes transmitted=09 00000336 9.00759029 =09 00000337 9.00759602 =09 00000338 9.00760365 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000339 9.00760937 LIBUSB-DRIVER - transfer(): direction in 00000340 9.00761700 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000341 9.00762463 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000342 9.00763130 LIBUSB-DRIVER - transfer(): size 48960=09 00000343 9.00763798 LIBUSB-DRIVER - transfer(): sequence 2642=09 00000344 9.00764179 =09 00000345 9.19294739 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2641: 14 bytes transmitted=09 00000346 9.21447468 =09 00000347 9.21448326 =09 00000348 9.21449089 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000349 9.21449757 LIBUSB-DRIVER - transfer(): direction in 00000350 9.21450424 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000351 9.21451092 LIBUSB-DRIVER - transfer(): size 768=09 00000352 9.21451759 LIBUSB-DRIVER - transfer(): sequence 2643=09 00000353 9.21452236 =09 00000354 9.68966293 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2643: 14 bytes transmitted=09 00000355 9.68968773 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2642: 44980 bytes transmitted=09 00000356 9.68976593 =09 00000357 9.68977165 =09 00000358 9.68977833 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000359 9.68978500 LIBUSB-DRIVER - transfer(): direction in 00000360 9.68979263 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000361 9.68979931 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000362 9.68980598 LIBUSB-DRIVER - transfer(): size 48960=09 00000363 9.68981266 LIBUSB-DRIVER - transfer(): sequence 2644=09 00000364 9.68981743 =09 00000365 9.71159649 =09 00000366 9.71160412 =09 00000367 9.71161175 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000368 9.71161842 LIBUSB-DRIVER - transfer(): direction in 00000369 9.71162510 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000370 9.71163177 LIBUSB-DRIVER - transfer(): size 768=09 00000371 9.71163845 LIBUSB-DRIVER - transfer(): sequence 2645=09 00000372 9.71164322 =09 00000373 10.03147507 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2644: 44984 bytes transmitted=09 00000374 10.03158092 =09 00000375 10.03158760 =09 00000376 10.03159428 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000377 10.03160095 LIBUSB-DRIVER - transfer(): direction in 00000378 10.03160858 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000379 10.03161621 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000380 10.03162289 LIBUSB-DRIVER - transfer(): size 48960=09 00000381 10.03162956 LIBUSB-DRIVER - transfer(): sequence 2646=09 00000382 10.03163338 =09 00000383 10.22002983 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2645: 14 bytes transmitted=09 00000384 10.22005272 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2646: 30340 bytes transmitted=09 00000385 10.22013950 =09 00000386 10.22014427 =09 00000387 10.22015285 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000388 10.22015858 LIBUSB-DRIVER - transfer(): direction in 00000389 10.22016621 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000390 10.22017288 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000391 10.22017956 LIBUSB-DRIVER - transfer(): size 48960=09 00000392 10.22018623 LIBUSB-DRIVER - transfer(): sequence 2647=09 00000393 10.22019100 =09 00000394 10.24284935 =09 00000395 10.24285698 =09 00000396 10.24286461 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000397 10.24287128 LIBUSB-DRIVER - transfer(): direction in 00000398 10.24287987 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000399 10.24288654 LIBUSB-DRIVER - transfer(): size 768=09 00000400 10.24289322 LIBUSB-DRIVER - transfer(): sequence 2648=09 00000401 10.24289703 =09 00000402 10.71766090 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2648: 14 bytes transmitted=09 00000403 10.71768379 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2647: 41984 bytes transmitted=09 00000404 10.71776867 =09 00000405 10.71777439 =09 00000406 10.71778202 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000407 10.71778774 LIBUSB-DRIVER - transfer(): direction in 00000408 10.71779537 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000409 10.71780205 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000410 10.71780872 LIBUSB-DRIVER - transfer(): size 48960=09 00000411 10.71781445 LIBUSB-DRIVER - transfer(): sequence 2649=09 00000412 10.71781921 =09 00000413 10.73895741 =09 00000414 10.73896503 =09 00000415 10.73897362 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000416 10.73898029 LIBUSB-DRIVER - transfer(): direction in 00000417 10.73898792 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000418 10.73899460 LIBUSB-DRIVER - transfer(): size 768=09 00000419 10.73900127 LIBUSB-DRIVER - transfer(): sequence 2650=09 00000420 10.73900604 =09 00000421 11.05545235 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2649: 44980 bytes transmitted=09 00000422 11.05555725 =09 00000423 11.05556393 =09 00000424 11.05557060 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000425 11.05557728 LIBUSB-DRIVER - transfer(): direction in 00000426 11.05558395 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000427 11.05559063 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000428 11.05559731 LIBUSB-DRIVER - transfer(): size 48960=09 00000429 11.05560398 LIBUSB-DRIVER - transfer(): sequence 2651=09 00000430 11.05560875 =09 00000431 11.25790215 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2650: 14 bytes transmitted=09 00000432 11.25792599 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2651: 31048 bytes transmitted=09 00000433 11.25800514 =09 00000434 11.25801086 =09 00000435 11.25801754 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000436 11.25802422 LIBUSB-DRIVER - transfer(): direction in 00000437 11.25803185 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000438 11.25803852 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000439 11.25804520 LIBUSB-DRIVER - transfer(): size 48960=09 00000440 11.25805187 LIBUSB-DRIVER - transfer(): sequence 2652=09 00000441 11.25805664 =09 00000442 11.27914715 =09 00000443 11.27915573 =09 00000444 11.27916336 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000445 11.27917004 LIBUSB-DRIVER - transfer(): direction in 00000446 11.27917671 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000447 11.27918339 LIBUSB-DRIVER - transfer(): size 768=09 00000448 11.27919006 LIBUSB-DRIVER - transfer(): sequence 2653=09 00000449 11.27919483 =09 00000450 11.75604630 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2653: 14 bytes transmitted=09 00000451 11.75607300 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2652: 40220 bytes transmitted=09 00000452 11.75615788 =09 00000453 11.75616455 =09 00000454 11.75617123 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000455 11.75617790 LIBUSB-DRIVER - transfer(): direction in 00000456 11.75618458 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000457 11.75619125 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000458 11.75619793 LIBUSB-DRIVER - transfer(): size 48960=09 00000459 11.75620461 LIBUSB-DRIVER - transfer(): sequence 2654=09 00000460 11.75620937 =09 00000461 11.77818775 =09 00000462 11.77819633 =09 00000463 11.77820301 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000464 11.77820969 LIBUSB-DRIVER - transfer(): direction in 00000465 11.77821732 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000466 11.77822399 LIBUSB-DRIVER - transfer(): size 768=09 00000467 11.77823067 LIBUSB-DRIVER - transfer(): sequence 2655=09 00000468 11.77823448 =09 00000469 12.07947254 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2654: 44980 bytes transmitted=09 00000470 12.07958221 =09 00000471 12.07958889 =09 00000472 12.07959557 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000473 12.07960224 LIBUSB-DRIVER - transfer(): direction in 00000474 12.07960892 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000475 12.07961559 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000476 12.07962227 LIBUSB-DRIVER - transfer(): size 48960=09 00000477 12.07962894 LIBUSB-DRIVER - transfer(): sequence 2656=09 00000478 12.07963371 =09 00000479 12.27011681 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2655: 14 bytes transmitted=09 00000480 12.28688431 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2656: 33516 bytes transmitted=09 00000481 12.28698921 =09 00000482 12.28699589 =09 00000483 12.28700256 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000484 12.28700924 LIBUSB-DRIVER - transfer(): direction in 00000485 12.28701591 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000486 12.28702354 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000487 12.28703022 LIBUSB-DRIVER - transfer(): size 48960=09 00000488 12.28703690 LIBUSB-DRIVER - transfer(): sequence 2657=09 00000489 12.28704071 =09 00000490 12.29170227 =09 00000491 12.29171085 =09 00000492 12.29171944 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000493 12.29172802 LIBUSB-DRIVER - transfer(): direction in 00000494 12.29173565 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000495 12.29174137 LIBUSB-DRIVER - transfer(): size 768=09 00000496 12.29174805 LIBUSB-DRIVER - transfer(): sequence 2658=09 00000497 12.29175186 =09 00000498 12.76803398 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2658: 14 bytes transmitted=09 00000499 12.76806259 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2657: 41804 bytes transmitted=09 00000500 12.76816654 =09 00000501 12.76817226 =09 00000502 12.76817989 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000503 12.76818657 LIBUSB-DRIVER - transfer(): direction in 00000504 12.76819515 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000505 12.76829910 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000506 12.76830578 LIBUSB-DRIVER - transfer(): size 48960=09 00000507 12.76831245 LIBUSB-DRIVER - transfer(): sequence 2659=09 00000508 12.76831532 =09 00000509 12.78497314 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2659: 1944 bytes transmitted=09 00000510 12.78507423 =09 00000511 12.78507996 =09 00000512 12.78508759 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000513 12.78509426 LIBUSB-DRIVER - transfer(): direction in 00000514 12.78510094 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000515 12.78510857 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000516 12.78511524 LIBUSB-DRIVER - transfer(): size 48960=09 00000517 12.78512192 LIBUSB-DRIVER - transfer(): sequence 2660=09 00000518 12.78512669 =09 00000519 12.78976440 =09 00000520 12.78977299 =09 00000521 12.78977966 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000522 12.78978634 LIBUSB-DRIVER - transfer(): direction in 00000523 12.78979301 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000524 12.78979969 LIBUSB-DRIVER - transfer(): size 768=09 00000525 12.78980637 LIBUSB-DRIVER - transfer(): sequence 2661=09 00000526 12.78981113 =09 00000527 13.10345554 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2660: 43920 bytes transmitted=09 00000528 13.10354710 =09 00000529 13.10355186 =09 00000530 13.10355854 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000531 13.10356522 LIBUSB-DRIVER - transfer(): direction in 00000532 13.10357189 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000533 13.10357857 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000534 13.10358524 LIBUSB-DRIVER - transfer(): size 48960=09 00000535 13.10359192 LIBUSB-DRIVER - transfer(): sequence 2662=09 00000536 13.10359573 =09 00000537 13.26963711 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2661: 14 bytes transmitted=09 00000538 13.29170513 =09 00000539 13.29171371 =09 00000540 13.29172134 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000541 13.29172802 LIBUSB-DRIVER - transfer(): direction in 00000542 13.29173470 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000543 13.29174137 LIBUSB-DRIVER - transfer(): size 768=09 00000544 13.29174900 LIBUSB-DRIVER - transfer(): sequence 2663=09 00000545 13.29175282 =09 00000546 14.10322189 =09 00000547 14.10322952 =09 00000548 14.10323811 LIBUSB-DRIVER - abort_endpoint(): endpoint 0x81=09 00000549 14.10324574 LIBUSB-DRIVER - abort_endpoint(): timeout 5000=09 00000550 14.10337257 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2662: 32808 bytes transmitted=09 00000551 14.10425758 =09 00000552 14.10426331 =09 00000553 14.10426998 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000554 14.10427666 LIBUSB-DRIVER - transfer(): direction in 00000555 14.10428333 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000556 14.10429001 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000557 14.10429668 LIBUSB-DRIVER - transfer(): size 48960=09 00000558 14.10430336 LIBUSB-DRIVER - transfer(): sequence 2664=09 00000559 14.10430622 =09 00000560 14.30555820 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2663: 14 bytes transmitted=09 00000561 14.32688904 =09 00000562 14.32689571 =09 00000563 14.32690334 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000564 14.32691002 LIBUSB-DRIVER - transfer(): direction in 00000565 14.32691669 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000566 14.32692337 LIBUSB-DRIVER - transfer(): size 768=09 00000567 14.32693005 LIBUSB-DRIVER - transfer(): sequence 2665=09 00000568 14.32693386 =09 00000569 14.88991451 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2665: 14 bytes transmitted=09 00000570 14.88994122 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2664: 44980 bytes transmitted=09 00000571 14.89003849 =09 00000572 14.89004421 =09 00000573 14.89005089 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000574 14.89005756 LIBUSB-DRIVER - transfer(): direction in 00000575 14.89006519 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000576 14.89007187 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000577 14.89007950 LIBUSB-DRIVER - transfer(): size 48960=09 00000578 14.89008617 LIBUSB-DRIVER - transfer(): sequence 2666=09 00000579 14.89008999 =09 00000580 14.91188526 =09 00000581 14.91189194 =09 00000582 14.91189957 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000583 14.91190624 LIBUSB-DRIVER - transfer(): direction in 00000584 14.91191292 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000585 14.91191959 LIBUSB-DRIVER - transfer(): size 768=09 00000586 14.91192627 LIBUSB-DRIVER - transfer(): sequence 2667=09 00000587 14.91193104 =09 00000588 15.15145397 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2666: 44984 bytes transmitted=09 00000589 15.15155506 =09 00000590 15.15156078 =09 00000591 15.15156841 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000592 15.15157413 LIBUSB-DRIVER - transfer(): direction in 00000593 15.15158176 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000594 15.15158844 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000595 15.15159512 LIBUSB-DRIVER - transfer(): size 48960=09 00000596 15.15160179 LIBUSB-DRIVER - transfer(): sequence 2668=09 00000597 15.15160465 =09 00000598 15.38911819 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2667: 14 bytes transmitted=09 00000599 15.40606308 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2668: 44452 bytes transmitted=09 00000600 15.40619564 =09 00000601 15.40620136 =09 00000602 15.40620804 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000603 15.40621471 LIBUSB-DRIVER - transfer(): direction in 00000604 15.40622330 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000605 15.40622997 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000606 15.40623665 LIBUSB-DRIVER - transfer(): size 48960=09 00000607 15.40624332 LIBUSB-DRIVER - transfer(): sequence 2669=09 00000608 15.40624714 =09 00000609 15.41283512 =09 00000610 15.41284180 =09 00000611 15.41284847 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000612 15.41285515 LIBUSB-DRIVER - transfer(): direction in 00000613 15.41286278 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000614 15.41286850 LIBUSB-DRIVER - transfer(): size 768=09 00000615 15.41287518 LIBUSB-DRIVER - transfer(): sequence 2670=09 00000616 15.41287994 =09 00000617 15.88803864 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2670: 14 bytes transmitted=09 00000618 15.88806629 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2669: 44452 bytes transmitted=09 00000619 15.88817310 =09 00000620 15.88817883 =09 00000621 15.88818645 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000622 15.88819218 LIBUSB-DRIVER - transfer(): direction in 00000623 15.88820076 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000624 15.88820744 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000625 15.88821411 LIBUSB-DRIVER - transfer(): size 48960=09 00000626 15.88822079 LIBUSB-DRIVER - transfer(): sequence 2671=09 00000627 15.88822460 =09 00000628 15.90993023 =09 00000629 15.90993690 =09 00000630 15.90994453 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000631 15.90995121 LIBUSB-DRIVER - transfer(): direction in 00000632 15.90995884 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000633 15.90996552 LIBUSB-DRIVER - transfer(): size 768=09 00000634 15.90997219 LIBUSB-DRIVER - transfer(): sequence 2672=09 00000635 15.90997601 =09 00000636 16.17546654 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2671: 4412 bytes transmitted=09 00000637 16.17559814 =09 00000638 16.17560387 =09 00000639 16.17561150 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000640 16.17561722 LIBUSB-DRIVER - transfer(): direction in 00000641 16.17562485 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000642 16.17563057 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000643 16.17563820 LIBUSB-DRIVER - transfer(): size 48960=09 00000644 16.17564392 LIBUSB-DRIVER - transfer(): sequence 2673=09 00000645 16.17564964 =09 00000646 16.38660049 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2672: 14 bytes transmitted=09 00000647 16.40800095 =09 00000648 16.40800667 =09 00000649 16.40801620 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000650 16.40802193 LIBUSB-DRIVER - transfer(): direction in 00000651 16.40802956 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000652 16.40803528 LIBUSB-DRIVER - transfer(): size 768=09 00000653 16.40804291 LIBUSB-DRIVER - transfer(): sequence 2674=09 00000654 16.40804672 =09 00000655 16.88566589 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2674: 14 bytes transmitted=09 00000656 16.88569069 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2673: 44980 bytes transmitted=09 00000657 16.88578796 =09 00000658 16.88579369 =09 00000659 16.88579941 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000660 16.88580704 LIBUSB-DRIVER - transfer(): direction in 00000661 16.88581276 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000662 16.88582039 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000663 16.88582611 LIBUSB-DRIVER - transfer(): size 48960=09 00000664 16.88583374 LIBUSB-DRIVER - transfer(): sequence 2675=09 00000665 16.88583755 =09 00000666 16.90703201 =09 00000667 16.90703964 =09 00000668 16.90704918 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000669 16.90705490 LIBUSB-DRIVER - transfer(): direction in 00000670 16.90706253 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000671 16.90706825 LIBUSB-DRIVER - transfer(): size 768=09 00000672 16.90707588 LIBUSB-DRIVER - transfer(): sequence 2676=09 00000673 16.90707970 =09 00000674 17.19945908 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2675: 44984 bytes transmitted=09 00000675 17.19955826 =09 00000676 17.19956398 =09 00000677 17.19957352 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000678 17.19957733 LIBUSB-DRIVER - transfer(): direction in 00000679 17.19958687 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000680 17.19959259 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000681 17.19960022 LIBUSB-DRIVER - transfer(): size 48960=09 00000682 17.19960594 LIBUSB-DRIVER - transfer(): sequence 2677=09 00000683 17.19960976 =09 00000684 17.39192009 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2676: 14 bytes transmitted=09 00000685 17.40908813 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2677: 35280 bytes transmitted=09 00000686 17.40920639 =09 00000687 17.40921211 =09 00000688 17.40921974 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000689 17.40922546 LIBUSB-DRIVER - transfer(): direction in 00000690 17.40923309 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000691 17.40924072 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000692 17.40924644 LIBUSB-DRIVER - transfer(): size 48960=09 00000693 17.40925407 LIBUSB-DRIVER - transfer(): sequence 2678=09 00000694 17.40925789 =09 00000695 17.41392326 =09 00000696 17.41393089 =09 00000697 17.41394043 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000698 17.41394615 LIBUSB-DRIVER - transfer(): direction in 00000699 17.41395378 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000700 17.41395950 LIBUSB-DRIVER - transfer(): size 768=09 00000701 17.41396713 LIBUSB-DRIVER - transfer(): sequence 2679=09 00000702 17.41397095 =09 00000703 17.89028358 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2679: 14 bytes transmitted=09 00000704 17.89030838 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2678: 43216 bytes transmitted=09 00000705 17.89044380 =09 00000706 17.89044952 =09 00000707 17.89045715 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000708 17.89046288 LIBUSB-DRIVER - transfer(): direction in 00000709 17.89047050 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000710 17.89047813 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000711 17.89048576 LIBUSB-DRIVER - transfer(): size 48960=09 00000712 17.89049149 LIBUSB-DRIVER - transfer(): sequence 2680=09 00000713 17.89049530 =09 00000714 17.91196632 =09 00000715 17.91197395 =09 00000716 17.91198158 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000717 17.91198730 LIBUSB-DRIVER - transfer(): direction in 00000718 17.91199493 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000719 17.91200256 LIBUSB-DRIVER - transfer(): size 768=09 00000720 17.91200829 LIBUSB-DRIVER - transfer(): sequence 2681=09 00000721 17.91201210 =09 00000722 18.22346306 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2680: 3352 bytes transmitted=09 00000723 18.22355652 =09 00000724 18.22356224 =09 00000725 18.22356987 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000726 18.22357559 LIBUSB-DRIVER - transfer(): direction in 00000727 18.22358322 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000728 18.22358894 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000729 18.22359657 LIBUSB-DRIVER - transfer(): size 48960=09 00000730 18.22360420 LIBUSB-DRIVER - transfer(): sequence 2682=09 00000731 18.22360802 =09 00000732 18.39905167 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2681: 14 bytes transmitted=09 00000733 18.42078209 =09 00000734 18.42078972 =09 00000735 18.42079735 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000736 18.42080498 LIBUSB-DRIVER - transfer(): direction in 00000737 18.42081070 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000738 18.42081833 LIBUSB-DRIVER - transfer(): size 768=09 00000739 18.42082405 LIBUSB-DRIVER - transfer(): sequence 2683=09 00000740 18.42082977 =09 00000741 18.89716339 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2683: 14 bytes transmitted=09 00000742 18.89719772 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2682: 44984 bytes transmitted=09 00000743 18.89730644 =09 00000744 18.89731407 =09 00000745 18.89731979 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000746 18.89732742 LIBUSB-DRIVER - transfer(): direction in 00000747 18.89733315 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000748 18.89734268 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000749 18.89734840 LIBUSB-DRIVER - transfer(): size 48960=09 00000750 18.89735603 LIBUSB-DRIVER - transfer(): sequence 2684=09 00000751 18.89735985 =09 00000752 18.91883278 =09 00000753 18.91884232 =09 00000754 18.91885185 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000755 18.91885567 LIBUSB-DRIVER - transfer(): direction in 00000756 18.91886520 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000757 18.91887093 LIBUSB-DRIVER - transfer(): size 768=09 00000758 18.91887856 LIBUSB-DRIVER - transfer(): sequence 2685=09 00000759 18.91888237 =09 00000760 19.24747276 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2684: 44980 bytes transmitted=09 00000761 19.24759102 =09 00000762 19.24759674 =09 00000763 19.24760437 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000764 19.24761009 LIBUSB-DRIVER - transfer(): direction in 00000765 19.24761963 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000766 19.24762535 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000767 19.24763298 LIBUSB-DRIVER - transfer(): size 48960=09 00000768 19.24763870 LIBUSB-DRIVER - transfer(): sequence 2686=09 00000769 19.24764442 =09 00000770 19.40099144 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2685: 14 bytes transmitted=09 00000771 19.41791725 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2686: 28932 bytes transmitted=09 00000772 19.41802979 =09 00000773 19.41803360 =09 00000774 19.41804314 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000775 19.41804695 LIBUSB-DRIVER - transfer(): direction in 00000776 19.41805649 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000777 19.41806412 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000778 19.41806984 LIBUSB-DRIVER - transfer(): size 48960=09 00000779 19.41807556 LIBUSB-DRIVER - transfer(): sequence 2687=09 00000780 19.41807938 =09 00000781 19.42277718 =09 00000782 19.42278290 =09 00000783 19.42279243 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000784 19.42280006 LIBUSB-DRIVER - transfer(): direction in 00000785 19.42280579 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000786 19.42281342 LIBUSB-DRIVER - transfer(): size 768=09 00000787 19.42281723 LIBUSB-DRIVER - transfer(): sequence 2688=09 00000788 19.42282104 =09 00000789 19.89866066 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2688: 14 bytes transmitted=09 00000790 19.89868736 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2687: 43744 bytes transmitted=09 00000791 19.89880371 =09 00000792 19.89881134 =09 00000793 19.89881706 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000794 19.89882469 LIBUSB-DRIVER - transfer(): direction in 00000795 19.89883041 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000796 19.89883804 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000797 19.89884377 LIBUSB-DRIVER - transfer(): size 48960=09 00000798 19.89885139 LIBUSB-DRIVER - transfer(): sequence 2689=09 00000799 19.89885521 =09 00000800 19.91984558 =09 00000801 19.91985321 =09 00000802 19.91986084 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000803 19.91986847 LIBUSB-DRIVER - transfer(): direction in 00000804 19.91987419 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000805 19.91988182 LIBUSB-DRIVER - transfer(): size 768=09 00000806 19.91988754 LIBUSB-DRIVER - transfer(): sequence 2690=09 00000807 19.91988945 =09 00000808 20.27145767 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2689: 4060 bytes transmitted=09 00000809 20.27156830 =09 00000810 20.27157593 =09 00000811 20.27158165 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000812 20.27158928 LIBUSB-DRIVER - transfer(): direction in 00000813 20.27159500 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000814 20.27160263 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000815 20.27160835 LIBUSB-DRIVER - transfer(): size 48960=09 00000816 20.27161598 LIBUSB-DRIVER - transfer(): sequence 2691=09 00000817 20.27161980 =09 00000818 20.39612007 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2690: 14 bytes transmitted=09 00000819 20.41790199 =09 00000820 20.41791153 =09 00000821 20.41791725 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000822 20.41792488 LIBUSB-DRIVER - transfer(): direction in 00000823 20.41793060 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000824 20.41793823 LIBUSB-DRIVER - transfer(): size 768=09 00000825 20.41794395 LIBUSB-DRIVER - transfer(): sequence 2692=09 00000826 20.41794968 =09 00000827 20.89321709 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2692: 14 bytes transmitted=09 00000828 20.89324951 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2691: 44980 bytes transmitted=09 00000829 20.89338112 =09 00000830 20.89338875 =09 00000831 20.89341736 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000832 20.89342117 LIBUSB-DRIVER - transfer(): direction in 00000833 20.89344025 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000834 20.89344597 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000835 20.89345360 LIBUSB-DRIVER - transfer(): size 48960=09 00000836 20.89347076 LIBUSB-DRIVER - transfer(): sequence 2693=09 00000837 20.89347649 =09 00000838 20.91494179 =09 00000839 20.91494560 =09 00000840 20.91495514 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000841 20.91497040 LIBUSB-DRIVER - transfer(): direction in 00000842 20.91497993 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000843 20.91498375 LIBUSB-DRIVER - transfer(): size 768=09 00000844 20.91500282 LIBUSB-DRIVER - transfer(): sequence 2694=09 00000845 20.91500664 =09 00000846 21.29553413 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2693: 44984 bytes transmitted=09 00000847 21.29569244 =09 00000848 21.29569817 =09 00000849 21.29570580 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000850 21.29572105 LIBUSB-DRIVER - transfer(): direction in 00000851 21.29572868 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000852 21.29573441 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000853 21.29576111 LIBUSB-DRIVER - transfer(): size 48960=09 00000854 21.29576874 LIBUSB-DRIVER - transfer(): sequence 2695=09 00000855 21.29578400 =09 00000856 21.40063858 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2694: 14 bytes transmitted=09 00000857 21.41799164 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2695: 19756 bytes transmitted=09 00000858 21.41813660 =09 00000859 21.41815186 =09 00000860 21.41816139 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000861 21.41816711 LIBUSB-DRIVER - transfer(): direction in 00000862 21.41818619 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000863 21.41819000 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000864 21.41819954 LIBUSB-DRIVER - transfer(): size 48960=09 00000865 21.41820526 LIBUSB-DRIVER - transfer(): sequence 2696=09 00000866 21.41821861 =09 00000867 21.42374611 =09 00000868 21.42375374 =09 00000869 21.42375946 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000870 21.42377853 LIBUSB-DRIVER - transfer(): direction in 00000871 21.42378426 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000872 21.42379189 LIBUSB-DRIVER - transfer(): size 768=09 00000873 21.42380714 LIBUSB-DRIVER - transfer(): sequence 2697=09 00000874 21.42381096 =09 00000875 21.89778709 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2697: 14 bytes transmitted=09 00000876 21.89781380 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2696: 43040 bytes transmitted=09 00000877 21.89791107 =09 00000878 21.89791679 =09 00000879 21.89792442 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000880 21.89793015 LIBUSB-DRIVER - transfer(): direction in 00000881 21.89793777 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000882 21.89794540 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000883 21.89795113 LIBUSB-DRIVER - transfer(): size 48960=09 00000884 21.89795876 LIBUSB-DRIVER - transfer(): sequence 2698=09 00000885 21.89796257 =09 00000886 21.91987801 =09 00000887 21.91988564 =09 00000888 21.91989517 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000889 21.91989899 LIBUSB-DRIVER - transfer(): direction in 00000890 21.91990852 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000891 21.91991425 LIBUSB-DRIVER - transfer(): size 768=09 00000892 21.91992188 LIBUSB-DRIVER - transfer(): sequence 2699=09 00000893 21.91992569 =09 00000894 22.31945610 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2698: 3528 bytes transmitted=09 00000895 22.31954765 =09 00000896 22.31955147 =09 00000897 22.31956100 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000898 22.31956482 LIBUSB-DRIVER - transfer(): direction in 00000899 22.31957436 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000900 22.31958008 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000901 22.31958771 LIBUSB-DRIVER - transfer(): size 48960=09 00000902 22.31959343 LIBUSB-DRIVER - transfer(): sequence 2700=09 00000903 22.31959724 =09 00000904 22.39594078 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2699: 14 bytes transmitted=09 00000905 22.41795349 =09 00000906 22.41795921 =09 00000907 22.41796875 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000908 22.41797638 LIBUSB-DRIVER - transfer(): direction in 00000909 22.41798401 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000910 22.41799164 LIBUSB-DRIVER - transfer(): size 768=09 00000911 22.41799736 LIBUSB-DRIVER - transfer(): sequence 2701=09 00000912 22.41799927 =09 00000913 22.69241524 LIBUSB-DRIVER - dispatch_power(): IRP_MN_SET_POWER: D2=09 00000914 22.69923592 LIBUSB-DRIVER - on_power_state_complete(): D2=09 00000915 22.69926071 LIBUSB-DRIVER - dispatch_power(): IRP_MN_SET_POWER: D2=09 00000916 22.70528221 LIBUSB-DRIVER - on_power_state_complete(): D2=09 00000917 22.89328766 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2701: 14 bytes transmitted=09 00000918 22.89331436 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2700: 44984 bytes transmitted=09 00000919 22.89340973 =09 00000920 22.89341736 =09 00000921 22.89342308 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000922 22.89343071 LIBUSB-DRIVER - transfer(): direction in 00000923 22.89343643 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000924 22.89344406 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000925 22.89345932 LIBUSB-DRIVER - transfer(): size 48960=09 00000926 22.89346695 LIBUSB-DRIVER - transfer(): sequence 2702=09 00000927 22.89347076 =09 00000928 22.91766739 =09 00000929 22.91767502 =09 00000930 22.91768456 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000931 22.91769028 LIBUSB-DRIVER - transfer(): direction in 00000932 22.91769791 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000933 22.91770363 LIBUSB-DRIVER - transfer(): size 768=09 00000934 22.91771126 LIBUSB-DRIVER - transfer(): sequence 2703=09 00000935 22.91771507 =09 00000936 23.34347916 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2702: 44980 bytes transmitted=09 00000937 23.34358215 =09 00000938 23.34358788 =09 00000939 23.34359550 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000940 23.34360123 LIBUSB-DRIVER - transfer(): direction in 00000941 23.34360886 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000942 23.34361458 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000943 23.34362411 LIBUSB-DRIVER - transfer(): size 48960=09 00000944 23.34362984 LIBUSB-DRIVER - transfer(): sequence 2704=09 00000945 23.34363365 =09 00000946 23.39233017 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2703: 14 bytes transmitted=09 00000947 23.40918541 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2704: 11292 bytes transmitted=09 00000948 23.40927315 =09 00000949 23.40927887 =09 00000950 23.40928650 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000951 23.40929222 LIBUSB-DRIVER - transfer(): direction in 00000952 23.40929985 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000953 23.40930557 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000954 23.40931320 LIBUSB-DRIVER - transfer(): size 48960=09 00000955 23.40931892 LIBUSB-DRIVER - transfer(): sequence 2705=09 00000956 23.40932465 =09 00000957 23.41401863 =09 00000958 23.41403008 =09 00000959 23.41403770 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000960 23.41404533 LIBUSB-DRIVER - transfer(): direction in 00000961 23.41405487 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000962 23.41406441 LIBUSB-DRIVER - transfer(): size 768=09 00000963 23.41407013 LIBUSB-DRIVER - transfer(): sequence 2706=09 00000964 23.41407776 =09 00000965 23.88874817 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2706: 14 bytes transmitted=09 00000966 23.88876534 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2705: 44628 bytes transmitted=09 00000967 23.88883781 =09 00000968 23.88884163 =09 00000969 23.88884544 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000970 23.88885117 LIBUSB-DRIVER - transfer(): direction in 00000971 23.88885498 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000972 23.88885880 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000973 23.88886452 LIBUSB-DRIVER - transfer(): size 48960=09 00000974 23.88886833 LIBUSB-DRIVER - transfer(): sequence 2707=09 00000975 23.88887024 =09 00000976 23.91010475 =09 00000977 23.91010857 =09 00000978 23.91011429 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000979 23.91011810 LIBUSB-DRIVER - transfer(): direction in 00000980 23.91012192 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00000981 23.91012764 LIBUSB-DRIVER - transfer(): size 768=09 00000982 23.91012955 LIBUSB-DRIVER - transfer(): sequence 2708=09 00000983 23.91013145 =09 00000984 24.36741829 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2707: 5116 bytes transmitted=09 00000985 24.36747551 =09 00000986 24.36747932 =09 00000987 24.36748314 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00000988 24.36748505 LIBUSB-DRIVER - transfer(): direction in 00000989 24.36749077 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00000990 24.36749458 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00000991 24.36749840 LIBUSB-DRIVER - transfer(): size 48960=09 00000992 24.36750412 LIBUSB-DRIVER - transfer(): sequence 2709=09 00000993 24.36750793 =09 00000994 24.38502693 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2708: 14 bytes transmitted=09 00000995 24.40622520 =09 00000996 24.40623093 =09 00000997 24.40623474 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00000998 24.40623856 LIBUSB-DRIVER - transfer(): direction in 00000999 24.40624428 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00001000 24.40624619 LIBUSB-DRIVER - transfer(): size 768=09 00001001 24.40625000 LIBUSB-DRIVER - transfer(): sequence 2710=09 00001002 24.40625191 =09 00001003 24.88125038 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2710: 14 bytes transmitted=09 00001004 24.88126564 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2709: 44984 bytes transmitted=09 00001005 24.88134193 =09 00001006 24.88134575 =09 00001007 24.88134956 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00001008 24.88135529 LIBUSB-DRIVER - transfer(): direction in 00001009 24.88135910 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00001010 24.88136292 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00001011 24.88136864 LIBUSB-DRIVER - transfer(): size 48960=09 00001012 24.88137245 LIBUSB-DRIVER - transfer(): sequence 2711=09 00001013 24.88137436 =09 00001014 24.89843750 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2711: 0 bytes transmitted=09 00001015 24.89849472 =09 00001016 24.89849663 =09 00001017 24.89850044 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00001018 24.89850616 LIBUSB-DRIVER - transfer(): direction in 00001019 24.89850807 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00001020 24.89851189 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00001021 24.89851570 LIBUSB-DRIVER - transfer(): size 48960=09 00001022 24.89852142 LIBUSB-DRIVER - transfer(): sequence 2712=09 00001023 24.89852333 =09 00001024 24.90231323 =09 00001025 24.90231895 =09 00001026 24.90232277 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer=09 00001027 24.90232658 LIBUSB-DRIVER - transfer(): direction in 00001028 24.90233231 LIBUSB-DRIVER - transfer(): endpoint 0x82=09 00001029 24.90233612 LIBUSB-DRIVER - transfer(): size 768=09 00001030 24.90233994 LIBUSB-DRIVER - transfer(): sequence 2713=09 00001031 24.90234184 =09 00001032 25.37741089 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 2713: 14 bytes transmitted=09 00001033 25.37743568 LIBUSB-DRIVER - isoch transfer_complete(): sequence 2712: 41980 bytes transmitted=09 00001034 25.37751389 =09 00001035 25.37751770 =09 00001036 25.37752724 LIBUSB-DRIVER - transfer(): isochronous transfer=09 00001037 25.37753105 LIBUSB-DRIVER - transfer(): direction in 00001038 25.37754059 LIBUSB-DRIVER - transfer(): endpoint 0x81=09 00001039 25.37754631 LIBUSB-DRIVER - transfer(): packet_size 0xc0=09 00001040 25.37755394 LIBUSB-DRIVER - transfer(): size 48960=09 00001041 25.37755966 LIBUSB-DRIVER - transfer(): sequence 2714=09 00001042 25.37756538 =09 00001... [truncated message content] |
|
From: Krakora, R. V <rob...@de...> - 2007-08-23 18:12:53
|
Here is what I am seeing... LIBUSB-DRIVER - on_power_state_complete(): D0 LIBUSB-DRIVER - release_all_interfaces(): releasing all interfaces bound to file object 0x8946d180 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 708: 14 bytes transmitted LIBUSB-DRIVER - on_power_state_complete(): D0 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 709 =20 =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 710 =20 =20 =20 LIBUSB-DRIVER - abort_endpoint(): endpoint 0x81 LIBUSB-DRIVER - abort_endpoint(): timeout 5000 LIBUSB-DRIVER - isoch transfer_complete(): sequence 710: 44980 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 711 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 709: 26 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 711: 44984 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 712 =20 =20 =20 LIBUSB-DRIVER - vendor_class_request(): type: class LIBUSB-DRIVER - vendor_class_request(): recipient: interface LIBUSB-DRIVER - vendor_class_request(): request: 0x09 LIBUSB-DRIVER - vendor_class_request(): value: 0x020e LIBUSB-DRIVER - vendor_class_request(): index: 0x0002 LIBUSB-DRIVER - vendor_class_request(): size: 9 LIBUSB-DRIVER - vendor_class_request(): direction: out LIBUSB-DRIVER - vendor_class_request(): timeout: 10000 LIBUSB-DRIVER - vendor_class_request(): 9 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 713 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 713: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 712: 44980 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 714 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 715 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 715: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 714: 28752 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 716 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 717 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 716: 44984 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 718 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 717: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 718: 15876 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 719 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 720 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 720: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 719: 40748 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 721 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 722 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 721: 44984 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 723 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 722: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 723: 21696 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 724 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 725 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 725: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 724: 35280 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 726 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 727 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 726: 44980 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 728 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 727: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 728: 29104 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 729 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 730 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 730: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 729: 43220 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 731 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 731: 528 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 732 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 733 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 732: 42512 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 734 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 733: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 734: 28400 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 735 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 736 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 736: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 735: 41984 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 737 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 737: 2468 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 738 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 739 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 738: 44452 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 740 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 739: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 740: 27696 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 741 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 742 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 742: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 741: 38632 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 743 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 744 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 743: 44980 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 745 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 744: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 745: 31928 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 746 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 747 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 747: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 746: 44808 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 748 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 748: 2116 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 749 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 750 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 749: 44100 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 751 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 750: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 751: 31224 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 752 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 753 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 753: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 752: 44100 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 754 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 755 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 754: 4232 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 756 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 755: 14 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 757 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 757: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 756: 44980 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 758 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 759 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 758: 44984 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 760 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 759: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 760: 26284 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 761 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 762 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 762: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 761: 41628 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 763 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 764 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 763: 44984 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 765 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 764: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 765: 27340 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 766 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 767 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 767: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 766: 37220 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 768 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 769 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 768: 44984 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 770 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 769: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 770: 32988 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 771 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 772 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 772: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 771: 44276 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 773 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 774 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 773: 44980 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 775 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 774: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 775: 38456 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 776 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 777 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 777: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 776: 43044 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 778 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 779 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 778: 2996 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 780 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 779: 14 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 781 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 781: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 780: 44984 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 782 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 783 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 782: 44980 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 784 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 783: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 784: 30872 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 785 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 786 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 786: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 785: 42864 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 787 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 788 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 787: 3000 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 789 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 788: 14 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 790 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 790: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 789: 44984 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 791 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 792 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 791: 44980 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 793 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 792: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 793: 23460 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 794 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 795 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 795: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 794: 44808 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 796 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 797 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 796: 4940 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 798 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 797: 14 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 799 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 799: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 798: 44980 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 800 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 801 =20 LIBUSB-DRIVER - dispatch_power(): IRP_MN_SET_POWER: D2 LIBUSB-DRIVER - on_power_state_complete(): D2 LIBUSB-DRIVER - dispatch_power(): IRP_MN_SET_POWER: D2 LIBUSB-DRIVER - on_power_state_complete(): D2 LIBUSB-DRIVER - isoch transfer_complete(): sequence 800: 44984 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 802 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 801: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 802: 13404 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 803 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 804 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 804: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 803: 44100 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 805 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 805: 1412 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 806 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 807 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 806: 43396 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 808 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 807: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 808: 12700 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 809 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 810 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 810: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 809: 44452 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 811 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 812 =20 LIBUSB-DRIVER - isoch transfer_complete(): sequence 811: 4940 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 813 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 812: 14 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 814 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 814: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 813: 44984 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 815 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 816 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 816: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 815: 44980 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 817 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 818 =20 LIBUSB-DRIVER - bulk or interrupt transfer_complete(): sequence 818: 14 bytes transmitted LIBUSB-DRIVER - isoch transfer_complete(): sequence 817: 3000 bytes transmitted =20 =20 LIBUSB-DRIVER - transfer(): isochronous transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x81 LIBUSB-DRIVER - transfer(): packet_size 0xc0 LIBUSB-DRIVER - transfer(): size 48960 LIBUSB-DRIVER - transfer(): sequence 819 =20 =20 =20 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer LIBUSB-DRIVER - transfer(): direction in LIBUSB-DRIVER - transfer(): endpoint 0x82 LIBUSB-DRIVER - transfer(): size 768 LIBUSB-DRIVER - transfer(): sequence 820 =20 [2868] PDFFilter[c7c]>> Tracing DISABLED Rob Krakora Software Engineer Delphi Electronics & Safety e-mail: rob...@de... phone: 765-451-8574 -----Original Message----- From: Krakora, Robert V=20 Sent: Thursday, August 23, 2007 10:53 AM To: 'lib...@li...' Subject: Isochronous Issues I am receiving Isochronous packets from a streaming audio device and I am seeing it take 200 to 700 milliseconds after all of the packets have been received before the completion routine in the driver is called. However, the packets themselves have nice 999.999 uS spacing. I have control and interrupt endpoints open as well. 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: Monday, August 20, 2007 3:04 PM To: lib...@li... Subject: Libusb-win32-devel Digest, Vol 15, Issue 17 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: how can I pre-install libusb drivers? (Xiaofan Chen) ---------------------------------------------------------------------- Message: 1 Date: Mon, 20 Aug 2007 07:44:23 +0800 From: "Xiaofan Chen" <xia...@gm...> Subject: Re: [Libusb-win32-devel] how can I pre-install libusb drivers? To: "Benedikt Sauter" <sa...@si...>, lib...@li... Message-ID: <a27...@ma...> Content-Type: text/plain; charset=3DISO-8859-1 On 8/19/07, Benedikt Sauter <sa...@si...> wrote: > Hello, > > Did anybody know how I can pre install libusdrivers? > > I have an multi device, which can be get by an program different > firmwares. Each firmware normally means an own usb device. > > http://www.embedded-projects.net/usbprog (there is an screenshot for > better association) > > Now I have to pre install all possible important drivers. But How? Has > got anybody a hint? > Stephan has already done that for you. You need Inno Setup. Read the template Inno Setup file libusb\examples\driver_installer_template.iss. [quote] ; This examples demonstrates how libusb's drivers ; can be installed automatically along with your ; application using an installer. ; ; Requirements: Inno Setup (http://www.jrsoftware.org/isdl.php) "; To use this script, do the following: ; - copy libusb's driver (libusb0.sys, libusb0.dll) to this folder ; - create an .inf and .cab file using libusb's 'inf-wiward.exe' ; and save the generated files in this folder. ; - in this script replace <your_inf_file.inf> with the name of your .inf file ; - customize other settings (strings) ; - open this script with Inno Setup ; - compile and run" [/quote] It works for me under Windows XP SP2. Hope this helps. Regards, 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 End of Libusb-win32-devel Digest, Vol 15, Issue 17 ************************************************** ***************************************************************************= ************* 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 ***************************************************************************= ************* |
|
From: Krakora, R. V <rob...@de...> - 2007-08-23 14:53:18
|
I am receiving Isochronous packets from a streaming audio device and I am seeing it take 200 to 700 milliseconds after all of the packets have been received before the completion routine in the driver is called. However, the packets themselves have nice 999.999 uS spacing. I have control and interrupt endpoints open as well. 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: Monday, August 20, 2007 3:04 PM To: lib...@li... Subject: Libusb-win32-devel Digest, Vol 15, Issue 17 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: how can I pre-install libusb drivers? (Xiaofan Chen) ---------------------------------------------------------------------- Message: 1 Date: Mon, 20 Aug 2007 07:44:23 +0800 From: "Xiaofan Chen" <xia...@gm...> Subject: Re: [Libusb-win32-devel] how can I pre-install libusb drivers? To: "Benedikt Sauter" <sa...@si...>, lib...@li... Message-ID: <a27...@ma...> Content-Type: text/plain; charset=3DISO-8859-1 On 8/19/07, Benedikt Sauter <sa...@si...> wrote: > Hello, > > Did anybody know how I can pre install libusdrivers? > > I have an multi device, which can be get by an program different > firmwares. Each firmware normally means an own usb device. > > http://www.embedded-projects.net/usbprog (there is an screenshot for > better association) > > Now I have to pre install all possible important drivers. But How? Has > got anybody a hint? > Stephan has already done that for you. You need Inno Setup. Read the template Inno Setup file libusb\examples\driver_installer_template.iss. [quote] ; This examples demonstrates how libusb's drivers ; can be installed automatically along with your ; application using an installer. ; ; Requirements: Inno Setup (http://www.jrsoftware.org/isdl.php) "; To use this script, do the following: ; - copy libusb's driver (libusb0.sys, libusb0.dll) to this folder ; - create an .inf and .cab file using libusb's 'inf-wiward.exe' ; and save the generated files in this folder. ; - in this script replace <your_inf_file.inf> with the name of your .inf file ; - customize other settings (strings) ; - open this script with Inno Setup ; - compile and run" [/quote] It works for me under Windows XP SP2. Hope this helps. Regards, 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 End of Libusb-win32-devel Digest, Vol 15, Issue 17 ************************************************** ***************************************************************************= ************* 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 ***************************************************************************= ************* |
|
From: Benedikt S. <sa...@si...> - 2007-08-20 20:15:10
|
yes, now it works in my installer script too! thx! Regards Bene Am 20.8.2007 schrieb "Krakora, Robert V" <rob...@de...>: > >Works for me too under Windows XP SP2. > >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: Monday, August 20, 2007 3:04 PM >To: lib...@li... >Subject: Libusb-win32-devel Digest, Vol 15, Issue 17 > >Send Libusb-win32-devel mailing list submissions to >=09l...@li... > >To subscribe or unsubscribe via the World Wide Web, visit >=09https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >or, via email, send a message with subject or body 'help' to >=09l...@li... > >You can reach the person managing the list at >=09l...@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: how can I pre-install libusb drivers? (Xiaofan Chen) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Mon, 20 Aug 2007 07:44:23 +0800 >From: "Xiaofan Chen" <xia...@gm...> >Subject: Re: [Libusb-win32-devel] how can I pre-install libusb >=09drivers? >To: "Benedikt Sauter" <sa...@si...>, >=09l...@li... >Message-ID: >=09<a27...@ma...> >Content-Type: text/plain; charset=3DISO-8859-1 > >On 8/19/07, Benedikt Sauter <sa...@si...> wrote: >> Hello, >> >> Did anybody know how I can pre install libusdrivers? >> >> I have an multi device, which can be get by an program different >> firmwares. Each firmware normally means an own usb device. >> >> http://www.embedded-projects.net/usbprog (there is an screenshot for >> better association) >> >> Now I have to pre install all possible important drivers. But How? Has >> got anybody a hint? >> > >Stephan has already done that for you. You need Inno Setup. > >Read the template Inno Setup file >libusb\examples\driver_installer_template.iss. > >[quote] > >; This examples demonstrates how libusb's drivers >; can be installed automatically along with your >; application using an installer. >; >; Requirements: Inno Setup (http://www.jrsoftware.org/isdl.php) > >"; To use this script, do the following: >; - copy libusb's driver (libusb0.sys, libusb0.dll) to this folder >; - create an .inf and .cab file using libusb's 'inf-wiward.exe' >; and save the generated files in this folder. >; - in this script replace <your_inf_file.inf> with the name of your >.inf file >; - customize other settings (strings) >; - open this script with Inno Setup >; - compile and run" >[/quote] > >It works for me under Windows XP SP2. > >Hope this helps. > >Regards, >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 > > >End of Libusb-win32-devel Digest, Vol 15, Issue 17 >************************************************** > >****************************************************************************= ************ > >Note: If the reader of this message is not the intended recipient, or an em= ployee or agent responsible for delivering this message to the intended recip= ient, you are hereby notified that any dissemination, distribution or copying= of this communication is strictly prohibited. If you have received this comm= unication in error, please notify us immediately by replying to the message a= nd deleting it from your computer. Thank you. > >****************************************************************************= ************ > >------------------------------------------------------------------------- >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 |
|
From: Krakora, R. V <rob...@de...> - 2007-08-20 19:05:35
|
Works for me too under Windows XP SP2. 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: Monday, August 20, 2007 3:04 PM To: lib...@li... Subject: Libusb-win32-devel Digest, Vol 15, Issue 17 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: how can I pre-install libusb drivers? (Xiaofan Chen) ---------------------------------------------------------------------- Message: 1 Date: Mon, 20 Aug 2007 07:44:23 +0800 From: "Xiaofan Chen" <xia...@gm...> Subject: Re: [Libusb-win32-devel] how can I pre-install libusb drivers? To: "Benedikt Sauter" <sa...@si...>, lib...@li... Message-ID: <a27...@ma...> Content-Type: text/plain; charset=3DISO-8859-1 On 8/19/07, Benedikt Sauter <sa...@si...> wrote: > Hello, > > Did anybody know how I can pre install libusdrivers? > > I have an multi device, which can be get by an program different > firmwares. Each firmware normally means an own usb device. > > http://www.embedded-projects.net/usbprog (there is an screenshot for > better association) > > Now I have to pre install all possible important drivers. But How? Has > got anybody a hint? > Stephan has already done that for you. You need Inno Setup. Read the template Inno Setup file libusb\examples\driver_installer_template.iss. [quote] ; This examples demonstrates how libusb's drivers ; can be installed automatically along with your ; application using an installer. ; ; Requirements: Inno Setup (http://www.jrsoftware.org/isdl.php) "; To use this script, do the following: ; - copy libusb's driver (libusb0.sys, libusb0.dll) to this folder ; - create an .inf and .cab file using libusb's 'inf-wiward.exe' ; and save the generated files in this folder. ; - in this script replace <your_inf_file.inf> with the name of your .inf file ; - customize other settings (strings) ; - open this script with Inno Setup ; - compile and run" [/quote] It works for me under Windows XP SP2. Hope this helps. Regards, 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 End of Libusb-win32-devel Digest, Vol 15, Issue 17 ************************************************** ***************************************************************************= ************* 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 ***************************************************************************= ************* |
|
From: Xiaofan C. <xia...@gm...> - 2007-08-19 23:44:29
|
On 8/19/07, Benedikt Sauter <sa...@si...> wrote: > Hello, > > Did anybody know how I can pre install libusdrivers? > > I have an multi device, which can be get by an program different > firmwares. Each firmware normally means an own usb device. > > http://www.embedded-projects.net/usbprog (there is an screenshot for > better association) > > Now I have to pre install all possible important drivers. But How? Has > got anybody a hint? > Stephan has already done that for you. You need Inno Setup. Read the template Inno Setup file libusb\examples\driver_installer_template.iss. [quote] ; This examples demonstrates how libusb's drivers ; can be installed automatically along with your ; application using an installer. ; ; Requirements: Inno Setup (http://www.jrsoftware.org/isdl.php) "; To use this script, do the following: ; - copy libusb's driver (libusb0.sys, libusb0.dll) to this folder ; - create an .inf and .cab file using libusb's 'inf-wiward.exe' ; and save the generated files in this folder. ; - in this script replace <your_inf_file.inf> with the name of your .inf file ; - customize other settings (strings) ; - open this script with Inno Setup ; - compile and run" [/quote] It works for me under Windows XP SP2. Hope this helps. Regards, Xiaofan |
|
From: Spiro T. <an-...@sp...> - 2007-08-19 19:09:21
|
Hello Benedikt, * On Sun, Aug 19, 2007 at 04:43:35PM +0200 Benedikt Sauter wrote: > Did anybody know how I can pre install libusdrivers? Have a look into the DDK or WDK: Preinstalling Driver Files To preinstall driver files, your device installation application should follow these steps: 1. On the target system, create a directory for the driver files. If your device installation application installs an application, the driver files should be stored in a subdirectory of the application directory. 2. Copy all files in the driver package from the distribution media to the directory created in Step 1. The driver package includes the driver or drivers, the INF file, the catalog file, and so forth. 3. Call SetupCopyOEMInf (described in Platform SDK documentation), specifying the INF file in the directory created in Step 1. Specify SPOST_PATH for the OEMSourceMediaType parameter and specify NULL for the OEMSourceMediaLocation parameter. SetupCopyOEMInf copies the INF file for the driver package into the %windir%\Inf directory on the target system and directs SetupAPI to store the source location of the INF file in its list of preprocessed INF files. SetupCopyOEMInf also processes the catalog file, so the PnP manager will install the driver the next time it recognizes a device listed in the INF file. When the user plugs in the device, the PnP manager recognizes the device, finds the INF file copied by SetupCopyOEMInf, and installs the drivers copied in Step 2. (For more information about copying INF files, see Copying INFs.) (taken from: DDK 3790.1830 Help, Windows DDK/General Driver Information/Device Installation/Design Guide/Writing a device installation application) Also interesting: http://www.osronline.com/DDKx/install/custom-install_7n53.htm The key to success is the call to SetupCopyOEMInf(). HTH, Spiro. -- Spiro R. Trikaliotis http://opencbm.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/ |
|
From: Benedikt S. <sa...@si...> - 2007-08-19 14:43:43
|
Hello, Did anybody know how I can pre install libusdrivers? I have an multi device, which can be get by an program different firmwares. Each firmware normally means an own usb device. http://www.embedded-projects.net/usbprog (there is an screenshot for better association) Now I have to pre install all possible important drivers. But How? Has got anybody a hint? Or know somebody where driver assistent of windows search libusb0.sys and libusb0.dll when I took all my .inf Files into Windows\inf ? Bene |
|
From: Benedikt S. <sa...@si...> - 2007-08-19 08:16:29
|
hm - didn't exists a global folder where windows automatically search before it ask where are the files in the filesystem? Regards Bene Am 19.8.2007 schrieb "Xiaofan Chen" <xia...@gm...>: >On 8/18/07, Benedikt Sauter <sa...@si...> wrote: >> how can I do this, >> that the windows driver installer can find my driver for a libusb device >> automatically? I put my .inf into Windows\inf, the libusb0.dll into >> Windows\system32 and the .sys into >> Windows\system32\drivers >> >> But the install wizard of windows find the .inf but can not find the .sys >> automatically? >> >> In which folder I have to put the .sys and .dll files? >> > >You put them in the same folder say c:\tempdriver. I think it is not a good >idea to put it to the Windows\inf folder. > >------------------------------------------------------------------------- >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 |
|
From: Xiaofan C. <xia...@gm...> - 2007-08-19 00:17:05
|
On 8/18/07, Benedikt Sauter <sa...@si...> wrote: > how can I do this, > that the windows driver installer can find my driver for a libusb device > automatically? I put my .inf into Windows\inf, the libusb0.dll into > Windows\system32 and the .sys into > Windows\system32\drivers > > But the install wizard of windows find the .inf but can not find the .sys > automatically? > > In which folder I have to put the .sys and .dll files? > You put them in the same folder say c:\tempdriver. I think it is not a good idea to put it to the Windows\inf folder. |
|
From: Benedikt S. <sa...@si...> - 2007-08-18 15:03:45
|
Hello, how can I do this, that the windows driver installer can find my driver for a libusb device automatically? I put my .inf into Windows\inf, the libusb0.dll into Windows\system32 and the .sys into Windows\system32\drivers But the install wizard of windows find the .inf but can not find the .sys automatically? In which folder I have to put the .sys and .dll files? Regards Bene |
|
From: Krakora, R. V <rob...@de...> - 2007-08-17 18:55:10
|
All: Below are a couple of Hotfixes that you may want to pick up if you are working with Windows XP SP2 and are encountering USB problems. It looks like they will be available in SP3 as well. I installed them and my Windows SP2 PC seems to be running fine. However, use at your own risk!!! Read the disclaimers on the download site carefully. KB890927 Details here: http://support.microsoft.com/kb/890927=20 Download here: http://thehotfixshare.net/board/index.php?automodule=3Ddownloads&showfile= =3D 628=20 KB924692 Details here: http://support.microsoft.com/kb/924692 Download here: http://thehotfixshare.net/board/index.php?automodule=3Ddownloads&req= =3Ddownl oad&code=3Dconfirm_download&id=3D1012=20 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 5:54 PM To: lib...@li... Subject: Libusb-win32-devel Digest, Vol 15, Issue 13 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) (Carl Kenner) (Krakora, Robert V) 2. Re: lots of bugs (Carl Kenner) (Carl Kenner) (Carl Kenner) ---------------------------------------------------------------------- Message: 1 Date: Thu, 16 Aug 2007 15:17:10 -0400 From: "Krakora, Robert V" <rob...@de...> Subject: Re: [Libusb-win32-devel] lots of bugs (Carl Kenner) (Carl Kenner) To: <lib...@li...> Message-ID: =09 <3C7...@US... Auto.net> =09 Content-Type: text/plain; charset=3D"us-ascii" 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 ************************************************************************ **************** ------------------------------ Message: 2 Date: Fri, 17 Aug 2007 07:23:51 +0930 From: "Carl Kenner" <car...@gm...> Subject: Re: [Libusb-win32-devel] lots of bugs (Carl Kenner) (Carl Kenner) To: lib...@li... Message-ID: <fab...@ma...> Content-Type: text/plain; charset=3DISO-8859-1 OK, so how do I know if it's the filter driver? On 17/08/07, Krakora, Robert V <rob...@de...> wrote: > > 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: > > <3C7...@US... > Auto.net> > > 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. > > ************************************************************************ > **************** > > > > ------------------------------ > > 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: > > <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 > > > > > 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 > > > > > > > > > > > > ------------------------------------------------------------------------ > - > > 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. > > ************************************************************************ **************** > > ------------------------------------------------------------------------ - > 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 13 ************************************************** ***************************************************************************= ************* 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 ***************************************************************************= ************* |
|
From: Xiaofan C. <xia...@gm...> - 2007-08-17 01:19:18
|
On 8/17/07, Krakora, Robert V <rob...@de...> wrote: > > 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. > Strongly agreed. That is why I thought Carl can not solve his problem with the current libusb-win32 stable version. Regards, Xiaofan |
|
From: Carl K. <car...@gm...> - 2007-08-16 21:53:54
|
OK, so how do I know if it's the filter driver? On 17/08/07, Krakora, Robert V <rob...@de...> wrote: > > 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: > > <3C7...@US... > Auto.net> > > Content-Type: text/plain; charset="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=ISO-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=ISO-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=ISO-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. > > ************************************************************************ > **************** > > > > ------------------------------ > > 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=ISO-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=ISO-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=ISO-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: > > <OF3...@re...> > Content-Type: text/plain; charset="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 > > > > > 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 > > > > > > > > > > > > ------------------------------------------------------------------------ > - > > 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. > > **************************************************************************************** > > ------------------------------------------------------------------------- > 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 > |
|
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 ***************************************************************************= ************* |
|
From: Stephan M. <Ste...@ia...> - 2007-08-16 13:27:11
|
> My program suddenly stopped working. > Can anyone tell me what error number 116 is? > (My program isn't written in C) #define ETIMEDOUT 116 > > 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 > > > > > > > ------------------------------------------------------------------------- > 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 |
|
From: Carl K. <car...@gm...> - 2007-08-16 12:57:46
|
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 > > > |
|
From: Xiaofan C. <xia...@gm...> - 2007-08-15 23:32:18
|
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 |
|
From: Xiaofan C. <xia...@gm...> - 2007-08-15 23:29:19
|
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 |
|
From: Krakora, R. V <rob...@de...> - 2007-08-15 19:18:14
|
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 ***************************************************************************= ************* |
50 messages has been excluded from this view by a project administrator.
