From: Francis Galiegue <fg@mandrakesoft.com>
To: linux-kernel@vger.kernel.org
Cc: jgarzik@mandrakesoft.com, Kernel list <kernel@linux-mandrake.com>
Subject: [PATCH] 2.4.2: cure the kapm-idled taking (100-epsilon)% CPU time
Date: Sun, 4 Mar 2001 00:03:56 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.21.0103040000550.922-200000@toy.mandrakesoft.com> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 422 bytes --]
As attachment. Don't ask me why it works. Rather, if you see why it works, I'd
like to know why :)
Patch also applies cleanly over 2.4.2-ac10.
--
Francis Galiegue, fg@mandrakesoft.com - Normand et fier de l'être
"Programming is a race between programmers, who try and make more and more
idiot-proof software, and universe, which produces more and more remarkable
idiots. Until now, universe leads the race" -- R. Cook
[-- Attachment #2: Type: TEXT/PLAIN, Size: 348 bytes --]
--- linux/arch/i386/kernel/apm.c.old Sat Mar 3 23:59:36 2001
+++ linux/arch/i386/kernel/apm.c Sat Mar 3 23:57:56 2001
@@ -557,7 +557,7 @@
{
u32 dummy;
- if (apm_bios_call_simple(APM_FUNC_IDLE, 0, 0, &dummy))
+ if (apm_bios_call(APM_FUNC_IDLE, 0, 0, &dummy, &dummy, &dummy, &dummy, &dummy))
return 0;
#ifdef ALWAYS_CALL_BUSY
next reply other threads:[~2001-03-03 23:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-03 23:03 Francis Galiegue [this message]
2001-03-03 23:15 ` [PATCH] 2.4.2: cure the kapm-idled taking (100-epsilon)% CPU time Francis Galiegue
2001-03-03 23:16 ` Alan Cox
2001-03-03 23:19 ` Francis Galiegue
2001-03-03 23:28 ` [kernel] " Philipp Rumpf
2001-03-04 0:02 ` Francis Galiegue
2001-03-03 23:35 ` [PATCH] 2.4.2: cure the kapm-idled taking (100-epsilon)% CPU Alan Cox
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=Pine.LNX.4.21.0103040000550.922-200000@toy.mandrakesoft.com \
--to=fg@mandrakesoft.com \
--cc=jgarzik@mandrakesoft.com \
--cc=kernel@linux-mandrake.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).