http://blog.gmane.org/gmane.comp.lib.libusb.devel.general hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18493 <pre>http://libusbk.sourceforge.net/UsbK3/group__stmk.html http://libusbk.sourceforge.net/UsbK3/xfer-stream_8c-example.html It seems to me the above streaming API can be a good addition to libusb-1.0. How do you like the idea? </pre> Xiaofan Chen 2012-05-26T09:41:23 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18482 <pre>Hello everyone :) I try to communicate with an USB device: http://nopaste.info/bc655859b3.html I want to read the 42 bytes of bEndpointAddress 0x83 EP 3 IN. Therefore I installed libusb under my Linux and wrote this little programm: http://nopaste.info/98c35ab092.html I dont understand why it doesnt work, so I am asking you. My output is: Device Opened Claimed Interface libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=2 read Error: -1 Data read: Released Interface Can somebody tell my what I am doing wrong? Thx in advance, fabske :) ------------------------------------------------------------------------------ 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/ </pre> Fabian Weiss 2012-05-23T14:38:58 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18476 <pre>You can ask Openmoko for one: http://wiki.openmoko.org/wiki/USB_Product_IDs#Open_registry_for_community_.2F_homebrew_USB_Product_IDs //Peter ------------------------------------------------------------------------------ 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/ </pre> Peter Stuge 2012-05-21T21:42:27 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18471 <pre>Hi, I'm having an issue with occasional lost interrupt transfers. On a USB analyser I can see the problem occurs when two interrupt transfers come in fairly close to each other (approx 1ms gap). Currently I am stacking up several (10) interrupt transfer requests at initialisation and then just resubmitting them every time I get a callback. Setup - #define HID_RX_BUFFER_SIZE 512 static void vRequestHIDData(int iIndex) { libusb_device_handle *ptDeviceHandle = [poUSBDevice ptGetDeviceHandle]; unsigned int uiHIDEndpoint = [poUSBDevice uiGetHIDEndpoint]; struct libusb_transfer *ptTransfer = g_atHIDRxTransfers[iIndex].ptTransfer; u8 *pu8Buffer = g_atHIDRxTransfers[iIndex].pu8Data; // Reload the transfer libusb_fill_interrupt_transfer(ptTransfer, // transfer ptDeviceHandle, // dev_handle uiHIDEndpoint, // endpoint pu8Buffer, // buffer </pre> John Stirling 2012-05-21T16:14:47 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18461 <pre>commit e01ea627d1c5caac9492870b315353173e7b8a61 Author: Xiaofan Chen &lt;xiaofanc&lt; at &gt;gmail.com&gt; Date: Sun May 13 19:50:38 2012 +0800 modified: examples/Makefile.am This is similar to the following libusb-1.0 patch. http://git.libusb.org/?p=libusb.git;a=commitdiff;h=93b0e09d53ed1d177631af918 Previous _LDFLAGS included both the freshly built libusb in ../libusb and -lusb, where libtool would usually resolve the latter to an already-installed libusb library in the system. The extra reference to a second libusb library may cause failures to build examples on some platforms and is wrong. diff --git a/examples/Makefile.am b/examples/Makefile.am index 3023b58..5292cef 100644 --- a/examples/Makefile.am +++ b/examples/Makefile.am &lt; at &gt;&lt; at &gt; -2,8 +2,8 &lt; at &gt;&lt; at &gt; INCLUDES = -I$(top_srcdir)/libusb noinst_PROGRAMS = lsusb testlibusb lsusb_SOURCES = lsusb.c -lsusb_LDADD = ../libusb/libusb.la -lusb +lsusb_LDADD = ../libusb/libusb.la testlibusb_SOURCES = testlibusb.c -testlibusb_LDADD = ../libusb/l</pre> Xiaofan Chen 2012-05-13T11:53:24 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18456 <pre>Pete removed the libusb list as recipient in his reply, so I'm forwarding. ----- Forwarded message from Pete Batard &lt;pete&lt; at &gt;akeo.ie&gt; ----- To: libusbx-devel&lt; at &gt;lists.sourceforge.net Subject: Re: [Libusbx-devel] [PATCH] Add topology calls Date: Fri, 11 May 2012 19:26:24 +0100 On 2012.05.11 19:08, Peter Stuge wrote: And you'll be free to take risks and live on the edge, for what is really a minor detail not worth spending much time on, when/if you carry the API in libusb. Your suggestion has been heard, and, as ever, I'm puzzled as to why you're trying to blow such a minor API item out of proportion, just to attempt to get "your way" in a project that had to fork precisely because of this behaviour. Well, if people vote to have get_parent to be removed from the public API because they see it too limiting, and we don't get user requests otherwise in the meantime, I don't have a problem keeping it private and reviewing its introduction to the public API once we have hotplug and an overhauled enum. But </pre> Peter Stuge 2012-05-11T18:29:30 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18453 <pre>Pete proposed some new topology APIs in libusbx, and I sent some comments and questions about them to their mailing list. I'm forwarding to the libusb-devel list in order to hear from more people - maybe you can answer my questions or have other thoughts on the proposal. Thanks! //Peter ----- Forwarded message from Peter Stuge &lt;peter&lt; at &gt;stuge.se&gt; ----- To: libusbx-devel&lt; at &gt;lists.sourceforge.net Subject: Re: [Libusbx-devel] [PATCH] Add topology calls Date: Fri, 11 May 2012 17:48:17 +0200 Pete Batard wrote: I think the proposed API could be simplified. There's a hard upper limit on the path length (7 ports including the HC) so I would suggest to drop the path_len input parameter and document that path must be uint8_t [7] or longer. Please explain this comment in more detail? Does it refer to the libusb_device refcounting? Are all devices refcounted by their children? //Peter ----- End forwarded message ----- ------------------------------------------------------------------------------ Live Security</pre> Peter Stuge 2012-05-11T15:50:33 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18444 <pre>Hi All, I am trying to get  notification whenever any USB device hot plugged in or plugged out. I used  LIBUSB API: libusb_set_pollfd_notifiers() in the following manner but i get event only whenever any device plugged out not for plug in. /*Code Snippet*/ libusb_context *ctx retval = libusb_init(&amp;ctx); libusb_pollfd_added_cb device_AddedCalBack; libusb_pollfd_removed_cb deviceRemovedCallBack;  device_AddedCalBack = &amp;sample_libusb_pollfd_added_cb;  deviceRemovedCallBack = &amp;sample_libusb_pollfd_removed_cb;  //register hot plug and unplug events.  if(retval ==0){ dbg_printf(TRC_VERBOSE, TRC_FLAGS_MUX, "****Calling libusb_set_pollfd_notifiers \n");  libusb_set_pollfd_notifiers(ctx, device_AddedCalBack, deviceRemovedCallBack, (void*)ctx); dbg_printf(TRC_VERBOSE, TRC_FLAGS_MUX, "****Call libusb_set_pollfd_notifiers returned %d \n",retval); Regards, Madhav ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all t</pre> madhav chauhan 2012-05-10T07:15:03 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18435 <pre>Hi, I'm attempting to use libusb-1.0 to stream audio data from an isochronous endpoint : Endpoint Descriptor (Audio): ------------------------------ Value Valuename 0x09 bLength 0x05 bDescriptorType 0x83 bEndpointAddress (In-Endpoint) 0x01 bmAttributes Transfer Type: Isochronous-Transfer Synchronization Type: None Usage Type: Data 0x00C0 wMaxPacketSize (192 Bytes) 0x01 bInterval 0x00 bRefresh 0x00 bSynchAddress Hex dump: 0x09 0x05 0x83 0x01 0xC0 0x00 0x01 0x00 0x00 (I'm using http://git.tuxfamily.org/microdiausp/microdiauserspace.git as an example of how to drive isochronous transfers.) As per above example, two transfers are set up via uiAudioEndpoint = 0x83; iMaxAudioPackets = 10; libusb_device *ptDevice = [poUSBDevice ptGetDevice]; iMaxIsoPacketSize = libusb_get_max_iso_packet_size(ptDevice, uiAudioEndpoint); iAudioBufferLength = iMaxIsoPacketSize * iMaxAudioPackets; int i; for (i=0; i&lt;NUM_TRANSFERS; i++) { atTransfers[i].ptAudioTrans</pre> John Stirling 2012-05-08T16:03:14 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18428 <pre>Hi Martin, Maybe you want to take a look at the following warnings. os/openbsd_usb.c: In function '_sync_control_transfer': os/openbsd_usb.c:638:2: warning: dereferencing type-punned pointer will break strict-aliasing rules os/openbsd_usb.c:639:2: warning: dereferencing type-punned pointer will break strict-aliasing rules os/openbsd_usb.c:640:2: warning: dereferencing type-punned pointer will break strict-aliasing rules localhost$ ./autogen.sh libtoolize: putting auxiliary files in `.'. libtoolize: copying file `./ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. libtoolize: copying file `m4/libtool.m4' libtoolize: copying file `m4/ltoptions.m4' libtoolize: copying file `m4/ltsugar.m4' libtoolize: copying file `m4/ltversion.m4' libtoolize: copying file `m4/lt~obsolete.m4' configure.ac:39: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded fro</pre> Xiaofan Chen 2012-05-08T10:21:27 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18420 <pre>Hello I can't seem to find a solution to this anywhere, but it seems strange that no one would have encountered this before. Please don't get mad if this stuff is old hat: I am writing a single threaded application that has a poll/select loop. I don't need asynchronous USB transfers at all, but I do need to poll the file descriptors associated with the USB device. This does not seem possible, or is it? Some pseudo code to give you some idea what's going on before the first poll: libusb_init(NULL) libusb_device_handle * handle = discover_my_device() // discover, open &amp; claim the device libusb_bulk_transfer(handle, endpoint OUT, message, ...) // the device will write an answer back Polling details: short poll_usb_fds(short events, int timeout) { int i, count = 0; struct pollfd * fds; const struct libusb_pollfd ** list = libusb_get_pollfds(NULL); if (list == NULL) { printf("could not list pollable file descriptors\n"); return -1; } for (i = 0; list[i] != NULL; i++) </pre> Mysingen 2012-04-29T21:53:25 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18413 <pre>Hello, I hope this is an appropriate things to post here. I have an AlertFM usb radio that is "windows only" that I want to use on my Ubuntu server. The plan is to set it up to listen for EAS warnings on our local radio station. (We live a long way from civilization and don't always have the TV on). If I can get the audio stream, I can do the rest easy enough (I've got that part written and tested using recordings of EAS audio messages). Anyway, I have a windows computer and captured some channel changing data using their software, and digging around I found this software which actually recommends hidapi for HID devices. No problem, I have that installed along with libusb and I think I even have it changing channels (one report sets the channel, and another reads back the current channel. Still an input report I can't seem to grab which gives signal strength data etc, but I could live without that.) What I don't have now is the audio stream. I'm not very familiar with USB, so this is a really</pre> Deron 2012-05-07T15:10:07 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18409 <pre> //Peter ------------------------------------------------------------------------------ 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/ </pre> Peter Stuge 2012-05-07T09:47:36 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18404 <pre>1) It may be necessary to create your own libusb.pc and libusb-1.0.pc since FreeBSD does not ship them. Ref: http://lists.freebsd.org/pipermail/freebsd-usb/2011-July/010470.html &gt;cat /usr/local/libdata/pkgconfig/libusb.pc prefix=/usr exec_prefix=${prefix} libdir=${exec_prefix}/lib includedir=${prefix}/include Name: libusb Description: USB access library Version: 0.1 Libs: -L${libdir} -lusb Cflags: -I${includedir} ~ &gt;cat /usr/local/libdata/pkgconfig/libusb-1.0.pc prefix=/usr exec_prefix=${prefix} libdir=${exec_prefix}/lib includedir=${prefix}/include Name: libusb Description: USB access library Version: 1.0.1 Libs: -L${libdir} -lusb Cflags: -I${includedir} 2) FreeBSD does not have libusb-1.0.so and libusb-1.0.a, only libusb.so and libusb.a. It may be necessary to create the symbolic link. 3) If the stock FreeBSD libusb is missing some function, try the svn head version. </pre> Xiaofan Chen 2012-05-06T13:50:17 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18403 <pre>http://libusb.sourceforge.net/api-1.0/group__desc.html libusb_get_descriptor() is in libusb-1.0. But I do not see this in FreeBSD's libusb-1.0 wrapper. http://svnweb.freebsd.org/base/head/lib/libusb/libusb.h?view=markup Maybe it is a good idea to add this one. Thanks. </pre> Xiaofan Chen 2012-05-06T13:38:50 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18400 <pre>I am using automake 1.12 and autoconf 2.69 and there are quite some warnings for libusb-compat. Not so sure how to fix them though since I know very little of auto-tools. mymacmini:libusb-compat-0.1 xiaofanc$ ./autogen.sh glibtoolize: putting auxiliary files in `.'. glibtoolize: copying file `./ltmain.sh' glibtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. glibtoolize: copying file `m4/libtool.m4' glibtoolize: copying file `m4/ltoptions.m4' glibtoolize: copying file `m4/ltsugar.m4' glibtoolize: copying file `m4/ltversion.m4' glibtoolize: copying file `m4/lt~obsolete.m4' /usr/local/share/aclocal/log4shib.m4:7: warning: underquoted definition of AM_PATH_LOG4SHIB /usr/local/share/aclocal/log4shib.m4:7: run info Automake 'Extending aclocal' /usr/local/share/aclocal/log4shib.m4:7: or see http://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal configure.ac:55: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:197: AC_LANG_CONFTEST is expand</pre> Xiaofan Chen 2012-05-06T00:31:15 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18394 <pre>#130: libusb-compat-0.1 does not call libusb_exit() --------------------------------+-------------------------- Reporter: xiaofan | Owner: Type: defect | Status: new Component: libusb-compat-0.1 | Keywords: libusb-compat Blocked By: | Blocks: --------------------------------+-------------------------- There is a potential problem in the libusb-compat layer because libusb-1.0 requires a call to libusb_exit(). However, libusb_exit() is never called by the compat layer even though libusb_init() is used. http://git.libusb.org/?p=libusb-compat-0.1.git;a=blob;f=libusb/core.c;js=1 Also ref here which shows that libusb_exit() is really necessary. http://libusb.6.n5.nabble.com/quot-memory-leak-quot-debug-message-after- libusb-close-and-upon-application-exit-td5581475.html </pre> libusb Trac 2012-05-05T13:48:18 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18385 <pre>Hi I am rewriting exisitng code to control a cheap dongle for DAB, to be used in conjunction with my sdr software. The code uses libusb for interfacing to the dongle and it seems I am managing to get some data out of it. The question is: Can I mix receiving a 2 Mbyte data stream from the dongle (using the usb bulk mode) with sending a control command (e.g. to switch to another frequency) or should I stop the incoming datastream first, then give my command and then resume the datastream? (The datastream is just a stream of samples, so logically there is no real harm done when I have to stop it for a while, however, resuming the stream complicates the software somewhat). Thanks in advance jan </pre> jan van katwijk 2012-05-03T14:03:52 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18380 <pre>There is a potential problem in the libusb-compat layer because libusb-1.0 requires a call to libusb_exit().  However, libusb_exit() is never called by the compat layer even though libusb_init() is used. http://git.libusb.org/?p=libusb-compat-0.1.git;a=blob;f=libusb/core.c;js=1 Also ref here which shows that libusb_exit() is really necessary. http://libusb.6.n5.nabble.com/quot-memory-leak-quot-debug-message-after-libusb-close-and-upon-application-exit-td5581475.html A potential solution is add a new API usb_exit(). </pre> Xiaofan Chen 2012-05-02T23:25:30 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18363 <pre>Hi, Here's a re-organized patch adding FreeBSD support to the current HIDAPI git version. I moved the libusb code out of the linux/ directory and created a libusb/ directory which applies for both Linux and FreeBSD versions of hidapi/libusb. Now that Linux and FreeBSD share code, it will be easier to maintain. Also, this version has improved character encoding over the last version. Let me know how it works for you. If so, I'll commit it. Thanks! Alan. ------------------------------------------------------------------------------ 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/_______________________________________________ libusb-devel mailing list libusb-devel&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusb-devel</pre> Alan Ott 2012-05-01T19:58:38 http://comments.gmane.org/gmane.comp.lib.libusb.devel.general/18362 <pre>I have written a Libusb 1.0 "driver" for a USB device. The driver uses a 'daemon' process to interface multiple client programs to the device and I can launch this daemon process under Linux via either the (old) hotplug mechanism or the (newer) udev mechanism. The driver itself (and the daemon) is mostly cross-platform (there are a few bits here and there that need cleaning up) and I am wondering what sort of mechanism(s) are available under MS-Windows to launch the daemon process upon plugging in the USB device (and killing it off once the device is removed). Under Linux is it just a matter of dropping control files and scripts into the proper places (eg in /etc/udev/rules.d and /lib/udev/). How does this work under MS-Windows? I don't do development work under MS-Windows -- the code is all cross-built on my Linux system. </pre> Robert Heller 2012-05-01T16:50:04 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.lib.libusb.devel.general