public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Suspend-devel list <suspend-devel@lists.sourceforge.net>,
	"Li, Shaohua" <shaohua.li@intel.com>,
	"Zhao, Yakui" <yakui.zhao@intel.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	"Zhang, Rui" <rui.zhang@intel.com>,
	"lenb@kernel.org" <lenb@kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"andi@firstfloor.org" <andi@firstfloor.org>
Subject: Re: ACPI suspend: test 64-bit waking vector (was Re: [PATCH] ACPI suspend: Always use the 32-bit waking vector)
Date: Wed, 17 Sep 2008 09:28:58 +0200	[thread overview]
Message-ID: <20080917072858.GA2659@elf.ucw.cz> (raw)
In-Reply-To: <200809170745.19645.rjw@sisk.pl>

On Wed 2008-09-17 07:45:18, Rafael J. Wysocki wrote:
> On Monday, 15 of September 2008, Pavel Machek wrote:
> > Hi!
> > 
> > ACPI specificiation tells us that x_firmware_waking_vector is
> > preffered, and maybe it works better than firmware_waking_vector on
> > some machines.
> > 
> > Unfortunately, it does not seem to work on thinkpad x60... but I am
> > not sure if I'm not doing something wrong.
> > 
> > Testing/ideas would be welcome.
> 
> Well, the spec says that if x_firmware_waking_vector is non-zero, the BIOS is
> supposed to call your wake-up code in Protected Mode ...

That's why I'm passing physical address of 32-bit code...

or am I supposed to pass 48-bit selector:offset pair? But what GDT
will BIOS use in that case?

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2008-09-17  7:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-04  5:51 [PATCH]: ACPI : Set 32bit and 64bit waking vector in FCAS table Zhao Yakui
2008-09-04  8:10 ` Rafael J. Wysocki
2008-09-04  9:18   ` Zhang Rui
2008-09-04  9:37     ` Rafael J. Wysocki
2008-09-04 12:07       ` Matthew Garrett
2008-09-05  1:17         ` Zhao Yakui
2008-09-05  1:21           ` Li, Shaohua
2008-09-05 10:48             ` Rafael J. Wysocki
2008-09-06 11:13             ` [PATCH] ACPI suspend: Always use the 32-bit waking vector Rafael J. Wysocki
2008-09-14 11:46               ` Pavel Machek
2008-09-14 23:56                 ` Rafael J. Wysocki
2008-09-15  9:50               ` Pavel Machek
2008-09-17  5:46                 ` Rafael J. Wysocki
2008-09-17  7:29                   ` Pavel Machek
2008-09-15 11:18               ` ACPI suspend: test 64-bit waking vector (was Re: [PATCH] ACPI suspend: Always use the 32-bit waking vector) Pavel Machek
2008-09-17  5:45                 ` Rafael J. Wysocki
2008-09-17  7:28                   ` Pavel Machek [this message]
2008-09-17 16:58                     ` Rafael J. Wysocki
2008-09-24  7:17               ` [PATCH] ACPI suspend: Always use the 32-bit waking vector Len Brown
2008-09-04  9:27   ` [PATCH]: ACPI : Set 32bit and 64bit waking vector in FCAS table Zhao Yakui
2008-09-04  9:48     ` Rafael J. Wysocki

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=20080917072858.GA2659@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=andi@firstfloor.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=rjw@sisk.pl \
    --cc=rui.zhang@intel.com \
    --cc=shaohua.li@intel.com \
    --cc=suspend-devel@lists.sourceforge.net \
    --cc=yakui.zhao@intel.com \
    /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