public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Nasrat <pauln@truemesh.com>
To: S?rgio Duarte e Silva <sduartes@mandic.com.br>
Cc: linux-kernel@vger.kernel.org, linux-8086@vger.kernel.org
Subject: Re: ELKS - 80188 Newbie
Date: Sun, 6 Jul 2003 22:11:43 +0100	[thread overview]
Message-ID: <20030706211143.GI7556@raq465.uk2net.com> (raw)
In-Reply-To: <3831.200.154.192.236.1057452982.squirrel@www.mandic.com.br>

On Sat, Jul 05, 2003 at 09:56:22PM -0300, S?rgio Duarte e Silva wrote:

> I would like to run Linux on an embedded 80188 Tern board
> (www.tern.com). Is there

ELKS (http://elks.sourceforge.net) has it's own mailing list:
linux-8086@vger.kernel.org you can subscribe using majordomo. This
would be the best place to discuss this.

It's not a Linux port rather a subset and implementation for 8086.
Currently it is mostly set up to run off PC architecture, depending on
the board it may run out of the box, or may require some porting. If the
board supports floppy or an IDE hdd you probably can quickly check if
you can get a bootable system

> anyone here that already made this? Is there any easy tutorial or boot
> code already made for this processor?

ELKS is bootable - and there is a user space, without a closer look I
couldn't say if it would work out of the box on this board.  There are
stock boot images, as well as EDE which is designed to install ELKS onto
the HDD.  Some of the ELKS developers are working on other install
scripts.

I suggest you subscribe to linux-8086 and we'll see what we can do to
help you.  Some more details about the board might help us. There is
also a #elks channel on irc.freenode.net.

Paul

           reply	other threads:[~2003-07-06 21:11 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <3831.200.154.192.236.1057452982.squirrel@www.mandic.com.br>]

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=20030706211143.GI7556@raq465.uk2net.com \
    --to=pauln@truemesh.com \
    --cc=linux-8086@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sduartes@mandic.com.br \
    /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