On Tue, Aug 10, 2010 at 09:04:03PM -0400, Dave Mielke wrote: > [quoted lines by Greg KH on 2010/08/10 at 16:19 -0700] > > >Ick, I've heard of this happening before on some devices, but I thought > >we had fixed all of these a long time ago. > > It did used to work right - as late as in what Debian calls 2.6.32-3. So, if > you mean further back than that, then it was working. This problem was first > seen when the user upgraded to what Debian calls 2.6.32-5. I don't know about > 2.6.32-4. Wierd, that kind of implies we messed something up in the driver then. > >Can this user test a patch out if I create one? If so, try the > >one below please. > > I shall ask him if he feels capable of doing that. Which kernel did you make > this patch against? It's against something that should be close to 2.6.35, but should apply cleanly to .32 I suppose. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
