public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: For comment: draft BIOS use document for the kernel
Date: 22 Jun 2001 12:05:08 -0700	[thread overview]
Message-ID: <9h04t4$ap9$1@cesium.transmeta.com> (raw)
In-Reply-To: <E15DV4q-0003qv-00@the-village.bc.nu> <Pine.LNX.3.95.1010622135228.3929C-100000@chaos.analogic.com>

Followup to:  <Pine.LNX.3.95.1010622135228.3929C-100000@chaos.analogic.com>
By author:    "Richard B. Johnson" <root@chaos.analogic.com>
In newsgroup: linux.dev.kernel
>
> On Fri, 22 Jun 2001, Alan Cox wrote:
> 
> > > I could not find any reference to BIOS int 0x15, function 0x87, block-
> > > move, used to copy the kernel to above the 1 megabyte real-mode
> > > boundary. I think this is still used.
> > 
> > I dont think the kernel has ever used it. The path has always been to enter
> > 32bit mode then relocate/uncompress the kernel, then run it
> > 
> 
> Then how does 1.44 megabytes of data from a floppy disk (that won't
> fit below 1 megabyte), that is accessed in real-mode, ever get to
> above 1 megabyte where it can be decompressed?
> 
> I think LILO copies each buffer read from a below 1 Megabyte buffer
> (which is the only place the floppy can put its data via the BIOS),
> to above 1 megabyte using the BIOS block-move function.
> 

This is done by LILO, which isn't part of the kernel.  SYSLINUX, for
example, enters protected mode directly (like the kernel itself does).

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt

  reply	other threads:[~2001-06-22 19:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-22 17:32 For comment: draft BIOS use document for the kernel Schilling, Richard
2001-06-22 17:42 ` Richard B. Johnson
2001-06-22 17:50   ` Alan Cox
2001-06-22 18:01     ` Richard B. Johnson
2001-06-22 19:05       ` H. Peter Anvin [this message]
2001-06-22 21:42       ` Alan Cox
2001-06-30 14:50         ` Pavel Machek
2001-06-22 18:19     ` Brian Gerst
2001-06-22 21:46       ` Alan Cox
2001-06-22 19:24     ` Albert D. Cahalan
2001-06-22 22:09       ` Alan Cox
2001-06-22 17:48 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2001-06-22 18:25 Comfort, Dan  W
2001-06-22 17:44 Dunlap, Randy
2001-06-22 17:55 ` Alan Cox
2001-06-22 16:20 Alan Cox
2001-06-22 15:50 ` Rob Landley
2001-06-22 16:32 ` Timur Tabi
2001-06-22 17:11 ` Brad Pepers
2001-06-30 14:47   ` Pavel Machek
2001-07-08 16:59     ` Brad Pepers
2001-06-23 20:26 ` Eric W. Biederman
2001-06-23 23:58 ` Riley Williams
2001-06-24  1:41 ` D. Stimits
2001-06-25 16:28 ` Timur Tabi

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='9h04t4$ap9$1@cesium.transmeta.com' \
    --to=hpa@zytor.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