Date: Tue, 27 Feb 2007 07:48:38 -0700 From: Scott Long <scottl@samsco.org> To: Matthew Jacob <lydianconcepts@gmail.com> Cc: "M. Warner Losh" <imp@bsdimp.com>, scsi@freebsd.org Subject: Re: Quirk for this? Message-ID: <45E444C6.40607@samsco.org> In-Reply-To: <7579f7fb0702261041ld6f4a09q732bbbc419cf1c73@mail.gmail.com> References: <45DE6C64.8020400@samsco.org> <20070223.100839.112608684.imp@bsdimp.com> <7579f7fb0702231017rdc246ebqeface91c9d5481e3@mail.gmail.com> <20070225.230019.1649768891.imp@bsdimp.com> <7579f7fb0702252331m7d3a61c5u224d898b4f04248c@mail.gmail.com> <45E3092A.5040404@samsco.org> <7579f7fb0702261041ld6f4a09q732bbbc419cf1c73@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I understand what you're saying. If you look in the umass driver, there is already a mechanism for quirks as well as a fairly large collection of quirks for bad SCSI protocol behavior from devices. These should all move up to CAM, I agree. However, what exists in CAM right now for XPORT-specific support is just a series of 'if' statements scattered around cam_xpt.c. If you moved Warner's quirk up as well as the other umass quirks, you're going to quickly make a royal mess out of cam_xpt.c. That's what I want to avoid. Once we figure out exactly what we want out of the XPORT code and get it a little more defined and organized, I think we can then start moving the quirks out of the umass driver. Until then, solving Warner's problem via umass.c is easy and doesn't complicate the end goal much at all. Scott Matthew Jacob wrote: > It may be a property specific to USB devices, but the code affected is > a property of the end target at the end of a transport, not the > transport itself. > > On 2/26/07, Scott Long <scottl@samsco.org> wrote: >> Matthew Jacob wrote: >> >> >> >> I took a look at Linux, and they have a quirk for this. A bunch of >> >> cameras have this bug, as do iPods and a few media readers... >> >> >> > >> > So, is your take then we should have a "subtract by N" read capacity >> quirk? >> >> If it's just a USB property, I'd like to avoid adding a quirk to the CAM >> core, especially one that requires multiple arguments. >> >> Scott >> >>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45E444C6.40607>