public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: "Emmanuel Thomé" <Emmanuel.Thome-MZpvjPyXg2s@public.gmane.org>,
	ole.rohne-vJEk5272eHo@public.gmane.org,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: s3_late_bios
Date: Mon, 08 Nov 2004 13:53:25 -0800	[thread overview]
Message-ID: <418FEAD5.1000007@root.org> (raw)
In-Reply-To: <20041108213558.GB4607-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>

Pavel Machek wrote:
>>Sorry I've been off for a week. Here is the version of the s3_late_bios
>>patch with the segment info coded in C.
>>
>>If somebody comes up with an attempt at resuming the video from the early
>>real mode phase by calling the pci bios, I'm all for testing it.
> 
> It looks good to me...

I'm not sure I understand the reason for this or how it works.  Does it 
POST VGA via the "lcall $0xc000,$3" or the "int 10h" method?  I assume 
the reason it's called by the PCI code is that you want the device to be 
set to D0 and device-specific resume methods called before POSTing it?
Why the switch to real mode to run the BIOS call?  Can't this be done 
from vm86 mode?

-- 
Nate


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

  parent reply	other threads:[~2004-11-08 21:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 14:49 s3_late_bios Emmanuel Thomé
     [not found] ` <20041108144947.GA31267-xkTd+U360DcAs8EywTwl9A@public.gmane.org>
2004-11-08 21:35   ` s3_late_bios Pavel Machek
     [not found]     ` <20041108213558.GB4607-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-11-08 21:53       ` Nate Lawson [this message]
     [not found]         ` <418FEAD5.1000007-Y6VGUYTwhu0@public.gmane.org>
2004-11-09 12:55           ` s3_late_bios Emmanuel Thomé
     [not found]             ` <20041109125522.GA8015-xkTd+U360DcAs8EywTwl9A@public.gmane.org>
2004-11-09 20:26               ` Nate Lawson
     [not found]                 ` <419127E6.3000603-Y6VGUYTwhu0@public.gmane.org>
2004-11-09 20:43                   ` Matthew Garrett
2004-11-10  7:20                   ` Emmanuel Thomé
     [not found]                     ` <20041110072003.GA13561-xkTd+U360DcAs8EywTwl9A@public.gmane.org>
2004-11-10 11:56                       ` Matthew Garrett
2004-11-10 14:11                         ` s3_late_bios ole.rohne-vJEk5272eHo
2004-11-10 16:25                         ` s3_late_bios Nate Lawson
2004-11-10 13:16                 ` s3_late_bios ole.rohne-vJEk5272eHo
2004-11-08 23:09   ` s3_late_bios Greg
     [not found]     ` <3195717504110815096a527710-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2004-11-09 12:56       ` s3_late_bios Emmanuel Thomé

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=418FEAD5.1000007@root.org \
    --to=nate-y6vguytwhu0@public.gmane.org \
    --cc=Emmanuel.Thome-MZpvjPyXg2s@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ole.rohne-vJEk5272eHo@public.gmane.org \
    --cc=pavel-+ZI9xUNit7I@public.gmane.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