public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Moles <jeremy-9vekgGPT+OA7YuNMryXyOw@public.gmane.org>
To: acpi-devel-TtF/mJH4Jtrk1uMJSBkQmQ@public.gmane.org
Subject: General Questions:
Date: Fri, 04 Feb 2005 07:32:34 -0500	[thread overview]
Message-ID: <1107520354.4248.16.camel@localhost> (raw)

Hello again ACPI gurus! Many thanks for the last tip; I was able to
decompile and "fix" the DSDT rather easily using the advice from your
responses.

I have a few questions about batteries:

I was looking around the battery driver code last night trying to find
out what the battery "alarm" actually does. Unfortuneately (and I only
spent a few minutes looking), I wasn't able to easily see what the
function of this feature was. I guess my first question is: does it do
anything at all? :)

Secondly, would it be beyond of the scope of ACPI for the battery driver
to generate ACPI events when the power gets low? Or is there already
something like this that exists that I'm missing? I tried
watching /proc/acpi/event last as my battery discharged and didn't see
any unusual activity.

Thirdly, does the kernel have access to the LED lights on a typical
laptop? That is, does it have the ability to ping the LED and make it
light up? Or, is that something controlled entirely by hardware? It
would be rather neat, I think, to use my "bluetooth" LED (since I don't
have bluetooth) in an arbitrary way.

Anyways. :)

-- 
Jeremy L. Moles
EmperorLinux
1-888-651-66
www.EmperorLinux.com
jeremy-LdSqz1EEwCk7YuNMryXyOw@public.gmane.org



-------------------------------------------------------
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

             reply	other threads:[~2005-02-04 12:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-04 12:32 Jeremy Moles [this message]
2005-02-04 14:47 ` General Questions: Rich Townsend

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=1107520354.4248.16.camel@localhost \
    --to=jeremy-9vekggpt+oa7yunmryxyow@public.gmane.org \
    --cc=acpi-devel-TtF/mJH4Jtrk1uMJSBkQmQ@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