linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: "Dan Williams" <dcbw@redhat.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: Wed, 14 Oct 2009 15:51:56 +0200	[thread overview]
Message-ID: <200910141551.56711.IvDoorn@gmail.com> (raw)
In-Reply-To: <200910132357.57094.bzolnier@gmail.com>

> > 1) the vendor driver never gets converted to cfg80211/mac80211, and
> > stays in staging forever, or finally gets booted out of staging because
> > nobody is working on converting it to mac80211.  mac80211/cfg80211 is a
> > hard requirement for being an accepted wireless driver.  And drivers do
> > have a shelf-life in staging.
> > 
> > 2) the vendor driver starts getting converted to use mac80211.  But I
> > would argue that a better use of *anyone's* time is to make rt2x00
> > better, instead of porting the ralink vendor drivers to mac80211.  It
> > would probably take less time to fix up rt2x00 for new hardware than to
> > port the ralink vendor drivers to mac80211.
> 
> Nobody is saying anything about porting the vendor drivers to mac80211.
> 
> 3) After the vendor driver gets cleaned up to the point that people are
> able to make any sense out of it the missing bits will get added to rt2x00.
> Several months later (after all current users are happy with the improved
> drivers) the old drivers will be removed from staging..

Wishful thinking. the Ralink drivers for rt2460, rt2560, rt2570, rt61 and rt73
coexisted for years with their rt2x00 counterparts before they were finally
abandoned after many arguments from people which wanted to preserve
those drivers for even more years.

Ivo

  parent reply	other threads:[~2009-10-14 13:52 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13 11:24 Current status of rt2800usb and staging/rt2870 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 13:51             ` Ivo van Doorn [this message]
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
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=200910141551.56711.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=bzolnier@gmail.com \
    --cc=dcbw@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).