On Fri, Mar 08, 2013 at 11:54:41AM +0200, Felipe Balbi wrote:
On Fri, Mar 08, 2013 at 05:38:53PM +0800, Peter Chen wrote:
On Thu, Mar 07, 2013 at 09:58:52AM +0100, Peter Bestler wrote:
Hi,
We try to get our device (based on p2020rdb) usb 2.0 compliant. We ran
the usb30cv test
Hi,
I tested your patch, Peter and it works fine. All tests of the usbcv30
are passing with my setup. Thank you so far.
So you get a tested-by: peter.best...@omicron.at
In my opinion we do it in the wrong order; we set the address before the
status stage
completes. But isn't the
On Thu, Mar 07, 2013 at 09:58:52AM +0100, Peter Bestler wrote:
Hi,
We try to get our device (based on p2020rdb) usb 2.0 compliant. We ran the
usb30cv test suite (version 1.0.1.2, chapter 9 tests for usb 2.0 devices) on
win7 with g_zero and g_serial. We access the device via an usb 3.0 hcd
On Fri, Mar 08, 2013 at 05:38:53PM +0800, Peter Chen wrote:
On Thu, Mar 07, 2013 at 09:58:52AM +0100, Peter Bestler wrote:
Hi,
We try to get our device (based on p2020rdb) usb 2.0 compliant. We ran the
usb30cv test suite (version 1.0.1.2, chapter 9 tests for usb 2.0 devices)
on win7
On Fri, Mar 08, 2013 at 11:54:41AM +0200, Felipe Balbi wrote:
On Fri, Mar 08, 2013 at 05:38:53PM +0800, Peter Chen wrote:
On Thu, Mar 07, 2013 at 09:58:52AM +0100, Peter Bestler wrote:
Hi,
We try to get our device (based on p2020rdb) usb 2.0 compliant. We ran
the usb30cv test
Peter Chen peter.c...@freescale.com writes:
On Thu, Mar 07, 2013 at 09:58:52AM +0100, Peter Bestler wrote:
Hi,
We try to get our device (based on p2020rdb) usb 2.0 compliant. We ran the
usb30cv test suite (version 1.0.1.2, chapter 9 tests for usb 2.0 devices) on
win7 with g_zero and
On Thu, Mar 07, 2013 at 09:58:52AM +0100, Peter Bestler wrote:
Hi,
We try to get our device (based on p2020rdb) usb 2.0 compliant. We ran the
usb30cv test suite (version 1.0.1.2, chapter 9 tests for usb 2.0 devices) on
win7 with g_zero and g_serial. We access the device via an usb 3.0 hcd