From: Dmitry Torokhov <dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
To: Karl Hegbloom <hegbloom-tbDHPZwbsQQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Synaptics and keyboard losing interrupts w/ACPI ?
Date: Sun, 4 Apr 2004 00:29:12 -0500 [thread overview]
Message-ID: <200404040029.12359.dtor_core@ameritech.net> (raw)
In-Reply-To: <1081055767.2239.7.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
On Sunday 04 April 2004 12:16 am, Karl Hegbloom wrote:
> On Sat, 2004-04-03 at 20:36, Dmitry Torokhov wrote:
> > I think you can leave it on but you will have to increase the poll interval.
> > Setting it to 30 sec or even 1 min will probably let you have your Synaptics
> > working and still have an idea on battery level.
>
> I will try this and see if it works, thank you.
>
> > > So, something is the matter with the ACPI battery code! I doubt I can
> > > find it... but I'll look in there anyway just for some exposure. :-)
> >
> > It is usually deep in the BIOS code, not something exposed in AML as far as
> > I can understand. Polling battery often takes long time, especially polling
> > full info as opposed to just state. :(
>
> Is there any reason why the ACPI code cannot cache that info, rather
> than looking it up each time the /proc file is accessed? (which is what
> I think it does now... am I right?)
>
It sort of does.. that's why there /proc/acpi/battery/BATX/info (slow access,
mostly static data) and /proc/acpi/battery/BATX/state. Now if only
applications weren't reading both of them all the time...
--
Dmitry
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-04-04 5:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 2:09 Synaptics and keyboard losing interrupts w/ACPI ? Karl Hegbloom
[not found] ` <1081044549.2179.281.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2004-04-04 2:45 ` Randy.Dunlap
[not found] ` <20040403184520.196ff775.rddunlap-3NddpPZAyC0@public.gmane.org>
2004-04-04 3:19 ` Karl Hegbloom
[not found] ` <1081048768.2179.293.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2004-04-04 3:49 ` Karl Hegbloom
[not found] ` <1081050591.2239.1.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2004-04-04 4:36 ` Dmitry Torokhov
[not found] ` <200404032336.39468.dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
2004-04-04 5:16 ` Karl Hegbloom
[not found] ` <1081055767.2239.7.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2004-04-04 5:29 ` Dmitry Torokhov [this message]
[not found] ` <200404040029.12359.dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
2004-04-04 5:54 ` Karl Hegbloom
[not found] ` <1081058079.2239.15.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2004-04-04 6:06 ` Dmitry Torokhov
[not found] ` <200404040106.15621.dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
2004-04-05 2:40 ` Stefan Seyfried
[not found] ` <20040405024043.GC5509-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2004-04-05 3:43 ` Karl Hegbloom
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=200404040029.12359.dtor_core@ameritech.net \
--to=dtor_core-ywtbtysyrb+lz21kgmrzwg@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=hegbloom-tbDHPZwbsQQ@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