On Sat, 24 Oct 2009, [UTF-8] Ozan Ã?aÄ?layan wrote: > Alan Stern wrote: > > Okay, that proves this really is a timing bug in the hardware. But we > > can't go around putting 2-millisecond delays in the kernel! Maybe you > > can test to see if smaller delays will fix the problem. If 50 > > microseconds or less doesn't work then it will be necessary to add a > > new timer to ehci-hcd. > > > > Okay I'll check with smaller values there but I couldn't get the meaning > of "if 50 us or less doesn't work then it will be necessary to add a new > timer to ehci-hcd". If everything works with a delay of 50 us or less then we probably can just put the udelay() statement into the kernel. If it doesn't (for example, if the delay has to be longer than 100 us) then we can't -- the delay would be too long. Instead we will have to add a new timer. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
