public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Miguel Bolanos <mike@linuxlabs.com>
To: linux-8086@vger.kernel.org
Subject: Future of ELKS
Date: Wed, 19 May 2004 14:55:25 -0600	[thread overview]
Message-ID: <1084985870.3062.23.camel@talena.hsol.net> (raw)

Good day to all,

The project seems to be finally awaking from a very long period of
inactivity, this can be reflected not only by the traffic on the mailing
list, but on the amount of people hanging around at the irc channel and
the quality of the discussions over there.

Based on this facts, I believe that it is important that all the people
involved and interested in ELKS, provide their own opinions on what the
future of ELKS should be... I know of many wanting to have specific
features that are not currently in the kernel.. and others that as well
have interesting ideas for code reduction and improvements. So if you
are one them, please feel free yourself, as all this feedback is
important for us upgrade the TODO and roadmap of the project.

The current things that are been done are:

- Creation of an additional kernel that will use linux 2.6 coding style,
this is been done because we are looking forward to enable the
possibility of including support for 8086 and similar on the official
linux kernel as an option... of course this is will take a long time,
and doesn't mean that work on the current "production kernel" will be
depricated or anything like that, we which to encorage you to keep
contributing on the "production" kernel.. and the "new" kernel project
will be a work in parallel that at some point will have all this
improvements on the production kernel merged.

- A possibility of using gcc to create 8086 binaries might be a
possibility with a patch created by our irc friend boto. If the tests of
this are successful we will enable elkscmd to let the users decide if
they which to use gcc-8086 or our current bcc :)

Anyways thats all for now. Hope to hear back from all.
best wishes

Mike


             reply	other threads:[~2004-05-19 20:55 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19 20:55 Miguel Bolanos [this message]
2004-05-20  3:39 ` Future of ELKS I'm in Void
2004-05-20 14:47   ` Miguel Bolanos
2004-05-20 11:42 ` Javier Sedano
2004-05-20 15:15   ` Miguel Bolanos
2004-05-20 15:37     ` Eduardo Pereira Habkost
2004-05-20 16:06       ` Andrey Romanenko
2004-05-21  5:51         ` Dan Olson
2004-05-20 17:30       ` Javier Sedano
2004-05-21  8:32         ` Gábor Lénárt
2004-05-21 14:15           ` Jody
2004-05-24  9:29             ` Gábor Lénárt
2004-05-24 18:20               ` Alan Cox
2004-05-20 23:43       ` David Given
2004-05-21  1:04         ` Stefan de Konink
2004-05-21  3:39           ` Chad Page
2004-05-29 16:58             ` Gregg C Levine
2004-05-21  5:55         ` Dan Olson
2004-05-21  6:08         ` Jody
2004-05-21 13:24         ` Eduardo Pereira Habkost
2004-05-21 16:30           ` David Given
2004-05-21 16:59             ` Michael McConnell
2004-05-22 12:12               ` David Given
2004-05-22 17:29                 ` Chad Page
2004-05-21 18:38             ` Jody
2004-05-22  8:53               ` jb1
2004-05-22 17:00                 ` Chad Page
2004-05-24  9:42               ` Gábor Lénárt
2004-05-20 16:54     ` Javier Sedano
2004-05-21  5:50     ` Dan Olson
2004-05-21  9:08       ` Arnaldo Carvalho de Melo
2004-05-21 10:24         ` Alan Cox
2004-05-24 12:20         ` Gábor Lénárt
  -- strict thread matches above, loose matches on Subject: below --
2004-05-20 13:40 Pat Gilliland
2004-05-21 17:53 ` Miguel Bolanos
2004-05-20 20:18 Tommy McCabe
2004-05-24 13:17 BODRATO Stefano

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=1084985870.3062.23.camel@talena.hsol.net \
    --to=mike@linuxlabs.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