From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: RE: vesafb Date: Tue, 08 May 2007 08:22:47 +0100 Message-ID: <46404167.76E4.0078.0@novell.com> References: <781BBA092A47E64699F1DCD567F4C2013ACD9C@hdb-exch2k3.phoenix.com> <13426df10705071257h69f8fc0exfc51bb67f2d09580@mail.gmail.com> <8A87A9A84C201449A0C56B728ACF491E0BA4A9@liverpoolst.ad.cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <8A87A9A84C201449A0C56B728ACF491E0BA4A9@liverpoolst.ad.cl.cam.ac.uk> 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: Ian Pratt Cc: ron minnich , xen-devel@lists.xensource.com, Jayant Mangalampalli List-Id: xen-devel@lists.xenproject.org >>> "Ian Pratt" 07.05.07 22:14 >>> >> It is pretty easy, I sent sample code to Ian, if somebody can show me >> how they want it to look in Xen, i.e. where the function gets called >> and all that, I guess I can try to put it in -unstable. > >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. 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?=20 Jan