From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: vesafb Date: Tue, 08 May 2007 08:50:55 +0100 Message-ID: <464047FF.76E4.0078.0@novell.com> References: <46404167.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: ron minnich , Ian Pratt , xen-devel@lists.xensource.com, Jayant Mangalampalli List-Id: xen-devel@lists.xenproject.org >>> Keir Fraser 08.05.07 09:40 >>> >On 8/5/07 08:22, "Jan Beulich" wrote: > >>> I think we want to parse the dom0 kernel's command line looking for a >>> 'vga=3D' parameter, and if present, setup the appropriate vesa mode = just >>> before un-pausing the newly created dom0. >>=20 >> 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=3D), leaving = unhandled >> any non-Linux OSes possibly usable as dom0? > >Er, what? > >GRUB only parses 'vga=3D' 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=3D' 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=3Dvesa-'. Yes, that would have been my second favorite. Jan