From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HmWmw-0001VL-DF for mharc-grub-devel@gnu.org; Fri, 11 May 2007 11:12:10 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HmWmt-0001TR-Kd for grub-devel@gnu.org; Fri, 11 May 2007 11:12:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HmWms-0001TE-68 for grub-devel@gnu.org; Fri, 11 May 2007 11:12:06 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HmWmr-0001TB-Sk for grub-devel@gnu.org; Fri, 11 May 2007 11:12:05 -0400 Received: from pne-smtpout3-sn1.fre.skanova.net ([81.228.11.120]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HmWfQ-0004BD-DX for grub-devel@gnu.org; Fri, 11 May 2007 11:04:24 -0400 Received: from [127.0.0.1] (88.193.32.97) by pne-smtpout3-sn1.fre.skanova.net (7.2.075) id 463F1A9800043742 for grub-devel@gnu.org; Fri, 11 May 2007 17:04:20 +0200 Message-ID: <464485FB.2090406@nic.fi> Date: Fri, 11 May 2007 18:04:27 +0300 From: =?ISO-8859-1?Q?Vesa_J=E4=E4skel=E4inen?= User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: The development of GRUB 2 References: <20070511155339.85f69598.jonny@csc.jp> <87ps578rug.fsf@lab.ossystems.com.br> <20070511140734.GD3625@aragorn> In-Reply-To: <20070511140734.GD3625@aragorn> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-detected-kernel: Solaris 8 (1) Subject: Re: gfxterm and vesa X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2007 15:12:07 -0000 Robert Millan wrote: > On Fri, May 11, 2007 at 09:31:03AM -0300, Otavio Salvador wrote: >> Jonny writes: >> >>> Robert Millan write: >>> >>>> Can you try 800x600x32 and 640x480x8 ? >>> Since my machine is't supporting a 32-bit color, 800x600x32 can't be used. If >>> it's 800x600x24, it works well. >> Ah nice. Robert, I think we might reduce the color depth used by >> default. We might even use 16 instead of 24 IMHO. What do you think? > > Not sure.. does 16 work on all machines? What about old PCs that don't > support VESA at all? I think we should have some way to probe all this > stuff before enabling gfxterm. > > The X people use discover and xresprobe. Perhaps we could do that too? > > As short term, if you think 640x480x16 is a reasonable default, we could set > that. But since this part of code belongs to upstream, I'd like to see if > they have some comments about it (forwarding). > > GRUB maintainers (specialy daChaac), do you have any comments on this? > Video mode setup function tries to use all available video drivers to initialize video mode. It uses first it founds working. So if someone writes VGA driver then you can add it to queue and if VBE2+ is not available then it would try next driver, in this case it would be VGA driver. You can specify video mode to be 800x600 without color depth so it will use most colorful mode it finds. But if first adapter has 800x600x16 and second would have 800x600x32 then it would take first as there was valid mode. Other option would be to probe for modes and then select one. But this should be in script or in custom module code. Or gfxmode would be extended to allow multiple selections like 1024x768;800x600;640x480. Also there are starting to be lots of wide screen LCD's that should be somehow supported too. I think that Video API do not have any limitation on this regard.