From owner-freebsd-current@FreeBSD.ORG Wed Mar 24 13:20:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F26916A4DE; Wed, 24 Mar 2004 13:20:28 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7A5243D39; Wed, 24 Mar 2004 13:20:27 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i2OLKMtf005249; Wed, 24 Mar 2004 16:20:23 -0500 (EST) Date: Wed, 24 Mar 2004 16:20:22 -0500 (EST) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Julian Elischer In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: FreeBSD current users cc: Marcel Moolenaar Subject: Re: SF Bay area hackfest X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Mar 2004 21:20:28 -0000 On Wed, 24 Mar 2004, Julian Elischer wrote: > > On Wed, 24 Mar 2004, Scott Long wrote: > > > Julian Elischer wrote: > > > who cares? > > > > That's the wrong answer. > > yes I know. > > It's just that we decided at the dev summit that we were dropping alpha > as a tier one platform and everyone seems to have forgotten that. > Sparc support is planned but we've had very little input from Sparc > developers (are there any?) As far as KSE goes, we've tried getting someone to help us on sparc64 and alpha, but so far no-one has stepped forward. And TLS support for sparc64 and alpha can be added to libpthread regardless of whether the library is fully functional on those archs. > > There is a formal statement from the project > > that sparc64 is a tier-1 platform and also the reference platform for 64 > > bit support. The definition of tier-1 is that new functionality is > > added to all tier-1 platforms. This is no exception. I'm not going to > > re-open the tier discussion right now, though we indeed need to review > > it in the next month or two. For rgiht now, plan on supporting all > > tier-1 platforms. You don't need to necessarily write all the code > > yourself for these, but you have to be prepared to take them into > > consideration and take responsibility for getting the code written > > by someone. And you know that we have tried to do this. -- Dan Eischen