From: "David S. Miller" <davem@redhat.com>
To: rkuhn@e18.physik.tu-muenchen.de
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at tg3.c:1557
Date: Wed, 07 Aug 2002 07:48:38 -0700 (PDT) [thread overview]
Message-ID: <20020807.074838.106638568.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0208071646570.3705-100000@pc40.e18.physik.tu-muenchen.de>
From: Roland Kuhn <rkuhn@e18.physik.tu-muenchen.de>
Date: Wed, 7 Aug 2002 16:49:24 +0200 (CEST)
Sorry, same problem as before. It looks like the spinlocked write method
does not work on the BCM5701 chip :-(
I'm still not entirely convinced of this :-)
Backout all of your changes and try this patch instead:
--- drivers/net/tg3.c.~1~ Wed Aug 7 07:56:39 2002
+++ drivers/net/tg3.c Wed Aug 7 07:57:08 2002
@@ -173,8 +173,18 @@
}
}
+static void tg3_write_mailbox_reg32(struct tg3 *tp, u32 off, u32 val)
+{
+ unsigned long flags;
+
+ spin_lock_irqsave(&tp->indirect_lock, flags);
+ pci_write_config_dword(tp->pdev, TG3PCI_REG_BASE_ADDR, off);
+ pci_write_config_dword(tp->pdev, TG3PCI_REG_DATA, val);
+ spin_unlock_irqrestore(&tp->indirect_lock, flags);
+}
+
#define tw32(reg,val) tg3_write_indirect_reg32(tp,(reg),(val))
-#define tw32_mailbox(reg, val) writel(((val) & 0xffffffff), tp->regs + (reg))
+#define tw32_mailbox(reg, val) tg3_write_mailbox_reg32(tp,(reg),(val))
#define tw16(reg,val) writew(((val) & 0xffff), tp->regs + (reg))
#define tw8(reg,val) writeb(((val) & 0xff), tp->regs + (reg))
#define tr32(reg) readl(tp->regs + (reg))
next prev parent reply other threads:[~2002-08-07 14:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 11:40 kernel BUG at tg3.c:1557 Roland Kuhn
2002-08-07 13:14 ` Alan Cox
2002-08-07 12:03 ` David S. Miller
2002-08-07 14:25 ` Roland Kuhn
2002-08-07 14:20 ` David S. Miller
2002-08-07 14:49 ` Roland Kuhn
2002-08-07 14:48 ` David S. Miller [this message]
2002-08-07 15:36 ` Roland Kuhn
2002-08-07 15:24 ` David S. Miller
2002-08-07 16:28 ` Roland Kuhn
2002-08-07 19:18 ` [SOLVED] " Roland Kuhn
2002-08-07 19:43 ` Roland Kuhn
2002-08-07 12:22 ` kernel
2002-08-07 13:08 ` Willy Tarreau
2002-08-07 19:52 ` kwijibo
2002-08-07 19:53 ` Roland Kuhn
2002-08-07 21:41 ` kwijibo
2002-08-07 22:10 ` Roland Kuhn
2002-08-07 22:40 ` David S. Miller
2002-08-08 8:33 ` Roland Kuhn
2002-08-08 12:39 ` Roland Kuhn
2002-08-08 15:32 ` David S. Miller
2002-08-30 23:43 ` David S. Miller
2002-09-11 9:11 ` Roland Kuhn
2002-09-18 13:57 ` Ryan Sweet
2002-08-07 23:42 ` Alan Cox
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=20020807.074838.106638568.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rkuhn@e18.physik.tu-muenchen.de \
/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.