On Thu, 2007-03-29 at 16:44 -0400, Chris Frey wrote:
> On Thu, Mar 22, 2007 at 06:04:02PM -0400, Rick Scott wrote:
> > I've been quiet on this so far, but good things don't last forever :)
> > Greg has, or will, submit the power change part for the inclusion in the
> > kernel, so bcharge may become
On Thu, Mar 22, 2007 at 06:04:02PM -0400, Rick Scott wrote:
> I've been quiet on this so far, but good things don't last forever :)
> Greg has, or will, submit the power change part for the inclusion in the
> kernel, so bcharge may become a non-issue. With a bit of luck, the whole
> driver may beco
I've been quiet on this so far, but good things don't last forever :)
Greg has, or will, submit the power change part for the inclusion in the
kernel, so bcharge may become a non-issue. With a bit of luck, the whole
driver may become a non-issue (fingers crossed, not holding my breathe).
The power
On 3/21/07, Chris Frey <[EMAIL PROTECTED]> wrote:
> Thanks. Looks like I can't use iProduct as a way to determine whether
> I'm talking to a Pearl or not. :-(
I would assume that it's the same going forward; 8100, 8800, 83xx, and
so forth. They all have microSD slots, so I would thing the interna
On Sat, Mar 17, 2007 at 02:01:01PM -0700, troy engel wrote:
> You have to do this manually since the logic loop missing 0x0004 is
> missing in older bcharge, so I renamed mine to bcharge.rpm. Starting
> from a raw plugin (0x0006) the running ./bcharge.rpm -o, I get:
>
> idVendor 0x0fca
On 3/17/07, Chris Frey <[EMAIL PROTECTED]> wrote:
>
> Thanks! What number is it when idProduct is 0x0001, if you use an old
> bcharge -o?
You have to do this manually since the logic loop missing 0x0004 is
missing in older bcharge, so I renamed mine to bcharge.rpm. Starting
from a raw plugin (0x0
On Sat, Mar 17, 2007 at 09:43:48AM -0700, troy engel wrote:
> Nope, when it's device 0x0006 it's iProduct = 4. From the newest
> bcharge (I'll reply in that thread about this), I see:
>
> idVendor 0x0fca Research In Motion, Ltd.
> idProduct 0x0006
> bcdDevice1.
On 3/16/07, Chris Frey <[EMAIL PROTECTED]> wrote:
>
> I'm mostly interested to know if iProduct is consistently a 5 on Pearl
> devices.
Nope, when it's device 0x0006 it's iProduct = 4. From the newest
bcharge (I'll reply in that thread about this), I see:
idVendor 0x0fca Research In M
