From owner-freebsd-usb@FreeBSD.ORG Tue Jan 17 19:30:33 2006 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DF5C16A41F for ; Tue, 17 Jan 2006 19:30:33 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD2A143D62 for ; Tue, 17 Jan 2006 19:30:24 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k0HJSn8P007334; Tue, 17 Jan 2006 12:28:49 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 17 Jan 2006 12:28:49 -0700 (MST) Message-Id: <20060117.122849.116442810.imp@bsdimp.com> To: mistry.7@osu.edu From: Warner Losh In-Reply-To: <200601171326.16816.mistry.7@osu.edu> References: <1137462090.835.24.camel@yak.mseubanks.net> <20060117120347.zs7gpbs6jog80444@netchild.homeip.net> <200601171326.16816.mistry.7@osu.edu> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 17 Jan 2006 12:28:49 -0700 (MST) Cc: freebsd-usb@freebsd.org Subject: Re: USB device implementation X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2006 19:30:33 -0000 > On Tuesday 17 January 2006 06:03, Alexander Leidinger wrote: > > "Michael S. Eubanks" wrote: > > > Okay. I will look into it some more. I need to get better idea > > > of how the USB driver code works. It looks like there are only > > > minor differences between my current driver code and the NetBSD > > > code. With respect to any questions and changes I make, should I > > > contact mux@ directly using the email address listed on the > > > contributors page? > > > > Every FreeBSD committer should expect to get a mail with some > > questions, so mailing to mux@FreeBSD.org is not forbidden. :-) > > > > But he's not "the USB guy in the block". He just tries to port the > > uhidev code (maybe because he needs it). So don't expect an answer > > to every question. > > > > Unfortunately we don't have an active USB guru around, except > > Hans-Petter Selasky (not a FreeBSD committer), but he develops a > > rewritten-from-scratch USB stack. So don't expect him to be able to > > answer questions reagarding the USB stack in -current. > From my personal experience and just looking at the commiter that has > been touching the usb files I'd add Ian Dowse > to that short guru list. He has been pretty busy recently, but if > you're willing to do your homework I'm sure he'd be happy to answer > any questions. I've also been doing a bunch inside the usb stack, although not having enough time either. > > So far HPS wasn't able to convince a committer to import his work. > > Partly because we think that a USB stack which is shared between > > the BSD's may be better, partly because the existing stack seems to > > work good enough for those committers which may be willing to > > import the new one or be able to mentor HPS. > As Warner said it takes time to work through such a large change. > Hans-Petter Selasky stack is trying to be free of the GIANT lock and > that's a bit tricky with USB, but ultimately the direction we are > heading for 7.0. Yes. There's also some concerns over the safety of the novel locking scheme that has been proposed for usb that take a lot of time and energy to work out. Eg, are they any better than the stock tools, does it work? Does it fill a void in our stock tools? etc Warner