From owner-freebsd-hackers Fri Dec 12 11:52:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA19238 for hackers-outgoing; Fri, 12 Dec 1997 11:52:23 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from bubba.NMSU.Edu (bubba.NMSU.Edu [128.123.3.39]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA19172 for ; Fri, 12 Dec 1997 11:51:50 -0800 (PST) (envelope-from ian@nmsu.edu) Received: from NMSU.Edu by bubba.NMSU.Edu (8.8.7/NMSU) id MAA17584; Fri, 12 Dec 1997 12:48:44 -0700 (MST) Received: from wilma by NMSU.Edu (8.8.4/NMSU-1.18) id MAA20316; Fri, 12 Dec 1997 12:50:05 -0700 (MST) Received: from nmsu.edu by wilma (SMI-8.6/NMSU) id MAA18340; Fri, 12 Dec 1997 12:49:50 -0700 Message-ID: <349195B3.9C3EEE2D@nmsu.edu> Date: Fri, 12 Dec 1997 12:51:15 -0700 From: Ian Logan Organization: Computing and Networking X-Mailer: Mozilla 4.03 [en] (X11; U; SunOS 5.6 sun4m) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: Jason Evans , Chuck Robey , freebsd-hackers@FreeBSD.ORG Subject: Re: Beginning SPARC port References: <15903.881931778@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > I'd also argue that the legacy stuff should just generally be left > alone until after the majority of the SPARC architecture support is > rolled into the toolchain and your UltraSPARC port is at least booting > single-user. :-) Unless someone's got a serious jones on for running > FreeBSD on their SPARCStation II right this very minute, waiting until > you've made more progress is only in their best interest if they want > maximum leverage for their own port. > > Jordan I guess I'm a little confused about what you're suggesting to leave out. A SS2 is indeed a very old box, and getting the code work right for a 4c seems to be a lot of work. However, from everything I've read upto now the newer 4m's (ie SparcStaion (4|5|10|20)) aren't that far off from the Ultra's, in other words they'll share alot of the same code. I don't see any reason why 4m & 4u support couldn't happen in parallel :-) Ian aka the guy wanting to write the 4m code. -- Ian Logan Computing & Networking New Mexico State University Email: ian@nmsu.edu Phone: 505-646-6034 Fax: 505-646-5278