linux-kernel - Re: Generic battery interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 28 Jul 2006 11:57:49 -0400
From:	Valdis.Kletnieks@...edu
To:	Shem Multinymous <multinymous@...il.com>
Cc:	Vojtech Pavlik <vojtech@...e.cz>, Pavel Machek <pavel@...e.cz>,
	"Brown, Len" <len.brown@...el.com>,
	Matthew Garrett <mjg59@...f.ucam.org>,
	kernel list <linux-kernel@...r.kernel.org>,
	linux-thinkpad@...ux-thinkpad.org, linux-acpi@...r.kernel.org
Subject: Re: Generic battery interface

On Fri, 28 Jul 2006 18:38:13 +0300, Shem Multinymous said:
>
> Another example: on my ThinkPad, the readouts provided by the EC
> change only every 2 seconds, regardless of how much you poll it.
> 
> Hence my proposal for a polling-based interface with kernel-side
> caching. This way, the hardware query rate is the minimum of two
> rates: what the application can use and what the kernel thinks is the
> hardware's change rate.

Is there a reliable (or hack-worthy) way for the kernel to determine how
often the values are re-posted by the hardware?

Content of type "application/pgp-signature" skipped