From: Ivo van Doorn <ivdoorn@gmail.com>
To: chris2553@googlemail.com
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
rt2400-devel@lists.sourceforge.net
Subject: Re: 2.6.25-rc2 regression in rt61pci wireless driver
Date: Tue, 19 Feb 2008 22:03:03 +0100 [thread overview]
Message-ID: <200802192203.03741.IvDoorn@gmail.com> (raw)
In-Reply-To: <200802192044.52327.chris2553@googlemail.com>
Hi,
> > > I've tried the patch but, unfortunately, my wireless LAN still dies after a few pings.
> >
> > Could you use below patch instead, and make a new dump of the register?
> > I'm still convinced the breakage occurs in the antenna diversity (or rather, I believe
> > it attempts a software diversity for your card while in fact it shouldn't).
> >
>
> Sorry, I've applied that patch and the LAN still dies after a few pings. BTW,
> this and the earlier patch both apply without error, but give warnings of 70
> line offsets. Were you expecting them to apply completely cleanly? I'm just
> wondering if there might be some code that you are expecting to be running (or
> not running) that is (or is not) present in the driver at 2.6.25-rc2.
Well to be honest I based the patch on rt2x00.git and not 2.6.25-rc2.
I know the patch would apply safely because the function that were changed
in that patch haven't changed between them. But some other functions were
moved. So that offset is correct. ;)
> The register dumps before and after are attached.
Thanks. I hope to have a new patch ready soon.
Ivo
next prev parent reply other threads:[~2008-02-19 21:03 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 12:06 2.6.25-rc2 regression in rt61pci wireless driver Chris Clayton
2008-02-18 18:11 ` Ivo van Doorn
2008-02-18 18:16 ` Ivo van Doorn
2008-02-18 22:51 ` Chris Clayton
2008-02-19 9:26 ` Ivo van Doorn
2008-02-19 19:00 ` Chris Clayton
2008-02-19 19:46 ` Ivo van Doorn
2008-02-19 20:44 ` Chris Clayton
2008-02-19 21:03 ` Ivo van Doorn [this message]
2008-02-19 23:04 ` [Rt2400-devel] " Chris Vine
2008-02-20 16:05 ` Dan Williams
2008-02-20 20:27 ` Chris Vine
2008-02-20 20:50 ` Ivo van Doorn
2008-02-20 21:16 ` Chris Vine
2008-02-21 21:07 ` Chris Vine
2008-02-21 21:51 ` Ivo van Doorn
2008-02-21 22:46 ` Chris Vine
2008-02-21 22:51 ` Ivo van Doorn
2008-02-21 23:04 ` Chris Clayton
2008-02-21 23:20 ` Chris Vine
2008-02-22 7:39 ` Chris Clayton
2008-02-22 19:11 ` Ivo van Doorn
2008-02-22 20:33 ` Chris Vine
2008-02-20 22:13 ` Chris Clayton
2008-02-22 15:46 ` Chris Clayton
2008-02-22 19:47 ` Ivo van Doorn
2008-02-25 21:04 ` Chris Clayton
2008-02-25 22:09 ` Ivo Van Doorn
2008-02-26 19:11 ` Chris Clayton
2008-02-26 19:48 ` John W. Linville
2008-02-26 20:30 ` Ivo Van Doorn
2008-02-26 21:44 ` Stefano Brivio
2008-02-26 21:13 ` Chris Clayton
2008-02-26 21:38 ` Stefano Brivio
2008-02-26 22:36 ` Chris Clayton
2008-02-27 7:26 ` Stefano Brivio
2008-02-27 15:51 ` John W. Linville
2008-02-27 17:25 ` John W. Linville
2008-02-27 17:45 ` Chris Clayton
2008-03-02 10:33 ` Stefano Brivio
2008-03-02 15:11 ` Chris Clayton
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=200802192203.03741.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=chris2553@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rt2400-devel@lists.sourceforge.net \
/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).