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: Brian H. <Bri...@da...> - 2006-04-06 15:26:21
|
A small update: Since I was not able to compile the libusb *.sys driver with Microsoft's DDK (Windows Server 2003 SP1) under the X64 free build environment, I decided to fall back to the regular X86 free build environment, and got the same errors (see previous e-mail message below). I checked out the libusb code from CVS yesterday... If someone can compile successfully using the ddk_make subdirectory, please point me in the right direction :) Thanks, --Brian Hindman > -----Original Message----- > From: lib...@li... > [mailto:lib...@li...]On Behalf Of > Brian Hindman > Sent: Thursday, April 06, 2006 12:30 AM > To: lib...@li... > Subject: RE: [Libusb-win32-devel] Re: [Libusb-win32-devel] 64-bit > Windows > > > Stephen, > > Hi. I now have a test setup with a 64-bit AMD machine. > However, I was > unable to compile the *.sys driver with Server 2003 DDK x64 build > environment. > > See below for the errors (after retrieving libusb CVS code > earlier in the > day). > Looks like there are quite a few "unresolved external > symbols". Is there a > missing file or include somewhere? > > Please help if you can. > > By the way, the filter driver seemed to compile and link correctly :) > > Thanks, > --Brian Hindman > > C:\cygwin\home\Administrator\libusb\ddk_make>make_driver.bat > 1 file(s) copied. > ..\src\driver\abort_endpoint.c > ..\src\driver\claim_interface.c > ..\src\driver\clear_feature.c > ..\src\driver\dispatch.c > ..\src\driver\driver_debug.c > ..\src\driver\driver_registry.c > ..\src\driver\get_configuration.c > ..\src\driver\get_descriptor.c > ..\src\driver\get_interface.c > ..\src\driver\get_status.c > ..\src\driver\ioctl.c > ..\src\driver\libusb_driver.c > ..\src\driver\pnp.c > ..\src\driver\power.c > ..\src\driver\release_interface.c > ..\src\driver\reset_device.c > ..\src\driver\reset_endpoint.c > ..\src\driver\set_configuration.c > ..\src\driver\set_descriptor.c > ..\src\driver\set_feature.c > ..\src\driver\set_interface.c > ..\src\driver\transfer.c > ..\src\driver\vendor_request.c > 23 file(s) copied. > ..\src\driver\driver_api.h > ..\src\driver\driver_debug.h > ..\src\driver\libusb_driver.h > ..\src\driver\usbdlib_gcc.h > 4 file(s) copied. > ..\src\driver\libusb_driver_rc.rc > 1 file(s) copied. > ..\src\driver\..\common.rc > ..\src\driver\..\inf_wizard_rc.rc > ..\src\driver\..\resource.rc > 3 file(s) copied. > BUILD: Adding /Y to COPYCMD so xcopy ops won't hang. > BUILD: Object root set to: ==> objfre_wnet_AMD64 > BUILD: Compile and Link for AMD64 > BUILD: Loading C:\WINDDK\3790~1.183\build.dat... > BUILD: Computing Include file dependencies: > BUILD: Examining c:\cygwin\home\administrator\libusb\ddk_make > directory for > file > s to compile. > c:\cygwin\home\administrator\libusb\ddk_make - 24 source > files (3,050 > lines) > > BUILD: Compiling (NoSync) c:\cygwin\home\administrator\libusb\ddk_make > directory > > BUILD: Linking c:\cygwin\home\administrator\libusb\ddk_make directory > Linking Executable - output\amd64\libusb0.sys for AMD64 > errors in directory c:\cygwin\home\administrator\libusb\ddk_make > windows.obj : error LNK2019: unresolved external symbol __imp_free > referenced in > function usb_setup_async > usb.obj : error LNK2001: unresolved external symbol __imp_free > descriptors.obj : error LNK2001: unresolved external symbol __imp_free > registry.obj : error LNK2001: unresolved external symbol __imp_free > windows.obj : error LNK2019: unresolved external symbol > __imp_CreateEventA > refer > enced in function usb_setup_async > windows.obj : error LNK2019: unresolved external symbol __imp_malloc > referenced > in function usb_setup_async > usb.obj : error LNK2001: unresolved external symbol __imp_malloc > descriptors.obj : error LNK2001: unresolved external symbol > __imp_malloc > registry.obj : error LNK2001: unresolved external symbol __imp_malloc > windows.obj : error LNK2019: unresolved external symbol > __imp_GetLastError > refer > enced in function usb_submit_async > error.obj : error LNK2001: unresolved external symbol > __imp_GetLastError > install.obj : error LNK2001: unresolved external symbol > __imp_GetLastError > windows.obj : error LNK2019: unresolved external symbol > __imp_DeviceIoControl re > ferenced in function usb_submit_async > windows.obj : error LNK2019: unresolved external symbol > __imp_ResetEvent > referen > ced in function usb_submit_async > windows.obj : error LNK2019: unresolved external symbol > __imp_CloseHandle > refere > nced in function usb_free_async > windows.obj : error LNK2019: unresolved external symbol > __imp_GetOverlappedResul > t referenced in function usb_io_sync > windows.obj : error LNK2019: unresolved external symbol > __imp_CreateFileA > refere > nced in function usb_os_find_devices > windows.obj : error LNK2019: unresolved external symbol > __imp_WaitForSingleObjec > t referenced in function _usb_reap_async > usb.obj : error LNK2019: unresolved external symbol > __imp_getenv referenced > in f > unction usb_init > error.obj : error LNK2019: unresolved external symbol > __imp_OutputDebugStringA r > eferenced in function output_debug_string > error.obj : error LNK2019: unresolved external symbol __imp_strerror > referenced > in function usb_strerror > error.obj : error LNK2019: unresolved external symbol __imp_fprintf > referenced i > n function usb_error > error.obj : error LNK2001: unresolved external symbol __imp__iob > error.obj : error LNK2019: unresolved external symbol > __imp_FormatMessageA > refer > enced in function usb_win_error_to_string > install.obj : error LNK2019: unresolved external symbol > __imp_SetupFindNextLine > referenced in function usb_install_driver_np > install.obj : error LNK2019: unresolved external symbol > __imp_SetupDiDestroyDevi > ceInfoList referenced in function usb_install_driver_np > registry.obj : error LNK2001: unresolved external symbol > __imp_SetupDiDestroyDev > iceInfoList > install.obj : error LNK2019: unresolved external symbol > __imp_SetupDiSetDeviceRe > gistryPropertyA referenced in function usb_install_driver_np > registry.obj : error LNK2001: unresolved external symbol > __imp_SetupDiSetDeviceR > egistryPropertyA > install.obj : error LNK2019: unresolved external symbol > __imp_CM_Get_DevNode_Sta > tus referenced in function usb_install_driver_np > install.obj : error LNK2019: unresolved external symbol > __imp_SetupDiGetDeviceRe > gistryPropertyA referenced in function usb_install_driver_np > registry.obj : error LNK2001: unresolved external symbol > __imp_SetupDiGetDeviceR > egistryPropertyA > install.obj : error LNK2019: unresolved external symbol > __imp_SetupDiEnumDeviceI > nfo referenced in function usb_install_driver_np > registry.obj : error LNK2001: unresolved external symbol > __imp_SetupDiEnumDevice > Info > install.obj : error LNK2019: unresolved external symbol > __imp_SetupDiGetClassDev > sA referenced in function usb_install_driver_np > registry.obj : error LNK2001: unresolved external symbol > __imp_SetupDiGetClassDe > vsA > install.obj : error LNK2019: unresolved external symbol > __imp_SetupCopyOEMInfA r > eferenced in function usb_install_driver_np > install.obj : error LNK2019: unresolved external symbol > __imp_SetupGetStringFiel > dA referenced in function usb_install_driver_np > install.obj : error LNK2019: unresolved external symbol > __imp_SetupCloseInfFile > referenced in function usb_install_driver_np > install.obj : error LNK2019: unresolved external symbol > __imp_SetupFindFirstLine > A referenced in function usb_install_driver_np > install.obj : error LNK2019: unresolved external symbol > __imp_SetupOpenInfFileA > referenced in function usb_install_driver_np > install.obj : error LNK2019: unresolved external symbol > __imp_GetFullPathNameA r > eferenced in function usb_install_driver_np > install.obj : error LNK2019: unresolved external symbol > __imp_GetProcAddress > ref > erenced in function usb_install_driver_np > install.obj : error LNK2019: unresolved external symbol > __imp_LoadLibraryA > refer > enced in function usb_install_driver_np > install.obj : error LNK2019: unresolved external symbol > __imp_FreeLibrary > refere > nced in function usb_service_load_dll > install.obj : error LNK2019: unresolved external symbol __imp_Sleep > referenced i > n function usb_service_stop > install.obj : error LNK2019: unresolved external symbol __imp_fputs > referenced i > n function usb_touch_inf_file_np > install.obj : error LNK2019: unresolved external symbol __imp_fgets > referenced i > n function usb_touch_inf_file_np > install.obj : error LNK2019: unresolved external symbol __imp_fputws > referenced > in function usb_touch_inf_file_np > install.obj : error LNK2019: unresolved external symbol __imp_fclose > referenced > in function usb_touch_inf_file_np > install.obj : error LNK2019: unresolved external symbol __imp_fgetws > referenced > in function usb_touch_inf_file_np > install.obj : error LNK2019: unresolved external symbol __imp_fopen > referenced i > n function usb_touch_inf_file_np > install.obj : error LNK2019: unresolved external symbol > __imp_GetVersionExA > refe > renced in function usb_touch_inf_file_np > install.obj : error LNK2019: unresolved external symbol > __imp_SetupDiGetDeviceIn > stallParamsA referenced in function usb_install_needs_restart_np > install.obj : error LNK2019: unresolved external symbol > __imp_SetEnvironmentVari > ableA referenced in function usb_install_needs_restart_np > install.obj : error LNK2019: unresolved external symbol > __imp_RegCloseKey > refere > nced in function usb_uninstall_service_np > registry.obj : error LNK2001: unresolved external symbol > __imp_RegCloseKey > install.obj : error LNK2019: unresolved external symbol > __imp_RegDeleteValueA re > ferenced in function usb_uninstall_service_np > registry.obj : error LNK2001: unresolved external symbol > __imp_RegDeleteValueA > install.obj : error LNK2019: unresolved external symbol > __imp_RegOpenKeyExA > refe > renced in function usb_uninstall_service_np > registry.obj : error LNK2001: unresolved external symbol > __imp_RegOpenKeyExA > install.obj : error LNK2019: unresolved external symbol > __imp_PostMessageA > refer > enced in function usb_uninstall_service_np > install.obj : error LNK2019: unresolved external symbol > __imp_FindWindowA > refere > nced in function usb_uninstall_service_np > descriptors.obj : error LNK2019: unresolved external symbol > __imp_realloc > refere > nced in function usb_parse_interface > registry.obj : error LNK2019: unresolved external symbol > __imp_GetVersion > refere > nced in function usb_registry_is_nt > registry.obj : error LNK2019: unresolved external symbol > __imp_RegQueryValueExA > referenced in function usb_registry_get_property > registry.obj : error LNK2019: unresolved external symbol > __imp_SetupDiOpenDevReg > Key referenced in function usb_registry_get_property > registry.obj : error LNK2019: unresolved external symbol > __imp_RegSetValueExA re > ferenced in function usb_registry_set_property > registry.obj : error LNK2019: unresolved external symbol > __imp_SetupDiCallClassI > nstaller referenced in function usb_registry_set_device_state > registry.obj : error LNK2019: unresolved external symbol > __imp_SetupDiSetClassIn > stallParamsA referenced in function usb_registry_set_device_state > registry.obj : error LNK2019: unresolved external symbol > __imp_RegEnumKeyExA > ref > erenced in function usb_registry_get_all_class_keys > bufferoverflowk.lib(gs_support.obj) : error LNK2019: > unresolved external > symbol > DriverEntry referenced in function GsDriverEntry > output\amd64\libusb0.sys : error LNK1120: 56 unresolved externals > BUILD: Done > > 1 executable built - 73 Errors > > > -----Original Message----- > > From: lib...@li... > > [mailto:lib...@li...]On Behalf Of > > Stephan Meyer > > Sent: Saturday, March 18, 2006 8:09 AM > > To: lib...@li... > > Subject: [Libusb-win32-devel] Re: [Libusb-win32-devel] > 64-bit Windows > > libusb build - anyone done it yet? > > > > > > > > > > Check out the latest version from the CVS. This version can be > > compiled using the Server 2003 DDK x64 build environments. > > > > I don't know if the CVS code actually runs on 64-bit Windows > > because I have no 64-bit system to test it on. > > > > Let me know if it works, > > > > Stephan > > > > > > > Hi. Has anyone ported libusb-win32 to 64-bit Windows? > > > I would rather not re-invent the wheel if I did not have to... > > > > > > If anyone is willing to send me or point me to their code, > > > I would be very grateful. > > > > > > I know that the big change in 64-bit Windows is that > > > pointers are now 64-bit. But, many other data types are > > > still 32-bit... > > > > > > Thanks, > > > --Brian Hindman > > > > > > > -----Original Message----- > > > > From: lib...@li... > > > > [mailto:lib...@li...]On > > > > Behalf Of Peer Royla > > > > Sent: Wednesday, March 01, 2006 3:59 AM > > > > To: lib...@li... > > > > Subject: [Libusb-win32-devel] compiling Error > > > > > > > > > > > > Hello , > > > > > > > > I tried to compile the driver by WINDDK, wrote Makefile > > and SOURCES. > > > > > > > > then type build and get 2000 errors like this: > > > > > > > > winddk\2600.1106\inc\ddk\wdm\wxp\usb100.h(137) : error > > > > C2061: syntax error > > > > : identifier 'bDescriptorType' > > > > > > > > dont know how to handle this. > > > > > > > > Anybody know the Answer? > > > > > > > > > > > > Peer > > > > > > > > -- > > > > Telefonieren Sie schon oder sparen Sie noch? > > > > NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie > > > > > > > > > > > > ------------------------------------------------------- > > > > This SF.Net email is sponsored by xPML, a groundbreaking > > > > scripting language > > > > that extends applications into web and mobile media. Attend > > > > the live webcast > > > > and join the prime developer group breaking into this new > > > > coding territory! > > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720& > > > dat=121642 > > > _______________________________________________ > > > Libusb-win32-devel mailing list > > > Lib...@li... > > > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > > > > > > -- > > > No virus found in this incoming message. > > > Checked by AVG Free Edition. > > > Version: 7.1.375 / Virus Database: 268.1.1/271 - Release > > Date: 2/28/2006 > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by xPML, a groundbreaking > > scripting language > > > that extends applications into web and mobile media. Attend > > the live webcast > > > and join the prime developer group breaking into this new > > coding territory! > > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720& > dat=121642 > > _______________________________________________ > > Libusb-win32-devel mailing list > > Lib...@li... > > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > > > ______________________________________________________________________ > XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club! > > Jetzt gratis testen! http://freemail.web.de/home/landingpad/?mc=021130 > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking > scripting language > that extends applications into web and mobile media. Attend > the live webcast > and join the prime developer group breaking into this new > coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720& dat=121642 _______________________________________________ Libusb-win32-devel mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.2.2/280 - Release Date: 3/13/2006 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Libusb-win32-devel mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.3.5/301 - Release Date: 4/4/2006 |
|
From: Brian H. <Bri...@da...> - 2006-04-06 05:30:25
|
Stephen,
Hi. I now have a test setup with a 64-bit AMD machine. However, I was
unable to compile the *.sys driver with Server 2003 DDK x64 build
environment.
See below for the errors (after retrieving libusb CVS code earlier in the
day).
Looks like there are quite a few "unresolved external symbols". Is there a
missing file or include somewhere?
Please help if you can.
By the way, the filter driver seemed to compile and link correctly :)
Thanks,
--Brian Hindman
C:\cygwin\home\Administrator\libusb\ddk_make>make_driver.bat
1 file(s) copied.
..\src\driver\abort_endpoint.c
..\src\driver\claim_interface.c
..\src\driver\clear_feature.c
..\src\driver\dispatch.c
..\src\driver\driver_debug.c
..\src\driver\driver_registry.c
..\src\driver\get_configuration.c
..\src\driver\get_descriptor.c
..\src\driver\get_interface.c
..\src\driver\get_status.c
..\src\driver\ioctl.c
..\src\driver\libusb_driver.c
..\src\driver\pnp.c
..\src\driver\power.c
..\src\driver\release_interface.c
..\src\driver\reset_device.c
..\src\driver\reset_endpoint.c
..\src\driver\set_configuration.c
..\src\driver\set_descriptor.c
..\src\driver\set_feature.c
..\src\driver\set_interface.c
..\src\driver\transfer.c
..\src\driver\vendor_request.c
23 file(s) copied.
..\src\driver\driver_api.h
..\src\driver\driver_debug.h
..\src\driver\libusb_driver.h
..\src\driver\usbdlib_gcc.h
4 file(s) copied.
..\src\driver\libusb_driver_rc.rc
1 file(s) copied.
..\src\driver\..\common.rc
..\src\driver\..\inf_wizard_rc.rc
..\src\driver\..\resource.rc
3 file(s) copied.
BUILD: Adding /Y to COPYCMD so xcopy ops won't hang.
BUILD: Object root set to: ==> objfre_wnet_AMD64
BUILD: Compile and Link for AMD64
BUILD: Loading C:\WINDDK\3790~1.183\build.dat...
BUILD: Computing Include file dependencies:
BUILD: Examining c:\cygwin\home\administrator\libusb\ddk_make directory for
file
s to compile.
c:\cygwin\home\administrator\libusb\ddk_make - 24 source files (3,050
lines)
BUILD: Compiling (NoSync) c:\cygwin\home\administrator\libusb\ddk_make
directory
BUILD: Linking c:\cygwin\home\administrator\libusb\ddk_make directory
Linking Executable - output\amd64\libusb0.sys for AMD64
errors in directory c:\cygwin\home\administrator\libusb\ddk_make
windows.obj : error LNK2019: unresolved external symbol __imp_free
referenced in
function usb_setup_async
usb.obj : error LNK2001: unresolved external symbol __imp_free
descriptors.obj : error LNK2001: unresolved external symbol __imp_free
registry.obj : error LNK2001: unresolved external symbol __imp_free
windows.obj : error LNK2019: unresolved external symbol __imp_CreateEventA
refer
enced in function usb_setup_async
windows.obj : error LNK2019: unresolved external symbol __imp_malloc
referenced
in function usb_setup_async
usb.obj : error LNK2001: unresolved external symbol __imp_malloc
descriptors.obj : error LNK2001: unresolved external symbol __imp_malloc
registry.obj : error LNK2001: unresolved external symbol __imp_malloc
windows.obj : error LNK2019: unresolved external symbol __imp_GetLastError
refer
enced in function usb_submit_async
error.obj : error LNK2001: unresolved external symbol __imp_GetLastError
install.obj : error LNK2001: unresolved external symbol __imp_GetLastError
windows.obj : error LNK2019: unresolved external symbol
__imp_DeviceIoControl re
ferenced in function usb_submit_async
windows.obj : error LNK2019: unresolved external symbol __imp_ResetEvent
referen
ced in function usb_submit_async
windows.obj : error LNK2019: unresolved external symbol __imp_CloseHandle
refere
nced in function usb_free_async
windows.obj : error LNK2019: unresolved external symbol
__imp_GetOverlappedResul
t referenced in function usb_io_sync
windows.obj : error LNK2019: unresolved external symbol __imp_CreateFileA
refere
nced in function usb_os_find_devices
windows.obj : error LNK2019: unresolved external symbol
__imp_WaitForSingleObjec
t referenced in function _usb_reap_async
usb.obj : error LNK2019: unresolved external symbol __imp_getenv referenced
in f
unction usb_init
error.obj : error LNK2019: unresolved external symbol
__imp_OutputDebugStringA r
eferenced in function output_debug_string
error.obj : error LNK2019: unresolved external symbol __imp_strerror
referenced
in function usb_strerror
error.obj : error LNK2019: unresolved external symbol __imp_fprintf
referenced i
n function usb_error
error.obj : error LNK2001: unresolved external symbol __imp__iob
error.obj : error LNK2019: unresolved external symbol __imp_FormatMessageA
refer
enced in function usb_win_error_to_string
install.obj : error LNK2019: unresolved external symbol
__imp_SetupFindNextLine
referenced in function usb_install_driver_np
install.obj : error LNK2019: unresolved external symbol
__imp_SetupDiDestroyDevi
ceInfoList referenced in function usb_install_driver_np
registry.obj : error LNK2001: unresolved external symbol
__imp_SetupDiDestroyDev
iceInfoList
install.obj : error LNK2019: unresolved external symbol
__imp_SetupDiSetDeviceRe
gistryPropertyA referenced in function usb_install_driver_np
registry.obj : error LNK2001: unresolved external symbol
__imp_SetupDiSetDeviceR
egistryPropertyA
install.obj : error LNK2019: unresolved external symbol
__imp_CM_Get_DevNode_Sta
tus referenced in function usb_install_driver_np
install.obj : error LNK2019: unresolved external symbol
__imp_SetupDiGetDeviceRe
gistryPropertyA referenced in function usb_install_driver_np
registry.obj : error LNK2001: unresolved external symbol
__imp_SetupDiGetDeviceR
egistryPropertyA
install.obj : error LNK2019: unresolved external symbol
__imp_SetupDiEnumDeviceI
nfo referenced in function usb_install_driver_np
registry.obj : error LNK2001: unresolved external symbol
__imp_SetupDiEnumDevice
Info
install.obj : error LNK2019: unresolved external symbol
__imp_SetupDiGetClassDev
sA referenced in function usb_install_driver_np
registry.obj : error LNK2001: unresolved external symbol
__imp_SetupDiGetClassDe
vsA
install.obj : error LNK2019: unresolved external symbol
__imp_SetupCopyOEMInfA r
eferenced in function usb_install_driver_np
install.obj : error LNK2019: unresolved external symbol
__imp_SetupGetStringFiel
dA referenced in function usb_install_driver_np
install.obj : error LNK2019: unresolved external symbol
__imp_SetupCloseInfFile
referenced in function usb_install_driver_np
install.obj : error LNK2019: unresolved external symbol
__imp_SetupFindFirstLine
A referenced in function usb_install_driver_np
install.obj : error LNK2019: unresolved external symbol
__imp_SetupOpenInfFileA
referenced in function usb_install_driver_np
install.obj : error LNK2019: unresolved external symbol
__imp_GetFullPathNameA r
eferenced in function usb_install_driver_np
install.obj : error LNK2019: unresolved external symbol __imp_GetProcAddress
ref
erenced in function usb_install_driver_np
install.obj : error LNK2019: unresolved external symbol __imp_LoadLibraryA
refer
enced in function usb_install_driver_np
install.obj : error LNK2019: unresolved external symbol __imp_FreeLibrary
refere
nced in function usb_service_load_dll
install.obj : error LNK2019: unresolved external symbol __imp_Sleep
referenced i
n function usb_service_stop
install.obj : error LNK2019: unresolved external symbol __imp_fputs
referenced i
n function usb_touch_inf_file_np
install.obj : error LNK2019: unresolved external symbol __imp_fgets
referenced i
n function usb_touch_inf_file_np
install.obj : error LNK2019: unresolved external symbol __imp_fputws
referenced
in function usb_touch_inf_file_np
install.obj : error LNK2019: unresolved external symbol __imp_fclose
referenced
in function usb_touch_inf_file_np
install.obj : error LNK2019: unresolved external symbol __imp_fgetws
referenced
in function usb_touch_inf_file_np
install.obj : error LNK2019: unresolved external symbol __imp_fopen
referenced i
n function usb_touch_inf_file_np
install.obj : error LNK2019: unresolved external symbol __imp_GetVersionExA
refe
renced in function usb_touch_inf_file_np
install.obj : error LNK2019: unresolved external symbol
__imp_SetupDiGetDeviceIn
stallParamsA referenced in function usb_install_needs_restart_np
install.obj : error LNK2019: unresolved external symbol
__imp_SetEnvironmentVari
ableA referenced in function usb_install_needs_restart_np
install.obj : error LNK2019: unresolved external symbol __imp_RegCloseKey
refere
nced in function usb_uninstall_service_np
registry.obj : error LNK2001: unresolved external symbol __imp_RegCloseKey
install.obj : error LNK2019: unresolved external symbol
__imp_RegDeleteValueA re
ferenced in function usb_uninstall_service_np
registry.obj : error LNK2001: unresolved external symbol
__imp_RegDeleteValueA
install.obj : error LNK2019: unresolved external symbol __imp_RegOpenKeyExA
refe
renced in function usb_uninstall_service_np
registry.obj : error LNK2001: unresolved external symbol __imp_RegOpenKeyExA
install.obj : error LNK2019: unresolved external symbol __imp_PostMessageA
refer
enced in function usb_uninstall_service_np
install.obj : error LNK2019: unresolved external symbol __imp_FindWindowA
refere
nced in function usb_uninstall_service_np
descriptors.obj : error LNK2019: unresolved external symbol __imp_realloc
refere
nced in function usb_parse_interface
registry.obj : error LNK2019: unresolved external symbol __imp_GetVersion
refere
nced in function usb_registry_is_nt
registry.obj : error LNK2019: unresolved external symbol
__imp_RegQueryValueExA
referenced in function usb_registry_get_property
registry.obj : error LNK2019: unresolved external symbol
__imp_SetupDiOpenDevReg
Key referenced in function usb_registry_get_property
registry.obj : error LNK2019: unresolved external symbol
__imp_RegSetValueExA re
ferenced in function usb_registry_set_property
registry.obj : error LNK2019: unresolved external symbol
__imp_SetupDiCallClassI
nstaller referenced in function usb_registry_set_device_state
registry.obj : error LNK2019: unresolved external symbol
__imp_SetupDiSetClassIn
stallParamsA referenced in function usb_registry_set_device_state
registry.obj : error LNK2019: unresolved external symbol __imp_RegEnumKeyExA
ref
erenced in function usb_registry_get_all_class_keys
bufferoverflowk.lib(gs_support.obj) : error LNK2019: unresolved external
symbol
DriverEntry referenced in function GsDriverEntry
output\amd64\libusb0.sys : error LNK1120: 56 unresolved externals
BUILD: Done
1 executable built - 73 Errors
> -----Original Message-----
> From: lib...@li...
> [mailto:lib...@li...]On Behalf Of
> Stephan Meyer
> Sent: Saturday, March 18, 2006 8:09 AM
> To: lib...@li...
> Subject: [Libusb-win32-devel] Re: [Libusb-win32-devel] 64-bit Windows
> libusb build - anyone done it yet?
>
>
>
>
> Check out the latest version from the CVS. This version can be
> compiled using the Server 2003 DDK x64 build environments.
>
> I don't know if the CVS code actually runs on 64-bit Windows
> because I have no 64-bit system to test it on.
>
> Let me know if it works,
>
> Stephan
>
>
> > Hi. Has anyone ported libusb-win32 to 64-bit Windows?
> > I would rather not re-invent the wheel if I did not have to...
> >
> > If anyone is willing to send me or point me to their code,
> > I would be very grateful.
> >
> > I know that the big change in 64-bit Windows is that
> > pointers are now 64-bit. But, many other data types are
> > still 32-bit...
> >
> > Thanks,
> > --Brian Hindman
> >
> > > -----Original Message-----
> > > From: lib...@li...
> > > [mailto:lib...@li...]On
> > > Behalf Of Peer Royla
> > > Sent: Wednesday, March 01, 2006 3:59 AM
> > > To: lib...@li...
> > > Subject: [Libusb-win32-devel] compiling Error
> > >
> > >
> > > Hello ,
> > >
> > > I tried to compile the driver by WINDDK, wrote Makefile
> and SOURCES.
> > >
> > > then type build and get 2000 errors like this:
> > >
> > > winddk\2600.1106\inc\ddk\wdm\wxp\usb100.h(137) : error
> > > C2061: syntax error
> > > : identifier 'bDescriptorType'
> > >
> > > dont know how to handle this.
> > >
> > > Anybody know the Answer?
> > >
> > >
> > > Peer
> > >
> > > --
> > > Telefonieren Sie schon oder sparen Sie noch?
> > > NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email is sponsored by xPML, a groundbreaking
> > > scripting language
> > > that extends applications into web and mobile media. Attend
> > > the live webcast
> > > and join the prime developer group breaking into this new
> > > coding territory!
> > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&
> > dat=121642
> > _______________________________________________
> > Libusb-win32-devel mailing list
> > Lib...@li...
> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> >
> > --
> > No virus found in this incoming message.
> > Checked by AVG Free Edition.
> > Version: 7.1.375 / Virus Database: 268.1.1/271 - Release
> Date: 2/28/2006
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by xPML, a groundbreaking
> scripting language
> > that extends applications into web and mobile media. Attend
> the live webcast
> > and join the prime developer group breaking into this new
> coding territory!
> >
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
______________________________________________________________________
XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club!
Jetzt gratis testen! http://freemail.web.de/home/landingpad/?mc=021130
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Libusb-win32-devel mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.2.2/280 - Release Date: 3/13/2006
|
|
From: Thomas S. <th...@th...> - 2006-04-05 09:00:04
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<newbie>Oh, I see, thanks. The USB_TYPE_CLASS case handles both.
</newbie>.<br>
<br>
T<br>
<br>
Stephan Meyer wrote:
<blockquote
cite="mid...@re..."
type="cite"><br>
<font size="2"><tt><br>
Vendor requests are implemented.</tt></font>
<br>
<font size="2"><tt>From windows.c (version 0.1.10.1):</tt></font>
<br>
<br>
<font size="2"><tt> case USB_TYPE_VENDOR: </tt></font>
<br>
<font size="2"><tt> case USB_TYPE_CLASS:</tt></font>
<br>
<br>
<font size="2"><tt> req.vendor.type = (requesttype
>> 5) & 0x03;</tt></font>
<br>
<font size="2"><tt> req.vendor.recipient = requesttype
& 0x1F;</tt></font>
<br>
<font size="2"><tt> req.vendor.request = request;</tt></font>
<br>
<font size="2"><tt> req.vendor.value = value;</tt></font>
<br>
<font size="2"><tt> req.vendor.index = index;</tt></font>
<br>
<br>
<font size="2"><tt>....</tt></font>
<br>
<br>
<br>
<font size="2"><tt><br>
> I need to create a small wrapper in c that interfaces between a USB<br>
> device via libusb-win32 and a .NET program. One problem I've
just found<br>
> is that it appears that vendor requests are not implemented in<br>
> libusb-win32. Is this true? In windows.c: usb_control_msg()
{ case<br>
> USB_TYPE_VENDOR: } is empty. Some code that one of my
partners wrote<br>
> using the linux libusb sends a vendor request like so:<br>
> <br>
> retval = usb_control_msg (curHandle, USB_TYPE_VENDOR |
USB_RECIP_DEVICE<br>
> | USB_ENDPOINT_IN,
request, value, index,<br>
> buf, size,
USB_TIMEOUT);<br>
> <br>
> Is it possible to do this in libusb-win32 as it is, or does this
ability<br>
> need to be added. I have the win DDK and am trying to grok its
ioctl<br>
> stuff, but I'm new to this. Any tips? <br>
> <br>
> T<br>
> <br>
> <br>
> -------------------------------------------------------<br>
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
language<br>
> that extends applications into web and mobile media. Attend the
live
webcast<br>
> and join the prime developer group breaking into this new coding
territory!<br>
>
<a class="moz-txt-link-freetext" href="http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642">http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642</a><br>
> _______________________________________________<br>
> Libusb-win32-devel mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Lib...@li...">Lib...@li...</a><br>
> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel">https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel</a><br>
</tt></font>
</blockquote>
</body>
</html>
|
|
From: Stephan M. <Ste...@ia...> - 2006-04-05 07:42:39
|
Vendor requests are implemented.
From windows.c (version 0.1.10.1):
case USB_TYPE_VENDOR:
case USB_TYPE_CLASS:
req.vendor.type = (requesttype >> 5) & 0x03;
req.vendor.recipient = requesttype & 0x1F;
req.vendor.request = request;
req.vendor.value = value;
req.vendor.index = index;
....
> I need to create a small wrapper in c that interfaces between a USB
> device via libusb-win32 and a .NET program. One problem I've just found
> is that it appears that vendor requests are not implemented in
> libusb-win32. Is this true? In windows.c: usb_control_msg() { case
> USB_TYPE_VENDOR: } is empty. Some code that one of my partners wrote
> using the linux libusb sends a vendor request like so:
>
> retval = usb_control_msg (curHandle, USB_TYPE_VENDOR |
USB_RECIP_DEVICE
> | USB_ENDPOINT_IN, request, value, index,
> buf, size, USB_TIMEOUT);
>
> Is it possible to do this in libusb-win32 as it is, or does this ability
> need to be added. I have the win DDK and am trying to grok its ioctl
> stuff, but I'm new to this. Any tips?
>
> T
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
> that extends applications into web and mobile media. Attend the live
webcast
> and join the prime developer group breaking into this new coding
territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
|
|
From: Thomas S. <th...@th...> - 2006-04-05 07:30:08
|
I need to create a small wrapper in c that interfaces between a USB
device via libusb-win32 and a .NET program. One problem I've just found
is that it appears that vendor requests are not implemented in
libusb-win32. Is this true? In windows.c: usb_control_msg() { case
USB_TYPE_VENDOR: } is empty. Some code that one of my partners wrote
using the linux libusb sends a vendor request like so:
retval = usb_control_msg (curHandle, USB_TYPE_VENDOR | USB_RECIP_DEVICE
| USB_ENDPOINT_IN, request, value, index,
buf, size, USB_TIMEOUT);
Is it possible to do this in libusb-win32 as it is, or does this ability
need to be added. I have the win DDK and am trying to grok its ioctl
stuff, but I'm new to this. Any tips?
T
|
|
From: <li...@ze...> - 2006-04-02 21:02:31
|
* On 2006-03-28 Stephan Meyer <ste...@we...> wrote : > > > > Summarizing: I want the normal windows driver to handle my mouse, but > > > > still be able to talk to the other endpoints using libusb. What would > > > > be the best way to handle this with libusb-win32 ? > > > > Solution 1): Add feature reports to your mouse. So that you can use > > > Windows' HidD_SetFeature() and HidD_GetFeature() API functions > > > to send vendor specific commands to your device (I haven't done this > > > on my own, so I don't know if this solution actually works). > > > > I will still need one bulk OUT enpoint though, for the purpose of > > firmware uploading. > > You don't need the extra endpoint. You can use feature reports for > this as well. Thank you all for your help; Instead of using the provided library from atmel, I have now created my own USB client stack, and successfully implemented the get_feature and set_feature requests. Both configuration and upgrading of firmware works as a charm. -- :wq ^X^Cy^K^X^C^C^C^C |
|
From: Black M. <bla...@ho...> - 2006-03-30 22:35:28
|
Yes, its a known problem that threading + libusb = bad.
plus, that only tells you if its attached. What iv done, is send a control
message from my main read/write thread, and have the device return somethng
like 'AOK', this tells you if its available, and if its actualy functioning
(and aquired)
>From: "chen hai" <ch...@xa...>
>Reply-To: lib...@li...
>To: "libusb-win32-devel" <lib...@li...>
>Subject: [Libusb-win32-devel] usb_bulk_read() + usb_find_devices() =
>stalled USB?
>Date: Thu, 30 Mar 2006 15:07:07 +0800
>
>Hi, folks:
>
>I'm writing a small program sampling datas from a USB device.
>
>In one thread, I read USB data with the following line:
> size = usb_bulk_read(apu_usb_dev, 0x81, buf, 320, 20);
>
>In another thread, I check the availablity of that USB device by calling
>the
>following function fired by a timer for every 3 seconds.
>
>int APU_USB_Ready(LPARAM lParam)
>{
> struct usb_bus * bus ;
> struct usb_device * dev ;
>
> usb_find_devices();
> for (bus = usb_get_busses(); bus ; bus = bus -> next) {
> for (dev = bus -> devices; dev; dev = dev -> next) {
> if (dev -> descriptor.idVendor == 0x5345 &&
> dev -> descriptor.idProduct == 0x1234)
> return 1 ;
> }
> }
> return 0 ;
>}
>
>It works for 20-40 minutes, then suddenly, size, the return value of
>usb_bulk_read()
>would get something less than zero, and the USB line is stalled. I checking
>the online
>manual of usb_bulk_read() and couldn't get much information there.
>
>Removed the call of APU_USB_Ready(), the program kept running for more than
>5 hours without
>getting any "less than 0" error from usb_bulk_read().
>
>Is this a known problem?
>
>Thanks
>
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by xPML, a groundbreaking scripting language
>that extends applications into web and mobile media. Attend the live
>webcast
>and join the prime developer group breaking into this new coding territory!
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>_______________________________________________
>Libusb-win32-devel mailing list
>Lib...@li...
>https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
|
|
From: Stephan M. <ste...@we...> - 2006-03-30 18:32:34
|
What does usb_bulk_read() return when it fails?
What error string does usb_strerror() return?
> Hi, folks:
>
> I'm writing a small program sampling datas from a USB device.
>
> In one thread, I read USB data with the following line:
> size = usb_bulk_read(apu_usb_dev, 0x81, buf, 320, 20);
>
> In another thread, I check the availablity of that USB device by calling the
> following function fired by a timer for every 3 seconds.
>
> int APU_USB_Ready(LPARAM lParam)
> {
> struct usb_bus * bus ;
> struct usb_device * dev ;
>
> usb_find_devices();
> for (bus = usb_get_busses(); bus ; bus = bus -> next) {
> for (dev = bus -> devices; dev; dev = dev -> next) {
> if (dev -> descriptor.idVendor == 0x5345 &&
> dev -> descriptor.idProduct == 0x1234)
> return 1 ;
> }
> }
> return 0 ;
> }
>
> It works for 20-40 minutes, then suddenly, size, the return value of usb_bulk_read()
> would get something less than zero, and the USB line is stalled. I checking the online
> manual of usb_bulk_read() and couldn't get much information there.
>
> Removed the call of APU_USB_Ready(), the program kept running for more than 5 hours without
> getting any "less than 0" error from usb_bulk_read().
>
> Is this a known problem?
>
> Thanks
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
|
|
From: Cory S. <co...@mo...> - 2006-03-30 10:06:25
|
I can get libftdi to work in Cygwin, but also experience issues you describe (read basically fails). I'm using libftdi 0.7 and have tried both libusb-win32 0.1.10.1 and CVS HEAD as of today. libftdi DOES work for me without problem providing I compile libftdi and my application *without* -mno-cygwin. My ftdi/usb reads fail when I compile libftdi and my application with -mno-cygwin. Unfortunately, one of the things I'm building is a JNI DLL to be used by Java -- which pretty much requires -mno-cygwin. I can try to debug this, but I'd appreciate any suggestions about what kinds of things I should be looking for in particular, and where. Thanks, best, Cory ----- On 2006-01-09 03:23, <morper@te...> wrote: Has anyone tried to use libusb-win32 together with libftdi from intra2net? (http://www.intra2net.com/de/produkte/opensource/ftdi/index.php)= . I have the problem that, when I try to read data from the device via libftdi based on libusb-win32, I only receive some single bytes with very high values (between 248 and 255). Using the same software under Linux with libusb works correctly. Thanks for any suggestions. |
|
From: chen h. <ch...@xa...> - 2006-03-30 07:06:33
|
Hi, folks:
I'm writing a small program sampling datas from a USB device.
In one thread, I read USB data with the following line:
size = usb_bulk_read(apu_usb_dev, 0x81, buf, 320, 20);
In another thread, I check the availablity of that USB device by calling the
following function fired by a timer for every 3 seconds.
int APU_USB_Ready(LPARAM lParam)
{
struct usb_bus * bus ;
struct usb_device * dev ;
usb_find_devices();
for (bus = usb_get_busses(); bus ; bus = bus -> next) {
for (dev = bus -> devices; dev; dev = dev -> next) {
if (dev -> descriptor.idVendor == 0x5345 &&
dev -> descriptor.idProduct == 0x1234)
return 1 ;
}
}
return 0 ;
}
It works for 20-40 minutes, then suddenly, size, the return value of usb_bulk_read()
would get something less than zero, and the USB line is stalled. I checking the online
manual of usb_bulk_read() and couldn't get much information there.
Removed the call of APU_USB_Ready(), the program kept running for more than 5 hours without
getting any "less than 0" error from usb_bulk_read().
Is this a known problem?
Thanks
|
|
From: Stephan M. <ste...@we...> - 2006-03-28 19:01:18
|
Ich schick Dir meine Antworten als private Email, dann brauchen wir die (englischsprachigen) Mitglieder dieser Mailing-Liste nicht mit unserer Diskussion zu belasten. Stephan =20 > Hallo Herr Meyer, >=20 > ich schreibe das ganze dann nochmal auf Deutsch. Ich studiere Angewandte= =20 > Informatik an der Hochschule Bremen. Ich werde demn=E4chst mein Diplom=20 > schreiben. Als Thema schwebt mir eine Untersuchung und Dokumentation des= =20 > LibUSB-Projektes vor. Da ein Dozent ein Firma gr=FCndet, will dieser=20 > evtl.. LibUSB einsetzen, falls es sich als ausreichend stabil erweist.=20 > In dem Zusammenhang wollte ich fragen ob es UML-Diagramme oder andere=20 > Beschreibungen der Klassen und Methoden zusammenh=E4nge gibt. Das=20 > wichtigste bei der Frage ist, ob die Arbeit schon getan ist. Oder ob an=20 > einer Deutschen Ausarbeitung von eurer Seite aus Interesse besteht. >=20 >=20 > Gru=DF Peer >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting langu= age > that extends applications into web and mobile media. Attend the live web= cast > and join the prime developer group breaking into this new coding territo= ry! > http://sel.as-us.falkag.net/sel=3Fcmd=3Dlnk&kid=3D110944&bid=3D241720&dat=3D121642= > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club! =09 Jetzt gratis testen! http://freemail.web.de/home/landingpad/=3Fmc=3D021130 |
|
From: Stephan M. <ste...@we...> - 2006-03-28 18:56:21
|
> > Solution 1): Add feature reports to your mouse. So that you can use > > Windows' HidD=5FSetFeature() and HidD=5FGetFeature() API functions > > to send vendor specific commands to your device (I haven't done this > > on my own, so I don't know if this solution actually works). >=20 > You are right; reading the HID spec more closefully, I think this is the= > right thing to do.=20 >=20 ... >=20 > I will still need one bulk OUT enpoint though, for the purpose of > firmware uploading. You don't need the extra endpoint. You can use feature reports for=20 this as well. =20 >=20 > Thanks, >=20 > Ico >=20 > >=20 > > >=20 > > > I am developing an USB pointer device. The device acts as a 'normal'= > > > UBS mouse, so it is recognized by every OS without using special > > > drivers. This all works fine. > > >=20 > > > I need to be able to change configuration settings on the device as > > > well. For this I added an extra OUT endpoint where I can send specia= l > > > commands to; this is used for configuring the device and uploading n= ew > > > firmware. > > >=20 > > > With linux, the HID mouse is claimed by the usbhid driver right away= , > > > but using the usb=5Fdetach=5Fkernel=5Fdriver=5Fnp() function I can still tak= e > > > control over the device. libusb-win32 does not support this call, > > > however. > > >=20 > > > Summarizing: I want the normal windows driver to handle my mouse, bu= t > > > still be able to talk to the other endpoints using libusb. What wou= ld > > > be the best way to handle this with libusb-win32 =3F > > =20 >=20 > --=20 > :wq > ^X^Cy^K^X^C^C^C^C >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting langu= age > that extends applications into web and mobile media. Attend the live web= cast > and join the prime developer group breaking into this new coding territo= ry! > http://sel.as-us.falkag.net/sel=3Fcmd=3Dlnk&kid=3D110944&bid=3D241720&dat=3D121642= > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= Erweitern Sie FreeMail zu einem noch leistungsst=E4rkeren E-Mail-Postfach! =09 Mehr Infos unter http://freemail.web.de/home/landingpad/=3Fmc=3D021131 |
|
From: peer <Nig...@gm...> - 2006-03-28 10:34:59
|
Hallo Herr Meyer, ich schreibe das ganze dann nochmal auf Deutsch. Ich studiere Angewandte Informatik an der Hochschule Bremen. Ich werde demnächst mein Diplom schreiben. Als Thema schwebt mir eine Untersuchung und Dokumentation des LibUSB-Projektes vor. Da ein Dozent ein Firma gründet, will dieser evtl.. LibUSB einsetzen, falls es sich als ausreichend stabil erweist. In dem Zusammenhang wollte ich fragen ob es UML-Diagramme oder andere Beschreibungen der Klassen und Methoden zusammenhänge gibt. Das wichtigste bei der Frage ist, ob die Arbeit schon getan ist. Oder ob an einer Deutschen Ausarbeitung von eurer Seite aus Interesse besteht. Gruß Peer |
|
From: Robert M. <mar...@co...> - 2006-03-28 05:55:57
|
Stephan Meyer wrote: > I'm no HID expert, but I think what you're trying to accomplish can > be done completely without libusb-win32: > > Solution 1): Add feature reports to your mouse. So that you can use > Windows' HidD_SetFeature() and HidD_GetFeature() API functions > to send vendor specific commands to your device (I haven't done this > on my own, so I don't know if this solution actually works). This is the way to go for mice and keyboards. Our keyboard chips have a feature report and we are able to download data to the keyboard without any problems in Windows. Also a feature report does not break the boot-protocol for keyboards. |
|
From: <li...@ze...> - 2006-03-27 17:39:45
|
* On 2006-03-27 Stephan Meyer <ste...@we...> wrote : > I'm no HID expert, but I think what you're trying to accomplish can > be done completely without libusb-win32: > > Solution 1): Add feature reports to your mouse. So that you can use > Windows' HidD_SetFeature() and HidD_GetFeature() API functions > to send vendor specific commands to your device (I haven't done this > on my own, so I don't know if this solution actually works). You are right; reading the HID spec more closefully, I think this is the right thing to do. My only problem is that I am using a very inflexible USB firmware library from Atmel in my device, which does not seem to support feature request. Maybe rewriting (part of) this library is the best solution after all, since there are more limitations to it that I run into every now and then. I will still need one bulk OUT enpoint though, for the purpose of firmware uploading. Thanks, Ico > > > > > I am developing an USB pointer device. The device acts as a 'normal' > > UBS mouse, so it is recognized by every OS without using special > > drivers. This all works fine. > > > > I need to be able to change configuration settings on the device as > > well. For this I added an extra OUT endpoint where I can send special > > commands to; this is used for configuring the device and uploading new > > firmware. > > > > With linux, the HID mouse is claimed by the usbhid driver right away, > > but using the usb_detach_kernel_driver_np() function I can still take > > control over the device. libusb-win32 does not support this call, > > however. > > > > Summarizing: I want the normal windows driver to handle my mouse, but > > still be able to talk to the other endpoints using libusb. What would > > be the best way to handle this with libusb-win32 ? > -- :wq ^X^Cy^K^X^C^C^C^C |
|
From: Stephan M. <ste...@we...> - 2006-03-27 17:36:58
|
There is no documentation about this project available except the minimal API docs that you can find online. What do you need=3F Sorry, but I actually don't understand what you want to do. Writing a diploma thesis about libusb=3F I don't know your university's requirements for diploma thesis projects, but is writing a documentation for an existin= g=20 and finished project enough to get your diploma=3F BTW, you can also send me an email in german if you have any further=20 questions. Stephan > Hello, >=20 > I have to write my Diplomwork for my studies. So i am interrested in wri= ting > a German Documentation about the LIBUSB. The Thema should be mostly abou= t > the Win32 Version. Is there Code and UML documentation is this work to d= o=3F I > would give my work then free to the Projekt. Are You interested on this=3F= > When this work is done before, i have to choose another Theme for my wor= k.=20 >=20 > Sorry about my bad English. >=20 >=20 > Grettings Peer >=20 > --=20 > Echte DSL-Flatrate dauerhaft f=FCr 0,- Euro*! > "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting langu= age > that extends applications into web and mobile media. Attend the live web= cast > and join the prime developer group breaking into this new coding territo= ry! > http://sel.as-us.falkag.net/sel=3Fcmd=3Dlnk&kid=3D110944&bid=3D241720&dat=3D121642= > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/=3Fmc=3D021193 |
|
From: Stephan M. <ste...@we...> - 2006-03-27 17:05:33
|
I'm no HID expert, but I think what you're trying to accomplish can be done completely without libusb-win32: Solution 1): Add feature reports to your mouse. So that you can use Windows' HidD_SetFeature() and HidD_GetFeature() API functions to send vendor specific commands to your device (I haven't done this on my own, so I don't know if this solution actually works). Solution 2.) If 1.) doesn't work, then move your 'control endpoint' to a seperat interface that exposes itself as a vendor specific HID, i.e. build a composite device that consist of a HID mouse and of a custom HID. Then use the second custom HID interface to send your vendor specific commands. Stephan > Hello, > > I am developing an USB pointer device. The device acts as a 'normal' > UBS mouse, so it is recognized by every OS without using special > drivers. This all works fine. > > I need to be able to change configuration settings on the device as > well. For this I added an extra OUT endpoint where I can send special > commands to; this is used for configuring the device and uploading new > firmware. > > With linux, the HID mouse is claimed by the usbhid driver right away, > but using the usb_detach_kernel_driver_np() function I can still take > control over the device. libusb-win32 does not support this call, > however. > > Summarizing: I want the normal windows driver to handle my mouse, but > still be able to talk to the other endpoints using libusb. What would > be the best way to handle this with libusb-win32 ? > > Thank you very much, > > > > -- > :wq > ^X^Cy^K^X^C^C^C^C > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 |
|
From: <Kar...@pr...> - 2006-03-26 09:00:42
|
I will be out of the office starting 24.03.2006 and will not return un= til 28.03.2006. I will respond to your message when I return. In urgent matter please contact Markus Kraus (mar...@pr... ) or Johann Loesl (joh...@pr...). Ich bin zur Zeit nicht im B=FCro und werde Ihre Email nach meiner R=FCc= kkehr als bald als m=F6glich beantworten. In dringenden F=E4llen wenden Sie s= ich bitte an Herrn Kraus (mar...@pr...) oder Herrn L=F6sl (Joh...@pr...). Mit freundlichen Gr=FC=DFe With best regards Karl Achter = |
|
From: Black M. <bla...@ho...> - 2006-03-25 17:32:29
|
Isent this kinda the point of the 'filter' driver? to slap inbeween a usb device and windows and let you talk to the device behind windows back? >From: li...@ze... >Reply-To: lib...@li... >To: lib...@li... >Subject: [Libusb-win32-devel] Extra endpoints on HID mouse device >Date: Sat, 25 Mar 2006 12:23:49 +0100 > >Hello, > >I am developing an USB pointer device. The device acts as a 'normal' >UBS mouse, so it is recognized by every OS without using special >drivers. This all works fine. > >I need to be able to change configuration settings on the device as >well. For this I added an extra OUT endpoint where I can send special >commands to; this is used for configuring the device and uploading new >firmware. > >With linux, the HID mouse is claimed by the usbhid driver right away, >but using the usb_detach_kernel_driver_np() function I can still take >control over the device. libusb-win32 does not support this call, >however. > >Summarizing: I want the normal windows driver to handle my mouse, but >still be able to talk to the other endpoints using libusb. What would >be the best way to handle this with libusb-win32 ? > >Thank you very much, > > > >-- >:wq >^X^Cy^K^X^C^C^C^C > > >------------------------------------------------------- >This SF.Net email is sponsored by xPML, a groundbreaking scripting language >that extends applications into web and mobile media. Attend the live >webcast >and join the prime developer group breaking into this new coding territory! >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >_______________________________________________ >Libusb-win32-devel mailing list >Lib...@li... >https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
|
From: <li...@ze...> - 2006-03-25 11:23:45
|
Hello, I am developing an USB pointer device. The device acts as a 'normal' UBS mouse, so it is recognized by every OS without using special drivers. This all works fine. I need to be able to change configuration settings on the device as well. For this I added an extra OUT endpoint where I can send special commands to; this is used for configuring the device and uploading new firmware. With linux, the HID mouse is claimed by the usbhid driver right away, but using the usb_detach_kernel_driver_np() function I can still take control over the device. libusb-win32 does not support this call, however. Summarizing: I want the normal windows driver to handle my mouse, but still be able to talk to the other endpoints using libusb. What would be the best way to handle this with libusb-win32 ? Thank you very much, -- :wq ^X^Cy^K^X^C^C^C^C |
|
From: Black M. <bla...@ho...> - 2006-03-23 15:27:31
|
an explicit timeout pram for the setconfiguration and such functions would be nice (Since every other function allready has one) >From: Hugo Villeneuve <hu...@hu...> >Reply-To: lib...@li... >To: lib...@li... >Subject: Re: [Libusb-win32-devel] Problem with usb_set_configuration >Date: Wed, 22 Mar 2006 10:34:26 -0500 > >On Tue, 21 Mar 2006 19:38:49 +0100 >Stephan Meyer <ste...@we...> wrote: > > > > > > > > Hi, > > > My device is working fine under Linux. Using the exact same source >code, I have a problem > > > when I call the usb_set_configuration() function. I observed that this >function never returns. > > > > The function should time out after 5s and cancel the request. > > Which version are you using? Can you try the latest version > > from the CVS? > >I should mention that a problem with our device is not to be excluded. This >is a device that we designed. It uses a stock usb stack provided with the >microcontroller we are using (Microchip), and the device reports itself as >a HID device. > >Hugo. > >-- >------------------------- >Hugo Villeneuve > >hu...@hu... >http://www.hugovil.com >------------------------- > > >------------------------------------------------------- >This SF.Net email is sponsored by xPML, a groundbreaking scripting language >that extends applications into web and mobile media. Attend the live >webcast >and join the prime developer group breaking into this new coding territory! >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >_______________________________________________ >Libusb-win32-devel mailing list >Lib...@li... >https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
|
From: Robert M. <mar...@co...> - 2006-03-23 06:50:55
|
Hugo Villeneuve wrote: > Is there a way for a device not to report itself as HID and still be able to be installed in Windows without the need for a driver? Only if it uses one of the other classes which Windows has class drivers for. Unfortunately none of them are useful at all because only HID devices are not accessed per default. Classes like mass storage get integrated into non-USB subsystems and are accessible to the user. |
|
From: Hugo V. <hu...@hu...> - 2006-03-22 15:41:07
|
Hi, In another thread, I explained that the usb device that we designed reports itself as an HID device. In the beginning, we did that to simplify development on Windows (no driver development). Now, with libusb on Linux, I find that my device no longer needs to be HID to work without a driver. On Windows, if I program my device to not report itself as a HID-class device (using 0xFF as the class), Windows is asking for the drivers when I plug-it in, and obviously that is not desired. Is there a way for a device not to report itself as HID and still be able to be installed in Windows without the need for a driver? Hugo. ------------------------- Hugo Villeneuve hu...@hu... http://www.hugovil.com ------------------------- |
|
From: Hugo V. <hu...@hu...> - 2006-03-22 15:28:32
|
On Tue, 21 Mar 2006 19:38:49 +0100 Stephan Meyer <ste...@we...> wrote: > > > > Hi, > > My device is working fine under Linux. Using the exact same source code, I have a problem > > when I call the usb_set_configuration() function. I observed that this function never returns. > > The function should time out after 5s and cancel the request. > Which version are you using? Can you try the latest version > from the CVS? I should mention that a problem with our device is not to be excluded. This is a device that we designed. It uses a stock usb stack provided with the microcontroller we are using (Microchip), and the device reports itself as a HID device. Hugo. -- ------------------------- Hugo Villeneuve hu...@hu... http://www.hugovil.com ------------------------- |
|
From: Hugo V. <hu...@hu...> - 2006-03-22 15:19:45
|
On Tue, 21 Mar 2006 19:38:49 +0100 Stephan Meyer <ste...@we...> wrote: > > Hi, > > My device is working fine under Linux. Using the exact same source code, I have a problem > > when I call the usb_set_configuration() function. I observed that this function never returns. > > The function should time out after 5s and cancel the request. > Which version are you using? Can you try the latest version > from the CVS? I'm using libusb-win32-0.1.10.1. I cannot compile libusb from source, and therefore I cannot try the CVS version. But I tried with libusb-win32-20051120, and things are different. It seems the call to usb_set_configuration() is now working correctly, and my device correctly receives the data I sent to it (confirmed visually: the device execute the requested command). After that, my application then waits to receive a packet from the device to confirm that the data was indeed received. I now have this error: LIBUSB_DLL: error: usb_reap_async: timeout error If, like in my previous tests with libusb-win32-0.1.10.1, the device is ready to transfer data to the PC while responding to an external event not related to the PC, the error message never appears again, each time I run my application. Hugo. |
50 messages has been excluded from this view by a project administrator.
