From: Grant Grundler <iod00d@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: ethtool -d MCAs rx2600
Date: Thu, 29 Jan 2004 19:18:37 +0000 [thread overview]
Message-ID: <20040129191837.GE13404@cup.hp.com> (raw)
In-Reply-To: <20040123231254.GC31911@cup.hp.com>
On Mon, Jan 26, 2004 at 12:39:42PM -0500, Jeff Garzik wrote:
> I get lockups occasionally on x86 too, but have had higher priority
> things to look at. Since regdump is mainly an engineer's tool, we felt
> it was a "use at your own risk" feature.
>
> But if we can fix it, all the better.
tg3_get_regs() is reading registers that don't exist.
Neither HPUX nor tru64 drivers attempt to touch NVRAM on BCM5700/1 chips.
And tg3 in most other places doesn't either.
It just needs to check TG3_FLAG_NVRAM before reading NVRAM regs.
Jack, you also using the bcm5701 chip?
Jeff, please apply. Following patch is against 2.6.2-rc2.
thanks,
grant
=== drivers/net/tg3.c 1.81 vs edited ==--- 1.81/drivers/net/tg3.c Wed Dec 31 23:40:32 2003
+++ edited/drivers/net/tg3.c Thu Jan 29 10:19:46 2004
@@ -5904,7 +5904,9 @@
GET_REG32_LOOP(MSGINT_MODE, 0x0c);
GET_REG32_1(DMAC_MODE);
GET_REG32_LOOP(GRC_MODE, 0x4c);
- GET_REG32_LOOP(NVRAM_CMD, 0x24);
+ if (tp->tg3_flags & TG3_FLAG_NVRAM) {
+ GET_REG32_LOOP(NVRAM_CMD, 0x24);
+ }
#undef __GET_REG32
#undef GET_REG32_LOOP
next prev parent reply other threads:[~2004-01-29 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 23:12 ethtool -d MCAs rx2600 Grant Grundler
2004-01-23 23:56 ` Grant Grundler
2004-01-26 16:30 ` Jack Steiner
2004-01-26 16:58 ` Matthew Wilcox
2004-01-26 17:39 ` Jeff Garzik
2004-01-29 19:18 ` Grant Grundler [this message]
2004-01-29 20:41 ` Jack Steiner
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=20040129191837.GE13404@cup.hp.com \
--to=iod00d@hp.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox