From: Adam Kropelin <akropel1@rochester.rr.com>
To: scott.feldman@intel.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH?] e100: 'cu_start: timeout waiting for cu'
Date: Sun, 8 Jun 2003 20:21:29 -0400 [thread overview]
Message-ID: <20030608202129.A18754@mail.kroptech.com> (raw)
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);
reply other threads:[~2003-06-09 0:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030608202129.A18754@mail.kroptech.com \
--to=akropel1@rochester.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.feldman@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox