From: Ivo van Doorn <ivdoorn@gmail.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
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:56:57 +0100 [thread overview]
Message-ID: <200612131856.58877.IvDoorn@gmail.com> (raw)
In-Reply-To: <1166031523.4741.0.camel@localhost.localdomain>
On Wednesday 13 December 2006 18:38, Dan Williams wrote:
> On Wed, 2006-12-13 at 12:12 -0500, 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
>
> How, by private ioctls? That's just wrong; I believe you still need to
> go through the 4-way handshake to get the right keying information even
> if you use PSK, which means you still need the supplicant, right?
rt2x00 completely uses the dscape stack, so I am not sure how he is
managing this wpa without wpa_supplicant with rt2x00.
Lennart, are you using rt2x00 or the legacy rt2500 driver?
> > 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. :)
Ivo
next prev parent reply other threads:[~2006-12-13 17:57 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 [this message]
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
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=200612131856.58877.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=dcbw@redhat.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).