From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jody Bruchon Subject: Re: Porting to different architectures Date: Mon, 31 Jul 2006 13:42:55 -0400 Message-ID: <44CE411F.3090003@nc.rr.com> References: <20060731140941.IIPE1187.ibm68aec.bellsouth.net@mail.bellsouth.net> <01ad01c6b4b2$07e4c790$6502a8c0@dionysus> <44CE232F.4080606@wallman.org.uk> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <44CE232F.4080606@wallman.org.uk> Sender: linux-8086-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Richard Wallman , linux-8086@vger.kernel.org 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@cvs.sourceforge.net" with > "anonymous@elks.cvs.sourceforge.net" 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? >