mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Lucas Silva" <mrprofetas@yahoo.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BIOS vs Kernel
Date: Mon, 26 Apr 2004 11:56:58 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0404261145210.1494@chaos> (raw)
In-Reply-To: <20040426150524.63980.qmail@web86406.mail.ukl.yahoo.com>

On Mon, 26 Apr 2004, [iso-8859-1] Lucas Silva wrote:

> Before I start working on this I would like to find
> out
> if it is possible or at least useful.
>
> Is it feasible?
> To create a BIOS that would help the kernel  (working
> together).
>
> What if the BIOS booted the PC in protected mode ,
>  enabling the A20 (taking away all that backwards
> support, so on),
>  And then implement a realible interface.
>
> Wouldn't that be faster?
> Would the kernel be able to communicate to it?
>
> Thanks Profetas

The reason why the BIOS boots in 'real' mode is because there
are 'real' mode drivers provided by vendors that are added during
the POST routine. For instance a SCSI boot disk, or a LAN card
used to boot. If I were not for this, you could just boot in
protected-mode.

However, the BIOS does much, much, more than boot the machine!
Modern motherboards are very dumb as soon as the power is
applied. They are literly built by the BIOS. The final construction
(like how pins of electronic blobs are connected and the internal
guts of gate-arrays) is all done by the BIOS. It's not just a
matter of turning on chips like the old IBM manuals show.

So you need the BIOS to build the board. It starts the boot-sequence
in 'real' mode so that's what you have. FYI, the BIOS code has
already transitioned to and from 32-bit linear address space,
probably several times, during the POST routine. It's really
quite trivial. Whether or not the boot-code gets to 32-bit mode
right away or later on in the boot sequence is simply dependent
upon being able to complete the loading of the operating system
from the IPL device.


Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5557.45 BogoMips).
            Note 96.31% of all statistics are fiction.



      parent reply	other threads:[~2004-04-26 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-26 15:05 Lucas Silva
2004-04-26 15:10 ` Norberto Bensa
2004-04-26 15:56 ` Richard B. Johnson [this message]

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=Pine.LNX.4.53.0404261145210.1494@chaos \
    --to=root@chaos.analogic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrprofetas@yahoo.co.uk \
    /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

all inboxes | Powered by JetHome®