public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pedro Venda <pjvenda-pQd4kjVL+REh2FBCd0jGRA@public.gmane.org>
To: Johan Vromans <jvromans-2pNSKKP3PSKEVqv0pETR8A@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: DockApps (Was: Smart Battery System driver)
Date: Fri, 21 Jan 2005 13:30:55 +0000	[thread overview]
Message-ID: <41F1040F.5020409@arrakis.dhis.org> (raw)
In-Reply-To: <16880.8771.253591.739342-KjnUIgV0B0bak1Ioo/c9IoRWq/SkRNHw@public.gmane.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Johan Vromans wrote:
| [Quoting Rich Townsend, on January 19 2005, 08:31, in "Re: Smart Battery Sy"]
|
|>However, I'm surprised that the GB applet doesn't get the AC state from
|>polling /proc/acpi/adapter/AC0/state. I use wmacpi, and that shows up
|>the AC state fine...
|
|
| Speaking of wmacpi: what is your favorite (acpi-related) docapp for
| your laptop?

I use the kde thingy, klaptopdaemon, I think... works very well. reports AC
adapter presence and battery charge in percentage. not sure if it reports time
to empty...

regards,
pedro venda.

| Most of them have some form of libacpi that does a varying job. It is
| clear that using the SBS info would be much easier, and better.

hacking the lib would be the best way to use enhanced SBS information, although
I guess the driver state is not very matured to get people writing libraries to
access it. Also, having info/state entries in /proc is being "deprecated". /sys
was built for that and gradually all kernel drivers will be using it for
userspace interaction...

regards,
pedro venda.
- --

Pedro João Lopes Venda
email: pjvenda-pQd4kjVL+REh2FBCd0jGRA@public.gmane.org
http://arrakis.dhis.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB8QQPeRy7HWZxjWERAr2ZAKCmoe3RITPablOLXkLfn3U3lOLZegCgy73d
gM0hwGZUxxBsoKDLk15nUEc=
=WT8Y
-----END PGP SIGNATURE-----


-------------------------------------------------------
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 13:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20 21:27 DockApps (Was: Smart Battery System driver) Johan Vromans
     [not found] ` <20050121101018.GB3945@himi.org>
     [not found]   ` <20050121101018.GB3945-Ji7FXtOmRLs@public.gmane.org>
2005-01-21 12:57     ` DockApps Johan Vromans
     [not found]       ` <m2hdlb7xem.fsf-KjnUIgV0B0bak1Ioo/c9IoRWq/SkRNHw@public.gmane.org>
2005-01-21 14:22         ` DockApps Simon Fowler
     [not found] ` <16880.8771.253591.739342-KjnUIgV0B0bak1Ioo/c9IoRWq/SkRNHw@public.gmane.org>
2005-01-21 13:30   ` Pedro Venda [this message]
     [not found]     ` <41F1040F.5020409-pQd4kjVL+REh2FBCd0jGRA@public.gmane.org>
2005-01-21 15:49       ` DockApps (Was: Smart Battery System driver) Fred Labrosse

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=41F1040F.5020409@arrakis.dhis.org \
    --to=pjvenda-pqd4kjvl+reh2fbcd0jgra@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=jvromans-2pNSKKP3PSKEVqv0pETR8A@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