On 20/11/2015 17:08, Alan Stern wrote:
> On Fri, 20 Nov 2015, Dmitry Katsubo wrote:
>
>> From: Dmitry Katsubo <dmitry.kats...@gmail.com>
>>
>> The patch extends the family of SATA-to-USB JMicron adapters that need
>> FUA to be disabled and applies the same p
From: Dmitry Katsubo <dmitry.kats...@gmail.com>
The patch extends the family of SATA-to-USB JMicron adapters that need
FUA to be disabled and applies the same policy for uas driver.
See details in http://unix.stackexchange.com/questions/237204/
Signed-off-by: Dmitry Katsubo <dm
On 2015-11-17 19:18, Alan Stern wrote:
> That line is completely inappropriate for uas; it applies only to
> usb-storage. Don't add it.
I got it. My first thought was like you have said (every module uses its
own structure), but I blindly tried to guess.
> Here you need to test devinfo->flags
On 2015-11-12 13:09, Dmitry Katsubo wrote:
> On 2015-11-11 16:16, Alan Stern wrote:
>>> Bus 001 Device 007: ID 152d:0567 JMicron Technology Corp. / JMicron USA
>>> Technology Corp.
>>> Device Descriptor:
>>>bLength18
>>
On 2015-11-11 16:16, Alan Stern wrote:
>> Bus 001 Device 007: ID 152d:0567 JMicron Technology Corp. / JMicron USA
>> Technology Corp.
>> Device Descriptor:
>>bLength18
>>bDescriptorType 1
>>bcdUSB 2.10
>>bDeviceClass0 (Defined at
On 10/11/2015 16:00, Alan Stern wrote:
On Tue, 10 Nov 2015, Dmitry Katsubo wrote:
Hello everyone,
Sorry for cross-posting from linux-s...@vger.kernel.org
In continuation to the issue described in [1] and [2]:
Unfortunately, I still suffer from the same problem on Linux kernel
v4.2.3
Hello everyone,
Sorry for cross-posting from linux-s...@vger.kernel.org
In continuation to the issue described in [1] and [2]:
Unfortunately, I still suffer from the same problem on Linux kernel
v4.2.3. The problem is in detailed described in [3], in particular I see
the following in dmesg:
