Date: Thu, 02 Feb 2006 14:49:12 -0700 From: Scott Long <scottl@samsco.org> To: Matthew Jacob <mj@feral.com> Cc: freebsd-scsi@freebsd.org, Florent Thoumie <flz@xbsd.org>, "Kenneth D. Merry" <ken@freebsd.org>, Nate Lawson <nate@root.org> Subject: Re: cvs commit: src/sys/cam/scsi scsi_da.c src/sys/dev/usb umass.c usbdevs Message-ID: <43E27E58.4020606@samsco.org> In-Reply-To: <20060202130620.A99168@ns1.feral.com> References: <20060130202806.DCC7916A4CA@hub.freebsd.org> <43DEF43A.6090804@root.org> <20060130213338.H79194@ns1.feral.com> <200601311239.10248.flz@xbsd.org> <43E06B06.80405@root.org> <20060202175041.GA92109@nargothrond.kdm.org> <20060202095828.D97756@ns1.feral.com> <43E252EC.1050803@root.org> <43E25C4D.9020804@samsco.org> <43E2650D.1060109@root.org> <20060202130620.A99168@ns1.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Jacob wrote: >>> >>> You're suggesting that the umass and firewire SIMs universally instruct >>> CAM to not send a SYNC CACHE for all targets? Easy, but I think it's >>> too big of a hammer. I'd like to see the da driver get modified to >>> check the WCE state as has been suggested. >> >> >> I agree, I wasn't clear. I meant that we should use the mode sense >> approach instead of adding quirks all the time for something that's >> endemic to a particular architecture. But if that doesn't work, >> perhaps something specific to USB and Firewire may be appropriate. > > > And how will you distinguish between "not currently enabled" and "not > supported"? > If WCE is not supported, will the device lie and report the WCE bit as set? Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43E27E58.4020606>