linux-8086.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alexander van Heukelum" <heukelum@freemail.nl>
To: Miguel Bolanos <mike@hsol.net>, linux-8086@vger.kernel.org
Subject: Re: Help Wanted!
Date: Wed, 28 Sep 2005 11:51:42 +0200	[thread overview]
Message-ID: <web-169077696@freemail.nl> (raw)
In-Reply-To: <1127539824.8686.33.camel@selene.hsol.net>

On Fri, 23 Sep 2005 23:30:24 -0600
 Miguel Bolanos <mike@hsol.net> wrote:
>Greetings to all,
>
>As you may have noticed the project has been stuck for quite a while, i
>am looking forward to bring it back to life, but and would like to ask
>for some help, obviously coders are very welcome, but also people
>willing to help writing docs, and even people looking forward to help us
>create a new look for the project website.
>Looking forward to hear back from you.

Hi!

I don't think I will be of much help, but the ELKS project has
interested me enough to keep myself subscribed to the list
(and the list hasn't received enough spam to annoy me ;) ) My
_personal_ opinion is that ELKS as it stands (8086-specific)
will never have enough support to become an interesting 
project. Supporting more architectures means that there is 
the need for a flexible compiler, and very portable code.

I think portable code is equivalent to "gcc-like" in this case, but 
gcc itself seems far too complex to ever work in a "small" 
environment. The TinyCC [1] compiler comes close, and already 
has non-i386 code generators. It lacks a pure 8086 generator, 
however. I also think that the compiler should implement a 32
bit int (and in fact adhere to the limits as given in susv3 [2]). 
That way there could be more code-sharing with other "modern"
projects, in particular dietlibc, uClibc, Busybox.

Anyhow: Good Luck :)

btw. Who is the maintainer of this list?
Majordomo says:
>>>>> info linux-8086
>Linux on 8086 -- non-MMU, very small address spaces
>
>Archives:
>  http://www.geocrawler.com/lists/3/Linux/
>>>>> who linux-8086
>**** Command disabled.

regards,
    Alexander

[1] http://fabrice.bellard.free.fr/tcc/
[2] http://unix.org

>regards
>
>Miguel.
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-8086" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html


  parent reply	other threads:[~2005-09-28  9:51 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
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 [this message]
  -- 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=web-169077696@freemail.nl \
    --to=heukelum@freemail.nl \
    --cc=linux-8086@vger.kernel.org \
    --cc=mike@hsol.net \
    /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).