-
Olof Johansson authored
It was mistakenly set to interrupt on the second packet instead of first, causing some interesting latency behaviour. Signed-off-by:
Olof Johansson <olof@lixom.net> Signed-off-by:
Jeff Garzik <jeff@garzik.org>
7c00db3d
It was mistakenly set to interrupt on the second packet instead of first, causing some interesting latency behaviour. Signed-off-by:Olof Johansson <olof@lixom.net> Signed-off-by:
Jeff Garzik <jeff@garzik.org>