On Wednesday 20 April 2005 12:26 pm, Gregg C Levine wrote:
> Hello from Gregg C Levine
> I'll probably get laughed at on the list, but have you verified that
> the chip works on a box running Windows?
>
> Battery manager chips sometimes don't like talking to systems who run
> Linux natively. I'm no
Oops,
0-index problem.
Just
subtract 1.
We'll
have to fix the documentation.
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of Junk
MailSent: Wednesday, April 20, 2005 11:36 AMTo:
owfs-developers@lists.sourceforge.netSubject: [Owfs-deve
Hello from Gregg C Levine
No, I was being overly dogmatic. It happens when you've reached my
level of training in being a Jedi Knight. And I happen to be a
confirmed Cynic. I was actually being polite regarding the whole
problem.
Yes we should do that. If need be we can provide stubs that respond
Hello from Gregg C Levine
I'll probably get laughed at on the list, but have you verified that
the chip works on a box running Windows?
Battery manager chips sometimes don't like talking to systems who run
Linux natively. I'm not sure how they've got the process for managing
battery packs for the
I'm trying to confirm the valid options for the
Ienable attribute for the 2438 Smart Battery Monitor. I see on the OWFS
manual page gives this info, but when I queried the Ienable status on my virgin
sensor, it returned 0 (which is not listed below) Are these
correct or are the values list
