All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Kendall Bennett <KendallB@scitechsoft.com>,
	linux-kernel@vger.kernel.org,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [Linux-fbdev-devel] Re: Generic VESA framebuffer driver and Video card BOOT?
Date: Fri, 22 Oct 2004 01:00:27 +0200	[thread overview]
Message-ID: <20041021230027.GA24762@elf.ucw.cz> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB600328792F@scsmsx403.amr.corp.intel.com>

Hi!

> >The rest of the code you have above seems superfluous to me as we have 
> >never needed to do that. Then again we boot the card using the BIOS 
> >emulator, which is different because it runs within a 
> >protected machine 
> >state.
> >
> >Have you taken a look at the X.org code? They have code in 
> >there to POST 
> >the video card also (either using vm86() or the BIOS emulator).
> >
> 
> I have done some experiments with this video post stuff.
> I think this should be done using x86 emulator rather than doing 
> in real mode. The reason being, with an userlevel emulator we can call
> it at different times during resume. The current real mode videopost
> does 

Actually Ole Rohne has patch that allows you to call real mode any
time you want.
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

  reply	other threads:[~2004-10-21 23:00 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-21 22:28 [Linux-fbdev-devel] Re: Generic VESA framebuffer driver and Video card BOOT? Pallipadi, Venkatesh
2004-10-21 22:28 ` Pallipadi, Venkatesh
2004-10-21 23:00 ` Pavel Machek [this message]
2004-10-22 17:10 ` Kendall Bennett
2004-10-22 17:10   ` [Linux-fbdev-devel] " Kendall Bennett
  -- strict thread matches above, loose matches on Subject: below --
2004-10-22 18:04 Pallipadi, Venkatesh
2004-10-22 17:16 Pallipadi, Venkatesh
2004-10-22 16:36 Pallipadi, Venkatesh
2004-10-22 17:19 ` Jon Smirl
2004-10-22 17:31 ` Stefan Dösinger
2004-10-21 23:44 Pallipadi, Venkatesh
2004-10-21 23:44 ` Pallipadi, Venkatesh
2004-10-22  1:39 ` Matthew Garrett
2004-10-22 12:57 ` Stefan Dösinger
2004-10-21 23:10 Pallipadi, Venkatesh
2004-10-21 23:10 ` Pallipadi, Venkatesh
2004-10-21 23:23 ` Pavel Machek
2004-10-14 19:02 Kendall Bennett
2004-10-15 18:36 ` Kendall Bennett
2004-10-15 21:51   ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-10-15 21:51     ` Antonino A. Daplas
2004-10-15 22:12   ` Kendall Bennett
2004-10-16  0:41     ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-10-16  0:41       ` Antonino A. Daplas
2004-10-26 11:14       ` Paulo Marques
2004-10-26 11:14         ` Paulo Marques
2004-10-27  1:58         ` Kendall Bennett
2004-10-27 11:11           ` Paulo Marques
2004-10-27 19:52             ` Kendall Bennett
2004-10-27 19:52               ` Kendall Bennett
2004-10-16 17:44 ` Jon Smirl
2004-10-18 19:34   ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-19 21:11 ` Pavel Machek
2004-10-20 17:01   ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-20 17:31     ` Pavel Machek
2004-10-20 18:44       ` Kendall Bennett
2004-10-20 19:10         ` Pavel Machek
2004-10-21 19:36           ` Kendall Bennett
2004-10-21 20:47             ` Richard Smith

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=20041021230027.GA24762@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=KendallB@scitechsoft.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.