On 21/09/16 17:44, Greg KH wrote:
On Wed, Sep 21, 2016 at 06:34:03PM +0200, Oliver Neukum wrote:
On Thu, 2016-08-18 at 13:50 +0300, Binyamin Sharet wrote:
On 08/18/2016 01:31 PM, Oliver Neukum wrote:
On Wed, 2016-08-17 at 14:34 +0300, Binyamin Sharet wrote:
After connecting such a device, NULL pointer dereference in the
You may need to connect another device or two after this one to
<< Attached: 160a_3184_dmesg_1.log >>
<< Attached: 160a_3184_dmesg_2.log >>
this fell through the cracks somehow. Does anybody know how
these devices should be to work with the driver?
Which device was this? I'm slowly working on a patchset to move this
type of checking to the USB core to hopefully prevent this type of thing
from have to be added to each USB driver individually.
It's the VT6656.
The problem cannot be reproduced here on the Raspberry PI 2.
Looking at those logs it looks like the device reset during firmware
Is the PSU for PI up to job?
The device is power hungry, I am using a 2.4A @5v power supply.
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html