From: Arjen Verweij <a.verweij@student.tudelft.nl>
Cc: netdev@oss.sgi.com
Subject: Re: wol support in forcedeth v25
Date: Wed, 08 Sep 2004 21:36:30 +0200 [thread overview]
Message-ID: <413F5F3E.1060400@student.tudelft.nl> (raw)
In-Reply-To: <200404201236.41188.adq@lidskialf.net>
Ahum. I should have adapted the subject, and I did mean to write "long
shot".
NOFI at all, I was just typing too fast ;)
Regards,
Arjen
Andrew de Quincey wrote:
>On Tuesday 20 April 2004 12:13, Arjen Verweij wrote:
>
>I found how I could get it going again, but its not the right way of doing
>it.. In nv_close(), if you comment out the lines "nv_stop_rx(dev);" and "if
>(np->wolenabled) nv_start_rx(dev);", WOL works.
>
>However this isn't the right way to do it, which is why I haven't supplied a
>patch. What its supposed to do it stop receiving, clear any buffers, then
>restart receiving again. But this seems to break WOL for some reason. There
>must be some extra operation required for it all to work properly... I'll
>keep looking.
>
>
>
>>OK, let me know if you need a guinea pig to test any patches you might
>>have.
>>
>>Regards,
>>
>>Arjen
>>
>>On Tue, 20 Apr 2004, Andrew de Quincey wrote:
>>
>>
>>>On Monday 19 April 2004 21:11, Arjen Verweij wrote:
>>>
>>>
>>>>Hi,
>>>>
>>>>Is the wol support in forcedeth v25 complete yet? I was trying it with
>>>>the 2.6.5 kernel it came with, tried the new forcedeth driver with a
>>>>2.6.3 kernel (because firewire seems broken in 2.6.5) however, my box
>>>>will not wake up as of yet.
>>>>
>>>>
>>>You're right! It _was_ working with patch-forced-0.25, but it ain't in
>>>2.6.5. I'll see if I can spot the problem.
>>>
>>>
>>>
>>>>According to the source there is a FIXME with a comment about powering
>>>>down the NIC. Does this mean that support for wol is incomplete for
>>>>now? Mind you, I am just curious, this is in no way meant as criticism.
>>>>
>>>>
>>>That would only be for when WOL is NOT used; I think it has to leave the
>>>NIC powered up for WOL to work... and as you say it ain't implemented
>>>yet.
>>>
>>>
>>>
>>>>On another note, Carl-Daniel mentioned that DEV_NEED_TIMERIRQ might be
>>>>removed from future releases. Is this still the case? Feedback would be
>>>>much appreciated, so I can keep my humble audience up to date on what's
>>>>going on at the wol front.
>>>>
>>>>Thank you guys for your excellent work,
>>>>
>>>>Arjen
>>>>http://atlas.et.tudelft.nl/verwei90/nforce2/index.html
>>>>
>>>>
prev parent reply other threads:[~2004-09-08 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 20:11 wol support in forcedeth v25 Arjen Verweij
2004-04-19 23:07 ` Andrew de Quincey
2004-04-20 11:13 ` Arjen Verweij
2004-04-20 11:36 ` Andrew de Quincey
2004-09-08 19:07 ` Arjen Verweij
2004-09-08 19:36 ` Arjen Verweij [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=413F5F3E.1060400@student.tudelft.nl \
--to=a.verweij@student.tudelft.nl \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).