All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: Re: Smart Battery System driver
Date: Fri, 21 Jan 2005 17:22:46 +0000	[thread overview]
Message-ID: <1106328167.30227.18.camel@tyrosine> (raw)
In-Reply-To: <41F136AE.3010603-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>

On Fri, 2005-01-21 at 12:06 -0500, Rich Townsend wrote:

> But aren't we really looking for a kernel-based libpower -- so that 
> *nothing* in userspace needs be exposed to the specifics of the hardware?

No. The kernel should provide information and functionality, not define
policy. A good comparison point might be the lm-sensors code - each
driver provides all the information it can, and the userland libsensors
abstracts that away from everything else.

-- 
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@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

  parent reply	other threads:[~2005-01-21 17:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20 22:04 Re: Smart Battery System driver Grover, Andrew
     [not found] ` <F760B14C9561B941B89469F59BA3A84708CBB988-sBd4vmA9Se6krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-01-20 22:12   ` Karol Kozimor
2005-01-21  0:03   ` Matthew Garrett
2005-01-21 12:02     ` Paul Ionescu
2005-01-21 10:06   ` Simon Fowler
     [not found]     ` <20050121100618.GA3945-Ji7FXtOmRLs@public.gmane.org>
2005-01-21 13:22       ` Rich Townsend
2005-01-21 14:14   ` Stefan Seyfried
     [not found]     ` <20050121141449.GA15288-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2005-01-21 17:06       ` Rich Townsend
     [not found]         ` <41F136AE.3010603-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
2005-01-21 17:22           ` Matthew Garrett [this message]
2005-01-21 18:04             ` Rich Townsend
     [not found]               ` <41F14424.6010600-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
2005-01-21 18:22                 ` Matthew Garrett
2005-01-21 17:56           ` Stefan Seyfried
  -- strict thread matches above, loose matches on Subject: below --
2005-01-15  0:13 Matthew Garrett
2005-01-15  3:03 ` Johannes Kuhlmann
2005-01-15 10:57   ` Johan Vromans
2005-01-16  8:55     ` Rich Townsend
2005-01-18  3:03       ` Rich Townsend
2005-01-18  4:39         ` Rich Townsend
2005-01-19  4:32           ` Rich Townsend
2005-01-20  3:03             ` Rich Townsend
2005-01-20 15:12               ` Pedro Venda
2005-01-20 16:04                 ` Rich Townsend
2005-01-20 21:10                   ` Stefan Seyfried
     [not found]                     ` <20050120211044.GA27543-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2005-01-21 13:16                       ` Pedro Venda
     [not found]                         ` <41F1009C.30201-pQd4kjVL+REh2FBCd0jGRA@public.gmane.org>
2005-01-21 17:48                           ` Stefan Seyfried

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=1106328167.30227.18.camel@tyrosine \
    --to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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 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.