Re: Porting to different architectures

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm here.

My main machine (the host) had an Athlon XP barbecue.

I'm using a temporary Linux box but haven't gotten around to putting thttpd on it yet.

I'll see what I can do, but I'll definitely need someone to mail me the ELKS source tarball again so I can put it back up. I've got real UNIX now, so you won't see CRLF problems anymore :)

Also, I have full access to the entire ELKS project. Mail me if you need stuff done and I'll try to take care of it.

Thanks!

Jody

Richard Wallman wrote:
Hans wrote:
There are still a number of people on this list but most of us are in
"screen saver" mode :-)

I've been following this project for about 7 years now, and it seems
like it regularly goes into "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've been working on getting it to work with GCC for 386+ processors,
and it's not pretty. GCC support would make porting a lot easier, given
the number of processor targets it supports.

The next trick would be to remove some of the PC-specific stuff - not
all systems have a BIOS, for example. I keep meaning to dig out the old
laptop I was given (286 based Toshiba thing) and get a serial console
working. I'm still keen to get it running on my Psion 3C. :)

(I have to admit I am a hardware designer :-).

May come in useful... :)

I am pretty sure that one of us can email you the latest source files

The SourceForge CVS server works, it's just the download instructions on
the site that are wrong.

If you replace "anonymous@xxxxxxxxxxxxxxxxxxx" with
"anonymous@xxxxxxxxxxxxxxxxxxxxxxxx" it all works well.

There doesn't seem to be any of the project admins (the ones with the
CVS SSH key) awake ATM - I was going to see if I could get a copy of the
key so that *someone* could commit changes! Failing that, I would
(reluctantly) have to fork the project just to keep things moving.

So, project admins - anyone awake?

-
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Kernel]     [Linux ia64]     [DCCP]     [Linux for ARM]     [Yosemite News]     [Linux SCSI]     [Linux Hams]

  Powered by Linux