linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Michael Renzmann <mrenzmann@madwifi-project.org>,
	madwifi-devel@lists.sourceforge.net,
	madwifi-users@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [Madwifi-devel] Survey: What are you using MadWifi for, and why?
Date: Tue, 17 Nov 2009 09:05:34 -0500	[thread overview]
Message-ID: <20091117140534.GD27743@tuxdriver.com> (raw)
In-Reply-To: <43e72e890911161701p61d0db5ag25a1459f900b3ab7@mail.gmail.com>

On Mon, Nov 16, 2009 at 05:01:09PM -0800, Luis R. Rodriguez wrote:

> If a few developers still exist who are committed to helping maintain
> madwifi until ath5k gets feature-parred the easiest solution now
> (since the HAL is open) is to just throw it into staging and hopefully
> that'll attract more developers to help keep it up to date with actual
> current kernels.

For the record, I would be generally opposed to adding madwifi to
drivers/staging.  We already have enough trouble with duplication of
hardware support between drivers/staging and drivers/net/wireless.

If madwifi has features that people need/want and that ath5k/mac80211
still lacks, lets talk about how to get them (or reasonabe replacements
for them) into the mainline kernel.  I'm sure some ideas will meet
some resistance, but if someone is motivated to continue pursuing
maintenance of madwifi than they should be motivated enough to at
least try to convince the rest of us why those features are worth
having in net/wireless, net/mac80211, and/or drivers/net/wireless.
Even if the solution is some quirky thing that "normal" people will
ignore, it is bound to be better to have mainline support than to
continue working out-of-tree.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2009-11-17 14:15 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2205.95.222.251.107.1258282369.squirrel@webmail.otaku42.de>
2009-11-17  1:01 ` [Madwifi-devel] Survey: What are you using MadWifi for, and why? Luis R. Rodriguez
2009-11-17 14:05   ` John W. Linville [this message]
2009-11-17 22:08     ` Marcel Holtmann
2009-11-17 16:04   ` Michael Renzmann
2009-11-17 16:38     ` Luis R. Rodriguez
2009-11-17 17:51       ` Tom Sharples
2009-11-17 18:05         ` Luis R. Rodriguez
2009-11-17 21:51       ` Bob Copeland
2009-11-17 23:23         ` Pat Erley
2009-11-18  7:23       ` Michael Renzmann
2009-11-17 17:40   ` David Acker
2009-11-17 20:57     ` Andrey Yurovsky
2009-11-17 21:37       ` Luis R. Rodriguez
2009-11-17 21:44         ` David Acker
2009-11-17 21:45           ` Luis R. Rodriguez
2009-11-17 21:53             ` David Acker
2009-11-17 22:04               ` Luis R. Rodriguez
2009-11-17 22:28                 ` David Acker
2009-11-17 22:39                   ` Luis R. Rodriguez
2009-11-17 23:39                     ` Tom Sharples
2009-11-17 23:44                       ` Luis R. Rodriguez
2009-11-17 22:54                   ` Jouni Malinen
2009-11-17 23:12                     ` Luis R. Rodriguez
2009-11-18 21:58                       ` Pavel Roskin
2009-11-18 22:08                         ` Luis R. Rodriguez
2009-11-18 23:05                           ` Jouni Malinen
2009-11-19  0:21                             ` Luis R. Rodriguez
2009-11-18 23:12                           ` Pavel Roskin
2009-11-19  0:05                             ` Tom Sharples
2009-11-17 22:06               ` Marcel Holtmann
2009-11-17 22:32                 ` David Acker
2009-11-17 23:22               ` Felix Fietkau
2009-11-18 15:35                 ` David Acker

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=20091117140534.GD27743@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=madwifi-devel@lists.sourceforge.net \
    --cc=madwifi-users@lists.sourceforge.net \
    --cc=mcgrof@gmail.com \
    --cc=mrenzmann@madwifi-project.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;
as well as URLs for NNTP newsgroup(s).