From: Ben Hutchings <bhutchings@solarflare.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: hayeswang <hayeswang@realtek.com>, <netdev@vger.kernel.org>,
'Stefan Becker' <chemobejk@gmail.com>,
'David Miller' <davem@davemloft.net>
Subject: Re: [PATCH] r8169: more driver shutdown WoL regression.
Date: Thu, 10 Nov 2011 14:02:24 +0000 [thread overview]
Message-ID: <1320933744.18929.82.camel@deadeye> (raw)
In-Reply-To: <20111110104117.GA23906@electric-eye.fr.zoreil.com>
On Thu, 2011-11-10 at 11:41 +0100, Francois Romieu wrote:
> hayeswang <hayeswang@realtek.com> :
> [...]
> > I find that the magic packet which I send is the broadcast packet, and the one
> > which you send is the unicast packet. That is, you could wake up the system by
> > using broadcast magic packet for the previous chips without the patch. However,
> > if you prefer to unicast magic packet, this patch is necessary. Besides, no
> > matter broadcast or unicast magic packet, the patch is necessary for 8105,
> > 8168e, and later chips.
>
> Ok, it makes some sense now.
>
> I am inclined to enable a broad understanding of ethtool WAKE_MAGIC
> feature as AMD's magic packet white paper does not limit it to
> broadcast packets and explicitely quotes unicast and multicast.
> Ben (and others), any opinion ?
[...]
Sorry, I've never looked into WoL in detail so I'm not sure quite what
the intended semantics of WAKE_MAGIC are.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2011-11-10 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 22:35 [PATCH] r8169: more driver shutdown WoL regression Francois Romieu
2011-11-09 7:49 ` hayeswang
2011-11-09 22:25 ` Francois Romieu
2011-11-10 4:11 ` hayeswang
2011-11-10 9:40 ` Stefan Becker
2011-11-10 10:41 ` Francois Romieu
2011-11-10 14:02 ` Ben Hutchings [this message]
2011-11-11 8:37 ` hayeswang
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=1320933744.18929.82.camel@deadeye \
--to=bhutchings@solarflare.com \
--cc=chemobejk@gmail.com \
--cc=davem@davemloft.net \
--cc=hayeswang@realtek.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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