All of lore.kernel.org
 help / color / mirror / Atom feed
From: Auke Kok <auke-jan.h.kok@intel.com>
To: Harry Coin <hcoin@n4comm.com>
Cc: netdev@vger.kernel.org
Subject: Re: e100.c patch to 2.6.18 fixing Wake on Lan (WOL)
Date: Mon, 15 Jan 2007 10:19:22 -0800	[thread overview]
Message-ID: <45ABC5AA.1060307@intel.com> (raw)
In-Reply-To: <4.3.2.7.2.20070115113616.03dcf4a8@www.n4comm.com>

Harry Coin wrote:
> Hello from Iowa.
> 
> Below please find a fix to the Wake On Lan function in the e100.c (intel 
> 10/100) driver.   With the original driver distributed in kernel 2.6.18 
> in debian etch, wake on lan did not work.   This was tested on 14 dell 
> optiplexes with built-in ethernet chips in a totally diskless 
> environment (initramfs / pxelinux).  All operations were normal save 
> wake on lan.

Oi,

I've done quite a bit of work especially on that since 2.6.18 and as far as I could see 
those changes fixed WoL, suspend/resume and netconsole, as was confirmed by Andrew 
Morton even.

Have you tried the version in 2.6.19?

> When WOL has been enabled with ethtools, the old driver assumes wrongly 
> that e100_configure will be called at least once with !netif_running.  
> Only in that instance will it set the chip to notice 'magic' wol packets 
> if the ethtools -s wol g has been called prior.
> 
> The old e100_down routine never does call e100_configure so that the 
> driver never does  turn off the 'disable WOL magic packet' bit.
> Neither does the .shutdown routine.   This fix tries to only enable the 
> WOL recognition only when e100_down is called for the last time
> before module unload or system shutdown, while leaving ifconfig down 
> untouched.    (testing for being run in the context of dev->stop).

that's exactly what my patches should fix as far as I can remember

> I have also submitted the above to the e1000 group at intel privately as 
> they are the 'maintainers', but this appears to be the only apropos open 
> group I thought to note he here as well.

I have not seen this patch before, care to Cc me to that? We also publically discuss 
e1000/e100 and ixgb issues on e1000-devel@lists.sourceforge.net. Feel free to Cc that list.

Cheers,

Auke

  reply	other threads:[~2007-01-15 18:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-15 15:12 3c59x.c patch to 2.6.18 fixing Wake on Lan (WOL) Harry Coin
2007-01-15 16:00 ` Dan Williams
2007-01-15 17:35   ` Harry Coin
2007-01-15 17:43   ` e100.c " Harry Coin
2007-01-15 18:19     ` Auke Kok [this message]
2007-01-15 19:24       ` Harry Coin
2007-01-15 19:42         ` Auke Kok

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=45ABC5AA.1060307@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=hcoin@n4comm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.