From: David Kimdon <david.kimdon@devicescape.com>
To: Pavel Roskin <proski@gnu.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
lwn@lwn.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Michael Buesch <mb@bu3sch.de>,
madwifi-devel@lists.sourceforge.net
Subject: Re: [Madwifi-devel] ANNOUNCE: SFLC helps developers assessar5k (enabling free Atheros HAL)
Date: Wed, 15 Nov 2006 15:28:16 -0800 [thread overview]
Message-ID: <20061115232816.GA20849@devicescape.com> (raw)
In-Reply-To: <1163619541.19111.6.camel@dv>
On Wed, Nov 15, 2006 at 02:39:01PM -0500, Pavel Roskin wrote:
> On Wed, 2006-11-15 at 14:21 -0500, John W. Linville wrote:
> > On Wed, Nov 15, 2006 at 07:42:14PM +0100, Michael Buesch wrote:
>
> I said it before, and it's worth repeating. Dissolving HAL in the
> sources is easy. It's just a matter of moving functions around without
> serious chances of breaking anything as long as the source compiles.
> The whole "HAL-based architecture" can be reshuffled and eliminated by
> one person in a few days.
>
> Making things work properly takes years. That's what MadWifi has been
> working on for a long time, using contributions and bug reports from
> scores of users and developers.
>
> Rejecting MadWifi because it's HAL based is like throwing away a diamond
> ring because it's too narrow.
I completely agree. The approach we are taking with dadwifi[1] is to
use much of the existing code from madwifi and port it to the d80211
stack. Today dadwifi works in monitor, sta and ap mode.
-David
[1] http://madwifi.org/wiki/DadWifi
>
> --
> Regards,
> Pavel Roskin
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Madwifi-devel mailing list
> Madwifi-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/madwifi-devel
next prev parent reply other threads:[~2006-11-15 23:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 3:10 ANNOUNCE: SFLC helps developers assess ar5k (enabling free Atheros HAL) John W. Linville
2006-11-15 3:10 ` John W. Linville
2006-11-15 18:42 ` Michael Buesch
2006-11-15 19:21 ` John W. Linville
2006-11-15 19:21 ` John W. Linville
2006-11-15 19:26 ` Michael Buesch
2006-11-15 19:26 ` Michael Buesch
2006-11-15 19:35 ` [Madwifi-devel] " Ben Greear
2006-11-15 19:35 ` Ben Greear
2006-11-16 14:18 ` Jochen Friedrich
2006-11-16 14:56 ` [Madwifi-devel] " Michael Renzmann
2006-11-16 14:56 ` Michael Renzmann
2006-11-15 19:26 ` Arjan van de Ven
2006-11-15 19:26 ` Arjan van de Ven
2006-11-15 19:39 ` [Madwifi-devel] " Pavel Roskin
2006-11-15 20:02 ` Michael Buesch
2006-11-16 5:37 ` Michael Renzmann
2006-11-16 10:07 ` Nick Kossifidis
2006-11-16 11:55 ` Michael Renzmann
2006-11-16 11:55 ` Michael Renzmann
2006-11-15 23:28 ` David Kimdon [this message]
2006-11-16 14:50 ` [Madwifi-devel] " Dan Williams
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=20061115232816.GA20849@devicescape.com \
--to=david.kimdon@devicescape.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lwn@lwn.net \
--cc=madwifi-devel@lists.sourceforge.net \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.