From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jozef Vesely <vesely@gjh.sk>
Cc: Jakub Vana <gugux@centrum.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: x86 - Realmode BIOS and Code calling module
Date: Mon, 06 Sep 2004 18:03:08 +0100 [thread overview]
Message-ID: <1094490175.4309.10.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0409061703510.31771-100000@eloth.gjh.sk>
On Llu, 2004-09-06 at 16:27, Jozef Vesely wrote:
> In-kernel BIOS calls are useful:
> I (and many others) have experienced problems with resuming from ACPI S3
> state. Some graphic cards need to have their state saved before suspend
> and restored after resume, otherwise the screen stays blank. VESA BIOS
> call 0x4f04, does exactly that.
As I understand it VESA 0x4F04 is for saving/restoring mode state, not
restoring the video card from poweroff. Correct me if I'm wrong here.
Secondly if you wanted to do this cleanly you could still do the save
from vm86 in user space and the restore on the 16bit return path having
checked a save was made and that the video bios hasn't gone for a walk.
next prev parent reply other threads:[~2004-09-06 18:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 9:36 x86 - Realmode BIOS and Code calling module Jakub Vana
2004-08-12 11:56 ` Alan Cox
2004-09-06 15:27 ` Jozef Vesely
2004-09-06 17:03 ` Alan Cox [this message]
2004-08-12 12:39 ` Grzegorz Kulewski
2004-08-12 12:50 ` Vojtech Pavlik
2004-08-16 7:49 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2004-08-12 13:38 Jakub Vana
2004-08-12 20:30 ` Alan Cox
2004-08-13 7:44 ` Vojtech Pavlik
2004-08-13 14:36 Jakub Vana
2004-08-13 21:54 ` Alan Cox
2004-08-14 20:10 Jakub Vana
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=1094490175.4309.10.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=gugux@centrum.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=vesely@gjh.sk \
/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