From: Ivo van Doorn <ivdoorn@gmail.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Jiri Benc <jbenc@suse.cz>,
"John W. Linville" <linville@tuxdriver.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] d80211, rt2x00: fixes
Date: Wed, 13 Dec 2006 18:49:07 +0100 [thread overview]
Message-ID: <200612131849.07265.IvDoorn@gmail.com> (raw)
In-Reply-To: <20061213171205.GB26415@csclub.uwaterloo.ca>
On Wednesday 13 December 2006 18:12, Lennart Sorensen wrote:
> On Wed, Dec 13, 2006 at 06:00:35PM +0100, Jiri Benc wrote:
> > John, in addition to the previous pull request, please also apply the
> > following two fixes.
>
> What is the state of the rx2x00 driver by now? I have been playing
> around with an rt2500 based card, with some success but not enough for
> me to switch over from wired ethernet yet on my machine. I used to get
> lots of hard lockups, but with the latest cvs snapshot in debian's
> rt2x00-source package, it no longer seems to lockup. It also now works
> with WPA without using wpa_supplicant (Yay! Good work.), it does
> however very frequently pause the transfer, and then after a while (20
> or 30 seconds probably) it will start moving data again and my transfer
> will continue. Is this considered normal for now? My card happens to
> be a linksys WMP54G version 4.0. At least pauses beat crashes. It's
> going the right way for a work in progress.
>
> I guess I should go read the bug tracking system and try out newer cvs
> versions. :)
Well results seem to vary between users. Since recently users have started
reporting panics and freezes with rt2x00. I have not yet traced that problem
to the source, because the panics I have received don't contain any rt2x00
or d80211 functions. But the presence of the rt2x00 module is the
important factor in reproducing the crash. :(
Others however seem to have more success with rt2x00, master mode
seems to work with reasonable speed. Association with managed mode
is still very shortlifed. People who manage to get associated are being
kicked from the AP quite quickly. (This could be because d80211 is not
sending NULL-frames every once in a while).
But since results vary much between users, I can still descrive the rt2x00
state as "experimental driver"
Ivo
next prev parent reply other threads:[~2006-12-13 17:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 17:00 [PATCH 0/2] d80211, rt2x00: fixes Jiri Benc
2006-12-13 17:00 ` [PATCH 1/2] rt2x00: fix breakage after pkt_type field was removed Jiri Benc
2006-12-13 17:00 ` Ivo van Doorn
2006-12-13 17:00 ` [PATCH 2/2] fix some wireless ext stuff Jiri Benc
2006-12-13 17:12 ` [PATCH 0/2] d80211, rt2x00: fixes Lennart Sorensen
2006-12-13 17:38 ` Dan Williams
2006-12-13 17:56 ` Ivo van Doorn
2006-12-13 20:54 ` Lennart Sorensen
2006-12-13 20:54 ` Lennart Sorensen
2006-12-13 21:28 ` Ivo Van Doorn
2006-12-13 22:28 ` Lennart Sorensen
2006-12-13 17:49 ` Ivo van Doorn [this message]
2006-12-13 20:58 ` Lennart Sorensen
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=200612131849.07265.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=jbenc@suse.cz \
--cc=linville@tuxdriver.com \
--cc=lsorense@csclub.uwaterloo.ca \
--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 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).