From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pat LaVarre Subject: Re: [PATCH] SCSI: limit mode sense usage Date: 28 Oct 2003 13:59:32 -0700 Sender: linux-scsi-owner@vger.kernel.org Message-ID: <1067374772.7040.87.camel@patehci2> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from email-out2.iomega.com ([147.178.1.83]:49641 "EHLO email.iomega.com") by vger.kernel.org with ESMTP id S261760AbTJ1U7h (ORCPT ); Tue, 28 Oct 2003 15:59:37 -0500 Received: from royntex01.iomegacorp.com (unknown [147.178.90.120]) by email.iomega.com (Postfix) with ESMTP id 81A79229A for ; Tue, 28 Oct 2003 13:59:36 -0700 (MST) List-Id: linux-scsi@vger.kernel.org To: linux-scsi@vger.kernel.org [[[ Sorry the GUI here at first transmitted this with the Subject prefix "[usb-storage] " in place. ]]] > > ... not clear to me what is the best way to take care of the devices that > > choke on page 3F ... > Some of us have suggested substituting: > -y "5A 00 08:00:00:00 00 00:1C 00" -i x1C // Mode Sense 10 of SBC/MMC > Page x08 Cacheing for 8 byte header, optional 8 byte block descriptor, > and xC byte standard page x08 length >>From a contemporaneous thread: - Host requests MODE_SENSE_10 and request 28 bytes - But the device only has 20 bytes, so it Translating, we see that the terms 20 28 here mean what more bus traces show as x14 x1C. That again suggests talk-like-Windows might be: -y "5A 00 08:00:00:00 00 00:1C 00" -i x1C Those devices that only agree to copy in x14 = 20 bytes may be omitting the optional 8 byte block descriptor, in accord with what I think I remember MMC requires, though simultaneously in discord with what I'm almost sure I remember SBC recommends. Pat LaVarre