Re: [Libusbx-devel] 3 warnings in git master from Xcode

On Mar 21, 2014, at 12:50 PM, Sean McBride wrote:On Fri, 21 Mar 2014 18:44:01 +, Nathan Hjelm said:        >I can't get scan-build to give me the the first oneIt's a compiler warning, not a static analyzer warning. I get it just building with Xcode 5.0.2. Again, I think las

Re: [Libusbx-devel] 3 warnings in git master from Xcode

On Mar 21, 2014, at 12:44 PM, Nathan Hjelm wrote:On Mar 21, 2014, at 11:49 AM, Sean McBride wrote:On Tue, 21 Jan 2014 07:43:10 -0700, Nathan Hjelm said:        >        > (2) os/darwin_usb.c:531:10: Implicit conversion loses integer        >precision: 'size_t' (aka '

Re: [Libusbx-devel] 3 warnings in git master from Xcode

On Mar 21, 2014, at 11:49 AM, Sean McBride wrote:On Tue, 21 Jan 2014 07:43:10 -0700, Nathan Hjelm said:        >        > (2) os/darwin_usb.c:531:10: Implicit conversion loses integer        >precision: 'size_t' (aka 'unsigned long') to 'int'        >

Re: [Libusbx-devel] 3 warnings in git master from Xcode

On Jan 21, 2014, at 10:30 AM, Tim Roberts wrote:Nathan Hjelm wrote:On Jan 20, 2014, at 4:56 PM, Tim Roberts wrote: Even if there isn't, the standard guarantees that those two constructs are identical. Any elements that don't have initializer values get zeroed. Not quite. This is true for global

Re: [Libusbx-devel] 3 warnings in git master from Xcode

On Jan 20, 2014, at 11:59 AM, Sean McBride wrote: > Hi all, > > With 1.0.18 coming, I though I'd try building git master with the latest > Xcode. I see 3 warnings: > > (1) core.c:1910:27: Missing field 'tv_usec' initializer > > can we just change: > struct timeval tv = { 0, }; > to: >

Re: [Libusbx-devel] 3 warnings in git master from Xcode

> On Jan 20, 2014, at 4:56 PM, Tim Roberts wrote: > > Sean McBride wrote: >> With 1.0.18 coming, I though I'd try building git master with the latest >> Xcode. I see 3 warnings: >> >> (1) core.c:1910:27: Missing field 'tv_usec' initializer >> >> can we just change: >>struct timeval tv =

Re: [Libusbx-devel] how can I compile the 32bit libusb.so ?

Try adding CFLAGS=-m32-NathanOn Dec 18, 2013, at 07:18 AM, Nothing wrote:./configure --prefix=`pwd`/install --build=i386-linux  ac_cv_func_malloc_0_nonnull=yes --disable-udev --with-picI use this comand but the file is still   64bitlibusb-1.0.so.0.1.0: ELF 64-bit LSB shared object, x86-64, version

Re: [Libusbx-devel] [libusbx] Hotplug support should not create threads (or document the fact) (#158)

The hotplug thread writes a message to an internal hotplug file descriptor. This message is read by the thread that calls libusb_handle_events() which then call the callback. The callback is never made by the hotplug thread. --- Reply to this email directly or view it on GitHub: https://github.c

Re: [Libusbx-devel] [PATCH 0/2] Add API for bulk streams, final version

On Oct 9, 2013, at 12:19 AM, Hans de Goede wrote: > Hi All, > > After a lot of work on this, in the end mostly on the Linux kernel to iron > out some xhci controller driver bugs wrt to streams (*), I'm happy to report > that I now have streams working reliable. So I intend to push these 2 patch

Re: [Libusbx-devel] [RFC 0/2] Add support for USB-3 bulk streams

One more thing about the API. It might be good to change: uint32_t API_EXPORTED libusb_transfer_get_stream_id (struct libusb_transfer *transfer); to: int API_EXPORTED libusb_transfer_get_stream_id (struct libusb_transfer *transfer, uint32_t *stream_id); This would allow the return of LIBUSB_E

Re: [Libusbx-devel] [RFC 0/2] Add support for USB-3 bulk streams

On Sep 13, 2013, at 11:36 AM, Pete Batard wrote: > and we provide our "own" stdint.h for earlier versions. See the msvc > directory. > We're also using uint#_t all over the place in both core and the Windows > backend => feel free to use anything you want from stdint.h/inttypes.h. MS > may ha

Re: [Libusbx-devel] [RFC 0/2] Add support for USB-3 bulk streams

On Sep 13, 2013, at 6:45 AM, Hans de Goede wrote: > Hi, > > On 09/13/2013 02:35 PM, Nathan Hjelm wrote: >> >> On Sep 13, 2013, at 3:18 AM, Hans de Goede wrote: > > > >>> 2) The alloc_streams backend op should not fail when the user requests more >

Re: [Libusbx-devel] [RFC 0/2] Add support for USB-3 bulk streams

On Sep 13, 2013, at 11:21 AM, Tim Roberts wrote: > Nathan Hjelm wrote: >> >> Pete, I know the Microsoft compiler is a sub-par C compiler so I want >> to make sure uint32_t is available before chaning the type of >> num_streams. Does it support standard C99 integer

Re: [Libusbx-devel] [RFC 0/2] Add support for USB-3 bulk streams

On Sep 13, 2013, at 3:18 AM, Hans de Goede wrote: > Hi, > > On 09/12/2013 11:12 PM, Nathan Hjelm wrote: >> >> On Sep 12, 2013, at 6:35 AM, Hans de Goede wrote: >> >>> Hi, >>> >>> On 09/11/2013 11:04 PM, Hans de Goede wrote: >>

Re: [Libusbx-devel] [RFC 0/2] Add support for USB-3 bulk streams

On Sep 12, 2013, at 6:35 AM, Hans de Goede wrote: > Hi, > > On 09/11/2013 11:04 PM, Hans de Goede wrote: >> Hi, >> >> On 09/11/2013 04:10 PM, Nathan Hjelm wrote: >>> >>> On Sep 11, 2013, at 7:15 AM, Nathan Hjelm wrote: >>> >&

Re: [Libusbx-devel] [RFC 0/2] Add support for USB-3 bulk streams

On Sep 11, 2013, at 7:15 AM, Nathan Hjelm wrote: > One question. Would it make sense to add an additional transfer type for > stream transfers? The stream_id field is not set to 0 by > libusb_fill_bulk_transfer so I can not reliably tell if a transfer is a > stream transfer in th

Re: [Libusbx-devel] [RFC 0/2] Add support for USB-3 bulk streams

One more thing. I think we should make the stream id either a uint32_t or unsigned int. It can never be negative and stream id 0 is not a valid stream. -Nathan -- How ServiceNow helps IT people transform IT departments: 1

Re: [Libusbx-devel] [RFC 0/2] Add support for USB-3 bulk streams

switch APIs. -Nathan On Sep 11, 2013, at 6:47 AM, Nathan Hjelm wrote: > Looks good to me. I will spend some time over the next couple of days > implementing stream support on Darwin. I don’t have any devices to test the > code with though. > > -Nathan > > On Sep 11, 2013

Re: [Libusbx-devel] [RFC 0/2] Add support for USB-3 bulk streams

Looks good to me. I will spend some time over the next couple of days implementing stream support on Darwin. I don’t have any devices to test the code with though. -Nathan On Sep 11, 2013, at 5:53 AM, Hans de Goede wrote: > Hi All, > > These 2 patches add support to the libusb API and Linux

Re: [Libusbx-devel] Reverting atexit call of libusb_exit from libusb-compat ?

On Sep 6, 2013, at 4:58 AM, Hans de Goede wrote: > Hi, > > On 09/05/2013 03:14 AM, Xiaofan Chen wrote: >> On Thu, Sep 5, 2013 at 3:26 AM, Hans de Goede wrote: >>> Hi, >>> >>> As discussed in much detail here: >>> https://bugzilla.redhat.com/show_bug.cgi?id=1003193 >>> >>> Calling libusb_exit

Re: [Libusbx-devel] [libusbx] OSX: Hotplug callback is only called once on startup, not on mount/unmount (#138)

Ok, so this is not a bug. You need to call libusb_handle_events to get hotplug callbacks. As for the hotplugtest program shutting down. It exits after 2 events: while (done < 2) { libusb_handle_events (NULL); } Each callback in the example increments done. If you

Re: [Libusbx-devel] [libusbx] OSX: Hotplug callback is only called once on startup, not on mount/unmount (#138)

Hmm, looks ok to me. One thing. Are you calling libusb_handle_events() anywhere? Hotplug callbacks are called from libusb_handle_events. --- Reply to this email directly or view it on GitHub: https://github.com/libusbx/libusbx/issues/138#issuecomment-23368768

Re: [Libusbx-devel] [libusbx] OSX: Hotplug callback is only called once on startup, not on mount/unmount (#138)

I don’t see anything wrong in your code. Please do the following and send me the output: - Clone the git master from github.com/libusbx/libusbx - Run: ./autogen.sh make export LIBUSB_DEBUG=4 ./examples/hotplugtest kVendorId kProductId Replace kVendorId and kProductId with the vendor and product

Re: [Libusbx-devel] Coverity: static analysis of libusbx

On Aug 26, 2013, at 8:18 PM, Nathan Hjelm wrote: > > On Aug 26, 2013, at 5:12 PM, Sean McBride wrote: > >> On Mon, 26 Aug 2013 22:33:10 +0000, Nathan Hjelm said: >> >>> Hmm, the conclusion is wrong. If ret > -1 the cached_device is always >>> not N

Re: [Libusbx-devel] Coverity: static analysis of libusbx

On Aug 26, 2013, at 5:12 PM, Sean McBride wrote: > On Mon, 26 Aug 2013 22:33:10 +0000, Nathan Hjelm said: > >> Hmm, the conclusion is wrong. If ret > -1 the cached_device is always >> not NULL. I should probably change: >> >> if (ret < 0 || (cached_dev

Re: [Libusbx-devel] Coverity: static analysis of libusbx

On Aug 26, 2013, at 04:22 PM, Sean McBride wrote:On Mon, 26 Aug 2013 20:47:33 +0200, Ludovic Rousseau said: I use Coverity as _another_ static analysis tool for my free softwareprojects. The clang static analyzer also gives one error in current git master: libusbx/libusb/os/darwin_usb.c:533:34: A

Re: [Libusbx-devel] [libusbx] Enable building on all Android architectures, including MIPS (working around an MIPS NDK linker bug). (#134)

git is much more powerful than hg. What you will probably want to do is something like this: git rebase -i HEAD~6 (rebase the last 6 commits) And use the squash command to squash the commits into 1. -Nathan On Aug 20, 2013, at 11:32 AM, Andrew Fernandes wrote: > What?! Six patches... ob

Re: [Libusbx-devel] Doing a libusbx 1.0.17-rc1 release

I was going to last week but discovered I don't have write access to libusbx on sourceforge. At this point it probably doesn't matter since I think 1.0.18 should probably be the first release as libusb. I am maintaining a branch with everything renamed except references to libusbx.org.-NathanOn Aug

Re: [Libusbx-devel] [libusbx] Linux: libusbx version 1.0.16.10809 compiled with --disable-udev sometimes blocks on libusb_get_device_list() call till a device is plugged/unplugged. (#130)

Closed #130 via f0fb99aeb93f45d2846f8884a348e90438d13ef8. --- Reply to this email directly or view it on GitHub: https://github.com/libusbx/libusbx/issues/130 -- Get 100% visibility into Java/.NET code with AppDynamics Lit

Re: [Libusbx-devel] Android build files and improved logging patches, (was "Improved log in non-console applications and Android")

Looks good to me too. I will build the rc tomorrow. -Nathan On Aug 8, 2013, at 7:09 PM, Pete Batard wrote: > On 2013.08.08 18:35, Toby Gray wrote: >> I've attached a rebase of patches 1 to 4 onto the master branch of libusbx. > > Thanks. Much appreciated. > > I have now merged 1&2 and pushed

Re: [Libusbx-devel] [PATCH] Core: Fix potential segfault caused by using freed memory

Good catch. I will push this later today. -Nathan On Aug 6, 2013, at 2:16 PM, Chris Dickens wrote: > When a transfer is submitted, the device is referenced in > libusb_submit_transfer() > and unreferenced in usbi_handle_transfer_completion(). This transfer could > potentially > be freed by a

Re: [Libusbx-devel] [libusbx] darwin: fix clang warnings about explicit conversion (b5acea3)

Not at all. The session id is internal to libusb so we can change it as we see fit.-NathanOn Aug 01, 2013, at 02:14 PM, Sean wrote:I just assumed change the session id to a uint64_t would be an API/ABI breakage... but didn't look...—Reply to this email directly or view it on GitHub.---

Re: [Libusbx-devel] [libusbx] darwin: fix clang warnings about explicit conversion (b5acea3)

Which is indeed the case! I will add some comments to that effect.While we are on this issue maybe we should discuss changing the session id to a uint64_t? I hate the use of long for this very reason.-NathanOn Aug 01, 2013, at 02:02 PM, Sean wrote:Might I suggest a comment in the code to that effe

Re: [Libusbx-devel] [libusbx] darwin: fix clang warnings about explicit conversion (b5acea3)

I know. But the lower 32 bits of the session ID should still be unique which is all I care about (since this is just the session id).-NathanOn Aug 01, 2013, at 01:34 PM, Sean wrote:Um, no. 'long' is precisely one of the types that is different size between 32 and 64 bit. See:https://developer.appl

Re: [Libusbx-devel] [libusbx] Task: Update website and documentation to reflect libusb and libusb merge (#123)

Yup. I still need to figure out how to approach Peter and get control of the domain. If he ever reverts our modifications (and removes my admin access) I will ask him for the domain. Otherwise I will try to get him to give us the domain before it renews next May. --- Reply to this email directl

Re: [Libusbx-devel] Doing a 1.0.17 release

On Jul 30, 2013, at 09:48 AM, Hans de Goede wrote:Hi, I see that Nathan and I both have been working on closing various bugs so that we can do a 1.0.17 bug-fix release. Nathan beat me wrt pushing his changes by mere seconds, which meant I had to do a rebase (GRMBL :) Hah, noticed that. Sorry for

[Libusbx-devel] [libusbx] Release 1.0.17 (#126)

This is just a token issue to be closed when we release. Required as closing all the other issues will close the milestone. --- Reply to this email directly or view it on GitHub: https://github.com/libusbx/libusbx/issues/126 -

Re: [Libusbx-devel] [libusbx] Mac OSX: libusbx crashes when unplugging a device (1.0.16) (#121)

Ack, commit 707d500b9fea002f075cf30458a602f28dbd1348 referenced the wrong issue. That commit closes this issue. --- Reply to this email directly or view it on GitHub: https://github.com/libusbx/libusbx/issues/121#issuecomment-21798023 --

Re: [Libusbx-devel] [libusbx] Mac OSX: libusbx crashes when unplugging a device (1.0.16) (#121)

Closed #121. --- Reply to this email directly or view it on GitHub: https://github.com/libusbx/libusbx/issues/121 -- Get your SQL database under version control now! Version control is standard for application code, but da

Re: [Libusbx-devel] [libusbx] Silence automake 1.14 warnings (#125)

Closed #125 via 872ff1704b79034af14cd09ac335bd97fe9be1ea. --- Reply to this email directly or view it on GitHub: https://github.com/libusbx/libusbx/issues/125 -- Get your SQL database under version control now! Version con

Re: [Libusbx-devel] [libusb] libusb-1.0.16-rc10 without udev ?

I have a possible fix. Please try the netlink_test branch @ https://github.com/hjelmn/libusbx.git Let me know if it resolves the issue. -Nathan On Jul 26, 2013, at 9:32 PM, Xiaofan Chen wrote: > On Sat, Jul 27, 2013 at 10:45 AM, Xiaofan Chen wrote: >> On Sat, Jul 27, 2013 at 12:04 AM, jakubo

Re: [Libusbx-devel] [libusbx] Linux: libusbx failed to build with --disable-udev (#124)

I think I see the issue. We need to include asm/types.h and sys/socket.h before netlink.h. I will create a branch to test this. --- Reply to this email directly or view it on GitHub: https://github.com/libusbx/libusbx/issues/124#issuecomment-21670131 --

Re: [Libusbx-devel] [libusbx] Linux: libusbx failed to build with --disable-udev (#124)

Yup, thats how the netlink support was tested and confirmed to work. Except you should never use that option when building libusb(x) for systems where udevd is running. -Nathan On Jul 26, 2013, at 9:33 PM, mcuee wrote: > BTW, I tested desktop Linux Ubuntu 12.04 x86 and --disable-udev works fi

Re: [Libusbx-devel] [libusbx] libusbx failed to build with --disable-udev (#124)

The thing is netlink should work just fine on almost all embeded linux distros. The problem here seems to be with the cross-comilation environment. I haven’t had a chance to look into it yet but there should be clear indications in the config.log why the netlink test is failing. -Nathan On Jul

Re: [Libusbx-devel] [libusbx] Mac OSX: libusbx crashes when unplugging a device (1.0.16) (#121)

On Jul 23, 2013, at 8:03 AM, Alan Stern wrote: > On Mon, 22 Jul 2013, Nathan Hjelm wrote: > >>> In Linux, when a device connects there are no special notifications for >>> each transfer. Pending transfers are automatically cancelled by the >>> kernel, and t

Re: [Libusbx-devel] [libusbx] Mac OSX: libusbx crashes when unplugging a device (1.0.16) (#121)

On Jul 22, 2013, at 8:28 AM, Alan Stern wrote: > On Sun, 21 Jul 2013, Nathan Hjelm wrote: > >> On Jul 21, 2013, at 8:11 PM, Alan Stern wrote: >> >>> On Sun, 21 Jul 2013, Nathan Hjelm wrote: >>> >>>> A little more detail about what is h

Re: [Libusbx-devel] [libusbx] Mac OSX: libusbx crashes when unplugging a device (1.0.16) (#121)

On Jul 21, 2013, at 8:11 PM, Alan Stern wrote: > On Sun, 21 Jul 2013, Nathan Hjelm wrote: > >> A little more detail about what is happening in this case. When the >> device gets disconnected the hotplug backend calls >> usbi_handle_disconnect which then �completes

Re: [Libusbx-devel] [libusbx] Mac OSX: libusbx crashes when unplugging a device (1.0.16) (#121)

On Jul 21, 2013, at 8:11 PM, Alan Stern wrote: > On Sun, 21 Jul 2013, Nathan Hjelm wrote: > >> A little more detail about what is happening in this case. When the >> device gets disconnected the hotplug backend calls >> usbi_handle_disconnect which then �completes

Re: [Libusbx-devel] [libusbx] Mac OSX: libusbx crashes when unplugging a device (1.0.16) (#121)

On Jul 20, 2013, at 11:23 AM, Lilk wrote: > Ok. When is 1.0.17 due? > We are using libusbx in a multi-platform application and it would be neat to > be able to use the new hotplug api in our application (without the > application crashing), with a graceful fallback, enabling us to just replace

Re: [Libusbx-devel] [libusbx] Mac OSX: libusbx crashes when unplugging a device (1.0.16) (#121)

Alright, that explains what is happening. The device is getting disconnected which triggers a call to usbi_handle_disconnect which cancels usbi_handle_transfer_completion. You are then getting notification from the os indicating the transfer failed. The fix I sent you avoid the segmentation faul

Re: [Libusbx-devel] [libusbx] Mac OSX: libusbx crashes when unplugging a device (1.0.16) (#121)

On Jul 19, 2013, at 10:31 PM, Nathan Hjelm wrote: > It might be sufficient to check if the list head is null before trying to > remove the transfer from the list since the transfer is not on a list when it > completes. Try adding the check: > > if (itransfer->list->

Re: [Libusbx-devel] [libusbx] Mac OSX: libusbx crashes when unplugging a device (1.0.16) (#121)

It might be sufficient to check if the list head is null before trying to remove the transfer from the list since the transfer is not on a list when it completes. Try adding the check: if (itransfer->list->list_head) on lone 1534 of io.c before: list_del(&itransfer->list); And let me know i

Re: [Libusbx-devel] [libusbx] Mac OSX: libusbx crashes when unplugging a device (1.0.16) (#121)

Ok, can you get me a stack trace as well. I have an idea where the crash might be but I need to stack trace to be sure. Please get a stack trace for libusbx compiled with -g3 so I can see line numbers. -Nathan On Jul 16, 2013, at 1:56 PM, Lilk wrote: > After upgrading from 1.0.15 to 1.0.16 my

Re: [Libusbx-devel] Configure - Error with libusbx 1.0.16

On Jul 11, 2013, at 6:34 PM, Xiaofan Chen wrote: > On Fri, Jul 12, 2013 at 2:34 AM, Jens Gutsche wrote: >> Hi, >> >> i have seen a new version on http://www.libusb.org/wiki but i cannot >> configure it. >> >> Here is the console output: >> >> bash-3.2$ ./configure --prefix=/usr --bindir=/usr

Re: [Libusbx-devel] [Patches for 1.0.16 0/2]: Allow hotplug users to wakeup handle_events

+1 from me. -Nathan On Jul 4, 2013, at 8:55 AM, Hans de Goede wrote: > Hi All, > > So to make sure the API is sane, and to give the hotplug stuff some extra > testing, I've ported Spice's usbredir code over to it. > > And everything worked in one go, until I tried to exit the spice client, at

Re: [Libusbx-devel] stress test failed under Linux

Sorry for the mistake. Don't know why I didn't catch that earlier.-NathanOn Jun 14, 2013, at 07:48 AM, Hans de Goede wrote:Hi, On 06/14/2013 02:43 PM, Xiaofan Chen wrote: > On Fri, Jun 14, 2013 at 5:59 PM, Hans de Goede wrote: >> Hmm, ok, error 11 is EAGAIN, so indeed you're

Re: [Libusbx-devel] hotplug_poll() on Linux hangs

On Jun 14, 2013, at 02:58 AM, Hans de Goede wrote:Hi, On 06/14/2013 10:19 AM, Chris Dickens wrote: > Hi, > > All looks good now, thanks! > > I actually went with the F_GETFL/F_SETFL approach first, then I saw how poll_posix.c did it with usbi_pipe() and decided to go that way, for consistency. >

Re: [Libusbx-devel] stress test failed under Linux

??? It looks like it is failing on pthread_create. That doesn't seem right. Can you run under valgrind and see if anything obvious is wrong? I will test in a Linux VM when I get home and see if I can reproduce the problem there.-NathanOn Jun 13, 2013, at 08:53 AM, Xiaofan Chen wrote:On Thu, Jun 13

Re: [Libusbx-devel] libusb and libusbx merging

Done.On Jun 12, 2013, at 11:24 AM, Nathan Hjelm wrote:I own the mailing list now and I see no reason not to re-add [libusb-devel] to the subject.-NathanOn Jun 12, 2013, at 10:54 AM, Tim Roberts wrote:Pete Batard wrote: > > Can you explain a bit more about this? Did the libusb-devel

Re: [Libusbx-devel] libusb and libusbx merging

I own the mailing list now and I see no reason not to re-add [libusb-devel] to the subject.-NathanOn Jun 12, 2013, at 10:54 AM, Tim Roberts wrote:Pete Batard wrote: > > Can you explain a bit more about this? Did the libusb-devel prefix > change or something? If so, do you have any idea what the r

[Libusbx-devel] libusb and libusbx merging

Peter's time has gotten to be very limited so I have opted to take over maintenance oflibusb. I have been in contact with the libusbx team to and invited them to rejoin libusbas maintainers and they have accepted. The plan is for us to work together in a 1.0.16release of libusbx. This release will

Re: [Libusbx-devel] libusbx broken on Mac OS X

Bah! I forgot about the nano version. Sorry. -Nathan On Jun 6, 2013, at 11:59 AM, Pete Batard wrote: > On 2013.06.06 18:08, Hans de Goede wrote: >> I've merged the pull request into master. > > Be mindful that when using github's merge, you lose the nano bump. > => the last 5 commits will repo

Re: [Libusbx-devel] libusbx broken on Mac OS X

On Jun 6, 2013, at 7:19 AM, Hans de Goede wrote: > Hi, > > On 06/06/2013 03:07 PM, Ludovic Rousseau wrote: >> Hello, >> >> I just tried to use the official master branch of libusbx on Mac OS X >> and I get a crash with the listdevs example: > > Ah yes, known issue (which I must admit I forgot

Re: [Libusbx-devel] [PATCH] RFC: Add a libusb_strerror() function

The contents of gettext-runtime/COPYING:The gettext-runtime package is partially under the LGPL and partially underthe GPL.The following parts are under the LGPL, see file intl/COPYING.LIB:  - the libintl and libasprintf libraries and their header files,  - the libintl.jar Java library,  - the GNU.

Re: [Libusbx-devel] [PATCH] RFC: Add a libusb_strerror() function

On May 30, 2013, at 10:17 AM, Ludovic Rousseau wrote:2013/5/30 Nathan Hjelm <hje...@me.com>: > > > On May 30, 2013, at 09:08 AM, Sean McBride <s...@rogue-research.com> wrote: > > On Thu, 30 May 2013 09:35:06 +0200, Johannes Stezenbach said: > >>I can't c

Re: [Libusbx-devel] [PATCH] RFC: Add a libusb_strerror() function

On May 30, 2013, at 09:08 AM, Sean McBride wrote:On Thu, 30 May 2013 09:35:06 +0200, Johannes Stezenbach said: >I can't comment on gettext on Windows, only that a quick search >shows there are several projects using it. Anyway, I trust you >to do the right decision for Windows, but it feels wrong

Re: [Libusbx-devel] Towards a 1.2.0 release, with hotplug support, please test

On May 24, 2013, at 3:03 PM, Sean McBride wrote: > On Fri, 24 May 2013 11:22:13 -0600, Nathan Hjelm said: > >>> Is this hotplug API opt-in? libusbx won't start observing the comings >> and goings of all USB devices by default I hope? >> >> The hotplu

Re: [Libusbx-devel] Towards a 1.2.0 release, with hotplug support, please test

On May 24, 2013, at 11:05 AM, Sean McBride wrote: > On Fri, 24 May 2013 10:53:22 -0600, Nathan Hjelm said: > >>>> So the question then maybe if there are any apps doing hotplug already >>>> (and thus on >>>> their own) for darwin, if there are no such

Re: [Libusbx-devel] Towards a 1.2.0 release, with hotplug support, please test

On May 24, 2013, at 10:44 AM, Sean McBride wrote: > On Fri, 24 May 2013 18:37:48 +0200, Hans de Goede said: > >>> Yup, there will probably be a race there but the fix may be a little >> more complicated than >>> it is under Linux. >> >> So the question then maybe if there are any apps doing ho

Re: [Libusbx-devel] Towards a 1.2.0 release, with hotplug support, please test

On May 24, 2013, at 10:37 AM, Hans de Goede wrote: > Hi, > > On 05/24/2013 06:07 PM, Nathan Hjelm wrote: >> >> On May 24, 2013, at 9:10 AM, Hans de Goede wrote: >> >>> Hi all, >>> >>> With some help from Pete, Xiaofan as well as Nathan

Re: [Libusbx-devel] Towards a 1.2.0 release, with hotplug support, please test

On May 24, 2013, at 9:10 AM, Hans de Goede wrote: > Hi all, > > With some help from Pete, Xiaofan as well as Nathan, I have been working on > integrating the libusb hp API work done by Nathan for 1.0.16 on top of > libusbx. > > The plan is to release this as 1.2.0 within the next few weeks. >

Re: [Libusbx-devel] [PATCH] Add support for BOS and Endpoint Companion USB 3.0 descriptors

On May 21, 2013, at 1:53 AM, Hans de Goede wrote: > Hi, > > On 05/21/2013 01:27 AM, Nathan Hjelm wrote: >> >> On May 20, 2013, at 5:23 PM, Pete Batard wrote: >> >>> On 2013.05.20 08:01, Hans de Goede wrote: >>>> I'm fine with cal

Re: [Libusbx-devel] Towards a 1.0.16 release, hotplug test branch, please test

On May 21, 2013, at 4:19 AM, Toby Gray wrote: > On 21/05/13 00:24, Nathan Hjelm wrote: >>>> and 2) >>>> change the one call to pipe to be a call to usbi_pipe instead of using >>>> #define? >>> Maybe I'm missing something there. >>>

Re: [Libusbx-devel] Towards a 1.0.16 release, hotplug test branch, please test

On May 21, 2013, at 4:48 AM, Toby Gray wrote: > On 20/05/13 23:43, Pete Batard wrote: >> On 2013.05.20 17:06, Nathan Hjelm wrote: >>> On May 20, 2013, at 09:51 AM, Toby Gray wrote: >>>> I've attached a handful of patches of changes needed to get WinCE

Re: [Libusbx-devel] [PATCH] Add support for BOS and Endpoint Companion USB 3.0 descriptors

On May 20, 2013, at 5:23 PM, Pete Batard wrote: > On 2013.05.20 08:01, Hans de Goede wrote: >> I'm fine with calling the next release either 1.0.16 or 1.2.0, with no >> real preference. > > As you may expect, I'd have a strong preference for 1.2.0. > >> I don't like 1.1.x because in some FOSS

Re: [Libusbx-devel] Towards a 1.0.16 release, hotplug test branch, please test

On May 20, 2013, at 4:43 PM, Pete Batard wrote: > On 2013.05.20 17:06, Nathan Hjelm wrote: >> On May 20, 2013, at 09:51 AM, Toby Gray wrote: >>> I've attached a handful of patches of changes needed to get WinCE >>> building (I've not tried it on hard

Re: [Libusbx-devel] Towards a 1.0.16 release, hotplug test branch, please test

On May 20, 2013, at 09:51 AM, Toby Gray wrote:On 16/05/13 21:47, Hans de Goede wrote: > Hi all, > > With some help from Pete, Xiaofan as well as Nathan, I have been working on > integrating the libusb hp API work done by Nathan for 1.0.16 on top of libusbx. > > We're planning to push these changes

Re: [Libusbx-devel] Towards a 1.0.16 release, hotplug test branch, please test

On May 19, 2013, at 7:42 AM, Xiaofan Chen wrote: > On Fri, May 17, 2013 at 4:47 AM, Hans de Goede wrote: >> Hi all, >> >> With some help from Pete, Xiaofan as well as Nathan, I have been working on >> integrating the libusb hp API work done by Nathan for 1.0.16 on top of >> libusbx. >> >> We

Re: [Libusbx-devel] Hotplug

What might be interesting to look into is I think libusb can listen for the event sent out by USBDeviceOpenSeize. I am not entirely sure (it might only apply to kernel drivers). This might be useful to force one libusb app to detach so another can use a device. Do any other platforms have a simi

Re: [Libusbx-devel] Hotplug

On Feb 12, 2013, at 3:41 AM, Kustaa Nyholm wrote: > On 12.2.2013 12.29, "Hans de Goede" wrote: >> >> I know, but I'm operating under the assumption that Nathan will eventually >> do a libusb release with his code, at which point having API compatibility >> would be good. And yes I know we don'

Re: [Libusbx-devel] libusbx-1.0.13 has been released

On Sep 26, 2012, at 12:21 AM, Lionel Debroux wrote:> > I think it turned out very good once > > it was done, but anyway, everyone is busy working on new and even > > better versions now. :) > > It is probably good enough for Mac OS X and Linux. But on Windows, > libusb-1.0.9 is basically not usabl

Re: [Libusbx-devel] libusbx-1.0.13 has been released

Agreed. Please move this to the libusbx mailing list. I couldn't care less about libusbx after the hid fiasco. -Nathan On Sep 24, 2012, at 9:42 PM, Jure Menart wrote: > Hi everybody, > > I'd like to share one unrelated thing: I AM NOT subscribed to the libusbx > related mailing lists and I A

Re: [Libusbx-devel] Isochronous error on mac

If the transaction should be working the user could try to change how far in the future the isoc transaction is scheduled for. He can do this by changing line 1370 (in 1.0.9) from:frame += 4;toframe += 6; or something similar.-NathanOn Jun 24, 2012, at 08:28 PM, Xiaofan Chen wrote:On Sun, Jun 24,

Re: [Libusbx-devel] libusbx v1.0.12 has been released

On Jun 15, 2012, at 3:59 PM, Pete Batard wrote: > On 2012.06.15 22:25, Nathan Hjelm wrote: >> Did you really put that HID junk back in there? This is a bad idea. HID >> users SHOULD NOT be using libusb and I will not add this IOHID support >> to the Darwin backend. >

Re: [Libusbx-devel] libusbx v1.0.12 has been released

On Jun 15, 2012, at 12:08 PM, Pete Batard wrote:All, It is my pleasure to announce the release of libusbx v1.0.12. In terms of bugfixes and new features, this new version brings the following improvements: * Fix a potential major regression with pthread on Linux * Fix missing thread ID from deb