[PATCH?] e100: 'cu_start: timeout waiting for cu'

• Next message: Ryan Anderson: "[PATCH][SPARSE] Runtime detection of gcc include paths"
• Previous message: Greg KH: "Re: USB Scanner Problem"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

e100 version 2.3.13-k1 added in 2.5.70 does not work in my system
(dual ppro, eepro100b card). dmesg says:

e100: eth0: cu_start: timeout waiting for cu

I tracked the problem to the reset changes in e100_phy.c. The patch
below solves the problem for me, as does removing the new e100_phy_reset()
call altogether. I've little clue what the right fix is, so this may be
totally bogus.

--Adam

--- linux-2.5.70/drivers/net/e100/e100_phy.c Tue May 27 18:20:46 2003
+++ linux-2.5.70-play/drivers/net/e100/e100_phy.c Sun Jun 8 20:33:47 2003
@@ -919,6 +919,7 @@
 unsigned char __devinit
 e100_phy_init(struct e100_private *bdp)
 {
+ e100_phy_reset(bdp);
         e100_phy_address_detect(bdp);
         e100_phy_isolate(bdp);
         e100_phy_id_detect(bdp);
@@ -930,7 +931,6 @@
         bdp->PhyDelay = 0;
         bdp->zlock_state = ZLOCK_INITIAL;
 
- e100_phy_reset(bdp);
         e100_phy_set_speed_duplex(bdp, false);
         e100_fix_polarity(bdp);
 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Ryan Anderson: "[PATCH][SPARSE] Runtime detection of gcc include paths"
• Previous message: Greg KH: "Re: USB Scanner Problem"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Jun 15 2003 - 22:00:19 EST