Comment 8 for bug 325581

Thanks for posting this patch, I'm kicking myself for not seeing this earlier. I would like to see this vetted by upstream since it changes behavior for all devices not just this specific one, so it could introduce regressions; for that reason I am going to hold off on it for Karmic.

I think it might be ok to include for Lucid, however even more preferable would be to fix this in the kernel so it's not necessary to work around it at all. For that reason I've added a kernel task. If the kernel team doesn't solve it directly, I'll look into the workaround further hopefully before Lucid ships. If you don't hear from me within a few months on this, give me a ping.