From: David Given <dg@cowlark.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Where does ELKS need to go?
Date: Mon, 21 Apr 2014 23:05:14 +0100 [thread overview]
Message-ID: <5355961A.4020005@cowlark.com> (raw)
In-Reply-To: <5352A80F.7000503@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2219 bytes --]
On 4/19/14, 5:45 PM, Harley Laue wrote:
[...]
> I'm pretty sure it's been mentioned in the past, but SDCC might be an
> option (though, I don't think there is a code generator for 8086-80286).
> Edoardo's suggestion of TACK might be a good fit as well. I've had some
> experience with SDCC, but I haven't ever tried TACK. I will say, SDCC
> has a fairly dedicated community behind it and the project is still
> quite active. TACK, however, doesn't seem to have had many commits in
> the last few years.
I'm the maintainer for TACK. It's actually had some development recently
--- and from people who aren't me, too! But unfortunately the design is
rather hostile to RISC architectures. But it's got decent C89 support
and a reasonable 8086 code generator, and it does have the big advantage
over bcc or pcc in that it's a complete toolchain --- it's got a libc,
an assembler and a linker in it, so it can be made to spit out binaries
with no external dependencies.
Adding a new target to TACK is a bit specialist but relatively easy.
Ping me if there's interest.
[...]
>> * What can/does ELKS offer compared to other small OSes such as NuttX?
> Running more than one process (I'm assuming at least.) IIRC, NuttX
> compiles the kernel into the application to run the single application
> on the hardware.
ELKS' big feature is that it's got a userland. Unfortunately I'm not
sure this is particularly useful these days, particularly as the way it
works is strongly dependent on having an MMU (the 8086's segmentation
counts as an MMU here). I doubt whether ELKS could be easily ported to a
non-MMU system. (How do you relocate a running process, for example?)
One option is to turn ELKS into a Unix emulation layer on top of NuttX,
but that would mean giving up a lot of what makes ELKS a Unix. And I'm
afraid that even for the 8086, ELKS has been superceded by Minix 2,
which is a lot more mature and robust than ELKS is.
--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
│
│ "You cannot truly appreciate _Atlas Shrugged_ until you have read it
│ in the original Klingon." --- Sea Wasp on r.a.sf.w
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 876 bytes --]
next prev parent reply other threads:[~2014-04-21 22:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 1:12 ELKS links broken Michael Sklaroff
2014-04-18 19:26 ` Edoardo Liverani
2014-04-18 20:03 ` Where does ELKS need to go? (was: ELKS links broken) Jody Bruchon
2014-04-18 21:44 ` Edoardo Liverani
2014-04-19 16:45 ` Where does ELKS need to go? Harley Laue
2014-04-19 18:28 ` Royce Williams
2014-04-19 18:33 ` Jody Lee Bruchon
2014-04-19 20:38 ` Royce Williams
2014-04-19 22:29 ` Edoardo Liverani
2014-04-21 22:05 ` David Given [this message]
2014-04-19 18:07 ` Where does ELKS need to go? (was: ELKS links broken) Chad
2014-04-19 20:43 ` Royce Williams
2014-04-19 21:14 ` Jody Bruchon
-- strict thread matches above, loose matches on Subject: below --
2014-04-21 12:04 Where does ELKS need to go? LM
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=5355961A.4020005@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).