Re: JMicron 20337 (152d:2338) and 3TB

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

 



On Thu, Aug 30, 2012 at 11:47 PM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote:
> On Thu, 30 Aug 2012, Alon Bar-Lev wrote:
>
>> Thank you!
>>
>> I will test this and report back.
>>
>> As this is in scsi layer, I guess it does not get the USB
>> vendor:product to automatically apply this workaround... :(
>
> I don't entirely understand this comment.  But it is true that the
> patch will affect every USB storage device, not just the JMicron 20337.
>
> Alan Stern
>

I was trying to figure out if there can be automatic workaround based
on USB vendor:product... If these exposed at this point then a patch
can be written to effect only this device.

I never traced the scsi module, but scsi_device does contain vendor,
model and rev, maybe these can be mapped to the JMicron 20337 device
and apply the workaround.

Just a though...

Thank you very much,
Alon
--
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