Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Rodolfo Giometti <giometti@enneenne.com>
Cc: Paul Mundt <lethal@linux-sh.org>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.arm.linux.org.uk,
	linux-mips@linux-mips.org
Subject: Re: Advice on battery support [was: Advice on APM-EMU reunion]
Date: Fri, 2 Feb 2007 22:35:23 +0100	[thread overview]
Message-ID: <20070202213523.GA5089@elf.ucw.cz> (raw)
In-Reply-To: <20070201095904.GE8882@enneenne.com>

Hi!

> > However, it has since been reposted:
> > 
> > http://article.gmane.org/gmane.linux.kernel/485833
> > http://article.gmane.org/gmane.linux.kernel/485834
> > http://article.gmane.org/gmane.linux.kernel/485835
> > http://article.gmane.org/gmane.linux.kernel/485837
> > 
> > and merged back in to -mm. This is all post 2.6.20 stuff, though..
> 
> Ok, starting from these patches I'd like to add a "battery support" to
> the kernel.
> 
> What I suppose to do is a new class with a proper methods useful to
> collect several info on battery status, such as get_ac_line_status()
> get_battery_status(), get_battery_flags(),
> get_remaining_battery_life() and so on.
> 
> The output will be APM-like into file "/proc/apm" (one line per
> battery, or just the "main"/first one?) so that existing applications
> continue to work and under sysfs into "/sysfs/class/battery".
> 
> Is it sane? :)

Yep. Notice that designing /sysfs/class/battery is not going to be
easy, and that some work was already done in context of olpc
project. Search the mailing lists...
							Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      parent reply	other threads:[~2007-02-02 21:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-29 23:07 Advice on APM-EMU reunion Rodolfo Giometti
2007-01-29 23:53 ` Richard Purdie
2007-01-29 23:59   ` Rodolfo Giometti
2007-01-30  1:00 ` Paul Mundt
2007-01-30 14:05   ` Ralf Baechle
2007-02-01  9:59   ` Advice on battery support [was: Advice on APM-EMU reunion] Rodolfo Giometti
2007-02-01 18:19     ` Matt Reimer
2007-02-02 21:27     ` [PATCH 1/1] APM-EMULATION: apm_get_power_status() should be NULL on init [was: Advice on battery support] Rodolfo Giometti
2007-02-02 21:35     ` Pavel Machek [this message]

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=20070202213523.GA5089@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=giometti@enneenne.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox