From: Alan Stern <stern@rowland.harvard.edu>
To: DocMAX <mail@vacharakis.de>
Cc: linux-usb@vger.kernel.org
Subject: Re: Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
Date: Fri, 12 Nov 2021 12:51:50 -0500 [thread overview]
Message-ID: <20211112175150.GA37212@rowland.harvard.edu> (raw)
In-Reply-To: <bfc48a4a-9648-dee8-20b0-dadfafa508e7@vacharakis.de>
On Fri, Nov 12, 2021 at 05:26:17PM +0100, DocMAX wrote:
> Sure:
>
> Bus 006 Device 006: ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 3.10
> bDeviceClass 0
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 9
> idVendor 0x2109 VIA Labs, Inc.
> idProduct 0x0715 VL817 SATA Adaptor
> bcdDevice 6.14
> iManufacturer 1 VIA Labs,Inc.
> iProduct 2 USB3.1 SATA Bridge
> iSerial 3 0000000000000004
Wow. Judging by the serial number values, you got the first four
devices of this sort ever made. (That is, unless they use the same
serial numbers on all of their devices!)
Anyway, the patch below should accomplish the same effect as the
module parameter override you've been using. Let us know if it works
properly.
Alan Stern
Index: usb-devel/drivers/usb/storage/unusual_devs.h
===================================================================
--- usb-devel.orig/drivers/usb/storage/unusual_devs.h
+++ usb-devel/drivers/usb/storage/unusual_devs.h
@@ -2291,6 +2291,13 @@ UNUSUAL_DEV( 0x2027, 0xa001, 0x0000, 0x
USB_SC_DEVICE, USB_PR_DEVICE, usb_stor_euscsi_init,
US_FL_SCM_MULT_TARG ),
+/* Reported by DocMAX <mail@vacharakis.de> */
+UNUSUAL_DEV( 0x2109, 0x0715, 0x0614, 0x0614,
+ "VIA Labs, Inc.",
+ "VL817 USB3.1 SATA Bridge",
+ USB_SC_DEVICE, USB_PR_DEVICE, NULL,
+ US_FL_IGNORE_UAS),
+
UNUSUAL_DEV( 0x2116, 0x0320, 0x0001, 0x0001,
"ST",
"2A",
next prev parent reply other threads:[~2021-11-12 17:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 9:37 Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor" DocMAX
2021-11-12 15:40 ` Alan Stern
2021-11-12 16:04 ` DocMAX
2021-11-12 16:23 ` Alan Stern
2021-11-12 16:26 ` DocMAX
2021-11-12 17:51 ` Alan Stern [this message]
2021-11-12 18:21 ` DocMAX
2021-11-12 20:49 ` Alan Stern
2021-11-12 20:57 ` DocMAX
2021-11-13 15:46 ` Alan Stern
2021-11-13 20:51 ` DocMAX
2022-01-20 7:28 Thomas Weißschuh
2022-01-20 7:46 ` Greg KH
2022-01-20 14:42 ` Alan Stern
2022-01-20 17:39 ` Thomas Weißschuh
2022-01-20 17:56 ` Alan Stern
2022-01-21 20:39 ` Thomas Weißschuh
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=20211112175150.GA37212@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=linux-usb@vger.kernel.org \
--cc=mail@vacharakis.de \
/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.