From: Kyle Moffett <mrmacman_g4@mac.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Pavel Machek <pavel@suse.cz>, Stefan Seyfried <seife@suse.de>,
Matthew Garrett <mjg59@srcf.ucam.org>,
linux-pm@lists.osdl.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH, RFC] [1/3] Generic in-kernel AC status
Date: Sun, 12 Feb 2006 06:27:48 -0500 [thread overview]
Message-ID: <0BA45EBB-57F5-42C8-AF6B-216A29F2EF8B@mac.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0602121116190.25363@yvahk01.tjqt.qr>
On Feb 12, 2006, at 05:17, Jan Engelhardt wrote:
>>>>> Ok. Maybe i am not seeing the point. But why do we need this in
>>>>> the kernel? Can't we handles this easily in userspace?
>>>>
>>>> Some kernel parts need to now: for example powernow-k8: some
>>>
>>> we can tell them from userspace.
>>
>> No, because battery will explode if you do not slow cpu down fast
>> enough.
>
> How is that? APC UPS don't explode either if they are switching to
> battery.
Yes, but APC UPS have big 3-inch fans blowing air over the batteries
to keep them from overheating; laptops dont. Besides which, have you
ever stuck your hand on a UPS while it's running a server on
battery? Those things get damn hot even with the fans, not even
considering the fact that a lead-acid battery is much more efficient
about storing and using energy than a Lithium-ion battery.
Incidentally, my UPS thermometer tells me that the peak load on-
battery temp is more than 120 F; would you _really_ want that sitting
on your lap in addition to all the heat generated by CPU, ram, GPU, etc?
There are real applications out there that have these problems, in
fact a lot of manufacturers have issued recalls because of exploding
batteries, power bricks, etc, indicating that this is not a simple
problem.
Cheers,
Kyle Moffett
--
Diplomacy involves walking softly and _carrying_ a big stick.
Actually using the big stick means the diplomacy part failed.
-- Rob Landley
next prev parent reply other threads:[~2006-02-12 11:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 12:57 Matthew Garrett
2006-02-08 13:03 ` [PATCH, RFC] [2/3] ACPI support for generic " Matthew Garrett
2006-02-08 13:04 ` [PATCH, RFC] [1/3] Generic " Matthew Garrett
2006-02-08 13:05 ` [PATCH, RFC] [3/3] APM support for generic " Matthew Garrett
2006-02-08 16:58 ` [linux-pm] Re: [PATCH, RFC] [1/3] Generic " Greg KH
2006-02-08 17:08 ` Matthew Garrett
2006-02-08 17:16 ` Greg KH
2006-02-08 17:49 ` Matthew Garrett
2006-02-09 5:46 ` Greg KH
2006-02-09 8:53 ` Gabor Gombas
2006-02-10 12:21 ` Pavel Machek
2006-02-10 13:13 ` Gabor Gombas
2006-02-10 13:19 ` Matthew Garrett
2006-02-10 13:54 ` Pavel Machek
2006-02-10 13:56 ` Gabor Gombas
2006-02-08 22:25 ` Philipp Matthias Hahn
2006-02-10 12:21 ` Pavel Machek
2006-02-10 8:06 ` Stefan Seyfried
2006-02-10 12:19 ` Pavel Machek
2006-02-10 12:32 ` Stefan Seyfried
2006-02-10 13:46 ` Pavel Machek
2006-02-12 10:17 ` Jan Engelhardt
2006-02-12 11:27 ` Kyle Moffett [this message]
2006-02-14 17:44 ` Thomas Renninger
2006-02-14 20:17 ` Rafael J. Wysocki
2006-02-15 12:36 ` Thomas Renninger
2006-02-15 12:47 ` Matthew Garrett
2006-02-15 15:04 ` Thomas Renninger
2006-02-16 22:44 ` Pavel Machek
2006-02-16 22:39 ` 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=0BA45EBB-57F5-42C8-AF6B-216A29F2EF8B@mac.com \
--to=mrmacman_g4@mac.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=mjg59@srcf.ucam.org \
--cc=pavel@suse.cz \
--cc=seife@suse.de \
/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
all inboxes | Powered by JetHome®