Comment 27 for bug 1716301

forget to mention test result:
same vendor request failed with -110 event long timeout

BTW, this looks like this is a bad adapter, however, I tried this adapter in Win10, it definitely can work.
In Windows, it must install dirver files from another company named Tplink, but from lsusb, its chip is from Ralink, whether the Tplink driver in Win10 might use some different vendor specific request ? I meant, Tplink driver uses some different request to implement some function, however, Tplink still uses Ralink USB id(146f:7601), so, if this, timeout (-110) will occur.