public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Matthew Garrett <mgarrett@chiark.greenend.org.uk>
Cc: Dave Airlie <airlied@linux.ie>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] reset VGA adapters via BIOS on resume... (non-fbdev/con)
Date: Sat, 23 Jul 2005 20:55:37 +0100	[thread overview]
Message-ID: <1122148537.27629.8.camel@localhost.localdomain> (raw)
In-Reply-To: <E1Dw6lc-0007IU-00@chiark.greenend.org.uk>

On Sad, 2005-07-23 at 00:17 +0100, Matthew Garrett wrote:
> Dave Airlie <airlied@linux.ie> wrote:
> 
> > 	At OLS at lot of people were giving out about cards not resuming,
> > so using a patch from Michael Marineau and help from lots of people
> > sitting around in a circle at OLS I've gotten a patch that restores video
> > on my laptop by going into real mode and re-posting the BIOS during
> > resume,
> 
> On laptops, the code at c000:0003 may jump to BIOS code that isn't
> present after system boot. In userspace, this isn't too much of a
> problem - the userspace code tends to just fall over rather than hanging
> the machine. What happens if the kernel hits illegal or inappropriate
> code on resume?

For Intel at least the recommendation is to use the BIOS "save
mode"/"restore mode" interface.


  parent reply	other threads:[~2005-07-23 19:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-22 18:52 [PATCH] reset VGA adapters via BIOS on resume... (non-fbdev/con) Dave Airlie
2005-07-22 23:17 ` Matthew Garrett
2005-07-23  0:31   ` Pavel Machek
2005-07-23  0:36     ` Matthew Garrett
2005-07-23  0:47       ` Pavel Machek
2005-07-23  6:53         ` Stefan Smietanowski
2005-07-24  6:08           ` Keith Owens
2005-07-25  6:39         ` Stefan Seyfried
2005-07-25  7:43           ` Dave Airlie
2005-07-25  7:48             ` Stefan Seyfried
2005-07-23 19:55   ` Alan Cox [this message]
2005-07-23 22:37     ` Dave Airlie

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=1122148537.27629.8.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=airlied@linux.ie \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgarrett@chiark.greenend.org.uk \
    /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