From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Dan Williams" <dcbw@redhat.com>,
"Ivo van Doorn" <ivdoorn@gmail.com>,
"Ozan Çağlayan" <ozan@pardus.org.tr>,
linux-wireless@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Current status of rt2800usb and staging/rt2870
Date: Thu, 15 Oct 2009 12:06:55 -0700 [thread overview]
Message-ID: <43e72e890910151206y59353608p5065f72eebd72ab@mail.gmail.com> (raw)
In-Reply-To: <200910151647.49050.bzolnier@gmail.com>
On Thu, Oct 15, 2009 at 7:47 AM, Bartlomiej Zolnierkiewicz
<bzolnier@gmail.com> wrote:
> On Wednesday 14 October 2009 18:55:23 Luis R. Rodriguez wrote:
>
>> I hear fishing in Poland is great this time of year.
>
> It got quite cold this week so I thought that I would try to fish
> the commit that broke Atheros AR9285 in Linus' tree (works in 2.6.31)
> and make recent kernels finally work on my laptop..
>
> Seems like there are two regressions actually:
>
> - later one making association/authentication impossible
And you reported this when and where?
> - earlier one making transfers stall
And you reported this when and where?
Curious how the issues you mention now spreading across sound and
wireless do not get fixed or seriously addressed. Have you considered
your tactics are perhaps not the best?
Have you tested newer kernels for ar9285? If there are regressions
obviously they should be fixed but without proper attention to the
issues they obviously cannot be fixed.
> There is also a ton of unrelated and related (mac80211) problems in
> between so the whole experience to trace regressions down is a real
> hell (I went through like 40 kernels already)..
I do agree there has been a hell of a lot of changes on
mac80211/cfg80211 over the last few kernels and you can argue whether
or not this has been a good thing -- personally I think it has had its
negative impact on users on older kernels but I do value the new
changes and most major changes have gone in right after the merge
window without opposition. When there are issues I at least do believe
we are attentive enough to help users and solve them on wireless and
contrary to staging you will at least have a larger group of members
working on the same wireless subsystem rather than addressing pigeon
hole solutions.
If you don't voice your own opinions and provide constructive
criticism instead of pointless and side tracked rants you are not
going to accomplish shit. So if you want to want to work on staging --
go at it -- but don't moan and bitch about how wireless proper is
being treated if you are not willing to man up and do something about
it.
> Oh, there is also an ath9k slab corruption already in 2.6.31 (I got
> it debugged initially though)..
We track reported ath9k bugs here:
http://wireless.kernel.org/en/users/Drivers/ath9k/bugs
When there is a bug report we follow up on it.
> However today it got a bit warmer and the snow is almost gone so
> I think that I'm going to take your advice after using the shortcut
> solution for my wireless problems..
>
> I'll just plug that cheap rt3070 stick laying around and modprobe
> that crappy rt2870sta..
Good luck with that buddy.
Luis
next prev parent reply other threads:[~2009-10-15 19:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 11:24 Ozan Çağlayan
2009-10-13 15:52 ` Ivo van Doorn
2009-10-13 17:27 ` Bartlomiej Zolnierkiewicz
2009-10-13 18:17 ` Ivo van Doorn
2009-10-13 19:21 ` Bartlomiej Zolnierkiewicz
2009-10-13 20:00 ` Ivo van Doorn
2009-10-13 20:42 ` Bartlomiej Zolnierkiewicz
2009-10-13 20:15 ` Dan Williams
2009-10-13 21:57 ` Bartlomiej Zolnierkiewicz
2009-10-13 22:21 ` Luis Correia
2009-10-14 14:14 ` John W. Linville
2009-10-13 22:24 ` Dan Williams
2009-10-13 22:42 ` Bartlomiej Zolnierkiewicz
2009-10-14 14:15 ` John W. Linville
2009-10-14 1:58 ` Thomas Fjellstrom
2009-10-14 13:51 ` Ivo van Doorn
2009-10-14 14:09 ` John W. Linville
2009-10-14 14:52 ` Bartlomiej Zolnierkiewicz
2009-10-14 14:56 ` John W. Linville
2009-10-14 15:28 ` Bartlomiej Zolnierkiewicz
2009-10-14 16:47 ` John W. Linville
2009-10-14 17:33 ` Bartlomiej Zolnierkiewicz
2009-10-14 18:26 ` Luis Correia
2009-10-14 20:41 ` Bartlomiej Zolnierkiewicz
2009-10-14 18:56 ` Ivo van Doorn
2009-10-14 20:10 ` Bartlomiej Zolnierkiewicz
2009-10-15 6:28 ` Gertjan van Wingerde
2009-10-15 9:47 ` Bartlomiej Zolnierkiewicz
2009-10-14 16:55 ` Luis R. Rodriguez
2009-10-15 14:47 ` Bartlomiej Zolnierkiewicz
2009-10-15 19:06 ` Luis R. Rodriguez [this message]
2009-10-16 17:13 ` Bartlomiej Zolnierkiewicz
2009-10-14 1:52 ` Mike Galbraith
2009-10-13 16:44 ` Bartlomiej Zolnierkiewicz
2009-10-13 20:41 ` Ozan Çağlayan
2009-10-13 20:44 ` Bartlomiej Zolnierkiewicz
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=43e72e890910151206y59353608p5065f72eebd72ab@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=bzolnier@gmail.com \
--cc=dcbw@redhat.com \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=ozan@pardus.org.tr \
/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
all inboxes | Powered by JetHome®