This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] beginnings of allowing more than the basic 80x25 VGAscre

To: <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] beginnings of allowing more than the basic 80x25 VGAscreen resolution
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Tue, 05 Jul 2005 07:22:25 -0600
Cc: xiaofeng.ling@xxxxxxxxx, kraxel@xxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 05 Jul 2005 13:20:41 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>> IIRC there are some fields in the multiboot info header for that
>> 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
>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

Yes that would clearly be necessary, but perhaps a much more
streamlined mechanism would do for XEN.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>