Hi Peter.

Sorry for the "BE" issue on the name. I'll remember. ;)
-And I think it's unlikely to be libusb, since the working drivers are already 
using it indirectly.

I've also been thinking that it could be a problem with my platform, but no, 
libusb works on my platform, so it *has* to be a software problem, and thus it 
will be possible to fix it.
It's still possible that it's a value read frm an uninitialized buffer.
Somehow, I believe that the problem would show up on LE machines at some point 
if that was the case.


Love
Jens

On Thu, 31 Oct 2013 11:10:44 +0100, Peter Stuge wrote:
> Jens Bauer wrote:
>> Yes, my guesses was round the USBLib
> 
> libusb (please note the name, it's neither USBLib nor LibUSB) had a
> big-endian bug with descriptors fixed three years ago by someone with
> a BE x achine; that's the last BE issue I've seen.
> 
> And transfered data isn't touched, it is just passed on as-is.
> 
> 
> //Peter
> 
> ------------------------------------------------------------------------------
> Android is increasing in popularity, but the open development platform that
> developers love is also attractive to malware creators. Download this white
> paper to learn more about secure code signing practices that can help keep
> Android apps secure.
> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
> _______________________________________________
> OpenOCD-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openocd-devel

------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to