[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7f670cac-aa36-4bb9-a2b1-4451e4e85fab@rowland.harvard.edu>
Date: Sat, 11 Mar 2023 11:54:33 -0500
From: Alan Stern <stern@...land.harvard.edu>
To: Yaroslav Furman <yaro330@...il.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-usb@...r.kernel.org, usb-storage@...ts.one-eyed-alien.net,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] uas: Add US_FL_NO_REPORT_OPCODES for JMicron JMS583Gen 2
On Sat, Mar 11, 2023 at 02:34:18PM +0200, Yaroslav Furman wrote:
> Just like other JMicron JMS5xx enclosures, it chokes on report-opcodes,
> let's avoid them.
>
> Tested-and-reported-by: Yaroslav Furman <yaro330@...il.com>
> Signed-off-by: Yaroslav Furman <yaro330@...il.com>
> ---
> drivers/usb/storage/unusual_uas.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/usb/storage/unusual_uas.h b/drivers/usb/storage/unusual_uas.h
> index c7b763d6d102..e4ff28ba93e5 100644
> --- a/drivers/usb/storage/unusual_uas.h
> +++ b/drivers/usb/storage/unusual_uas.h
> @@ -97,6 +97,13 @@ UNUSUAL_DEV(0x152d, 0x0539, 0x0000, 0x9999,
> USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> US_FL_NO_REPORT_OPCODES),
>
> +/* Reported by: Yaroslav Furman <yaro330@...il.com> */
> +UNUSUAL_DEV(0x152d, 0x0583, 0x0000, 0x9999,
> + "JMicron",
> + "JMS583Gen 2",
> + USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> + US_FL_NO_REPORT_OPCODES),
> +
The new entry should be inserted in the correct location, according to
the ordering by vendor ID and product ID. (Hint: 0x583 > 0x567.)
> /* Reported-by: Claudio Bizzarri <claudio.bizzarri@...il.com> */
> UNUSUAL_DEV(0x152d, 0x0567, 0x0000, 0x9999,
> "JMicron",
Alan Stern
Powered by blists - more mailing lists