Re: Battery management?

Hi Michael!

No, I haven't progressed beyond the patch I sent to the list awhile back.
I think it will mostly be a matter of rearranging the ds2760 code to fit
the new world order, and hooking up to battery.c (zap just did this, so we
can pattern our work after his). We should check with Jamey or pb, but I
think the battery code in arch/arm/common/ipaq is not functional, and
still needs to be adapted from the 2.4 way of doing things to the 2.6 way.

I really want to help with this and all the other stuff, but I'm buried
under schoolwork until May 27. But I can probably afford a few minutes
here and there to try to answer questions.

Matt

On Tue, 20 Apr 2004, Michael Opdenacker wrote:

> Hi Matt!
>
> What's up!
> Have you progressed on this battery management topic?
>
> If you don't have time at the moment, I can try to have a look...
>
> By the way, once battery management works and touchscreen calibration is
> ready (any good news, Alain?), I agree it makes sense to go mobile and
> chroot to an ext2 partition on a CF card.
>
> Cheers,
>
> Michael.
>
> >On Thu, 2004-04-01 at 23:37, Matthew Reimer wrote:
> >
> >
> >>Can you give us an idea of how this battery stuff should work in a 2.6
> >>world? Do I presume correctly that in 2.4 it was hooked up through hal,
> >>but that hal is gone in 2.6?
> >>
> >>
> >
> >It did present an interface through the HAL, yes (/proc/hal/battery to
> >be specific) but virtually nothing used it. The majority of
> >applications interrogated the battery through the APM emulation layer,
> >and a few more advanced programs read from /proc/asic/battery directly.
> >So the demise of the HAL probably won't have much impact on this code.
> >
> >
> >
> >>Should it be another soc device, say, shamcop_battery.c?
> >>
> >>
> >
> >I think the right thing to do is to implement the OWM interface as a SoC
> >device, then have a battery_ds2760 module (approximately equivalent to
> >the old h3600_asic_battery.c) that hooks onto that and in turn exposes
> >an interface to applications through drivers/misc/battery.c.
> >
> >p.
> >
> >
> >
> >
> >
>
>
> --
>
> Michael Opdenacker
> http://opdenacker.org/
>
>
Received on Tue Apr 20 2004 - 13:58:17 EDT