Renesas 3.0 Windows 10 Driver

broken image
broken image

If USB devices send the descriptor with invalid size, driver might behave in undefined operation.Ģ-6.

broken image

Driver did not check the descriptor size. – The PERSTB of the system is asserted after resume.Ģ-5. – C_PORT_CONNECTION of the downstream port of the hub is not changed after resume. This issue occurs only under the following conditions: USB3.0 Devices connected with USB3.0 HUB are not detected after S3/S4 resume. We have never seen this BSOD on the real system. There is a possibility of BSOD when OverCurrent indication occurs before WindowsOS detects the device. There is a possibility of BSOD when a user changes the resolution of the video capture application and an ISO device is disconnected. We found this on code review.V2.1.16.0 or later version includes this bug.Ģ-2. Short packet is out of this issue.We have never seen this BSOD on the real system. There is a possibility of BSOD when OUT transaction with data shorter than 8byte is transferred. HUB’s icon isn’t shown on the Devices and Printers of Windows7.Ģ-1.

broken image

IOCTL_USB_USER_REQUEST(UWSBUSER_GET_POWER_STATE_MAP) is supported.ġ-2.

broken image