From: "Jan Beulich" <JBeulich@novell.com>
To: Keir.Fraser@cl.cam.ac.uk
Cc: xen-devel@lists.xensource.com
Subject: Re: beginnings of allowing more than the basic 80x25 VGA screen resolution
Date: Mon, 04 Jul 2005 02:00:29 -0600 [thread overview]
Message-ID: <s2c898b4.074@lucius.provo.novell.com> (raw)
>We could certainly add a way to propagate the mode option through to
>the vga driver, but is the Linux vga driver really unable to switch
>modes without bios help? Is there support for a protected-mode
vesa/vbe
>driver instead?
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
interface doesn't cover the mode switching functions as far as I
remember). Only the video board specific frame buffer drivers are able
to switch modes, and the bad thing (for me personally) is that even in
2.6.12 there still is no (64-bit) support for the i915 chipset. So I
continue to be required to live with the video mode that XEN 'sets'
prior to loading dom0, and short of it supporting a VESA console my
first minimal attempt was to at least increase (and propagate) the size
to the maximum possible without significant changes.
Jan
next reply other threads:[~2005-07-04 8:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-04 8:00 Jan Beulich [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-04 8:35 beginnings of allowing more than the basic 80x25 VGA screen resolution Jan Beulich
[not found] <s2c898b4.073@lucius.provo.novell.com>
2005-07-04 8:14 ` Keir Fraser
2005-07-04 8:51 ` Gerd Knorr
2005-07-06 21:37 ` Matthias Huber
[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=s2c898b4.074@lucius.provo.novell.com \
--to=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.