From: "Michael Chan" <mchan@broadcom.com>
To: "Grant Grundler" <iod00d@hp.com>
Cc: "David S. Miller" <davem@davemloft.net>,
"Peter Chubb" <peterc@gelato.unsw.edu.au>,
netdev@oss.sgi.com
Subject: Re: TG3 fix for slow switches (Was: TG3 driver failure on HP 16-way)
Date: Tue, 31 May 2005 10:22:37 -0700 [thread overview]
Message-ID: <1117560157.4310.16.camel@rh4> (raw)
In-Reply-To: <20050531153819.GA20793@esmail.cup.hp.com>
On Tue, 2005-05-31 at 08:38 -0700, Grant Grundler wrote:
> Michael,
> Peter bounced this email to me after we talked about issues he was
> having with the rx8620 (HP 16-way ia64, sx1000 chipset) "IOX Core LAN".
> It sounded like the same problem I tracked down with rx8620 IOX Core LAN
> in March. Here is the summary :
>
> | In May, 2004, tg3 v3.4 changed how MAC_LED_CTRL (0x40c) was getting
> | programmed and how to determine what to program into LED_CTRL. The new
> | code trusted NIC_SRAM_DATA_CFG (0x00000b58) to indicate what to write
> | to LED_CTRL and MII EXT_CTRL registers. On "IOX Core Lan", SRAM was
> | saying MODE_MAC (0x0) and that doesn't work.
>
Thanks Grant, I'll chase this down and find a solution to this problem.
next prev parent reply other threads:[~2005-05-31 17:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-23 0:02 TG3 fix for slow switches (Was: TG3 driver failure on HP 16-way) Michael Chan
2004-12-23 4:31 ` David S. Miller
2005-05-31 15:38 ` Grant Grundler
2005-05-31 17:22 ` Michael Chan [this message]
2005-05-31 18:36 ` Grant Grundler
2005-05-31 17:42 ` Michael Chan
2005-05-31 19:03 ` Grant Grundler
2005-05-31 18:22 ` Michael Chan
-- strict thread matches above, loose matches on Subject: below --
2004-12-23 8:14 Michael Chan
2004-12-21 0:12 Peter Chubb
2004-12-21 0:15 ` David S. Miller
2004-12-21 1:11 ` Peter Chubb
2004-12-21 6:19 ` David S. Miller
2005-01-06 23:19 ` David S. Miller
2005-01-07 0:17 ` Darren Williams
2005-01-07 3:48 ` David S. Miller
2005-01-07 5:30 ` Darren Williams
2005-01-07 5:28 ` David S. Miller
2005-01-07 9:25 ` Darren Williams
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=1117560157.4310.16.camel@rh4 \
--to=mchan@broadcom.com \
--cc=davem@davemloft.net \
--cc=iod00d@hp.com \
--cc=netdev@oss.sgi.com \
--cc=peterc@gelato.unsw.edu.au \
/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).