public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "D. Stimits" <stimits@idcomm.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org
Subject: Re: For comment: draft BIOS use document for the kernel
Date: Sat, 23 Jun 2001 19:41:50 -0600	[thread overview]
Message-ID: <3B35455E.5EF33B04@idcomm.com> (raw)
In-Reply-To: <E15DTfd-0003gI-00@the-village.bc.nu>

Alan Cox wrote:
> 
> Linux 2.4 BIOS usage reference
> 
> Boot Sequence
> -------------
> 
> Linux is normally loaded either directly as a bootable floppy image or from
> hard disk via a boot loader called lilo. The kernel image is transferred
> into low memory and a parameter block above it.
> 
> When booting from floppy disk the BIOS disk parameter tables are replaced
> by a new table set up to allow a maximum sector count of 36 (the track size
> for a 2.88Mb ED floppy)
> 
> int 0x13, AH=0x02 is issued to to probe and find the disk geometry.
> int 0x13, AH=0x00 is used to reset the floppy controller.
> int 0x13, AH=0x02 is then issued repeatedly to load tracks of data. The
>         boot loader ensures no issued requests cross the track boundaries
> 
> int 0x10 service 3 is used during the boot loading sequence to obtain the
> cursor position. int 0x10 service 13 is used to display loading messages
> as the loading procedure continues. int 0x10 AH=0xE is used to display a
> progress bar of '=' characters during the bootstrap
> 
> Control is then transferred to the loaded image whether by the floppy boot
> loader or other services
> 

If it is within the realm of the paper, I'd like to know the differences
when booting from an ATAPI cdrom (or the fact that there is no
difference). Or for SCSI cdrom if relevant or useful to the purposes of
the paper.

D. Stimits, stimits@idcomm.com

  parent reply	other threads:[~2001-06-24  1:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-22 16:20 For comment: draft BIOS use document for the kernel 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 [this message]
2001-06-25 16:28 ` Timur Tabi
  -- strict thread matches above, loose matches on Subject: below --
2001-06-22 17:32 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
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
2001-06-22 17:44 Dunlap, Randy
2001-06-22 17:55 ` Alan Cox
2001-06-22 18:25 Comfort, Dan  W

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=3B35455E.5EF33B04@idcomm.com \
    --to=stimits@idcomm.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