From: Roger Luethi <rl@hellgate.ch>
To: Thomas Skora <thomas@skora.net>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] via-rhine.c, wol-bugfix, Kernel 2.6.11.5
Date: Thu, 24 Mar 2005 08:41:09 +0100 [thread overview]
Message-ID: <20050324074109.GA14926@k3.hellgate.ch> (raw)
In-Reply-To: <87psxp6fq4.fsf@powers.localnet>
On Thu, 24 Mar 2005 01:37:55 +0100, Thomas Skora wrote:
> The via-rhine driver in the actual kernel release 2.6.11.5 resets
> wake-on-lan-settings of the chip. This leads to the fact, that wol is
> disabled after the first reboot. I've attached a little patch, that
> fixes the problem.
This patch won't apply to the 2.6.11.5 I have here -- the driver is
clearing ~0xFC already. The description makes me suspect that the patch
is meant to go the other way, and that would be wrong. Use ethtool if
you want to enable WOL, default in Linux net drivers is off.
Please don't send patches as application/octet-stream, that's
annoying. Send either text/plain or inline.
Roger
next prev parent reply other threads:[~2005-03-24 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 0:37 [PATCH] via-rhine.c, wol-bugfix, Kernel 2.6.11.5 Thomas Skora
2005-03-24 7:41 ` Roger Luethi [this message]
2005-03-24 11:37 ` Thomas Skora
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=20050324074109.GA14926@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@skora.net \
--cc=torvalds@osdl.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