public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Rich Townsend <rhdt-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
To: "Rockefeller,
	Harry" <harryr-UjZhlPPWhclBDgjK7y7TUQ@public.gmane.org>,
	Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Battery alarm ->  was General Questions:
Date: Fri, 04 Feb 2005 14:46:18 -0500	[thread overview]
Message-ID: <4203D10A.3090306@bartol.udel.edu> (raw)
In-Reply-To: <B774920D825C2D4880A3C1B0D6EF9418034150B4-YbQoUGCEyAW+LrQOllSzDQC/G2K4zDHf@public.gmane.org>

Rockefeller, Harry wrote:

<snip>

> 
> My notebook, Uniwill N351S1, is - supposedly - both APM and ACPI 2.0
> supported.  Would something as important as battery alarm simply not
> be implemented in ACPI?

Certainly. Many manufacturers have broken ACPI implementations; as far 
as they're concerned, if it works with Windows, then it "works". It's 
probably the case that Windows polls the battery, rather than relying on 
the alarm, so that broken implementations will still function.

> FWIW, /proc/acpi/battery/BAT0/info gives both design capacity warning
> and low data.

These are fixed (non-settable) quantities, that have little to do with 
the alarm.

> 
> A 'grep BTP dsdt.dsl' turns up:      BTP0,     16,

But no _BTP, which means no alarm.

> 
> Can I modify dsdt.dsl to add this ACPI function myself?

In principle, yes. If you like, I can have a look at your DSDT to see 
how easy it would be to add in _BTP.

cheers,

Rich


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

  parent reply	other threads:[~2005-02-04 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-04 19:36 Battery alarm -> was General Questions: Rockefeller, Harry
     [not found] ` <B774920D825C2D4880A3C1B0D6EF9418034150B4-YbQoUGCEyAW+LrQOllSzDQC/G2K4zDHf@public.gmane.org>
2005-02-04 19:46   ` Rich Townsend [this message]
     [not found]     ` <4203D10A.3090306-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
2005-02-04 18:14       ` Jeremy Moles
  -- strict thread matches above, loose matches on Subject: below --
2005-02-04 20:20 Rockefeller, Harry

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4203D10A.3090306@bartol.udel.edu \
    --to=rhdt-obnux95toyn10jlvftc4ga@public.gmane.org \
    --cc=Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=harryr-UjZhlPPWhclBDgjK7y7TUQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox