From: Andrew Morton <akpm@osdl.org>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Martin Filip <bugtraq@smoula.net>,
linux-kernel@vger.kernel.org, Ayaz Abdulla <aabdulla@nvidia.com>,
stable@kernel.org
Subject: Re: forcedeth - WOL [SOLVED]
Date: Wed, 27 Sep 2006 20:39:06 -0700 [thread overview]
Message-ID: <20060927203906.f4fc331e.akpm@osdl.org> (raw)
In-Reply-To: <20060928022447.GA3890@atjola.homenet>
On Thu, 28 Sep 2006 04:24:47 +0200
Björn Steinbrink <B.Steinbrink@gmx.de> wrote:
> On 2006.09.28 04:04:38 +0200, Björn Steinbrink wrote:
> > On 2006.09.27 18:36:25 -0700, Andrew Morton wrote:
> > > On Thu, 28 Sep 2006 03:01:33 +0200
> > > Björn Steinbrink <B.Steinbrink@gmx.de> wrote:
> > >
> > > > > > > Do we know if this reversal *always* happens with this driver, or only
> > > > > > > sometimes?
> > > >
> > > > I only tried 2.6.18 twice this time, but when I wrote my own tool to do
> > > > it, I had probably 20-30 power on -> ethtool -> poweroff cycles before I
> > > > decided to look into Bugzilla. As it looked like being fixed already and
> > > > I did use the nForce NIC for testing only, I didn't spend any further
> > > > time on it back then.
> > >
> > > What I'm angling towards is: "is this just a driver bug"?
> >
> > I just took a peek at the code.
> >
> > The version on bugzilla (last attachment, comment #22), which was
> > reported to work correctly, has the MAC address reversal hardcoded.
> > The driver in 2.6.18 has some logic to detect if it should reverse the
> > MAC address. So it looks like a hardware oddity/bug that the driver
> > wants to fix but fails. I'll see what happens if I force address
> > reversal and if I can decipher anything, but probably someone else will
> > have to cast the runes...
>
> OK, please excuse me wasting your time, it's late over here... I've
> actually been looking at Linus' git tree (pulled yesterday) while
> writing that mail, not 2.6.18.
> 2.6.18 does _not_ contain the address reversal detection.
> Using the git tree instead of 2.6.18 WOL works as expected, without
> having to reverse the MAC address.
>
hm, OK, thanks. Ayaz, do you think 5070d3408405ae1941f259acac7a9882045c3be4 is
a suitable thing for 2.6.18.x?
next prev parent reply other threads:[~2006-09-28 3:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 17:50 forcedeth - WOL Martin Filip
2006-09-27 18:35 ` Alistair John Strachan
2006-09-27 20:26 ` Martin Filip
2006-09-27 20:48 ` Francois Romieu
2006-09-27 21:20 ` John W. Linville
2006-09-27 18:38 ` Björn Steinbrink
2006-09-27 20:38 ` forcedeth - WOL [SOLVED] Martin Filip
2006-09-27 23:57 ` Andrew Morton
2006-09-28 0:04 ` Björn Steinbrink
2006-09-28 0:40 ` Björn Steinbrink
2006-09-28 1:01 ` Björn Steinbrink
2006-09-28 1:36 ` Andrew Morton
2006-09-28 2:04 ` Björn Steinbrink
2006-09-28 2:24 ` Björn Steinbrink
2006-09-28 3:39 ` Andrew Morton [this message]
2006-09-28 11:37 ` Martin Filip
2006-09-28 17:09 ` Ayaz Abdulla
2006-09-28 1:03 ` Andrew Morton
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=20060927203906.f4fc331e.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=B.Steinbrink@gmx.de \
--cc=aabdulla@nvidia.com \
--cc=bugtraq@smoula.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox