On Mon, Aug 24, 2009 at 02:38:24PM -0700, Theodore Charles III wrote:
> I initially downloaded Barry, OpenSync, KitchenSync, and Kontact, and 
> had everything running smoothly. In connecting my 9630 to use the mass 
> storage mode (in order to get to the SD card), I noticed this:
> 
> r...@tessai:~# lsusb
> Bus 001 Device 024: ID 0fca:8004 Research In Motion, Ltd.
> 
> r...@tessai:~# lsusb
> Bus 001 Device 024: ID 0fca:8004 Research In Motion, Ltd.
> 
> r...@tessai:~# lsusb
> Bus 001 Device 025: ID 0fca:8007 Research In Motion, Ltd.
> 
> r...@tessai:~# lsusb
> Bus 001 Device 025: ID 0fca:8007 Research In Motion, Ltd.
> 
> Notice how the device ID changes? When I enable auto-MSC mode, the 
> device id will remain 8004, which kills my udev rules. I'm guessing that 
> there is something in barry that looks for the MSC mode and tells the 
> kernel that the vendor id is 8004. Am I wrong? I haven't tried setting 
> my 9630 to ask on connect for MSC mode. I'll let you know more after I do.

The change in Device number from 024 to 025 means that it reset itself
somehow.  Only bcharge does this normally, but since it looks like your udev
rules don't match for 8004, then bcharge shouldn't be running.

Perhaps the Blackberry itself resets when the usb_storage module tries to
make use of the mass storage mode?  Does this product ID change happen
if you comment out all udev rules that call bcharge?

There is nothing in Barry that checks for mass storage endpoints.  It
doesn't really care if they are there are not.  Bcharge merely tries
to reset the device into a mode that charges properly at 500mA, and
exposes the database USB endpoints, preferrably with both database and
Mass Storage endpoints available.  Mass storage is completely up to
the kernel.



> BUS=="usb", SUBSYSTEM=="usb_device", ACTION=="add", 
> ATTR{idVendor}=="0fca", ATTR{idProduct}=="8007", SYMLINK+="bb-%k", 
> RUN="/usr/sbin/bcharge -p %p"

It should be safe to duplicate the rules with different product IDs.
This is what the existing Barry rules do, and if possible, I'd like
to update them for the 9630, if you can help me test, since I don't have
such a device.

Once you have something that works, a patch against the existing rules
would be excellent.

Thanks,
- Chris


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Reply via email to