On Thu, Mar 25, 2010 at 06:22:28PM +1300, CzechWonderNine wrote:
> >>       endpoint added to map with bEndpointAddress: 0x81
> >
> >         pair.read = 0x81
> >
> >         pair.type = 0x2
> >
> >       endpoint_desc #1 loaded
> >

[...]

> >>       endpoint added to map with bEndpointAddress: 0x2
> >
> >         pair.write = 0x2
> >
> >         pair.type = 0x2
> >
> >         pair added! (read: 0x81,write: 0x2,type: 0x2)
> >
> >       endpoint_desc #2 loaded

[...]

> >>       endpoint added to map with bEndpointAddress: 0x0
> >
> >         pair.write = 0x0
> >
> >         pair.type = 0x0
> >
> >       endpoint_desc #3 loaded

[...]

> >>       endpoint added to map with bEndpointAddress: 0x0
> >
> >         pair.write = 0x0
> >
> >         pair.type = 0x0
> >
> >     interface added to map with bInterfaceNumber: 0

[...]

> > BulkWrite to endpoint 0x2:
> >
> >     00000000: 00 00 10 00 01 ff 00 00 a8 18 da 8d 6c 02 00 00
> >>  ............l...
> >
> >
> >> BulkRead: (-110, No error): Timeout in usb_bulk_read


There are two oddities on this device.  One is that there is a pair
of endpoints with the endpoint address for both set to zero.

I suspect that this means the firmware is wonky, or the linux kernel
is wonky on your machine.

I'd recommend trying a firmware upgrade on your device if you can swing it.

The second problem is that it times out on the very first "hello" message.
I'd be curious if, after this timeout, the device shows up in the lsusb
list anymore.

Also, I've seen timeouts like this on certain devices that didn't like
the charging sequence.  They would either let you charge (with bcharge) or
let you access the databases, but not both.

To test this, move the /etc/udev/rules.d/10-blackberry.rules file to a
different directory, and then replug your device.  Then try the above
test as root again, and post the output.

- Chris


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Reply via email to