From: Colin Leroy <colin@colino.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: netconsole & sungem
Date: Wed, 19 May 2004 22:10:56 +0200 [thread overview]
Message-ID: <20040519221056.54d7f732@jack.colino.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
Hi,
I tried to make netconsole work (with the attached patch copied from e1000), but can't get anything on the cable... the destination station doesn't see anything (nor Ethereal).
Are there any traps I didn't see ? (I have netconsole as a module and it loads ok:
netconsole: local port 32768
netconsole: interface eth0
netconsole: remote port 6666
netconsole: remote IP 192.168.0.4
netconsole: remote ethernet address 08:00:20:76:3c:57
netconsole: local IP 192.168.0.11
netconsole: network logging started
)
TIA,
--
Colin
[-- Attachment #2: sungem.diff --]
[-- Type: text/plain, Size: 962 bytes --]
--- drivers/net/sungem.c.orig 2004-05-19 20:47:15.000000000 +0200
+++ drivers/net/sungem.c 2004-05-19 22:09:25.920632936 +0200
@@ -2441,6 +2441,22 @@
return 0;
}
+#ifdef CONFIG_NET_POLL_CONTROLLER
+/*
+ * Polling 'interrupt' - used by things like netconsole to send skbs
+ * without having to re-enable interrupts. It's not called while
+ * the interrupt routine is executing.
+ */
+
+static void gem_poll(struct net_device *dev)
+{
+ struct gem *gp = dev->priv;
+ disable_irq(gp->pdev->irq);
+ gem_interrupt(gp->pdev->irq, (void *)dev, NULL);
+ enable_irq(gp->pdev->irq);
+}
+#endif
+
static int gem_set_settings(struct net_device *dev, struct ethtool_cmd *cmd)
{
struct gem *gp = dev->priv;
@@ -2810,6 +2826,9 @@
dev->change_mtu = gem_change_mtu;
dev->irq = pdev->irq;
dev->dma = 0;
+#ifdef CONFIG_NET_POLL_CONTROLLER
+ dev->poll_controller = gem_poll;
+#endif
if (register_netdev(dev)) {
printk(KERN_ERR PFX "Cannot register net device, "
next reply other threads:[~2004-05-19 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 20:10 Colin Leroy [this message]
2004-05-19 21:49 ` netconsole & sungem Benjamin Herrenschmidt
2004-05-20 7:53 ` Colin Leroy
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=20040519221056.54d7f732@jack.colino.net \
--to=colin@colino.net \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).