From: Clark Williams <williams@redhat.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Rodolfo Giometti <giometti@linux.it>, linux-mips@linux-mips.org
Subject: Re: Battery status
Date: Fri, 22 Jul 2005 16:10:16 -0500 [thread overview]
Message-ID: <1122066616.10743.33.camel@riff> (raw)
In-Reply-To: <20050722191732.GB3770@linux-mips.org>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
On Fri, 2005-07-22 at 15:17 -0400, Ralf Baechle wrote:
> On Fri, Jul 22, 2005 at 09:53:56AM -0500, Clark Williams wrote:
>
> > > I'd like to implement a way to allow userspace to read battery status
> > > (or percentage). I notice this port of APM interface for ARM
> > > architecture «arch/arm/kernel/apm.c» and I think I can use comething
> > > similar... what do you think about that?
> >
> > You might want to look at how acpi is presented in the /proc interface.
> > You could hook your battery status routines into the acpi entries:
> >
> > /proc/acpi/battery/BAT0/{alarm,info,status}
> >
> > Just a thought.
>
> Forget it. One of the great advantages of MIPS is that Intel has ACPI.
> On the open Richter scale for stupidity ACPI in computing is a 9.8.
I never said that I liked ACPI, just that I liked the /proc interface.
I'm not really a fan of putting an interpreter into the system
firmware...
Clark
--
Clark Williams <williams@redhat.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-22 21:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 14:22 Battery status Rodolfo Giometti
2005-07-22 14:53 ` Clark Williams
2005-07-22 15:14 ` Rodolfo Giometti
2005-07-22 15:25 ` Clark Williams
2005-07-22 15:34 ` Rodolfo Giometti
2005-07-22 19:08 ` Clark Williams
2005-07-23 12:17 ` Rodolfo Giometti
2005-07-22 19:17 ` Ralf Baechle
2005-07-22 21:10 ` Clark Williams [this message]
2005-07-22 21:23 ` Ralf Baechle
2005-07-22 22:07 ` Clark Williams
2005-07-22 22:16 ` Ralf Baechle
2005-07-22 23:14 ` Alan Cox
2005-07-25 12:00 ` Maciej W. Rozycki
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=1122066616.10743.33.camel@riff \
--to=williams@redhat.com \
--cc=giometti@linux.it \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.