[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



>>> Gerd Knorr <kraxel@xxxxxxx> 05.07.05 15:42:50 >>>
>On Tue, Jul 05, 2005 at 02:28:27PM +0100, Keir Fraser wrote:
>> 
>> On 5 Jul 2005, at 14:22, Jan Beulich wrote:
>> 
>> >>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.
>
>Well, I'd simply leave that job completely to grub as it has to
>deal with that anyway and the multiboot spec have fields to pass
>on that info to the booted kernel.  Xen would simply take that
>and pass it on to the Dom0 kernel, thats it.  And maybe adjust
>it's own row/column counts in case it's vga text mode.

I'm not sure I follow here.

First of all, at least grub 0.9x (which is what I think is currently in
wide-spread use) doesn't seem to have even infrastructure to report
video information, not to think about changing the video mode. But I
agree that that'd be the best place for this to live.

Second, simply passing on the multi-boot info to the guest kernel would
still require that the interface between XEN and the guest kernel be
changed. And if a change is required, then passing the information in a
XEN-determined format seems more portable to me, especially if you
expect EFI to be used as boot loader at some point even on x86, because
then the information would perhaps come in yet another format (and
whatever Linux people might think, I believe that elilo shouldn't become
yet another intermediate layer for booting XEN then).

>> >> 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.
>> 
>> If that's the case, I'm sure Gerd can point out the 'moving parts'
that 
>> we actually need to get basic text output working. I was hoping
video.S 
>> alone would be sufficient... :-)
>
>Text mode is really simple, that is just another screen size
>than 80x25, but completely identical otherwise.  Font stuff is
>handled by bios and vga hardware, nothing to worry about here.

That builds on the assumption that the boot loader actually has the
necessary infrastructure. With the assumption that it's quite far away
from that, I would still think that XEN should try provide the ability
to change modes (at least until the boot loader actually does).

>In graphics mode you simply have a linear frame buffer and
>you'll have to do everything yourself.  Linux has compiled-in
>fonts for that.  Quite alot of stuff from drivers/video would
>be needed to get that going in xen, but I wouldn't even try to
>make xen render text in graphics mode and leave that completely
>to the dom0 kernel ...

Once XEN is so stable that you can afford not seeing its initial
messages, leaving the screen alone when in graphics mode is certainly an
option. But I don't think that's an option right now.

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.