public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: thoma-iYtK5bfT9M8b1SvskN2V4Q@public.gmane.org
Cc: Markus Gaugusch <markus-z+rTbpWsRgbk7+2FdBfRIA@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Sony Vaio Battery Info
Date: Sat, 21 Dec 2002 22:45:04 +0100	[thread overview]
Message-ID: <20021221214504.GA1923@zaurus> (raw)
In-Reply-To: <3E02CEB5.9080506-xhPu7QH+N+StU9/U+hoEgQ@public.gmane.org>

Hi!

> Markus Gaugusch wrote:
> >As previously written, reading the battery info on sony vaio laptops
> >(FX/FXA series) takes very long time (~0.6 sec). Battery state takes 
> >only
> >~0.1 sec, but this is still too long for constantly using a battery
> >monitor.
> 
> 
> Hallo Marcus,
> (perhaps you remember me:-)
> 
> I have a SONY-VAIO FX505, is the 'keybord-look-bug' fixed? (I still 
> run an half-year-old ACPI)
> 
> In my opinion the info-file need only to be read ONCE, because it 
> contains only 'static' infos about the battery.

Like capacity at last charge? That can change, too.
OTOH Reading it once in 3 hours should be ok
-- 
				Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  parent reply	other threads:[~2002-12-21 21:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19 20:13 Sony Vaio Battery Info Markus Gaugusch
     [not found] ` <Pine.LNX.4.50.0212192106570.950-100000-KjnUIgV0B0bsKMwAuzqOxrNldLUNz+W/@public.gmane.org>
2002-12-20  8:03   ` Malte Thoma
     [not found]     ` <3E02CEB5.9080506-xhPu7QH+N+StU9/U+hoEgQ@public.gmane.org>
2002-12-21 21:45       ` Pavel Machek [this message]
2002-12-20 16:09   ` Stephen White

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=20021221214504.GA1923@zaurus \
    --to=pavel-+zi9xunit7i@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=markus-z+rTbpWsRgbk7+2FdBfRIA@public.gmane.org \
    --cc=thoma-iYtK5bfT9M8b1SvskN2V4Q@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