From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1GpEwt-0004ne-Tz for mharc-grub-devel@gnu.org; Tue, 28 Nov 2006 21:13:23 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GpEwr-0004kU-Iw for grub-devel@gnu.org; Tue, 28 Nov 2006 21:13:21 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GpEwq-0004kI-RH for grub-devel@gnu.org; Tue, 28 Nov 2006 21:13:21 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GpEwq-0004kE-MN for grub-devel@gnu.org; Tue, 28 Nov 2006 21:13:20 -0500 Received: from [192.55.52.88] (helo=mga01.intel.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GpEwq-0000Qe-D5 for grub-devel@gnu.org; Tue, 28 Nov 2006 21:13:20 -0500 Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by mga01.intel.com with ESMTP; 28 Nov 2006 18:13:19 -0800 Received: from bmao-mobl.ccr.corp.intel.com (HELO [10.239.36.173]) ([10.239.36.173]) by fmsmga001.fm.intel.com with ESMTP; 28 Nov 2006 18:13:18 -0800 X-ExtLoop1: 1 X-IronPort-AV: i="4.09,473,1157353200"; d="scan'208"; a="170287451:sNHT19900916" Message-ID: <456CECBD.80509@intel.com> Date: Wed, 29 Nov 2006 10:13:17 +0800 From: "bibo,mao" User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: The development of GRUB 2 References: <200611281235.48809.okuji@enbug.org> <456C2F8C.1040709@intel.com> <87bqmrgkyu.fsf@night.trouble.net> In-Reply-To: <87bqmrgkyu.fsf@night.trouble.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: multiboot2: variable data size 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: Wed, 29 Nov 2006 02:13:21 -0000 Johan Rydberg wrote: > "bibo,mao" writes: > > > If kernel image is bzImage, x64 efi bootloader need switch to 32 bit > > protect mode(or real mode) from 64 bit long mode, and if kernel > > image is gzipped/plain format, efi bootloader can directly jump to > > 64-bit kernel entry address without mode switch. > > My opinion is that bzImages should be avoided on EFI platforms, or the > decompress-code in Linux has to be rewritten. bzImage supporting mainly is to be compliant with legacy bios, user need not care for detailed bootloader procedure, user always installs linux kernel with command "make install" which will generate bzImage format. Now on some platform there are two kinds of bios: efi bios and legacy bios, if bzImage is supported then one kernel image can run two kinds of bios. > > It took me a good couple of hours of debugging to find out that Linux > simply ignores the memory layout and assumes that low memory is free > to use as it likes. current decompress-code with bzImage possibly touches low memory at 0x1000--0x9000, or decompress-code needs to be rewritten, or put mode switching code below 0x1000. thanks bibo,mao > > ~j > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/grub-devel