Re: vesafb

["Jan Beulich" <jbeulich@novell.com>]

>>> Keir Fraser <Keir.Fraser@cl.cam.ac.uk> 08.05.07 09:40 >>>
>On 8/5/07 08:22, "Jan Beulich" <jbeulich@novell.com> wrote:
>
>>> I think we want to parse the dom0 kernel's command line looking for a
>>> 'vga=' parameter, and if present, setup the appropriate vesa mode just
>>> before un-pausing the newly created dom0.
>> 
>> So you want the same counter intuitive mechanism that native Linux uses
>> (in that GrUB parses the kernel command line), rather than having the
>> command line option apply directly to Xen (i.e. vesa=), leaving unhandled
>> any non-Linux OSes possibly usable as dom0?
>
>Er, what?
>
>GRUB only parses 'vga=' for Linux images. It doesn't do so for multiboot
>images. And, even if it did, what does that have to do with non-Linux dom0
>OSes?

Exactly, and Ian intends to do the same thing (i.e. parse the Linux-dom0
command line). This is what I consider counter-intuitive - Xen should only
care about its own command line (unless absolutely needed to make
assumptions about dom0's), and GrUB really shouldn't look at Linux'
command line either.

>The reason we plan to use Linux-style 'vga=' is because we can leverage the
>fact that people have already learned the hex mode numbers they care about
>from using native Linux. Actually I will probably go for 'vga=vesa-<mode>'.

Yes, that would have been my second favorite.

Jan