From: Mike Galbraith <efault@gmx.de>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Luis Correia <luis.f.correia@gmail.com>,
linux-wireless@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [wireless] rt2870sta BUGs on shutdown, 2.6.30.2->git.today+git.wireless.today
Date: Thu, 30 Jul 2009 19:09:40 +0200 [thread overview]
Message-ID: <1248973780.7091.10.camel@marge.simson.net> (raw)
In-Reply-To: <200907301852.28172.IvDoorn@gmail.com>
On Thu, 2009-07-30 at 18:52 +0200, Ivo van Doorn wrote:
> I planned, and actually did write, a lengthy reply for this thread, when I completed the reply
> I reconsidred and opted for this shorter reply. Every 2 or 3 months this discussion is started
> again and I am f***ing tired of it, so excuse me but I am not going to throw myself into
> this completely pointless discussion
>
> What you are suggesting in your mail is something the rt2x00 project did for 5 years, we stopped
> with that 4 months ago because it wasn't working out. Apparently you have more experience in this
> matter so I hope you will find a way to make that solution work out.
>
> If you want to maintain the legacy drivers then do it, start a new project and start maintaining
> the code. I can forward you all the users with complains about the "good enough" drivers. It is
> good to know that you apparently have the resources to maintain the old drivers.
> Most people who are helping with the rt2800pci/usb drivers lack the required time to boost the driver
> into such a state it can be widely adopted. But every time it amazes me that the people who want
> to develop and have the time to do it, all want to jump on the old Ralink code... Apparently there
> is some appeal to maintaining crap rather then helping to ship out proper drivers to the users.
>
> But I'll shut up now, as I said this discussion is held every few months, so perhaps that when
> the discussion is started again in a couple of months I am more interested in a lengthy reply.
Hohum. Please remove me from CC for any further discussion.
-Mike
next prev parent reply other threads:[~2009-07-30 17:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 9:22 [wireless] rt2870sta BUGs on shutdown, 2.6.30.2->git.today+git.wireless.today Mike Galbraith
2009-07-30 9:29 ` Johannes Berg
2009-07-30 9:44 ` Mike Galbraith
2009-07-30 9:55 ` Johannes Berg
2009-07-30 10:05 ` Mike Galbraith
2009-07-30 12:11 ` [rt2800 doesn't authenticate (wpapsk/tkip)] " Mike Galbraith
2009-08-01 5:25 ` rt2800usb: memory corruption? Mike Galbraith
2009-08-01 10:55 ` Mike Galbraith
2009-08-02 0:21 ` Pavel Roskin
2009-08-02 5:16 ` Mike Galbraith
2009-08-02 6:29 ` Mike Galbraith
2009-08-02 6:47 ` Mike Galbraith
2009-08-06 10:12 ` Pavel Roskin
2009-07-30 10:06 ` [wireless] rt2870sta BUGs on shutdown, 2.6.30.2->git.today+git.wireless.today Luis Correia
2009-07-30 13:17 ` Bartlomiej Zolnierkiewicz
2009-07-30 16:52 ` Ivo van Doorn
2009-07-30 17:09 ` Mike Galbraith [this message]
2009-07-30 17:11 ` Johannes Berg
2009-07-30 17:26 ` Greg KH
2009-07-30 18:04 ` Dan Williams
2009-07-30 18:13 ` Greg KH
2009-08-02 9:10 ` Peter Teoh
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=1248973780.7091.10.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=bzolnier@gmail.com \
--cc=ivdoorn@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=luis.f.correia@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).