From: Andrew de Quincey <adq@lidskialf.net>
To: a.verweij@student.tudelft.nl
Cc: netdev@oss.sgi.com
Subject: Re: wol support in forcedeth v25
Date: Tue, 20 Apr 2004 00:07:59 +0100 [thread overview]
Message-ID: <200404200007.59345.adq@lidskialf.net> (raw)
In-Reply-To: <Pine.GHP.4.44.0404192205070.11806-100000@elektron.its.tudelft.nl>
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
next prev parent reply other threads:[~2004-04-19 23:07 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 [this message]
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
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=200404200007.59345.adq@lidskialf.net \
--to=adq@lidskialf.net \
--cc=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).