From: Ivo van Doorn <ivdoorn@gmail.com>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: rt2x00 is still experimental?
Date: Sat, 12 Jul 2008 10:25:43 +0200 [thread overview]
Message-ID: <200807121025.43801.IvDoorn@gmail.com> (raw)
In-Reply-To: <1215811139.30975.10.camel@dv>
Hi,
> Can we please have rt2x00 drivers considered stable in Linux 2.6.27?
No.
> My experience running rt73 day by day with WPA on a very crowded network
> shows that it's a pretty reliable driver already.
Perhaps managed mode, but not adhoc mode, beaconing is still broken.
In addition the leds are broken as well, and hardware encryption isn't in either.
But to make a very important nore:
rt2400pci: unknown status
rt2500pci: TX rate problems, LED problems
rt2500usb: Completely broken, segfault on unplug, no HW crypto
rt61pci: TX rate problems, LED problems, no HW crypto
rt73usb: TX rate problems, LED problems. no HW crypto
I have 4 open Fedora bugreports, and 3 open Kernel bugreports
When I finally have my testsystem capable of running a >=2.6.26 kernel
then I can test rt2400pci, and _perhaps_ I can mark that one as stable since
it seems to work quite well on 2.6.25.
But marking the drivers as stable with be a per-rt2x00-driver decision, so what
I can do is moving the CONFIG_EXPERIMENTAL dependency to the drivers instead
of globally on CONFIG_RT2X00
> I realize that distros would enable whatever they want, and most people
> here have CONFIG_EXPERIMENTAL on anyway, but still, it could help direct
> users towards better supported hardware and make CONFIG_EXPERIMENTAL
> more relevant.
>
> The latest commits to the drivers/net/wireless/rt2x00 directory seem to
> confirm that the major issues have been addressed already.
Not sure what you saw in the latest commits, but they are not confirming anything
about stability. ;)
Ivo
next prev parent reply other threads:[~2008-07-12 8:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 21:18 rt2x00 is still experimental? Pavel Roskin
2008-07-12 8:25 ` Ivo van Doorn [this message]
2008-07-12 14:46 ` Pavel Roskin
2008-07-12 15:13 ` Ivo van Doorn
2008-07-12 15:31 ` Michael Buesch
2008-07-12 16:15 ` Stefanik Gábor
2008-07-12 22:07 ` Stefan Monnier
2008-07-14 7:56 ` Johannes Berg
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=200807121025.43801.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.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