From owner-freebsd-usb@FreeBSD.ORG Tue Sep 16 07:35:31 2008 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6D39106566C; Tue, 16 Sep 2008 07:35:31 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe14.tele2.se [212.247.155.161]) by mx1.freebsd.org (Postfix) with ESMTP id 017078FC1C; Tue, 16 Sep 2008 07:35:30 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=ZtwMFzhc6XSROYQlMkMA/A==:17 a=6I5d2MoRAAAA:8 a=ORaZzADKHaVeJ42eVcQA:9 a=9sO5otT3i1YC8U0OspMA:7 a=GjG0WebW57JNIsO3tdCtDadf15EA:4 a=LY0hPdMaydYA:10 Received: from [62.113.133.218] (account mc467741@c2i.net [62.113.133.218] verified) by mailfe14.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 336993831; Tue, 16 Sep 2008 09:35:28 +0200 From: Hans Petter Selasky To: Scott Long Date: Tue, 16 Sep 2008 09:37:16 +0200 User-Agent: KMail/1.9.7 References: <200809112044.43749.hselasky@c2i.net> <200809152229.28590.hselasky@c2i.net> <48CED452.6020709@samsco.org> In-Reply-To: <48CED452.6020709@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809160937.17718.hselasky@c2i.net> Cc: current@freebsd.org, fbsd-current@mawer.org, Julian Elischer , freebsd-usb@freebsd.org, volker@vwsoft.com, ticso@cicely.de Subject: Re: "legacy" usb stack fixes 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, 16 Sep 2008 07:35:31 -0000 On Monday 15 September 2008, Scott Long wrote: > Hans Petter Selasky wrote: > > Hi, > > > > Please find a link to my implementation. Panics when unplugging USB Mass > > Storage Devices is now a thing of the past, I hope. Any comments ? > > > > http://perforce.freebsd.org/chv.cgi?CH=149821 > > > > --HPS > > So you're sticking with a SIM per umass target, and adding a global lock? > Yes, and I don't free the SIM until unloading the "umass" module. --HPS