Re: [Libusbx-devel] [PATCH] Samples: Add FX2/FX3 firmware upload to RAM

2012-08-09 Thread Markus
Hi Pete, my answers became a bit longer than intended. Here's my 5 cent, but generally, I'd leave the decision to you: > Now, this being said, I don't have that much of an issue bumping the > limit, but 4K seems awfully large for a file path. Would 512 bytes > be OK with you? I'm perfectly ok wi

Re: [Libusbx-devel] Handles for Windows WaitForXXX API?

2012-08-09 Thread g...@novadsp.com
Peter, On 09/08/2012 02:53, Peter Stuge wrote: > g...@novadsp.com wrote: > > Another point is that the code is absolutely unportable, which kindof > misses one big point of using the portable libusb-1.0 API. Indeed. Not an issue here. > No good since there can be no data from device until you in

Re: [Libusbx-devel] Handles for Windows WaitForXXX API?

2012-08-09 Thread Peter Stuge
g...@novadsp.com wrote: > > No good since there can be no data from device until you initiate a > > transfer. > > ? err, no. My device might well start to write back down the pipe as > soon as it has been configured. That would be a violation of the USB protocol. What device controller are you

Re: [Libusbx-devel] Handles for Windows WaitForXXX API?

2012-08-09 Thread g...@novadsp.com
Hello Pete On 09/08/2012 15:33, Peter Stuge wrote: >> >> ? err, no. My device might well start to write back down the pipe as >> soon as it has been configured. > > That would be a violation of the USB protocol. > My bad. Sloppy phrasing. Configured as in 'told what to do'. ---

Re: [Libusbx-devel] Handles for Windows WaitForXXX API?

2012-08-09 Thread Peter Stuge
g...@novadsp.com wrote: > Hello Pete (Note that Pete is another guy. :) > >> ? err, no. My device might well start to write back down the pipe as > >> soon as it has been configured. > > > > That would be a violation of the USB protocol. > > My bad. Sloppy phrasing. Configured as in 'told what

Re: [Libusbx-devel] Handles for Windows WaitForXXX API?

2012-08-09 Thread Tim Roberts
g...@novadsp.com wrote: >> No good since there can be no data from device until you initiate a >> transfer. > ? err, no. My device might well start to write back down the pipe as > soon as it has been configured. No, although it may be a matter of semantics. Your device can queue up data to be s

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

2012-08-09 Thread Pete Batard
On 2012.08.09 11:31, sebasti...@gmx-topmail.de wrote: > Maybe we got the jackpot (at least I hope so)?! My test computer finally > showed the segmentation fault today morning. Good. The more data we get, the better we'll be able to fix the issue. > You'll find all information in the attached fil

Re: [Libusbx-devel] [PATCH] Samples: Add FX2/FX3 firmware upload to RAM

2012-08-09 Thread Jon Sturm
On Thu, Aug 9, 2012 at 3:01 AM, Markus wrote: > Hi Pete, > > my answers became a bit longer than intended. Here's my 5 cent, > but generally, I'd leave the decision to you: > >> Now, this being said, I don't have that much of an issue bumping the >> limit, but 4K seems awfully large for a file pat

Re: [Libusbx-devel] [PATCH] Samples: Add FX2/FX3 firmware upload to RAM

2012-08-09 Thread Orin Eman
On Thu, Aug 9, 2012 at 4:57 PM, Jon Sturm wrote: > On Thu, Aug 9, 2012 at 3:01 AM, Markus wrote: > > Hi Pete, > > > > my answers became a bit longer than intended. Here's my 5 cent, > > but generally, I'd leave the decision to you: > > > >> Now, this being said, I don't have that much of an issu