[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070201095904.GE8882@enneenne.com>
Date: Thu, 1 Feb 2007 10:59:04 +0100
From: Rodolfo Giometti <giometti@...eenne.com>
To: Paul Mundt <lethal@...ux-sh.org>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.arm.linux.org.uk, linux-mips@...ux-mips.org
Subject: Advice on battery support [was: Advice on APM-EMU reunion]
On Tue, Jan 30, 2007 at 10:00:55AM +0900, Paul Mundt wrote:
> 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? :)
Thanks in advance,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti@...eenne.com
Linux Device Driver giometti@...dd.com
Embedded Systems giometti@...ux.it
UNIX programming phone: +39 349 2432127
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists