From: "Hans" <hans64@ht-lab.com>
To: linux-8086@vger.kernel.org
Subject: Re: Porting to different architectures
Date: Mon, 31 Jul 2006 16:00:06 +0100 [thread overview]
Message-ID: <01ad01c6b4b2$07e4c790$6502a8c0@dionysus> (raw)
In-Reply-To: 20060731140941.IIPE1187.ibm68aec.bellsouth.net@mail.bellsouth.net
Hi Chris,
There are still a number of people on this list but most of us are in
"screen saver" mode :-)
Porting ELKS to another (embedded) processor will definitely bring ELKS back
to live (IMHO) but this is a huge and complicated task. Just changing the
compiler from BCC to say Watcom is already a difficult task (I have to admit
I am a hardware designer :-).
I tried Jody's http://compsolutions.ath.cx:88/elks/ site as well and indeed
it looks down. I am pretty sure that one of us can email you the latest
source files,
Hans
www.ht-lab.com
----- Original Message -----
From: <chriscureau@bellsouth.net>
To: <linux-8086@vger.kernel.org>
Sent: Monday, July 31, 2006 3:09 PM
Subject: Porting to different architectures
> Hello, all!
>
> I was glad to see that the ELKS project had a new maintainer...but when I
> saw that the distribution site was down, I thought I'd better check to see
> whether anyone was really still alive here. Assuming there is someone out
> there reading my mail, I have two ideas to discuss...
>
> A friend of mine and I are in the process of building a single board
> computer based on Western Design Center's 65c265, which is a 16-bit MCU
> which supports program sizes up to 64k, and data sizes up to the limit of
> memory (16M). Naturally, our first choice for an operating system for this
> hardware would be a unix-variant...and since ELKS is already coded for the
> 8086, we thought we could do a pretty straight port of it. I'd really
> like to get the latest release, but unfortunately it looks as if Jody
> Bruchon's site is down.
>
> Actually, that brings me to my next idea...I have a server at home with a
> 6M/512k DSL connection. I know, it's not a super fast connection, but it
> is available...and I would like to offer it to be used as a mirror for the
> ELKS project. I will also offer whatever help I can for fixing the CVS
> repository, or perhaps considering with others a move to SVN.
>
> I hope that there is still life in this code yet...it would be rather nice
> to see Linux booting on our hardware. :-)
>
> Thanks,
> Chris Cureau
>
> -
> 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
>
next prev parent reply other threads:[~2006-07-31 15:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 14:09 Porting to different architectures chriscureau
2006-07-31 15:00 ` Hans [this message]
2006-07-31 15:35 ` Richard Wallman
2006-07-31 16:03 ` David Given
2006-07-31 16:24 ` Richard Wallman
2006-07-31 16:32 ` David Given
2006-07-31 17:42 ` Jody Bruchon
2006-08-01 6:49 ` Richard Wallman
2006-08-01 17:15 ` Segin
2006-07-31 19:47 ` Javier Sedano
2006-07-31 21:44 ` Alan Cox
2006-08-01 2:57 ` Tom McCabe
2006-08-01 5:27 ` Jody Bruchon
2006-08-01 13:22 ` Alan Cox
2006-08-01 14:41 ` Vikas N Kumar
2006-08-01 15:28 ` Hans
2006-07-31 15:16 ` Petr Koval
2006-07-31 15:29 ` CVS access Mattia Jona-Lasinio
2006-07-31 15:43 ` Petr Koval
2006-07-31 15:51 ` Petr Koval
2006-08-02 13:24 ` Mattia Jona-Lasinio
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='01ad01c6b4b2$07e4c790$6502a8c0@dionysus' \
--to=hans64@ht-lab.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