On Mon, 22 Sep 2003, Christoph Hellwig wrote:

> If we want drivers to mess with blist flags that's the more general
> solution, yes.  But the blist flags really are a target thing and
> I'd prefer to keep host drivers a bit away from this.  Of course
> this doesn't really work for the usb case where the host driver only
> deals with emulated targets that are all completly hosed.
> 
> Maybe sdev->scsi_level should recognize a new level, SCSI_TOTALLY_B0RKED
> for those usb-storage devices where the vendor somehow heard of the
> spec but nothing that isn't excercised by the windows drivers has
> the slightest chance of working..

Please be careful when setting this up.  The mode-sense pages are vitally
important for USB CD devices, and they all seem to work fine.  It's just
the disk-type devices that have been causing trouble.

Many of them seem to share the failure mode observed by Linus: when asked
to send 128 bytes of m-s page 8 they apparently forget that the connection
is only full-speed with a 64-byte packet maximum, and they try to send all
128 bytes in a single packet.  But other failure modes have cropped up as
well.

Alan Stern



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to