Hi, On Mon, Nov 9, 2015 at 1:57 AM, Yunzhi Li <lyz@xxxxxxxxxxxxxx> wrote: > It seems that we are debugging two different issues, your new patch which > rewrite > the microframe scheduler doesn't resolve my problem. My patch fix chrome-os > issue > #46547 not related to the particular Microsoft keyboard any keyboard could > be used > to reproduce the issue. As far as I can tell my microframe rewrite patch is totally a no-op (it doesn't do anything useful at all). I'll try to write some test code showing why I think the old function is broken and why the new one works, but my new version doesn't fix any known issues. Whatever the problem is with the Microsoft keyboard is still unknown. I'll try to dig into it more today. I think I'm starting to understand enough about how USB works that I might be able to make sense of the analyzer trace now too. I can also post a screenshot of that... -Doug -- 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
