From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Gregg C Levine <obiwanthejediknight@worldnet.att.net>
Cc: ELKS <Linux-8086@Vger.Kernel.Org>
Subject: Re: Has anyone ever tried ELKS out on an embedded configuration?
Date: 28 May 2002 12:51:20 +0100 [thread overview]
Message-ID: <1022586680.4123.41.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <000701c20604$dd4c5bc0$b251580c@who>
On Tue, 2002-05-28 at 06:02, Gregg C Levine wrote:
> Hello from Gregg C Levine
> Since the webpages for ELKS make some mention of the fact that the
> distrobution can be managed on an embedded setup, I thought I'd ask that
> question. So without further waiting: Has anyone ever tried ELKS out on an
> embedded configuration? And as it happens I have gotten a few of the ELKS
> images to come up on the Bochs platform.
It will run basically as is on the old AMD 2 chip x86 stuff. It needs
some work to get it running on the 801C86 for onboard peripherals
however.
prev parent reply other threads:[~2002-05-28 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 5:02 Has anyone ever tried ELKS out on an embedded configuration? Gregg C Levine
2002-05-28 11:51 ` Alan Cox [this message]
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=1022586680.4123.41.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Linux-8086@Vger.Kernel.Org \
--cc=obiwanthejediknight@worldnet.att.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