From owner-freebsd-current@FreeBSD.ORG Sat Feb 5 15:28:32 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65BBD106566B; Sat, 5 Feb 2011 15:28:32 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.c2i.net [212.247.154.162]) by mx1.freebsd.org (Postfix) with ESMTP id BA2B98FC0C; Sat, 5 Feb 2011 15:28:31 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=LfWZgthhXpRoR/5kSLoV97TeOFxNHdDd5OkOatCv3DI= c=1 sm=1 a=WcA_fa_ncYIA:10 a=Q9fys5e9bTEA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=BTbq75n6na95gJPr-bQA:9 a=tfypEOXCPI3hb4LtNU8jDVTagz4A:4 a=PUjeQqilurYA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe06.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 83333337; Sat, 05 Feb 2011 16:28:29 +0100 From: Hans Petter Selasky To: Donald Allen Date: Sat, 5 Feb 2011 16:28:28 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.2-PRERELEASE; KDE/4.4.5; amd64; ; ) References: <201102051534.54590.hselasky@c2i.net> In-Reply-To: X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq, NwSZ4V"|LR.+tj}g5 %V,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( :AuzV9:.hESm-x4h240C`9=w MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201102051628.28754.hselasky@c2i.net> Cc: freebsd-current@freebsd.org, freebsd-usb@freebsd.org Subject: Re: Intermittent pauses copying from one usb drive to another X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 05 Feb 2011 15:28:32 -0000 On Saturday 05 February 2011 16:18:56 Donald Allen wrote: > Does whoever is responsible for CAM/SCSI > know about this and do you know if there are plans to fix it? What is the > point of "supporting" USB devices (and we aren't talking about an odd-ball > device here; these are USB disks), when the "support" is partially broken? As far as I know there are no ongoing plans to fix this issue. Yes, we need to support the oddballs too, of course. Currently a lot of quirks have been pushed into the umass driver, but I guess that we need to add more quirks, and probably switch around from black-listing into white-listing, so that the quirks are turned on by default. Thanks for your understanding! --HPS