Re: USB mass-storage devices and READ CAPACITY(16)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 20 Jun 2012, Josh Boyer wrote:

> Alan Stern <stern@...> writes:
> > > > That certainly sound reasonable to me. Note that the 071b:3203 really
> > > > needs the US_FL_NO_READ_CAPACITY_16 flag though, as it wrongly reports
> > > > a capacity of -1 when there is no sd card in its slot, and in response
> > > > to that the kernel tries READ CAPACITY(16) and things go downhill
> > > > from there...
> > > 
> > > Yes, we need to be able to have both flags set for the same device.  
> > > For that card reader they would mean try READ CAPACITY(10) first, and 
> > > if it fails, don't try READ CAPACITY(16).
> > 
> > In other words, I'm suggesting we adopt this patch and get rid Hans's 
> > new unusual_devs entry.
> > 
> > Alan Stern
> 
> This patch solves an issue we hit in Fedora as well.  Will you be sending a
> proper patch for 3.5 with stable CC'd?

Since nobody has objected, yes, I will.  In the near future.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux