From: Gerd Knorr <kraxel@suse.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Jan Beulich <JBeulich@novell.com>
Subject: Re: beginnings of allowing more than the basic 80x25 VGA screen resolution
Date: 04 Jul 2005 10:51:11 +0200 [thread overview]
Message-ID: <87k6k7q7i8.fsf@bytesex.org> (raw)
In-Reply-To: <315a6c1b10ddfeec1deb95372aaad890@cl.cam.ac.uk>
Keir Fraser <Keir.Fraser@cl.cam.ac.uk> writes:
> > As far as I know, not only the VGA driver does not do any mode
> > switching, even the VESA one doesn't (because the protected mode
Exactly. A simple way to get more screen lines is to load a 8x8
screen font though.
> real-mode assembly file. Any video card we care about these days
> should support VBE 2.0/3.0 I think, and those interfaces don;t require
> you to be runnign in real mode.
vbe 2.0 yes, not sure about 3.0.
For mode switching from protected mode you need 3.0 though, 2.0
protected mode support is _very_ limited (you can do panning and
palette register programming, but no mode switching). And I think
even for vbe 3.0 you need some real mode code to figure the protected
mode entry point, so paravirtual linux wouldn't be able to do that
without help from xen.
Gerd
--
panic("it works"); /* avoid being flooded with debug messages */
next prev parent reply other threads:[~2005-07-04 8:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s2c898b4.073@lucius.provo.novell.com>
2005-07-04 8:14 ` beginnings of allowing more than the basic 80x25 VGA screen resolution Keir Fraser
2005-07-04 8:51 ` Gerd Knorr [this message]
2005-07-06 21:37 ` Matthias Huber
2005-07-07 7:59 ` Gerd Knorr
2005-07-04 8:35 Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2005-07-04 8:00 Jan Beulich
[not found] <s2c890b4.055@lucius.provo.novell.com>
2005-07-04 7:50 ` Keir Fraser
2005-07-04 7:28 Jan Beulich
2005-07-01 15:48 Jan Beulich
2005-07-01 15:52 ` Jon Smirl
2005-07-01 16:02 ` Keir Fraser
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=87k6k7q7i8.fsf@bytesex.org \
--to=kraxel@suse.de \
--cc=JBeulich@novell.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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.