From owner-freebsd-scsi@FreeBSD.ORG Sat Feb 24 07:04:22 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 E3CE516A403 for ; Sat, 24 Feb 2007 07:04:22 +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 A333713C428 for ; Sat, 24 Feb 2007 07:04:22 +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 l1O73hLl035308; Sat, 24 Feb 2007 00:03:44 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 24 Feb 2007 00:03:45 -0700 (MST) Message-Id: <20070224.000345.1102528636.imp@bsdimp.com> To: lydianconcepts@gmail.com From: "M. Warner Losh" In-Reply-To: <7579f7fb0702231017rdc246ebqeface91c9d5481e3@mail.gmail.com> References: <45DE6C64.8020400@samsco.org> <20070223.100839.112608684.imp@bsdimp.com> <7579f7fb0702231017rdc246ebqeface91c9d5481e3@mail.gmail.com> X-Mailer: Mew version 4.2 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]); Sat, 24 Feb 2007 00:03:44 -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: Sat, 24 Feb 2007 07:04:23 -0000 In message: <7579f7fb0702231017rdc246ebqeface91c9d5481e3@mail.gmail.com> "Matthew Jacob" writes: : > 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? : : There are two problems here that I see: : : a) The GEOM taste code cannot be overridden. : : b) How do we accomodate/detect broken h/w? : : I'm inclined to think that GEOM stuff cannot/should not be "fixed". : The second question is the harder one. I agree that GEOM shouldn't be the agent of change. : You personally can fix this for yourself by doing your own specialized : quirk matching and just adjusting the READ CAPACITY results : accordingly. We have to ask whether this particular breakage is both : widespread enough and the devices important enough to try and : generalize some solution for. So far I've only found one, and this is a device that is easily 4 or 5 years old. If there's an easy way to cope, it is worth fixing. However, it may be unique to my device... Warner