From: "allan" <allan@asix.com.tw>
To: "'Grant Grundler'" <grundler@chromium.org>
Cc: 'Eugene' <elubarsky@gmail.com>,
netdev@vger.kernel.org, "'Freddy Xin'" <freddy@asix.com.tw>,
"'ASIX Louis [蘇威陸]'" <louis@asix.com.tw>
Subject: RE: drivers/net/usb/asix: bug in asix_get_wol
Date: Sat, 17 Dec 2011 10:35:42 +0800 [thread overview]
Message-ID: <001c01ccbc64$95f5d7d0$c1e18770$@com.tw> (raw)
In-Reply-To: <CANEJEGvPqWVa+i9yfACU1Aoe1wdKCiO+dMtSgzcjiDqxM2ddRA@mail.gmail.com>
Dear Grant,
I will double check this issue and submit the revised patch to Linux kernel mainline source next week. Thanks a lot for your great helps.
---
Best regards,
Allan Chou
Technical Support Division
ASIX Electronics Corporation
TEL: 886-3-5799500 ext.228
FAX: 886-3-5799558
E-mail: allan@asix.com.tw
http://www.asix.com.tw/
-----Original Message-----
From: grundler@google.com [mailto:grundler@google.com] On Behalf Of Grant Grundler
Sent: Saturday, December 17, 2011 6:16 AM
To: ASIX Allan Email [office]
Cc: Eugene; netdev@vger.kernel.org; Freddy Xin; ASIX Louis [蘇威陸]
Subject: Re: drivers/net/usb/asix: bug in asix_get_wol
On Thu, Dec 15, 2011 at 9:15 PM, ASIX Allan Email [office]
<allan@asix.com.tw> wrote:
> Resend without attachment due to below email server error.
...
> -----Original Message-----
> From: ASIX Allan Email [office] [mailto:allan@asix.com.tw]
> Sent: Friday, December 16, 2011 11:38 AM
> To: 'Grant Grundler'; 'Eugene'
> Cc: 'netdev@vger.kernel.org'; 'Freddy Xin'; ASIX Louis [蘇威陸]
> Subject: RE: drivers/net/usb/asix: bug in asix_get_wol
> Importance: High
>
> Dear Grant and Eugene,
>
> Please refer to the attached file and below statements to modify the
> asix_get_wol() routine and let us know if this suggestion can solve
> your issues or not? Thanks a lot.
Allan,
Thanks for the response but it doesn't answer my previous question.
Let me ask the same question differently.
Does WOL support in asix driver need more than the four lines of code?
Ie does MONITOR_MODE need to be enabled or anything like that?
> ================
> static void
> asix_get_wol(struct net_device *net, struct ethtool_wolinfo *wolinfo)
> {
> struct usbnet *dev = netdev_priv(net);
> u8 opt;
>
> if (asix_read_cmd(dev, AX_CMD_READ_MONITOR_MODE, 0, 0, 1, &opt) < 0) {
> wolinfo->supported = 0;
> wolinfo->wolopts = 0;
> return;
> }
> wolinfo->supported = WAKE_PHY | WAKE_MAGIC;
> wolinfo->wolopts = 0;
> if (opt & AX_MONITOR_LINK)
> wolinfo->wolopts |= WAKE_PHY;
> if (opt & AX_MONITOR_MAGIC)
> wolinfo->wolopts |= WAKE_MAGIC;
> }
This looks remarkably similar to the code Eugene said enables WOL for
him (and it works). I not able to find any difference.
If you believe it was a mistake to remove these four lines of code,
please submit a patch (See Documentation/SubmittingPatches) to add
them back. You can add a "Tested-by: Eugene <elubarsky@gmail.com>"
line after your own "Signed-off-by:" in the patch.
thanks!
grant
prev parent reply other threads:[~2011-12-17 2:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-11 1:02 drivers/net/usb/asix: bug in asix_get_wol Eugene
2011-12-11 23:29 ` Grant Grundler
2011-12-13 13:03 ` Eugene
2011-12-15 16:48 ` Grant Grundler
2011-12-16 3:37 ` ASIX Allan Email [office]
2011-12-16 5:15 ` ASIX Allan Email [office]
2011-12-16 22:15 ` Grant Grundler
2011-12-17 2:35 ` allan [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='001c01ccbc64$95f5d7d0$c1e18770$@com.tw' \
--to=allan@asix.com.tw \
--cc=elubarsky@gmail.com \
--cc=freddy@asix.com.tw \
--cc=grundler@chromium.org \
--cc=louis@asix.com.tw \
--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).