On 07/06/2015 07:13 PM, Greg KH wrote:
But, have you tried the in-kernel driver for this device?
Hi Greg! Yes, I have. Sorry for not making this clear. The symptoms are as described in bug #57171. I haven't tested it again in recent months but I can do that for you when I'm back home if you want.
I too would very much prefer to see the in-kernel driver fixed. It doesn't seem to be happening, though. I don't have the specific knowledge to help fix it.
I share your misgivings about having redundant drivers. My idea was that maybe we could restrict this alternate driver to USB device IDs that are known to work well with it but not with the in-kernel driver, at least until the in-kernel driver is fixed, since the main issue here is that the in-kernel driver currently doesn't support those devices even though it claims to.
This is only a stopgap that isn't meant to stay indefinitely, though. It's a generally very unsatisfying solution, but I don't know how else to keep those devices supported until the in-kernel driver is fixed.
Mind you, if this discussion unlocks things and the in-kernel driver gets fixed, that's definitely the best outcome as far as I'm concerned. :)
Cheers, -- P. _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
