From: "Tom Sharples" <tsharples@qorvus.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>,
"Michael Renzmann" <mrenzmann@madwifi-project.org>
Cc: <madwifi-users@lists.sourceforge.net>,
"linux-wireless" <linux-wireless@vger.kernel.org>,
<madwifi-devel@lists.sourceforge.net>
Subject: Re: [Madwifi-devel] Survey: What are you using MadWifi for, and why?
Date: Tue, 17 Nov 2009 09:51:48 -0800 [thread overview]
Message-ID: <C32E4D5CD18647DE9A4F47C6EB1A94C2@qlaptop2> (raw)
In-Reply-To: 43e72e890911170838g26172725ga4a843dc5292c29f@mail.gmail.com
Comments inline:
>
> My point was that there are already hundreds of users already on ath5k
> and ath9k and that obviously you will get a biased view of MadWifi /
> ath5k situation (I don't consider MadWifi any type of alternative to
> ath9k).
We have way more users than this running just our version. There are
probably tens of thousands of "users" (embedded systems) that run some
flavor of madwifi.
>>
>> The development of any software should happen with the user's needs and
>> requirements in mind
>
> Note I didn't say otherwise.
Your comments, at best, give short shrift to the many, many embedded users,
esp those who run the 2.4.x kernel. Does anyone actually think it would be
practical to remotely upgrade tens of thousands of unattended devices, some
of which are miles away from the nearest human, to a 2.6 kernel? Even if
only 5% fail to come back online, it would be a logistical and
customer-relations disaster. These aren't windows desktops where someone can
just curse and then powercycle.
>
> Well to me they are clear and I don't need a survey to understand
> this. ath5k currently lacks:
>
> * DFS
> * Multi-BSS AP functionality
> * Roaming
> * ANI
>
You also need to add to this list:
* Fast-frames
* Compression
* Half / quarter channels (hopefully done in a sensible fashion like AirOS
without the countrycode / regdomain BS)
We need to aknowledge that "user" includes not just those surfing on their
laptops, but the far larger number of embedded devices running madwifi each
and every day, in critical systems, with excellent reliability.
Tom S.
next prev parent reply other threads:[~2009-11-17 18:49 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 [this message]
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=C32E4D5CD18647DE9A4F47C6EB1A94C2@qlaptop2 \
--to=tsharples@qorvus.com \
--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