From: Frans Pop <elendil@planet.nl>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: p0g0@madwifi-project.org, madwifi-project@venema.h4ckr.net,
Cliff.Holden@atheros.com, mb@bu3sch.de, nbd@openwrt.org,
mickflemm@gmail.com, proski@gnu.org, me@bobcopeland.com,
juhosg@openwrt.org, linux-kernel@vger.kernel.org
Subject: Re: [madwifi-project] Death to MadWifi!
Date: Tue, 12 May 2009 11:14:21 +0200 [thread overview]
Message-ID: <200905121114.24355.elendil@planet.nl> (raw)
In-Reply-To: <43e72e890905112332j3e32fb8q942fb75f882b2384@mail.gmail.com>
Luis R. Rodriguez wrote:
> Trust me, I'm not concerned at all -- reason for me sending this
> e-mail was having to hear a rant from a user about MadWifi being such
> crap and about devices not being supported properly.
Let me give at least one counter example.
I have used madwifi in the past but switched to ath5k when it came
available for my old Trust Atheros-based PCMCIA card, mostly because of
the ease of compilation and partly because of the better "free-ness".
There is at least one area where the madwifi driver was and probably still
is far superior: properly blinking the leds on the card to show the
power/connection state and during data transfer.
It's not a major issue and though I've mentioned this at least once in a
bug report or mail, this admittedly was back when there were more
important things to fix. I probably should submit a proper bug report
about it now.
I'm not asking for this to be fixed with this mail. I only mention it
because the title and tone of this mail, and the fact of its recurring
theme, offend me somewhat.
The way FOSS normally works is that one variant of alternative software
will gradually die a natural death once a clear superior is established.
There should be no need for members of rival projects to try to actively
kill eachother off (the rival project that is, not its members).
Cheers,
FJP
P.S. This is the only post I've seen from this thread as apparently it
started somewhere other than LKML.
next prev parent reply other threads:[~2009-05-12 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43e72e890905111627r54fd4fa4r26d9511c1fd625a2@mail.gmail.com>
[not found] ` <4A0908AB.1070606@madwifi-project.org>
2009-05-12 6:32 ` [madwifi-project] Death to MadWifi! Luis R. Rodriguez
2009-05-12 9:14 ` Frans Pop [this message]
2009-05-12 12:38 ` Bob Copeland
2009-05-12 13:22 ` Xavier Bestel
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=200905121114.24355.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=Cliff.Holden@atheros.com \
--cc=juhosg@openwrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madwifi-project@venema.h4ckr.net \
--cc=mb@bu3sch.de \
--cc=mcgrof@gmail.com \
--cc=me@bobcopeland.com \
--cc=mickflemm@gmail.com \
--cc=nbd@openwrt.org \
--cc=p0g0@madwifi-project.org \
--cc=proski@gnu.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