From: David Acker <dacker@roinet.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
Andrey Yurovsky <andrey@cozybit.com>,
Michael Renzmann <mrenzmann@madwifi-project.org>,
madwifi-devel@lists.sourceforge.net,
madwifi-users@lists.sourceforge.net,
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 17:32:50 -0500 [thread overview]
Message-ID: <4B032492.2080709@roinet.com> (raw)
In-Reply-To: <1258495587.2003.41.camel@violet>
Marcel Holtmann wrote:
> Hi David,
>
>> The problem with switching to ath5k would be the loss of performance
>> related features (compression, fast frames, turbo), and some required
>> features (half/quarter rates are required for some channels on some
>> radios). Also, I don't know if ath5k will work on products based on
>> Atheros WiSOCs like Ubiquiti's PicoStation and Bullet. A lesser issue
>> (more of a pain for me than an ath5k issue) is that I have some
>> platforms that use an older kernel and moving up to a newer kernel will
>> have to be done without hardware vendor support.
>
> and that is exactly not a valid point to include MadWifi into the
> staging tree. If you are running older kernels, the staging tree doesn't
> help you at all.
True. I happen to agree that Madwifi shouldn't go into staging. I
would rather see the features I noted ported into ath5k. Thanks!
-ack
next prev parent reply other threads:[~2009-11-17 22:32 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
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 [this message]
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=4B032492.2080709@roinet.com \
--to=dacker@roinet.com \
--cc=andrey@cozybit.com \
--cc=linux-wireless@vger.kernel.org \
--cc=madwifi-devel@lists.sourceforge.net \
--cc=madwifi-users@lists.sourceforge.net \
--cc=marcel@holtmann.org \
--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).