hello :) the zero endpoint phenomenon is gone with the new firmware upgrade
:)
the problem does not seem to be that it is not detecting the pearl it seems
to be that somthing in the kernel is not letting go of the pearl like it
should do :O
and ohhh thats what you mean by non pearl device :O sorry :) this is my
first blackberry so i dont have any others.
good luck hunting :) i will be sifting threw my kernel config and google
looking for ub :)
On 8/17/07, Chris Frey <[EMAIL PROTECTED]> wrote:
>
> On Thu, Aug 16, 2007 at 10:58:13PM -0400, Martin Owens wrote:
> > Chris;
>
> Hi Martin,
>
>
> > It might be worth putting a check in the btool for the pearl to check
> > how big the usb config is, I notice that the pearl with the fix is 97
> > long and in the same mode my unfixed pearl is only 69 long.
>
> If we're talking about the "0 endpoint" phenomenon, the problem is
> that the endpoints we need, for talking to the databases, are the
> endpoints that are missing. Checking the size would only tell me that
> the information I need is not there...
>
>
> > unfortunately nothing in the usb configuration looks like a firmware
> > version a real hardware model or anything that could be called
> > pearlish; I begining to think RIM hates the usb standard because I'm
> > so annoyed that I won't be able to identify this stupid device.
>
> You can detect the Pearl and Curve by the fact that they show up as
> Mass Storage devices when first plugged in. Other than that, you
> have to actually talk to the device (and overcome all the hurdles
> that btool has to). I'm sure there are database records in the device
> somewhere that would tell you.
>
> Unfortunately, it's probably not implemented yet. You might try
> using the "double bcharge" trick (I forget if you tried that),
> and then running a full backup with the GUI. Then untar the backup
> file and use strings and grep to search for identification data.
>
> If you wanted to try your hand at reverse engineering, I think I have
> some usb capture logs I could give you, and see if during Windows's
> initial handshaking the needed data shows up.
>
>
> > As an aside could you all send me a lsusb -v of your various non pearl
> > devices so I can compare them, make sure you do one in mode 4, one in
> > mode 6 and one in mode 1?
>
> This is an old, non-pearl device. It only has mode 0001.
>
> - Chris
>
> Bus 002 Device 003: ID 0fca:0001 Research In Motion, Ltd. Blackberry
> Handheld
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 1.01
> bDeviceClass 255 Vendor Specific Class
> bDeviceSubClass 255 Vendor Specific Subclass
> bDeviceProtocol 255 Vendor Specific Protocol
> bMaxPacketSize0 16
> idVendor 0x0fca Research In Motion, Ltd.
> idProduct 0x0001 Blackberry Handheld
> bcdDevice 1.04
> iManufacturer 1 Research In Motion
> iProduct 2 RIM-Handheld
> iSerial 0
> bNumConfigurations 2
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 46
> bNumInterfaces 1
> bConfigurationValue 1
> iConfiguration 0
> bmAttributes 0x80
> (Bus Powered)
> MaxPower 500mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 4
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 255 Vendor Specific Subclass
> bInterfaceProtocol 255 Vendor Specific Protocol
> iInterface 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x83 EP 3 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 10
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x06 EP 6 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 10
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x82 EP 2 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 10
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x05 EP 5 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 10
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 46
> bNumInterfaces 1
> bConfigurationValue 1
> iConfiguration 0
> bmAttributes 0x80
> (Bus Powered)
> MaxPower 500mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 4
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 255 Vendor Specific Subclass
> bInterfaceProtocol 255 Vendor Specific Protocol
> iInterface 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x83 EP 3 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 10
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x06 EP 6 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 10
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x82 EP 2 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 10
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x05 EP 5 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 10
> Device Status: 0x0000
> (Bus Powered)
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Barry-devel mailing list
> Barry-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/barry-devel
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
