On Sat, May 24, 2008 at 12:56:12PM +0100, Federico G. Schwindt wrote:
> > We were the first to get Blackberries charging natively on non-Windows
> > machines.  The "bcharge.cc" program was released December 2006.
> 
>   The uberry(4) driver in our tree is dated 2006-11-27 :-)

Those are close debuts. :-)

Before bcharge, devices in the open source world would tend to get stuck
at 100mA, instead of the 500mA that Windows machines were capable of.

Taking a peek at the CVS history for uberry, it seems the commands to
boost it to 500mA were added around August 2007, and this change
was based on bcharge.

http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/uberry.c?rev=1.11&content-type=text/x-cvsweb-markup


>   you're not giving us a dmesg or any useful information, but i guess your
> blackberry is detected as uberry? if so, libusb only works on ugen devices,
> and the device needs to exist in /dev.

Sorry, I didn't think to send dmesg.  It did indeed detect the device
as uberry.  I'm not familiar with ugen, so I will read up on it.
Thank you!

I assume I'll have to disable uberry somehow, in order to use ugen?


> > Barry takes the approach that, given a working libusb, all Blackberry
> > functionality can happen in userspace, from charging to backups to
> > modem support.  But modem support on the newer Blackberries is fairly
> 
>   charging is already provided by the uberry driver.

Absolutely.  I just meant to explain what Barry's goals were.  It is a
combination of research + library + user applications.

I know folks have differing opinions on what belongs in kernel space vs.
user space, and I'm not familiar enough with OpenBSD to know where that
balance lies.

- Chris


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Reply via email to