On Mon, May 22, 2000, Donald Becker <becker@scyld.com> wrote:
; > changes so you might not satisfy the minimal clock frequency
; > specification.
;
; The very old code used eeprom_delay(100), which mean 100ns, *not* 100usec.
Now I am confused.
If I greep the driver that was in 2.2.6 kernel I get
visitor@earth:~/work/net/kernels > grep eeprom_delay linux-2.2.6/drivers/net/eepro100.c
#define eeprom_delay(nanosec) udelay(1);
eprom_delay(100);
eprom_delay(150);
eprom_delay(100);
eprom_delay(100);
visitor@earth:~/work/net/kernels >
So the "nanosec" parameter gets trashed and you delay
for 1 us in all of the cases.
-
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/
This archive was generated by hypermail 2b29 : Tue May 23 2000 - 21:00:23 EST