APMD-List:
Archives

  From: Avery Pennarun <apenwarr@worldvisions.ca>
  To  : <craigm@milkyway.gsfc.nasa.gov>
        < apmd-list@worldvisions.ca>
  Date: Fri, 25 Jun 1999 17:40:14 -0400

Re: apmd-3.0beta5-8

On Fri, Jun 25, 1999 at 12:07:18PM -0400, Craig Markwardt wrote:

> Heh heh.  In the patch I submitted, apmd_proxy was called for all
> kinds of low battery messages.  David Brownell suggested that he was
> getting too many notifications and rearranged that bit of code.

Oops.  I guess I missed that when I merged in his patch.  It was a big one
and most of it looked like an improvement :)

> I agree with you, we should treat the two similarly; apmd_proxy should be
> called.  Here's a patch snippet.
> [...patch snippet snipped...]

That's what I was thinking.

> Will you be putting out a new version soon?  I know I've submitted a
> few patches to you for this and other install bugs.  apmd_proxy should
> be updated to better reflect our understanding of what needs to be
> done.  David Brownell also suggested we add more documentation for
> BIOS workarounds and how to use apmd_proxy (cardctl suspend,
> soundoff/on, chvt).

I'm going out of town for a week, so there won't be an apmd release until at
least the first Monday in July.  Meanwhile, if you want to fix up apmd_proxy
or add documentation, just send it to me and I'll merge it all when I get
back.

Now, as to ignoring BIOS-generated "low battery" warnings... I'm surprised
so many people think they're useful.  I don't see the point of them at all,
myself.  With "synthetic" messages from apmd, we have complete control over
when messages get logged -- with the BIOS-generated warnings, they seem to
happen randomly, with no ability to configure them, and apparently with at
least one person the threshold value is 49% - way too high.

Why not just throw them out completely and make _all_ battery warnings
synthetic?

Have fun,

Avery