linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: DervishD <lkml@dervishd.net>
To: guorke <gourke@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mabye simple,but i confused
Date: Thu, 16 Jun 2005 09:54:00 +0200	[thread overview]
Message-ID: <20050616075400.GB57@DervishD> (raw)
In-Reply-To: <d73ab4d005061522254f2e5933@mail.gmail.com>

 * guorke <gourke@gmail.com> dixit:
> 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 ?

    Well, let's start with the Master Boot Record. In PC's the BIOS
loads the MBR at address 0x7c00, but the MBR is responsible for
loading the OS bootsector, if any. And the bootsectors are written
assuming that they're loaded by a MBR or *by the BIOS itself* so the
address they assume is 0x7c00. But the MBR is already at that
address! What can it do? Well, it moves itself out of the place.

    The problem is that the kernel itself could be loaded directly by
the BIOS (a long time ago, it was possible to boot from a raw floppy
containing an image of the kernel), and the first sector would be
loaded at 0x7c00, so the bootsector, MBR, loader or whatever has to
move out of that address at the very beginning. Why the physical
address 0x00090000 was used? I don't know. Well, it's well at the top
of the 640k base memory and the segment starts with 1001 in binary,
which is a fancy number XDD

    Hope that helps.

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
http://www.pleyades.net & http://www.gotesdelluna.net
It's my PC and I'll cry if I want to...

  reply	other threads:[~2005-06-16  7:51 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 [this message]
2005-06-16  8:55   ` guorke
2005-06-16 12:31 ` Richard B. Johnson
2005-06-20  1:55   ` guorke
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=20050616075400.GB57@DervishD \
    --to=lkml@dervishd.net \
    --cc=gourke@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).