From: Adam Sulmicki <adam@cfar.umd.edu>
To: Thomas Horsten <thomas@horsten.com>
Cc: Halil Demirezen <nitrium@bilmuh.ege.edu.tr>,
<linux-kernel@vger.kernel.org>
Subject: Re: about bios
Date: Mon, 5 May 2003 19:52:26 -0400 (EDT) [thread overview]
Message-ID: <20030505193733.T76699-100000@www.missl.cs.umd.edu> (raw)
In-Reply-To: <Pine.LNX.4.40.0305060101350.7106-100000@jehova.dsm.dk>
> This is why, even though Linux does not use the BIOS at any point after
> booting, some chipset setup code is still required and therefore you
> can't just burn a Linux kernel into flash and start it directly (there
> is a project called LinuxBIOS that was working on a replacement BIOS for
> some common chipsets, intended for embedded systems).
'was working'? The project is alive and well.
It is much more than just embedded systems. In fact with recent addition
of legacy bios support we are able to boot other operating systems (BSD,
Win, etc). Being able to boot Windows provides easy migration patch to
Linux :-)
By the way. Yes you can burn the linux kernel into flash (together with
linuxBIOS) and boot it this way. But given that many motherboards limit
your flash size to 256KiB you probably want to put the kernel on the
CompactFlash over ide nevertheless. Interestingly enough if not this size
limit we might have ended up using Linux Kernel as hardware initalizator
to some degree.
<shameless plug>
In fact we are presenting a paper on LinuxBIOS booting other operating
systems this summer during Usenix 03.
</shameless plug>
Adam
--
Adam Sulmicki
http://www.eax.com The Supreme Headquarters of the 32 bit registers
next prev parent reply other threads:[~2003-05-05 23:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 22:50 about bios Halil Demirezen
2003-05-05 22:45 ` Thomas Horsten
2003-05-05 23:04 ` Halil Demirezen
2003-05-05 23:08 ` Thomas Horsten
2003-05-05 23:52 ` Adam Sulmicki [this message]
2003-05-06 8:03 ` Thomas Horsten
2003-05-06 10:06 ` Eric W. Biederman
2003-05-06 12:28 ` Mr. James W. Laferriere
2003-06-18 14:43 ` Adam Sulmicki
2003-06-18 15:18 ` Mr. James W. Laferriere
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=20030505193733.T76699-100000@www.missl.cs.umd.edu \
--to=adam@cfar.umd.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=nitrium@bilmuh.ege.edu.tr \
--cc=thomas@horsten.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 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).