| commit | 513b6bee0156812bce4f38c497dfc7cf9ee9a609 | |
| author | Ben Dooks <ben-linux@fluff.org> | |
| Tue, 5 Feb 2008 00:02:22 +0000 (5 00:02 +0000) | ||
| committer | Jeff Garzik <jeff@garzik.org> | |
| Mon, 11 Feb 2008 16:06:36 +0000 (11 11:06 -0500) | ||
| tree | c4ace2c39a97a610ff8cde80a73e13ef58d41f9a | treesnapshot (tar.gz zip) |
| parent | f42d8aeaf9a32ec130bc99f2e4ba84cafb028244 | commitdiff |
DM9000: Update retry count whilst identifying chip
Reading the ID register does not always return the correct ID
from the device, so we retry several times to see if we get
a correct value.
These failures seem to be excaserbated by the speed of the
access to the chip (possibly time between issuing the address
and then the data cycle).
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
Reading the ID register does not always return the correct ID
from the device, so we retry several times to see if we get
a correct value.
These failures seem to be excaserbated by the speed of the
access to the chip (possibly time between issuing the address
and then the data cycle).
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
| drivers/net/dm9000.c | diffblobblamehistory |