Date: Thu, 22 Aug 2002 16:24:09 +0900 From: Hidetoshi Shimokawa <simokawa@sat.t.u-tokyo.ac.jp> To: Nate Lawson <nate@root.org> Cc: scsi@freebsd.org Subject: Re: CDB6/10 negotiation Message-ID: <ybs1y8rtkyu.wl@ett.sat.t.u-tokyo.ac.jp> In-Reply-To: <Pine.BSF.4.21.0208211327510.57170-100000@root.org> References: <Pine.BSF.4.21.0208211327510.57170-100000@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At Wed, 21 Aug 2002 13:37:50 -0700 (PDT), Nate Lawson wrote: > > I am available to do the full version suggested by Ken once we agree on a > path. However, there are a lot of people re-working CAM and I don't want > to replicate work. > > Consensus is suggesting the best approach is to put USB transport checks > under CAM_NEW_TRAN_CODE in cam_xpt.c and then use them to set > device-specific behavior. This will then restrict the commands sent to > the device according to what's reported in its inquiry. At some point > when this is working, cmd6workaround can be removed and most quirks can be > removed. The quirks that remain will truly be quirks where a device > reports capabilities it doesn't really support. > > Thoughts? Another simple but ugly soluition is rewriting inquiry response and faking to be T_RBC device rather than T_DIRECT at the trasport layer. RBC doesn't have 6 bytes command so no need to worry about it. (If the device doesn't support READ_6, it shouldn't be T_DIRECT and it should be T_RBC whatever it responses ;-) At first, I introduced cmd6workaround for SBP-II/Firewire devices, but the current driver(*) doesn't exploit it anymore and rewriting inquiry response becase I found a device which hangs up on the first 6bytes command and doesn't accept any commands anymore. (*) http://people.freebsd.org/~simokawa/ BTW, thanks for fixing cmd6workaround(), do you have a plan to MFC? /\ 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 freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ybs1y8rtkyu.wl>