From owner-freebsd-scsi@FreeBSD.ORG Fri Feb 23 17:10:28 2007 Return-Path: X-Original-To: scsi@freebsd.org Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D0F7816A401 for ; Fri, 23 Feb 2007 17:10:28 +0000 (UTC) (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 7000D13C4A5 for ; Fri, 23 Feb 2007 17:10:28 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l1NH8dWQ028892; Fri, 23 Feb 2007 10:08:39 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 23 Feb 2007 10:08:39 -0700 (MST) Message-Id: <20070223.100839.112608684.imp@bsdimp.com> To: scottl@samsco.org From: Warner Losh In-Reply-To: <45DE6C64.8020400@samsco.org> References: <20070221.160542.-169061472.imp@bsdimp.com> <45DE6C64.8020400@samsco.org> 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]); Fri, 23 Feb 2007 10:08:39 -0700 (MST) Cc: scsi@freebsd.org Subject: Re: Quirk for this? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Feb 2007 17:10:28 -0000 > M. Warner Losh wrote: > > I have a umass device that lies about the size of the device: > > > > umass0: on uhub1 > > da0 at umass-sim0 bus 0 target 0 lun 0 > > da0: Removable Direct Access SCSI-2 device > > da0: 1.000MB/s transfers > > da0: 61MB (125441 512 byte sectors: 64H 32S/T 61C) > > > > However, when I plug it in with other umass devices, this is what I > > see: > > > > umass0: on uhub2 > > da0 at umass-sim0 bus 0 target 0 lun 0 > > da0: Removable Direct Access SCSI-0 device > > da0: 40.000MB/s transfers > > da0: 61MB (125440 512 byte sectors: 64H 32S/T 61C) > > > > The 125440 number is what is reported by ata as well. > > > > Is there some way I can quirk this to not get a huge cascade of errors > > when the last sector is read by the tasting code? I didn't see any > > way when I was reading the code, but the quirks are scatter in a few > > different files and I might have missed something. > > > > Warner > > I don't understand, it changes its inquiry and size data depending on > how many other devices are plugged into the bus with it? That's highly > bizarre. No, there is no size coercion quirk. We could add one, but we > need to decide on what an appropriate coercion is, and how to trigger > it. Size coerecion is highly, highly hard to get right. OK. Maybe I was unclear in my first post. One of the SanDisk devices that I have, the first one listed, reports the size wrong. It is one too big. This is the USB/CF adapter whatsit. No matter which CF card I plug into it, it is reported one too large. This is a bug in the USB/CF adapter. This is shown first in the list above. The other USB/CF adapter, as well as my PC Card/CF adapter, reports the correct size for the card (which is shown second). The question is: Given that I know that the first USB/CF adapter always reports one too big, is there a way this can be fixed? Warner