From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MfcYr-0007sY-Cw for mharc-grub-devel@gnu.org; Mon, 24 Aug 2009 12:38:25 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MfcYp-0007q3-Ml for grub-devel@gnu.org; Mon, 24 Aug 2009 12:38:23 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MfcYl-0007jr-RM for grub-devel@gnu.org; Mon, 24 Aug 2009 12:38:23 -0400 Received: from [199.232.76.173] (port=56073 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MfcYl-0007jj-LT for grub-devel@gnu.org; Mon, 24 Aug 2009 12:38:19 -0400 Received: from smarthost01.mail.zen.net.uk ([212.23.3.140]:46041) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MfcYl-0001bz-7W for grub-devel@gnu.org; Mon, 24 Aug 2009 12:38:19 -0400 Received: from [82.69.40.219] (helo=riva.pelham.vpn.ucam.org) by smarthost01.mail.zen.net.uk with esmtp (Exim 4.63) (envelope-from ) id 1MfcYk-0004Ew-42 for grub-devel@gnu.org; Mon, 24 Aug 2009 16:38:18 +0000 Received: from cjwatson by riva.pelham.vpn.ucam.org with local (Exim 3.36 #1 (Debian)) for grub-devel@gnu.org id 1MfcYj-0007ve-00; Mon, 24 Aug 2009 17:38:17 +0100 Date: Mon, 24 Aug 2009 17:38:17 +0100 From: Colin Watson To: The development of GRUB 2 Message-ID: <20090824163817.GI11691@riva.ucam.org> Mail-Followup-To: The development of GRUB 2 References: <20090810110102.GP11691@riva.ucam.org> <20090810114940.GI9344@thorin> <20090810115835.GU11691@riva.ucam.org> <20090810151541.GB11134@thorin> <20090810154933.GA11691@riva.ucam.org> <20090810164117.GC11691@riva.ucam.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-Originating-Smarthost01-IP: [82.69.40.219] X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Subject: Re: [PATCH] Improve handling of "keep" in gfxpayload 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: Mon, 24 Aug 2009 16:38:24 -0000 On Mon, Aug 24, 2009 at 04:26:09PM +0200, Vladimir 'phcoder' Serbinenko wrote: > On Mon, Aug 10, 2009 at 6:41 PM, Colin Watson wrote: > > On Mon, Aug 10, 2009 at 06:27:04PM +0200, Vladimir 'phcoder' Serbinenko wrote: > >> Framebuffer console works just fine with no KMS if video mode is > >> already set and video parameters passed. At least technically. > > > > Feel free to show me what I'm doing wrong, but it demonstrably does not > > work right now and right here, and Matthew Garrett (whose opinion I > > value very highly when it comes to kernelspace) says that the code > > necessary to make this work does not exist in Linux right now. > > AFAIK efifb does exactly that. Try adding efifb keyword to linux command line. Right, that's fine once the kernel has woken up to some extent, but it doesn't load in early boot when it can be important to be able to see output (drivers only get initialised once the kernel gets up far enough to call driver_init) and it doesn't address the problem of automatically unloading the boot console driver later to put a better framebuffer in place once the kernel has scanned the PCI bus and so on. Besides, hardcoding the framebuffer module to load in grub.cfg would be bad. Yes, there are various ways in which this can be hacked up for a given environment, as long as you don't mind some warts. However, making it work with no user configuration (as it does right now, aside from the multiple video mode transitions, if GRUB doesn't do anything special) really does need actual kernel work. Look at where CONFIG_VGA_CONSOLE is handled in arch/x86/kernel/setup.c for an example of the sort of thing I mean. -- Colin Watson [cjwatson@ubuntu.com]