Hi HPS,
Hi Kohji,
Can you test the attached patch? Does it make any difference for your WD HDD
USB 3.0 enumeration?
--HPS
I'm sorry for my late response.
We tried your patch, although the U1 state transition wasn't found in
the USB bus log, the HDD was not recognized correctly.
Thanks,
Hi HPS,
On 03/30/15 10:54, Hans Petter Selasky wrote:
On 03/30/15 06:54, Kohji Okuno wrote:
Hi HPS
I have a question.
Why do we try to enter U1 mode in SuperSpeed?
This is the following codes(***)
In our proprietary environmen(This has a xHCI controller), when a
device accept U1, the
On 03/30/15 11:36, Kohji Okuno wrote:
Hi HPS,
I will try programming values 0xFF.
By the way, why should we set these timeout value?
I think, we don't have to change from default values (U1 Timeout = 0,
U2 Timeout= 0).
Hi,
I think the default '0' is the same like '255' - disable power save?
On 03/30/15 06:54, Kohji Okuno wrote:
Hi HPS
I have a question.
Why do we try to enter U1 mode in SuperSpeed?
This is the following codes(***)
In our proprietary environmen(This has a xHCI controller), when a
device accept U1, the device may be strange status. Acutually, when I
tried to
On 03/30/15 10:54, Hans Petter Selasky wrote:
On 03/30/15 06:54, Kohji Okuno wrote:
Hi HPS
I have a question.
Why do we try to enter U1 mode in SuperSpeed?
This is the following codes(***)
In our proprietary environmen(This has a xHCI controller), when a
device accept U1, the device may be
On 03/30/15 11:19, Hans Petter Selasky wrote:
On 03/30/15 10:54, Hans Petter Selasky wrote:
On 03/30/15 06:54, Kohji Okuno wrote:
Hi HPS
I have a question.
Why do we try to enter U1 mode in SuperSpeed?
This is the following codes(***)
In our proprietary environmen(This has a xHCI
Hi Kohji,
Can you test the attached patch? Does it make any difference for your WD
HDD USB 3.0 enumeration?
--HPS
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to
