All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bas Mevissen <ml-Y9IUUvl1dgU0Iwp8Nzs06g@public.gmane.org>
To: Markus Gaugusch <markus-z+rTbpWsRgbk7+2FdBfRIA@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Battery status reading problems
Date: Mon, 22 Sep 2003 09:55:08 +0200	[thread overview]
Message-ID: <3F6EAADC.4020509@basmevissen.nl> (raw)
In-Reply-To: <Pine.LNX.4.58.0309192257480.1613-KjnUIgV0B0bsKMwAuzqOxrNldLUNz+W/@public.gmane.org>

Markus Gaugusch wrote:
> On Sep 18, Jan Rychter <jan-JAsPCFd0eodBDgjK7y7TUQ@public.gmane.org> wrote:
> 
>>Reading the battery status still consumes insane amounts of CPU time
> 
> Recently, a bug has been fixed by some nice person at intel - the AML code
> was executed twice. Although half of the time is still not perfect, it is
> a lot better now.
> 

But on Windows, there is no slowdown noticeable. Is that just the 
different implementation or is there still something (too) slow in the 
Intel ACPI CA code?

Bas.





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

  parent reply	other threads:[~2003-09-22  7:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-19  6:23 Battery status reading problems Jan Rychter
     [not found] ` <m2vfrpthxt.fsf-dTJq59+VGzkkCw8IV3R6h0EOCMrvLtNR@public.gmane.org>
2003-09-19 21:02   ` Markus Gaugusch
     [not found]     ` <Pine.LNX.4.58.0309192257480.1613-KjnUIgV0B0bsKMwAuzqOxrNldLUNz+W/@public.gmane.org>
2003-09-22  7:55       ` Bas Mevissen [this message]
     [not found]         ` <3F6EAADC.4020509-Y9IUUvl1dgU0Iwp8Nzs06g@public.gmane.org>
2003-09-22  7:56           ` Markus Gaugusch
     [not found]             ` <Pine.LNX.4.53.0309220954120.9385-sxQ525G0OhRQK2oVCIMtW7NldLUNz+W/@public.gmane.org>
2003-09-22 11:37               ` Alan Cox
     [not found]                 ` <1064230622.8592.14.camel-Z+iYsftfazAXoXS6vNje7nviChZXdy279dF7HbQ/qKg@public.gmane.org>
2003-09-22 12:52                   ` Ducrot Bruno
2003-09-23 12:14                   ` Bas Mevissen
     [not found]                     ` <3F703933.50604-Y9IUUvl1dgU0Iwp8Nzs06g@public.gmane.org>
2003-09-23 16:25                       ` Nils Faerber
     [not found]                         ` <1064334307.14784.92.camel-65LrUGLyukAb1SvskN2V4Q@public.gmane.org>
2003-09-23 16:44                           ` Markus Gaugusch
2003-09-23 18:11                           ` liste-9nAOAgdJVo4b1SvskN2V4Q
     [not found]                             ` <Pine.LNX.4.58.0309232001000.1228-KnfdeQs3A3X/9pzu0YdTqQ@public.gmane.org>
2003-09-26  5:38                               ` Jan Rychter
     [not found]                                 ` <m24qz0f6ry.fsf-dTJq59+VGzkkCw8IV3R6h0EOCMrvLtNR@public.gmane.org>
2003-09-26  8:55                                   ` Toon van der Pas
     [not found]                                     ` <20030926085542.GA28731-UrA3525iEjFfB9KAG+eifygtU7bT7/Jf@public.gmane.org>
2003-09-26 12:25                                       ` David G Hamblen
2003-09-26  9:25                                   ` Markus Gaugusch
2003-09-25 10:44                       ` Pavel Machek

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=3F6EAADC.4020509@basmevissen.nl \
    --to=ml-y9iuuvl1dgu0iwp8nzs06g@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=markus-z+rTbpWsRgbk7+2FdBfRIA@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.