|
libusbx is only a interface library for
programs that wish to access USB devices. By itself libusbx
doesn't access the device. A program must be written which uses
libusbx to access the device. The program gpsbabel may or may not
use libusbx. There are other was to access USB devices.
On linux the appropriate "udev" rule must exist for libusbx to access the device. This is a linux system security issue, not libusbx. On windows the current version of libusbx uses "WinUSB" to access the device. WinUSB places restrictions on what libusbx can do in windows. I believe there is an effort to remove WinUSB from the picture in future libusbx releases. Pete gives the link below on what needs to be done. Unless you are writing your custom device interface software, it is unlikely that libusbx is your concern. The programmer should have done this for you. Chuck On 7/21/2012 9:00 AM, Luiz Andrade wrote: I'm sorry, but i still have doubts. |
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
