Date: Mon, 20 May 2002 23:39:01 +0900 From: Hidetoshi Shimokawa <simokawa@sat.t.u-tokyo.ac.jp> To: "Kenneth D. Merry" <ken@kdm.org> Cc: Matthew Dillon <dillon@apollo.backplane.com>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/cam/scsi scsi_da.c Message-ID: <ybsznyudgu2.wl@ett.sat.t.u-tokyo.ac.jp> In-Reply-To: <20020519172841.A51662@panzer.kdm.org> References: <200205192159.g4JLxSx22676@freefall.freebsd.org> <20020519170221.A51589@panzer.kdm.org> <200205192312.g4JNCsKs098352@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At Sun, 19 May 2002 17:28:41 -0600, Kenneth D. Merry <ken@kdm.org> wrote: > -stable and -current both have the code to handle devices that don't like 6 > byte commands. > > The reason all those quirks are still in there is that we would need to > contact everyone to see if the code we've got to detect devices with this > issue actually works for their device. If the device returns a > non-standard error code, it won't get flagged as a device that doesn't > support 6 byte commands. Unfortunately, there are many USB devices which don't return any SCSI error for 6 byte commands. For such devices, you have to do one of the following: 1. sysctl kern.cam.da.no_6_byte=1 2. Replace two '#if 0' with '#if 1' in dadone() of scsi_da.c. 3. Add a quirk. > Well, they're more ATAPI than anything else. The better fix in -current > at least would be to use the new transport settings code to determine that > devices on transport X don't support 6 byte commands. What we've got now It sounds good. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ybsznyudgu2.wl>