From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Hans" Subject: Re: Help Wanted! Date: Tue, 27 Sep 2005 22:06:24 +0100 Message-ID: <015301c5c3a7$761e7730$6402a8c0@dionysus> References: <1127539824.8686.33.camel@selene.hsol.net> <00c201c5c393$36d31860$6402a8c0@dionysus> <1a19a18005092712103c1b1c0c@mail.gmail.com> <200509272113.54472.dg@cowlark.com> Reply-To: "Hans" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: Sender: linux-8086-owner@vger.kernel.org List-Id: Content-Type: text/plain; format="flowed"; charset="us-ascii"; reply-type="original" To: linux-8086@vger.kernel.org >(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" To: Sent: Tuesday, September 27, 2005 9:13 PM Subject: Re: Help Wanted!