Date: Sat, 24 Feb 2007 00:03:45 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: lydianconcepts@gmail.com Cc: scsi@freebsd.org Subject: Re: Quirk for this? Message-ID: <20070224.000345.1102528636.imp@bsdimp.com> In-Reply-To: <7579f7fb0702231017rdc246ebqeface91c9d5481e3@mail.gmail.com> References: <45DE6C64.8020400@samsco.org> <20070223.100839.112608684.imp@bsdimp.com> <7579f7fb0702231017rdc246ebqeface91c9d5481e3@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <7579f7fb0702231017rdc246ebqeface91c9d5481e3@mail.gmail.com>
"Matthew Jacob" <lydianconcepts@gmail.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070224.000345.1102528636.imp>