Linux-8086 Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chad <chad.page@gmail.com>
To: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: GCC port for Intel 8086, 80186 and 80286
Date: Thu, 30 Aug 2007 09:54:18 -0700	[thread overview]
Message-ID: <f784f5260708300954h31be8527v6a61124321aeb683@mail.gmail.com> (raw)
In-Reply-To: <37367b3a0708300943v6614801cp26111f8ff7378989@mail.gmail.com>

2007/8/30, Rask Ingemann Lambertsen <rask@sygehus.dk>:

>    I've just posted an update which inludes support for generating ELKS
> binaries. Please see
> <URL:http://gcc.gnu.org/ml/gcc-patches/2007-08/msg02195.html>.

Awesome - I would so have loved to have this way back when.  Now to
find time to try it out...

On 8/30/07, Alan Carvalho de Assis <acassis@gmail.com> wrote:
> Hi Rask,
> congratulations!
>
> I hope ELKS become active newly and in future it can be integrated to
> main kernel just like happened to uclinux. I known ELKS is based in a
> very old kernel source, but we can dream about it.
>
> Just dreaming :-)

If you're interested in working on mainline tree stuff look into a
ucLinux port to i386, if there isn't already one*, and in addition a
cool ucLinux-centric distribution/packaging.  OpenEmbedded would be a
good base since you can build for many different archs, but it can be
a bit interesting to wrangle ;)

(* - yes this sounds nuts... but it might be faster than regular Linux
and probably smaller.  At least Samsung's people measured that while
working on mmu-less ARM ucLinux.)

- Chad

  reply	other threads:[~2007-08-30 16:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09 20:56 GCC port for Intel 8086, 80186 and 80286 Rask Ingemann Lambertsen
2007-08-09 22:36 ` Royce Williams
2007-08-10  7:27 ` Hans
2007-08-10  8:41   ` Rask Ingemann Lambertsen
2007-08-30 15:16 ` Rask Ingemann Lambertsen
2007-08-30 16:43   ` Alan Carvalho de Assis
2007-08-30 16:54     ` Chad [this message]
2007-08-30 23:42     ` Alan Cox
2007-08-31  8:37       ` Eddy
2007-08-31 12:58         ` Vikas N Kumar

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=f784f5260708300954h31be8527v6a61124321aeb683@mail.gmail.com \
    --to=chad.page@gmail.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