From owner-freebsd-sparc Thu Jan 27 8:42:33 2000 Delivered-To: freebsd-sparc@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3A6ED15645 for ; Thu, 27 Jan 2000 08:42:30 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id IAA04334; Thu, 27 Jan 2000 08:42:21 -0800 Date: Thu, 27 Jan 2000 08:42:17 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Lyndon Griffin Cc: freebsd-sparc@FreeBSD.ORG Subject: Re: Timeline for development In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-sparc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It's more complicated. You'd better add in different variant timelines for which PCI bus chip will/won't be supported. There are some endian issues for PCI devices. The Qlogic ISP driver is ready for SBus and PCI (it exists in the NetBSD version) but hasn't really been shaken out on UltraSparc machines except in it's linux instantation- and there are some swizzling issues that will have to be worked out. Maybe a list of 'goal' machines. Frankly, this effort could save a lot of wear and tear on all of us if it just concentrates on sun4m/sun4u. On Thu, 27 Jan 2000, Lyndon Griffin wrote: > Does this look right for a timeline for development? Am I missing > anything? Am I overstating anything? Is anything out of order? > > Timeline milestones: > bootstrap > boot loader > console kernel > single user > "full" kernel > userland > multiuser > merge into current > release and enter release cycles > > <:) Lyndon Griffin > http://www.bsd4us.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-sparc" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message