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

2013-09-13 Thread Hans de Goede
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: >>> Hi, >>> >>> On 09/11/2013 04:10 PM, Nathan Hjelm wrote: On Sep 11, 2013, at 7:15 AM, Nathan Hjelm wrote: > One

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

2013-09-13 Thread Nathan Hjelm
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: Hi, On 09/11/2013 04:10 PM, Nathan Hjelm wrote: >>>

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

2013-09-13 Thread Hans de Goede
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 >> streams >> then available, instead it should simply allocate the number of >> available streams >> a

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

2013-09-13 Thread Tim Roberts
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 types (stdint.h)? I'm struggling to avoid commenting on your political statement there.

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

2013-09-13 Thread Nathan Hjelm
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 types (stdint.h)? > > I'm st

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

2013-09-13 Thread Nathan Hjelm
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 >>> streams >>>then available, instead

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

2013-09-13 Thread Nathan Hjelm
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

2013-09-13 Thread Pete Batard
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 have neglected to update their C compiler to modern standards, but

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

2013-09-13 Thread Nathan Hjelm
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