From: Stefan Lippers-Hollmann <s.L-H@gmx.de>
To: linux-wireless@vger.kernel.org
Cc: "Will Dyson" <will.dyson@gmail.com>,
"Ivo van Doorn" <ivdoorn@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
rt2400-devel@lists.sourceforge.net
Subject: Re: [Rt2400-devel] Please pull 'upstream' branch of rt2x00
Date: Thu, 10 Jan 2008 21:32:40 +0100 [thread overview]
Message-ID: <200801102132.42666.s.L-H@gmx.de> (raw)
In-Reply-To: <8e6f94720801100352t615025b6j1c2cc0081626fee5@mail.gmail.com>
Hi
On Donnerstag, 10. Januar 2008, Will Dyson wrote:
[...]
> Sorry to be out of the loop, but what is wrong with rt61pci? It works
> really really well for me, using John's "everything" branch.
>
> Hmm. Looking at Linus's tree, I can see that rt61pci is missing at
> least 1 critical fix from Mattias Nissler that has been in
> wireless-2.6 for a long time now.
>
> rt2x00: Allow rt61 to catch up after a missing tx report
>
> I'd be pretty disappointed if we released 2.6.24 without this. It is a
> simple fix for a really obnoxious problem (although one that triggers
> rarely on my hardware).
The same goes for (which can be easily rediffed against linux-2.6):
[PATCH 06/12] rt2x00: Put 802.11 data on 4 byte boundary
without it, at least rt61pci, rt73usb and rt2500usb (plain
2.6.24-rc7-git2) trigger the well known:
WARNING: at net/mac80211/rx.c:1486 __ieee80211_rx()
Pid: 0, comm: swapper Not tainted 2.6.24-rc7-git2-slh64-smp-1 #1
Call Trace:
<IRQ> [<ffffffff80232e4a>] __wake_up_common+0x5a/0x90
[<ffffffff881fed9e>] :mac80211:__ieee80211_rx+0xbde/0xd00
[<ffffffff880cb3e6>] :ehci_hcd:ehci_work+0x5d6/0x8e0
[<ffffffff881f028b>] :mac80211:ieee80211_tasklet_handler+0xbb/0x120
[<ffffffff80243507>] tasklet_action+0x47/0xb0
[<ffffffff80243415>] __do_softirq+0x75/0xe0
[<ffffffff8020d62c>] call_softirq+0x1c/0x30
[<ffffffff8020f9f5>] do_softirq+0x35/0x90
[<ffffffff802432a6>] irq_exit+0x96/0xa0
[<ffffffff8020fad0>] do_IRQ+0x80/0x100
[<ffffffff8020af60>] default_idle+0x0/0x40
[<ffffffff8020af60>] default_idle+0x0/0x40
[<ffffffff8020c981>] ret_from_intr+0x0/0xa
<EOI> [<ffffffff80220e60>] lapic_next_event+0x0/0x10
[<ffffffff8020af89>] default_idle+0x29/0x40
[<ffffffff8020b00f>] cpu_idle+0x6f/0xe0
> There are also a bunch of antenna selection fixes that never went
> upstream. These are required for my card to operate well at rates
> greater than 1Mbit, even when fairly close to the AP.
>
> But aside from these issues, the latest 2.6.24-rc7 seems ok for me. My
> testing of it is somewhat limited, due to the terrible performance.
> But I can associate, browse the web and run iperf tests.
I can just agree to this statement, rt73usb works really well (at steady
~2.4 MB/s) and rt61pci is the first driver to actually work at all (yes,
the same performance issues, but rt61-legacy freezes using wpa2psk;
rt2500usb seems to have more problems).
All tests based on plain 2.6.24-rc7-git2 (amd64 and wpa2psk/ CCMP) + the
following patches:
- [PATCH 06/12] rt2x00: Put 802.11 data on 4 byte boundary
- [PATCH] rt2x00: Corectly initialize rt2500usb MAC
Thanks a lot
Stefan Lippers-Hollmann
next prev parent reply other threads:[~2008-01-10 20:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-06 22:37 Please pull 'upstream' branch of rt2x00 Ivo van Doorn
2008-01-06 22:38 ` [PATCH 01/12] rt2x00: Fix chipset debugfs file Ivo van Doorn
2008-01-06 22:38 ` [PATCH 02/12] rt2x00: Always call ieee80211_stop_queue() when return NETDEV_TX_BUSY Ivo van Doorn
2008-01-06 22:38 ` [PATCH 03/12] rt2x00: Only set the TBCN flag when the interface is configured to send beacons Ivo van Doorn
2008-01-06 22:39 ` [PATCH 04/12] rt2x00: Store queue idx and entry idx in data_ring and data_entry Ivo van Doorn
2008-01-06 22:40 ` [PATCH 05/12] rt2x00: Move start() and stop() handlers into rt2x00lib.c Ivo van Doorn
2008-01-06 22:40 ` [PATCH 06/12] rt2x00: Put 802.11 data on 4 byte boundary Ivo van Doorn
2008-01-11 0:32 ` Johannes Berg
2008-01-11 19:51 ` Ivo van Doorn
2008-01-06 22:40 ` [PATCH 07/12] rt2x00: Move packet filter flags Ivo van Doorn
2008-01-06 22:41 ` [PATCH 08/12] rt2x00: Cleanup write_tx_desc() arguments Ivo van Doorn
2008-01-06 22:41 ` [PATCH 09/12] rt2x00: Determine MY_BSS from descriptor Ivo van Doorn
2008-01-06 22:41 ` [PATCH 10/12] rt2x00: Move init_txring and init_rxring into rt2x00lib Ivo van Doorn
2008-01-06 22:42 ` [PATCH 11/12] rt2x00: Correctly initialize data and desc pointer Ivo van Doorn
2008-01-06 22:42 ` [PATCH 12/12] rt2x00: Release rt2x00 2.0.14 Ivo van Doorn
2008-01-10 11:52 ` [Rt2400-devel] Please pull 'upstream' branch of rt2x00 Will Dyson
2008-01-10 15:46 ` John W. Linville
2008-01-10 17:29 ` Ivo van Doorn
2008-01-15 0:44 ` Will Dyson
2008-01-10 17:29 ` Ivo van Doorn
2008-01-10 20:32 ` Stefan Lippers-Hollmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-04 14:36 Ivo van Doorn
2008-08-05 1:21 ` [Rt2400-devel] " Will Dyson
2008-08-05 1:43 ` Larry Finger
2008-08-05 18:30 ` Ivo van Doorn
2008-08-05 18:11 ` Johannes Berg
2008-08-05 18:44 ` Ivo van Doorn
2007-10-27 11:34 Ivo van Doorn
2007-10-27 12:47 ` [Rt2400-devel] " John W. Linville
2007-10-27 14:45 ` Ivo van Doorn
2007-10-27 16:19 ` Ivo van Doorn
2007-08-19 18:18 Ivo van Doorn
2007-08-23 20:55 ` [Rt2400-devel] " John W. Linville
2007-07-25 20:49 Ivo van Doorn
2007-07-26 2:19 ` [Rt2400-devel] " John W. Linville
2007-07-26 21:22 ` Ivo van Doorn
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=200801102132.42666.s.L-H@gmx.de \
--to=s.l-h@gmx.de \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rt2400-devel@lists.sourceforge.net \
--cc=will.dyson@gmail.com \
/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).