From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 20:21:53 2009 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 9DEDE106564A for ; Sun, 25 Jan 2009 20:21:53 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe08.swip.net [212.247.154.225]) by mx1.freebsd.org (Postfix) with ESMTP id 087AB8FC17 for ; Sun, 25 Jan 2009 20:21:52 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=neEVqQTEdNsA:10 a=wYO06tke1OGfzKJGpPEA:9 a=34Ai5ik5vuyHX7skhdoA:7 a=bdXs_iuYIHYAG01iRxmEoudO-KMA:4 a=SV7veod9ZcQA:10 a=LY0hPdMaydYA:10 Received: from [85.19.218.115] (account mc467741@c2i.net HELO [10.37.1.92]) by mailfe08.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 1184158238; Sun, 25 Jan 2009 21:21:51 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Sun, 25 Jan 2009 21:24:06 +0100 User-Agent: KMail/1.9.7 References: <20090125063441.GC1755@server.vk2pj.dyndns.org> <497CC3C4.1070708@FreeBSD.org> In-Reply-To: <497CC3C4.1070708@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901252124.10886.hselasky@c2i.net> Cc: Peter Jeremy Subject: Re: Prblem whit USB in FreeBSD 8 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: Sun, 25 Jan 2009 20:21:53 -0000 On Sunday 25 January 2009, Maxim Sobolev wrote: > Peter Jeremy wrote: > > On 2009-Jan-24 12:30:56 -0800, Maxim Sobolev wrote: > >> I wonder if this situation can be handled automatically. To my ignorant > >> view, our USB mass storage driver can try sending "synchronize cache" > >> command and if that fails then failback to the NO_SYNCHRONIZE_CACHE > >> behavior. > > > > This has been discussed in the past. The problem is that some drives > > lock up when you send a "synchronize cache" command so this isn't a > > general solution. > > So what? The drive that is not in the quirks won't work anyway, so that > if by auto-detection you can make at least fraction of those drivers > working out of the box it would be an improvement. I wonder how other > operating systems (Windows, Linux) cope with this issue. Not sure about > a Linux, but I really doubt Windows has anything like our quirks, yet > all drives work with it. > Hi, I was thinking about moving the mass storage quirks into the usb2_quirk module so that they can be set by "usbconfig". To some extent I agree that we should try to make things work out of the box. What I could easily do is to add a sysctl which you can set that automatically turns on the most common Mass Storage quirks for all USB Mass Storage Devices plugged. What do you think? --HPS