From: Jeff Garzik <jeff@garzik.org>
To: Tim Mann <mann@vmware.com>
Cc: netdev@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2.6.22-rc4-git6] forcedeth: use unicast receive mode for WoL
Date: Wed, 20 Jun 2007 19:15:26 -0400 [thread overview]
Message-ID: <4679B50E.7080605@garzik.org> (raw)
In-Reply-To: <20070614131638.1a5cef4c@mann-lx.eng.vmware.com>
Tim Mann wrote:
> I happened to notice that a system with an NVidia NIC using the
> forcedeth driver won't wake-on-LAN if the interface was in promiscuous
> mode when you power off. By experiment, it looks like
> the hardware needs to have NvRegPacketFilterFlags set to
> NVREG_PFF_ALWAYS|NVREG_PFF_MYADDR (i.e., receive unicast packets to my
> address) in order for WoL to work.
>
> Jeff Garzik writes: "NVIDIA says the patch looks OK." I didn't venture
> to insert a signed-off-by line with his name on it, though.
>
> Signed-off-by: Tim Mann <mann@vmware.com>
applied to #upstream-fixes (2.6.22)
prev parent reply other threads:[~2007-06-20 23:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 20:16 [PATCH 2.6.22-rc4-git6] forcedeth: use unicast receive mode for WoL Tim Mann
2007-06-20 23:15 ` Jeff Garzik [this message]
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=4679B50E.7080605@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=mann@vmware.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).