netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: John Wong <kernel@implode.net>
Cc: c-d.hailfinger.kernel.2004@gmx.net, netdev@oss.sgi.com
Subject: Re: forcedeth and kernel 2.6.5 has "no link"
Date: Fri, 16 Apr 2004 21:06:40 +0200	[thread overview]
Message-ID: <40802EC0.2070108@colorfullife.com> (raw)
In-Reply-To: <20040416183844.GA2923@gambit.implode.net>

[-- Attachment #1: Type: text/plain, Size: 547 bytes --]

John Wong wrote:

>Under kernel 2.6.4, ethtool reports:
>
>Settings for eth0:
>        Link detected: yes
>
>This is with forcedeth 0.23
>
>Under kernel 2.6.5, ethtool reports:
>
>Settings for eth0:
>        Supports Wake-on: g
>        Wake-on: d
>        Link detected: no
>
>This is with forcedeth 0.25
>  
>
Odd. I'm not aware of any changes that might cause that difference. I'll 
check the diff.

>I had submitted the bugzilla id 2283.  2496 is something that I am
>experiencing too.
>  
>
Could you try the attached patch?


--
    Manfred

[-- Attachment #2: patch-forced-test --]
[-- Type: text/plain, Size: 607 bytes --]

--- 2.6/drivers/net/forcedeth.c	2004-04-10 09:52:45.000000000 +0200
+++ build-2.6/drivers/net/forcedeth.c	2004-04-13 18:58:59.000000000 +0200
@@ -1263,6 +1263,14 @@
 				dev->name, id1, id2, i);
 		np->phyaddr = i;
 
+		if (id1 == 0x0015 && (id2 &0xfff0) == 0xf440) {
+			printk(KERN_DEBUG "%s: open: Found ICS, applying workaround.\n", dev->name);
+        		/* workaround for ICS1893 PHY */
+            		mii_rw(dev, i, 0x0018, 0xD200);
+			set_current_state(TASK_UNINTERRUPTIBLE);
+			schedule_timeout(HZ);
+		}
+
 		spin_lock_irq(&np->lock);
 		nv_update_linkspeed(dev);
 		spin_unlock_irq(&np->lock);

  reply	other threads:[~2004-04-16 19:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-16 18:38 forcedeth and kernel 2.6.5 has "no link" John Wong
2004-04-16 19:06 ` Manfred Spraul [this message]
2004-04-17 20:20   ` John Wong

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=40802EC0.2070108@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=c-d.hailfinger.kernel.2004@gmx.net \
    --cc=kernel@implode.net \
    --cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).