All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Patrick Mansfield <patmans@us.ibm.com>,
	Matthew Dharm <mdharm-usb@one-eyed-alien.net>,
	thomas schorpp <t.schorpp@gmx.de>,
	USB Storage list <usb-storage@lists.one-eyed-alien.net>,
	Timothy Thelin <Timothy.Thelin@wdc.com>,
	Linux SCSI list <linux-scsi@vger.kernel.org>,
	linux-ide@vger.kernel.org
Subject: Re: [usb-storage] [Merging ATA passthru] on integrating SMART/ATA-Security in usb-storage driver
Date: Mon, 07 Nov 2005 17:05:52 -0500	[thread overview]
Message-ID: <1131401153.3333.6.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0511071552360.5165-100000@iolanthe.rowland.org>

On Mon, 2005-11-07 at 15:59 -0500, Alan Stern wrote:
> > That is, is usb-storage forcing scsi-2 when the device tells us it is
> > scsi-3 compliant, or is the hardware reporting devices are scsi-2, yet
> > requiring non-LUN value in cdb[1]?
> 
> I think we may have both.  However I don't know how this Cypress chip
> reports itself.  A system log showing the INQUIRY data would be very
> helpful.

We were told in prior emails that it actually reports a level of zero
(i.e. no compliance with any SCSI standard).  My original proposal was
just not to modify the CDB[1] for this case if we could get the INQUIRY
passed through unmangled.

> It's quite possible that usb-storage no longer needs to force the 
> scsi-level to 2.  No one has recently tested what would happen without 
> it.  Matt probably has the best selection of devices for testing...
> 
> There is one problem we have with devices that report themselves as SCSI-3 
> or SCSI-4 but hang when they receive a REPORT LUNS command.  That's easily 
> handled by making usb-storage set the NOREPORTLUN flag.  Maybe that's all 
> we need to do.

If you could try this out, I'd be grateful.

Thanks,

James



  reply	other threads:[~2005-11-07 22:06 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-04 18:30 [usb-storage] [Merging ATA passthru] on integrating SMART/ATA-Security in usb-storage driver Timothy Thelin
2005-11-04 18:58 ` James Bottomley
2005-11-04 20:30   ` Matthew Dharm
2005-11-04 20:49     ` James Bottomley
2005-11-05 23:55       ` Matthew Dharm
2005-11-06  0:49         ` James Bottomley
2005-11-06  3:38           ` thomas schorpp
2005-11-06 21:58           ` Matthew Dharm
2005-11-06 22:28             ` thomas schorpp
2005-11-06 23:52               ` Patrick Mansfield
2005-11-07 16:59                 ` Matthew Dharm
2005-11-07 17:05                 ` Matthew Dharm
2005-11-07 17:24                   ` Patrick Mansfield
2005-11-07 17:46                     ` Alan Stern
2005-11-07 18:06                       ` thomas schorpp
2005-11-07 19:33                         ` Alan Stern
2005-11-07 20:07                           ` thomas schorpp
2005-11-07 17:53                     ` Christoph Hellwig
2005-11-07 17:54                     ` thomas schorpp
2005-11-07 18:57                       ` Patrick Mansfield
2005-11-07 19:53                         ` Alan Stern
2005-11-07 20:47                           ` Patrick Mansfield
2005-11-07 20:59                             ` Alan Stern
2005-11-07 22:05                               ` James Bottomley [this message]
2005-11-08 17:09                                 ` Alan Stern
2005-11-08 23:05                                   ` Mike Anderson
2005-11-09 15:35                                     ` Alan Stern
2005-12-01 11:35                                 ` [PATCH] writable scsi_level [was: [Merging ATA passthru] on integrating SMART/ATA-Security in usb-storage driver] Douglas Gilbert
2005-11-08 13:51                             ` [usb-storage] [Merging ATA passthru] on integratingSMART/ATA-Security in usb-storage driver Pat LaVarre
2005-11-06 23:15             ` [usb-storage] [Merging ATA passthru] on integrating SMART/ATA-Security " James Bottomley
2005-11-07 18:14         ` Patrick Mansfield
2005-11-04 23:56     ` Andries Brouwer
2005-11-04 23:46 ` Pete Zaitcev
2005-11-05 16:20   ` thomas schorpp
2005-11-05 18:01     ` [usb-storage] [Merging ATA passthru] on integratingSMART/ATA-Security " Pat LaVarre
  -- strict thread matches above, loose matches on Subject: below --
2005-11-08 19:50 [usb-storage] [Merging ATA passthru] on integrating SMART/ATA-Security " Timothy Thelin
2005-11-09  9:04 ` thomas schorpp
2005-11-09  9:45   ` thomas schorpp
2005-11-09 10:05     ` thomas schorpp
2005-11-09 13:21     ` Mark Lord
2005-11-09 14:05       ` thomas schorpp
2005-11-07 20:18 Timothy Thelin
2005-11-07 17:51 Timothy Thelin
2005-11-02 22:18 Timothy Thelin
2005-11-02 23:22 ` thomas schorpp
2005-11-02 23:45 ` Matthew Dharm
2005-11-04  4:08   ` James Bottomley
2005-11-04 17:28     ` Matthew Dharm
2005-11-04 18:33       ` James Bottomley
2005-11-04 20:30         ` Matthew Dharm
2005-11-04 20:53           ` James Bottomley
2005-11-02 20:33 Timothy Thelin
2005-11-02 21:55 ` thomas schorpp
2005-11-02 14:08 thomas schorpp
2005-11-02 16:05 ` [usb-storage] " Alan Stern
2005-11-02 19:12   ` thomas schorpp
2005-11-02 19:26     ` Alan Stern
2005-11-02 20:41       ` thomas schorpp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1131401153.3333.6.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=Timothy.Thelin@wdc.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mdharm-usb@one-eyed-alien.net \
    --cc=patmans@us.ibm.com \
    --cc=stern@rowland.harvard.edu \
    --cc=t.schorpp@gmx.de \
    --cc=usb-storage@lists.one-eyed-alien.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.