From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Dqls9-00080Y-GD for mharc-grub-devel@gnu.org; Fri, 08 Jul 2005 01:58:02 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Dqlrt-0007xl-Se for grub-devel@gnu.org; Fri, 08 Jul 2005 01:57:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Dqlrh-0007td-FL for grub-devel@gnu.org; Fri, 08 Jul 2005 01:57:44 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dqlrf-0007jS-T4 for grub-devel@gnu.org; Fri, 08 Jul 2005 01:57:31 -0400 Received: from [212.43.237.68] (helo=kotoba.storever.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Dqlb1-0003T0-1d for grub-devel@gnu.org; Fri, 08 Jul 2005 01:40:19 -0400 Received: from ASSP-nospam (localhost [127.0.0.1]) by kotoba.storever.com (Postfix) with ESMTP id 362CEFF31FAE for ; Fri, 8 Jul 2005 07:33:27 +0200 (CEST) Received: from 127.0.0.1 ([127.0.0.1] helo=ip6-localhost) by ASSP-nospam ; 8 Jul 05 05:33:26 -0000 From: "Yoshinori K. Okuji" Organization: enbug.org To: The development of GRUB 2 Date: Fri, 8 Jul 2005 07:33:16 +0200 User-Agent: KMail/1.7.2 References: <42CBEB1C.4030609@nic.fi> In-Reply-To: <42CBEB1C.4030609@nic.fi> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200507080733.16262.okuji@enbug.org> Subject: Re: Some issues with VBE support. 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, 08 Jul 2005 05:57:48 -0000 On Wednesday 06 July 2005 16:30, Vesa J=E4=E4skel=E4inen wrote: > Otherwise I have already implemented all needed real mode stubs to call > VBE. I implemented these to kern/i386/pc/startup.S as there were > existing helpers for VGA. That's good. > Can GRUB_MEMORY_MACHINE_SCRATCH_ADDR be used freely on this context? I > need to some low memory addresses to get information from VBE. For now I > have used this and it seems to work correctly, but there could be some > issues that I don't see now? The scratch memory is meant to be used for any temporary region which must= =20 reside at lower memory, in particular by BI0S calls. So, if you don't need = to=20 make the information persistent, it is the right way to use the scratch=20 memory for this. Okuji