Date: Fri, 12 Dec 1997 03:51:00 -0800 (PST) From: Jason Evans <jasone@canonware.com> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: freebsd-hackers@freebsd.org Subject: Re: Beginning SPARC port Message-ID: <Pine.LNX.3.95.971211075254.19030U-100000@paladio> In-Reply-To: <26799.881843800@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 11 Dec 1997, Jordan K. Hubbard wrote: > Great! I'd almost concluded that this had just faded away again, and > it's good to hear that SME didn't just give up when we were unable to > find any available personnel here. My boss mentioned talking with you the first week that I was at Sun, and I latched on. =) It wouldn't have happened if I hadn't shown extreme interest in working on it. > Ah, so that really means you're good for at least 60 hours a week > then! Good man! Real dedication! ;-) Yeah, something like that. Uh huh. =) Maybe not every week, but yes, I expect to spend those kinds of hours on the project. > I guess you're probably going to want to start with the compiler > issues first then, eh? Peter? Soren? John Polstra? You might wish to > step forward and shake hands with Jason here, guys, because he's > probably going to be the principal motive force behind your toolchain > upgrade in -current! :-) Compiler issues... gcc already supports the target platform. Standard gcc supports SPARC, and Cygnus has a patch to support the Ultra (V8+). What are the issues you refer to? Since FreeBSD is supported in the release version of gcc, don't you guys just copy it into your tree and call it good? Since the Ultra compiler won't be self-hosted until well after the kernel is up and running, why is this important as a first step? Even linker/loader issues seem like a longer term goal, because the kernel itelf is bootstrapped (unless there's shared code there - I haven't looked yet). It seems to me that the first major steps are: 1) Get the kernel to boot (and more or less work). 2) Probe hardware devices. 3) Create minimal number of device drivers for a minimal complete system. 4) Move to self hosting. > Absolutely. Assuming that you've done all that's required to prevent > collision (and again, it's going to take Peter or John P to more fully > answer that question) you can use the full CVS command set to manage > your tree there. You could even set up a local cvsupd and offer it to > others via cvsup, allowing your repository to be replicated in the > same manner as ours is. Great. This is exactly what I wanted to hear. I'll start messing with it asap. The parts for my (x86) FreeBSD box should be here tomorrow (fingers crossed). Jason Jason Evans Email: [jasone@canonware.com] Home phone: [(650) 856-8204] Quote: ["Invention is 1% inspiration, 99% perspiration" - Thomas Edison]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.3.95.971211075254.19030U-100000>