On Thu, 2005-09-08 at 13:58, Bogdan Costescu wrote:
Can the original poster give an explanation ? I've enjoyed a rather
well functioning 3c59x driver for the past ~6 years without such
double reading. Plus:
- this operation is I/O expensive
- it is performed inside a region protected by a spinlock
- it is performed often, every 60 seconds
Is there some specific hardware that exhibits a problem that is solved
by this double reading ?
Nothing critical. The idea is to avoid an extra delay of 60 seconds
before detecting link-up.
Please see http://bugzilla.kernel.org/show_bug.cgi?id=5025
-Tommy