From owner-freebsd-arch@FreeBSD.ORG Mon May 22 20:47:03 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B88316A5B4 for ; Mon, 22 May 2006 20:47:03 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9003643D45 for ; Mon, 22 May 2006 20:47:02 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id DBEA746D01; Mon, 22 May 2006 16:46:56 -0400 (EDT) Date: Mon, 22 May 2006 21:46:56 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Eugene M. Kim" In-Reply-To: <447220E5.8080604@astralblue.net> Message-ID: <20060522214429.X246@fledge.watson.org> References: <20060522143521.J21787@fledge.watson.org> <20060522085405.Y34519@ns1.feral.com> <20060522172636.Y21787@fledge.watson.org> <447220E5.8080604@astralblue.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: arch@freebsd.org, Matthew Jacob Subject: Re: Willing to adopt Firewire (was Re: your mail) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 20:47:03 -0000 On Mon, 22 May 2006, Eugene M. Kim wrote: > Robert Watson wrote: >> Yes -- we're beginning to reach the point where we can start issuing >> ultimatums on device drivers, but need USB and Firewire dealt with before >> we can begin to push out stragglers. For better or worse, those two >> hardware categories can't be ignored. Being at a point where we can >> universally make assumptions about MPSAFEty is a very good place to be, and >> we're very close with the network stack. > > Quick question: Has anyone stepped up for MP-guarding Firewire and boys? I > plan to begin hacking Firewire code soon (mainly to add support for 1394 > audio devices), so I probably can adopt them if they've been orphaned. Not as far as I know -- I've not seen any real activity in the Firewire code in some time, and certainly no movement in the direction of making it MPSAFE. Your contribution here would be much appreciated! Robert N M Watson