From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MaWmd-0007Ut-8G for mharc-grub-devel@gnu.org; Mon, 10 Aug 2009 11:27:35 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaWma-0007Th-Jg for grub-devel@gnu.org; Mon, 10 Aug 2009 11:27:32 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaWmW-0007Px-3v for grub-devel@gnu.org; Mon, 10 Aug 2009 11:27:32 -0400 Received: from [199.232.76.173] (port=52147 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaWmV-0007Po-OQ for grub-devel@gnu.org; Mon, 10 Aug 2009 11:27:27 -0400 Received: from xvm-190-8.ghst.net ([217.70.190.8]:43025 helo=aybabtu.com) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MaWmV-0000dh-Ai for grub-devel@gnu.org; Mon, 10 Aug 2009 11:27:27 -0400 Received: from [192.168.10.10] (helo=thorin) by aybabtu.com with esmtp (Exim 4.69) (envelope-from ) id 1MaWmT-0003YB-P5 for grub-devel@gnu.org; Mon, 10 Aug 2009 17:27:26 +0200 Received: from rmh by thorin with local (Exim 4.69) (envelope-from ) id 1MaWmT-0002yH-6a for grub-devel@gnu.org; Mon, 10 Aug 2009 17:27:25 +0200 Date: Mon, 10 Aug 2009 17:27:25 +0200 From: Robert Millan To: The development of GRUB 2 Message-ID: <20090810152725.GC11134@thorin> References: <20090810110102.GP11691@riva.ucam.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: free as in freedom X-Message-Flag: Worried about Outlook viruses? Switch to Thunderbird! www.mozilla.com/thunderbird X-Debbugs-No-Ack: true User-Agent: Mutt/1.5.18 (2008-05-17) 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, 10 Aug 2009 15:27:32 -0000 On Mon, Aug 10, 2009 at 02:05:15PM +0200, Vladimir 'phcoder' Serbinenko wrote: > What is the linux behaviour with 0x0F04? Does it just keep the mode? > What if the same mode is passed as a value? Does linux redoes the > modesetting? If 0x0F04 works ok I would prefer to always pass it when > kernel is booted in graphical mode. VESA mode numbers are an artifact > and when grub2 has its own graphical drivers it won't correspond to > anything. I might be missing something, but AFAICT VESA mode numbers are only passed by the user in the "vga=" option. There's also the `vid_mode' parameter in Linux header, but it's only used by legacy code, and with the 32-bit boot protocol Linux doesn't read it. Does 0x0F04 really do something when used in combination with Linux' vesafb? -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all."