Difference between revisions of "Talk:Maintenance"
(Charge threshold?) |
|||
| Line 7: | Line 7: | ||
http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-September/029556.html --gst | http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-September/029556.html --gst | ||
| + | ---- | ||
| + | |||
| + | I see that when the charge threshold is set in Windows, it lasts through reboots (even into Linux) and battery changes. The only thing that resets it is disconnection of the AC power. This suggests that the setting is stored in the embedded controller (rather than RAM, CMOS or battery). However, I can't see any obvious corresponding field in {{path|/proc/acpi/ibm/ecdump}}. | ||
| + | |||
| + | --[[User:Thinker|Thinker]] 17:04, 6 Nov 2005 (CET) | ||
| + | ---- | ||
Revision as of 17:04, 6 November 2005
In regard to the question about controlling the charge threshold from Linux: apparently this isn't controlled by some standard means such as an ACPI method, but rather by direct I/O port tweaking done by the Battery MaxiMiser driver for Windows. It would be very hard to figure this out without specs.
--Thinker 17:56, 2 Oct 2005 (CEST)
maybe it would be possible to use a windows tool like SoftICE to capture the communication required to set the treshholds? as soon as we have some sort of specification adding support for it to the kernel should be rather trivial. --gst
http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-September/029556.html --gst
I see that when the charge threshold is set in Windows, it lasts through reboots (even into Linux) and battery changes. The only thing that resets it is disconnection of the AC power. This suggests that the setting is stored in the embedded controller (rather than RAM, CMOS or battery). However, I can't see any obvious corresponding field in /proc/acpi/ibm/ecdump.
--Thinker 17:04, 6 Nov 2005 (CET)
