All of lore.kernel.org
 help / color / mirror / Atom feed
From: guorke <gourke@gmail.com>
To: linux-os@analogic.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: mabye simple,but i confused
Date: Mon, 20 Jun 2005 09:55:29 +0800	[thread overview]
Message-ID: <d73ab4d0050619185556d25234@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0506160819350.29979@chaos.analogic.com>

Thanks,I must read it carefully

On 6/16/05, Richard B. Johnson <linux-os@analogic.com> wrote:
> On Thu, 16 Jun 2005, guorke wrote:
> 
> > in understangding the linux kernel, the authors says
> > "..Moves itself from address 0x00007c00 to address 0x00090000.."
> >
> > What i confused is why the Boot Loader do this, i asked google,but
> > still no answe.
> > who can make me understand it ?
> > Thanks.
> 
> The IBM 'IPL' (initial program load) address was specified to be
> at 7c00. There was room here for only one "sector", which in the
> early days was 512 bytes. The very first sector, the boot sector,
> was loaded into this address and then execution was started at
> a specified offset so that this boot code could load the rest
> of the operating system. To load the rest of the operating system,
> one needs to move the boot-code to somewhere it won't get
> overwritten by subsequent reads from the disk.
> 
> To load Linux, the boot developers wanted to load code 64k at
> a time. The only address in real-mode, that was guaranteed to
> not be in use, where the boot code could load a whole 64k was
> at 90000 hex. This provides a buffer from which the boot-loader
> can copy 64k at a time into the protected-mode address space
> starting at 0x00100000. The boot-loader uses real-mode BIOS
> services to copy the code to the 1 megabyte address which can't
> be reached in real mode.
> 
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.6.11.9 on an i686 machine (5537.79 BogoMips).
>  Notice : All mail here is now cached for review by Dictator Bush.
>                  98.36% of all statistics are fiction.
>

  reply	other threads:[~2005-06-20  1:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16  5:25 mabye simple,but i confused guorke
2005-06-16  7:54 ` DervishD
2005-06-16  8:55   ` guorke
2005-06-16 12:31 ` Richard B. Johnson
2005-06-20  1:55   ` guorke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-20 18:53 Nick Warne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d73ab4d0050619185556d25234@mail.gmail.com \
    --to=gourke@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.