Do you like another one (me) testing this patch?
Is there a way to determine WHY the transmit wasn't done within 50 ticks?
I've seen that more but not all transmissions succeed when i set the timeout
to 500 ticks. (This was during kernel 2.1.105, i haven't checked the timeout
with the pre kernels.)
As i understand it, the only difference between pcnet32.c and lance.c is
the 32bit access. But i've seen that lance.c reports `no DMA needed' during
and boot and it shows no problems when i simultaneously serve ppp0 and eth0.
Does this `no DMA needed' mean anything?
Maybe it's the same problem as with the lance.c driver when it reports
"Tx FIFO error! Status a2e2.".
Alan Cox said
> That means that the device is having problems because it is being held off
> the bus for too long.
Bye,
Mark
+-----------------------------------------------------+----------------------+
| the wizard himself, Mark-André Hopf | Every sufficiently |
| hopf@informatik.uni-rostock.de | developed technology |
| Visit the TOAD GUI Toolkit Project Homepage at | is indistinguishable |
| http://toad.home.pages.de/ | from magic. (A.C.C.) |
+-----------------------------------------------------+----------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/