From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754288Ab2FLVQg (ORCPT ); Tue, 12 Jun 2012 17:16:36 -0400 Received: from terminus.zytor.com ([198.137.202.10]:45940 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752720Ab2FLVQf (ORCPT ); Tue, 12 Jun 2012 17:16:35 -0400 Message-ID: <4FD7B1AB.6030708@zytor.com> Date: Tue, 12 Jun 2012 14:16:27 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: Brandon Falk CC: linux-kernel@vger.kernel.org Subject: Re: [question] x86/x86_64 boot process References: <4FD7AF24.8080607@zytor.com> In-Reply-To: X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/12/2012 02:14 PM, Brandon Falk wrote: > All I really see related to the post-setup stage is: > > 'The 32-bit (non-real-mode) kernel starts at offset (setup_sects+1)*512 > in the kernel file (again, if setup_sects == 0 the real value is 4.) > It should be loaded at address 0x10000 for Image/zImage kernels and > 0x100000 for bzImage kernels.' > > I've read this document a few times, and it doesn't seem to mention if > the kernel assists in loading. Do I have to load up the whole > protected-mode kernel? Just the first few sectors? I guess that's what > I'm trying to figure out, and I feel the boot.txt has not answered > that for me. > I would also strongly discourage you from writing a new bootloader if you can avoid it. You *certainly* want to avoid the use of the fixed 0x90000 address, that is a decade obsolete. -hpa