> Hi David. Has there been any progress on this issue?
>
> (thread at http://marc.theaimsgroup.com/?t=111749614000002&r=1&w=2)
Taking a look at that, I found one case that _might_ explain it. That
scenario could crop more (or less) based on loads and timings, and I've
suspected that the VIA chips have significantly different timings for
certain things. This patch handles that case differently, just expecting
the unlink completion code (later) to restart the schedule.
I sanity tested this, but that's all.
- Dave
--- g26.orig/drivers/usb/host/ehci-q.c 2005-09-12 17:58:21.000000000 -0700
+++ g26/drivers/usb/host/ehci-q.c 2005-09-14 10:26:07.000000000 -0700
@@ -781,7 +781,7 @@ static void qh_link_async (struct ehci_h
/* (re)start the async schedule? */
head = ehci->async;
timer_action_done (ehci, TIMER_ASYNC_OFF);
- if (!head->qh_next.qh) {
+ if (!head->qh_next.qh && !ehci->reclaim) {
u32 cmd = readl (&ehci->regs->command);
if (!(cmd & CMD_ASE)) {
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |