public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: "linux kernel" <linux-kernel@vger.kernel.org>,
	alan@lxorguk.ukuu.org.uk, " Mads Martin Jørgensen" <mmj@suse.com>
Subject: Re: 2.4.4-ac8 doesn't work with Lite-On 82c168 PNIC rev 32
Date: Fri, 11 May 2001 20:53:23 -0400	[thread overview]
Message-ID: <3AFC8983.3FDB9513@mandrakesoft.com> (raw)
In-Reply-To: <20010511165749.B12289@lucon.org> <3AFC8896.47AA1481@mandrakesoft.com>

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

Here's another patch to try, for PNIC.  Feedback welcome.
-- 
Jeff Garzik      | Game called on account of naked chick
Building 1024    |
MandrakeSoft     |

[-- Attachment #2: patch-pnic --]
[-- Type: text/plain, Size: 743 bytes --]

diff -ur 2.4/drivers/net/tulip/media.c build-2.4/drivers/net/tulip/media.c
--- 2.4/drivers/net/tulip/media.c	Fri May 11 22:12:51 2001
+++ build-2.4/drivers/net/tulip/media.c	Fri May 11 22:10:03 2001
@@ -409,8 +409,6 @@
 	struct tulip_private *tp = dev->priv;
 	unsigned int bmsr, lpa, negotiated, new_csr6;
 
-	if (tp->full_duplex_lock)
-		return 0;
 	bmsr = tulip_mdio_read(dev, tp->phys[0], MII_BMSR);
 	lpa = tulip_mdio_read(dev, tp->phys[0], MII_LPA);
 	if (tulip_debug > 1)
@@ -428,7 +426,7 @@
 		}
 	}
 	negotiated = lpa & tp->advertising[0];
-	tp->full_duplex = (mii_nway_result(negotiated) & LPA_DUPLEX) ? 1 : 0;
+	tp->full_duplex = tp->full_duplex_lock | (mii_nway_result(negotiated) & LPA_DUPLEX) ? 1 : 0;
 
 	new_csr6 = tp->csr6;
 

      reply	other threads:[~2001-05-12  0:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-11 23:57 2.4.4-ac8 doesn't work with Lite-On 82c168 PNIC rev 32 H . J . Lu
2001-05-12  0:49 ` Jeff Garzik
2001-05-12  0:53   ` Jeff Garzik [this message]

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=3AFC8983.3FDB9513@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hjl@lucon.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmj@suse.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