public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hans" <hans64@ht-lab.com>
To: linux-8086@vger.kernel.org
Subject: Re: Help Wanted!
Date: Tue, 27 Sep 2005 22:06:24 +0100	[thread overview]
Message-ID: <015301c5c3a7$761e7730$6402a8c0@dionysus> (raw)
In-Reply-To: 200509272113.54472.dg@cowlark.com

>(DOS gets away with it because, basically, DOS is crap. It relies on the 
>BIOS
>to do a lot of the work, which ELKS can't really do.

Why not?

I actually like the BIOS :-)  since it is the BIOS which enables me to write 
a debug style monitor which runs on my FPGA board and with very minor 
modifications on my 64bits desktop. I actually believe that the success of 
ELKS relies on the definition of an easy to port BIOS/HAL layer. I would 
even suggest that we define a standard set of BIOS calls.  If your processor 
doesn't support software interrupt then perhaps a CALL instruction would 
work?

>Can ELKS be ported to *other* architectures that i86? Would it be feasible 
>to
>use it on a modern, flat architecture like ARM?

I assume with flat you are referring to a segment/offset style of 
architecture, I haven't check the ELKS code in any detail but I assume this 
issue can easily be resolved?

I would forget about ARM since they have a very good uCLinux port and gcc 
support.

Regards,
Hans
www.ht-lab.com




-- 
+- David Given --McQ-+ "Hydrogen fusion, the sun makes shine
|  dg@cowlark.com    | Vascular pressure makes the ivy twine.
| (dg@tao-group.com) | Because of Rayleigh, the sky's so blue.
+- www.cowlark.com --+ Hormonal fixation is why I love you." --- Zarf
----- Original Message ----- 
From: "David Given" <dg@cowlark.com>
To: <linux-8086@vger.kernel.org>
Sent: Tuesday, September 27, 2005 9:13 PM
Subject: Re: Help Wanted!



  parent reply	other threads:[~2005-09-27 21:06 UTC|newest]

Thread overview: 18+ 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 [this message]
2005-09-27 21:48             ` David Given
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

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='015301c5c3a7$761e7730$6402a8c0@dionysus' \
    --to=hans64@ht-lab.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox