From: "Jan Beulich" <JBeulich@novell.com>
To: Keir.Fraser@cl.cam.ac.uk
Cc: xiaofeng.ling@intel.com, kraxel@suse.de, xen-devel@lists.xensource.com
Subject: Re: beginnings of allowing more than the basic 80x25 VGAscreen resolution
Date: Tue, 05 Jul 2005 07:22:25 -0600 [thread overview]
Message-ID: <s2ca350f.099@lucius.provo.novell.com> (raw)
>> IIRC there are some fields in the multiboot info header for that
kind
>> of stuff, so grub could setup that and pass on the info to xen (and
>> xen in turn to the dom0 kernel?).
>>
>> multiboot kernels are started in 32-bit protected mode by the boot
>> loader, i.e. xen has (unlike linux) no 16-bit startup code. Thus
>> doing 16-bit BIOS calls once xen is running is a bit difficuilt ...
>
>GRUB has code for switching back into real mode to do bios calls. We
>could take that, plus video.S, and put them in Xen. Then add an info
>structure for passing video info up to domain0. It's pretty ugly, but
I
>think there is no nice solution here. Would we also need vesa/vga
>driver code from Linux for setting up font data in some graphics
modes?
Yes that would clearly be necessary, but perhaps a much more
streamlined mechanism would do for XEN.
Jan
next reply other threads:[~2005-07-05 13:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 13:22 Jan Beulich [this message]
[not found] <s2ca4091.019@lucius.provo.novell.com>
2005-07-05 14:47 ` beginnings of allowing more than the basic 80x25 VGAscreen resolution Gerd Knorr
-- strict thread matches above, loose matches on Subject: below --
2005-07-05 14:11 Jan Beulich
[not found] <s2ca350f.097@lucius.provo.novell.com>
2005-07-05 13:28 ` Keir Fraser
2005-07-05 13:42 ` Gerd Knorr
2005-07-05 12:10 Ling, Xiaofeng
2005-07-05 12:58 ` Gerd Knorr
2005-07-05 13:07 ` Keir Fraser
2005-07-05 17:22 ` David Hopwood
2005-07-06 8:40 ` 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=s2ca350f.099@lucius.provo.novell.com \
--to=jbeulich@novell.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=kraxel@suse.de \
--cc=xen-devel@lists.xensource.com \
--cc=xiaofeng.ling@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.