From: David Given <dg@cowlark.com>
To: linux-8086@vger.kernel.org
Subject: Re: Help Wanted!
Date: Tue, 27 Sep 2005 22:48:14 +0100 [thread overview]
Message-ID: <200509272248.17224.dg@cowlark.com> (raw)
In-Reply-To: <015301c5c3a7$761e7730$6402a8c0@dionysus>
[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]
On Tuesday 27 September 2005 22:06, Hans wrote:
[...]
> Why not?
The short answer is because the BIOS is not reentrant, which means it can only
do one thing at a time. Remember the bad old days when accessing the floppy
disk would make the system freeze? That's the BIOS' fault.
Also, the BIOS is *extremely* basic. The BIOS elevator algorithms for MFM hard
disks sucked hugely; I once ran big Linux on a 386 with an MFM drive, and was
amazed at just how much faster Linux' disk access was, simply because it was
scheduling the I/O transfers more efficiently. I'm not even sure the BIOS
does DMA. Remember that the B stands for Basic...
Now, it *might* be possible to multitask during a BIOS call provided only one
task was accessing the BIOS at any time. You still wouldn't be able to, e.g.,
access the hard disk while the floppy drive was in use, but at least the
system shouldn't just freeze.
[...]
> I would forget about ARM since they have a very good uCLinux port and gcc
> support.
Yeah, but uCLinux is still very large compared to an ELKS kernel.
(BTW, someone has told me via email that they have Minix 2 running on a i86
machine, but the TCP/IP stack tends to eat most of the available memory. So
it does actually work.)
--
+- David Given --McQ-+ "Information wants to be free, but my mail client
| dg@cowlark.com | does not want to be chock-full of herbal pot
| (dg@tao-group.com) | alternative spam." --- Sant Lupus on Slashdot
+- www.cowlark.com --+
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-27 21:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-24 5:30 Help Wanted! Miguel Bolanos
2005-09-24 9:35 ` Hans
2005-09-24 19:43 ` Rex Walburn
2005-09-27 18:38 ` Hans
2005-09-27 19:10 ` Isaque Galdino
2005-09-27 20:13 ` David Given
2005-09-27 20:30 ` Dan Olson
2005-09-27 21:06 ` Hans
2005-09-27 21:48 ` David Given [this message]
2005-09-28 2:32 ` Rex Walburn
2005-09-28 12:45 ` Javier Sedano
2005-09-27 19:30 ` Dan Olson
2005-09-28 9:29 ` jb1
2005-09-28 15:30 ` Gregg C Levine
2005-09-29 9:14 ` jb1
2005-09-28 9:51 ` Alexander van Heukelum
-- strict thread matches above, loose matches on Subject: below --
2005-09-28 16:33 hansydelm
2005-09-28 16:48 hansydelm
2006-02-01 22:33 Help Wanted? Cathal Mullaney
2006-02-01 22:57 ` Lee Revell
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=200509272248.17224.dg@cowlark.com \
--to=dg@cowlark.com \
--cc=linux-8086@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.