[Top] [All Lists]

Re: wol support in forcedeth v25

To: Andrew de Quincey <adq@xxxxxxxxxxxxx>
Subject: Re: wol support in forcedeth v25
From: Arjen Verweij <A.Verweij2@xxxxxxxxxxxxxx>
Date: Tue, 20 Apr 2004 13:13:09 +0200 (METDST)
Cc: netdev@xxxxxxxxxxx
In-reply-to: <200404200007.59345.adq@xxxxxxxxxxxxx>
Reply-to: a.verweij@xxxxxxxxxxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
OK, let me know if you need a guinea pig to test any patches you might



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
> >

<Prev in Thread] Current Thread [Next in Thread>