From: Julien Wajsberg <julien.wajsberg@gmail.com>
To: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How's the nforce4 support in Linux?
Date: Tue, 29 Mar 2005 08:47:51 +0200 [thread overview]
Message-ID: <2a0fbc5905032822477759310c@mail.gmail.com> (raw)
In-Reply-To: <42456E1B.9070000@stud.feec.vutbr.cz>
On Sat, 26 Mar 2005 15:13:47 +0100, Michal Schmidt
<xschmi00@stud.feec.vutbr.cz> wrote:
> Julien Wajsberg wrote:
> > Good point... I just tried, but forcedeth doesn't support netpoll. If
> > you have a pointer, I could try to implement it ;-)
>
> Can you try the attached patch for forcedeth?
> It compiles for me, but I don't have nForce hardware to test it.
Okay, it works :)
maybe I'll have something for you to debug at the next crash...
--
Julien
> --- linux-2.6.12-rc1/drivers/net/forcedeth.c.orig 2005-03-26 15:00:12.000000000 +0100
> +++ linux-2.6.12-rc1/drivers/net/forcedeth.c 2005-03-26 15:08:56.000000000 +0100
> @@ -1480,6 +1480,13 @@ static void nv_do_nic_poll(unsigned long
> enable_irq(dev->irq);
> }
>
> +#ifdef CONFIG_NET_POLL_CONTROLLER
> +static void nv_poll_controller(struct net_device *dev)
> +{
> + nv_do_nic_poll((long) dev);
> +}
> +#endif
> +
> static void nv_get_drvinfo(struct net_device *dev, struct ethtool_drvinfo *info)
> {
> struct fe_priv *np = get_nvpriv(dev);
> @@ -1962,6 +1969,9 @@ static int __devinit nv_probe(struct pci
> dev->get_stats = nv_get_stats;
> dev->change_mtu = nv_change_mtu;
> dev->set_multicast_list = nv_set_multicast;
> +#ifdef CONFIG_NET_POLL_CONTROLLER
> + dev->poll_controller = nv_poll_controller;
> +#endif
> SET_ETHTOOL_OPS(dev, &ops);
> dev->tx_timeout = nv_tx_timeout;
> dev->watchdog_timeo = NV_WATCHDOG_TIMEO;
>
>
>
next prev parent reply other threads:[~2005-03-29 6:48 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 22:59 How's the nforce4 support in Linux? Julien Wajsberg
2005-03-25 23:14 ` Lee Revell
2005-03-26 0:38 ` Julien Wajsberg
2005-03-26 0:48 ` Lee Revell
2005-03-29 18:58 ` Tomasz Torcz
2005-03-29 20:40 ` Lee Revell
2005-03-30 15:00 ` Tomasz Torcz
2005-03-30 16:45 ` Lennart Sorensen
2005-03-30 19:19 ` Martin Schlemmer
2005-03-30 21:01 ` Lee Revell
2005-03-31 5:58 ` Martin Schlemmer
2005-03-25 23:20 ` Lee Revell
2005-03-26 0:17 ` Julien Wajsberg
2005-03-26 14:13 ` Michal Schmidt
2005-03-29 6:47 ` Julien Wajsberg [this message]
2005-03-25 23:21 ` Lee Revell
2005-03-25 23:41 ` Julien Wajsberg
2005-04-05 13:42 ` Julien Wajsberg
2005-04-05 14:10 ` Richard B. Johnson
2005-04-05 22:58 ` Julien Wajsberg
2005-04-06 11:41 ` Richard B. Johnson
2005-04-06 16:02 ` Bartlomiej Zolnierkiewicz
2005-04-10 23:43 ` Julien Wajsberg
2005-04-10 23:27 ` Julien Wajsberg
-- strict thread matches above, loose matches on Subject: below --
2005-03-26 16:01 Chuck
2005-03-26 15:19 ` Arjan van de Ven
2005-03-26 17:32 ` Marcin Dalecki
2005-03-27 12:26 ` Chuck
2005-04-02 23:55 ` Julien Wajsberg
2005-03-25 9:37 Chuck Ebbert
[not found] <3LwFC-4Ko-15@gated-at.bofh.it>
[not found] ` <3LwYW-4Xx-11@gated-at.bofh.it>
[not found] ` <3LwYZ-4Xx-25@gated-at.bofh.it>
2005-03-24 10:00 ` Asfand Yar Qazi
2005-03-24 10:11 ` Arjan van de Ven
2005-03-24 16:29 ` Lennart Sorensen
2005-03-24 16:41 ` Raphael Jacquot
2005-03-24 20:41 ` Jeff Garzik
2005-03-25 2:15 ` Robert Hancock
2005-03-25 2:40 ` Lee Revell
[not found] <3Lxis-5a0-29@gated-at.bofh.it>
[not found] ` <3Lxis-5a0-31@gated-at.bofh.it>
[not found] ` <3Lxis-5a0-33@gated-at.bofh.it>
[not found] ` <3Lxis-5a0-27@gated-at.bofh.it>
2005-03-24 10:11 ` Asfand Yar Qazi
2005-03-24 9:20 Asfand Yar Qazi
2005-03-24 9:30 ` Jeff Garzik
2005-03-24 9:34 ` Arjan van de Ven
2005-03-24 10:03 ` Tupshin Harper
2005-03-24 16:27 ` Lennart Sorensen
2005-03-24 21:01 ` Jeff Garzik
2005-03-28 15:31 ` Andi Kleen
2005-03-30 19:42 ` Jeff Garzik
2005-03-30 20:17 ` Indrek Kruusa
2005-03-30 20:25 ` Jeff Garzik
2005-03-30 20:48 ` Indrek Kruusa
2005-03-30 21:06 ` Francois Romieu
2005-03-30 21:47 ` Jeff Garzik
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=2a0fbc5905032822477759310c@mail.gmail.com \
--to=julien.wajsberg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xschmi00@stud.feec.vutbr.cz \
/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