From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1E6jdL-0006dQ-5N for mharc-grub-devel@gnu.org; Sun, 21 Aug 2005 02:48:44 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1E6jdE-0006cW-0c for grub-devel@gnu.org; Sun, 21 Aug 2005 02:48:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1E6jd8-0006bV-8M for grub-devel@gnu.org; Sun, 21 Aug 2005 02:48:32 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E6jd4-0006ZZ-OS for grub-devel@gnu.org; Sun, 21 Aug 2005 02:48:28 -0400 Received: from [212.43.237.68] (helo=kotoba.storever.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1E6jYx-0001Os-LS for grub-devel@gnu.org; Sun, 21 Aug 2005 02:44:11 -0400 Received: from ASSP-nospam (localhost [127.0.0.1]) by kotoba.storever.com (Postfix) with ESMTP id 46642FF78295 for ; Sun, 21 Aug 2005 08:43:51 +0200 (CEST) Received: from 127.0.0.1 ([127.0.0.1] helo=ip6-localhost) by ASSP-nospam ; 21 Aug 05 06:43:51 -0000 From: "Yoshinori K. Okuji" Organization: enbug.org To: The development of GRUB 2 Date: Sun, 21 Aug 2005 08:42:29 +0200 User-Agent: KMail/1.7.2 References: <20050820232532.78284.qmail@web35304.mail.mud.yahoo.com> In-Reply-To: <20050820232532.78284.qmail@web35304.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508210842.30398.okuji@enbug.org> Subject: Re: x86_64 imporatant information 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: Sun, 21 Aug 2005 06:48:39 -0000 On Sunday 21 August 2005 01:25, Ruslan Nikolaev wrote: > I think it's just because we need to use special memory model > "-mcmodel=kernel" that's designed especially for kernel. Does we have > problems when LMA != VMA and using this memory model? I can't find such > information... You have already gotten the answer by yourself. You should specify a different address for LMA. This is called "physical address" in ELF. Okuji