All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Tetsuo Handa <a5497108@anet.ne.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: TG3 doesn't work in kernel 2.4.27 (David S. Miller)
Date: Mon, 16 Aug 2004 14:38:24 -0700	[thread overview]
Message-ID: <20040816143824.15238e42.davem@redhat.com> (raw)
In-Reply-To: <200408162049.FFF09413.8592816B@anet.ne.jp>

On Mon, 16 Aug 2004 20:51:03 +0900
Tetsuo Handa <a5497108@anet.ne.jp> wrote:

>  From 2.4.26 till 2.4.27-rc3 were all OK.
> This trouble happens with 2.4.27-rc4 and later.

It's Sun's buggy 5704 Fiber auto-negotiation changes.

Here is a hacky possible fix, can you try it?

===== drivers/net/tg3.c 1.190 vs edited =====
--- 1.190/drivers/net/tg3.c	2004-07-21 14:14:20 -07:00
+++ edited/drivers/net/tg3.c	2004-08-16 14:24:53 -07:00
@@ -5266,6 +5266,8 @@
 	tw32_f(MAC_LOW_WMARK_MAX_RX_FRAME, 2);
 
 	if (GET_ASIC_REV(tp->pci_chip_rev_id) == ASIC_REV_5704 &&
+	    !(tp->pci_chip_rev_id == CHIPREV_ID_5704_A0 ||
+	      tp->pci_chip_rev_id == CHIPREV_ID_5704_A1) &&
 	    tp->phy_id == PHY_ID_SERDES) {
 		/* Enable hardware link auto-negotiation */
 		u32 digctrl, txctrl;

  reply	other threads:[~2004-08-16 21:42 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040816110000.1120.31256.Mailman@lists.us.dell.com>
2004-08-16 11:51 ` TG3 doesn't work in kernel 2.4.27 (David S. Miller) Tetsuo Handa
2004-08-16 21:38   ` David S. Miller [this message]
2004-08-25 17:48     ` Mike Waychison
2004-08-25 19:08       ` David S. Miller
2004-08-25 20:04         ` Mike Waychison
2004-08-26  0:58           ` David S. Miller
2004-08-26 10:49             ` Brian Somers
2004-08-26 19:37               ` David S. Miller
2004-08-29  9:56                 ` Pekka Pietikainen
2004-09-10 12:35                 ` Brian Somers
2004-09-10 19:40                   ` Roland Dreier
2004-09-10 20:53                   ` David S. Miller
2004-09-10 21:05                     ` Roland Dreier
2004-09-10 21:45                       ` David S. Miller
2004-09-10 22:14                     ` Brian Somers
2004-08-30 23:11               ` David S. Miller
2004-09-03 19:12                 ` Paul Larson
2004-09-03 19:19                   ` Mike Waychison
2004-09-03 20:18                     ` Roland Dreier
2004-09-03 20:30                       ` David S. Miller
2004-09-03 20:40                         ` Roland Dreier
2004-09-03 23:24                         ` Roland Dreier
2004-09-07 18:33                           ` Jake Moilanen
2004-09-07 19:52                             ` Roland Dreier
2004-09-08 12:34                               ` Jake Moilanen
2004-09-08 13:07                                 ` Anton Blanchard
2004-09-13 22:48                                   ` David S. Miller
2004-09-14 22:20                                     ` Mike Waychison
2004-09-14 22:36                                       ` David S. Miller
2004-09-14 22:58                                       ` Jake Moilanen
2004-09-15  0:34                                       ` Roland Dreier
2004-09-08 13:55                                 ` Paul Larson
2004-09-10 16:00                                   ` Paul Larson
2004-09-03 20:08                   ` David S. Miller

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=20040816143824.15238e42.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=a5497108@anet.ne.jp \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.