From owner-freebsd-current Mon Sep 3 13:13:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from btclick.com (mta02.btfusion.com [62.172.195.247]) by hub.freebsd.org (Postfix) with ESMTP id 15DEC37B401 for ; Mon, 3 Sep 2001 13:13:19 -0700 (PDT) Received: from heather.plazza.uk ([213.120.117.63]) by btclick.com (Netscape Messaging Server 4.05) with ESMTP id GJ3S6501.X3W; Mon, 3 Sep 2001 21:13:17 +0100 Date: Mon, 3 Sep 2001 21:14:30 +0100 (BST) From: Nick Hibma X-X-Sender: To: Julian Elischer Cc: , Subject: Re: Firewire driver available In-Reply-To: <3B93DC65.249BF99E@elischer.org> Message-ID: <20010903211302.E27613-100000@heather.plazza.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I haven't looked at the OHCI spec for firewire at all, but it seems that it was intended to be one specification. The OHCI spec puts a lot of processing into the hands of the chip and the interaction is smart enough to not require weird locking or delays (like the UHCI requires), so it could be worthwhile to have a look whether we could integrate the two. Nick > Moved to current: > > Is there any chance that the OHCI code inthe firewire driver and the OHCI > code in the USB drivers might be rationalised? > > Both seem to talk with the CAM system (from quick reading) as well, > so it might seem that there is some common functionality. > > BTW is the struct ahb_softc{} seems to suggest it's from the ahb driver.... > > > -- > +------------------------------------+ ______ _ __ > | __--_|\ Julian Elischer | \ U \/ / hard at work in > | / \ julian@elischer.org +------>x USA \ a very strange > | ( OZ ) \___ ___ | country ! > +- X_.---._/ presently in San Francisco \_/ \\ > v > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message