From: "Charles Lepple" <clepple@ghz.cc>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [REPOST] "apm: suspend: Unable to enter requested state" after 2.5.31 (incl. 2.6.0testX)
Date: Tue, 29 Jul 2003 12:05:55 -0400 (EDT) [thread overview]
Message-ID: <32460.216.12.38.216.1059494755.squirrel@www.ghz.cc> (raw)
In-Reply-To: <1059491223.6094.6.camel@dhcp22.swansea.linux.org.uk>
Alan Cox said:
> Does it work any better if you change the 0x0, 0x00409200 to
>
> 0x00109300, 0x00409200 ?
Is this what you're referring to?
--- arch/i386/kernel/apm.c.orig 2003-07-27 12:57:00.000000000 -0400
+++ arch/i386/kernel/apm.c 2003-07-29 11:18:52.000000000 -0400
@@ -424,7 +424,7 @@
static DECLARE_WAIT_QUEUE_HEAD(apm_suspend_waitqueue);
static struct apm_user * user_list;
static spinlock_t user_list_lock = SPIN_LOCK_UNLOCKED;
-static struct desc_struct bad_bios_desc = { 0, 0x00409200 };
+static struct desc_struct bad_bios_desc = { 0x00109300, 0x00409200 };
static char driver_version[] = "1.16ac"; /* no
spaces */
I tried this on top of 2.6.0-test2, and it didn't work. Where does the
first number in that initializer come from?
In case it has something to do with the APM entry points:
apm: entry fcd4:0 cseg16 f000 dseg 9f80 [...]
thanks,
--
Charles Lepple <clepple@ghz.cc>
http://www.ghz.cc/charles/
next prev parent reply other threads:[~2003-07-29 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 14:50 Charles Lepple
2003-07-29 15:07 ` Alan Cox
2003-07-29 16:05 ` Charles Lepple [this message]
2003-07-29 18:10 ` Alan Cox
2003-07-30 1:05 ` Stephen Rothwell
2003-07-30 1:38 ` Charles Lepple
2003-07-30 2:21 ` Stephen Rothwell
2003-07-30 16:48 ` [REPOST] "apm: suspend: Unable to enter requested state" after2.5.31 " Charles Lepple
2003-07-30 14:43 ` [REPOST] "apm: suspend: Unable to enter requested state" after 2.5.31 " Alan Cox
2003-07-30 15:16 ` Stephen Rothwell
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=32460.216.12.38.216.1059494755.squirrel@www.ghz.cc \
--to=clepple@ghz.cc \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®