From: Pavel Roskin <proski@gnu.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] MadWifi reference edition
Date: Tue, 12 Nov 2013 19:16:50 -0500 [thread overview]
Message-ID: <20131112191650.32cba01c@IRBT4585> (raw)
Hello!
This might be of interest for developers working on ath5k and ath9k
drivers. It may be useful to have working MadWifi code for reference
to see how MadWifi accesses hardware registers, what packets it would
send, how it would communicate with other devices, how fast the
connections would be.
I fully realize that the MadWifi code is ugly and I don't want anyone
to use it for any new serious project (I know that existing embedded
systems still use MadWifi). Still, it's very unhelpful for developers
that the MadWifi site is down and the MadWifi code doesn't compile for
the latest kernels.
So I forked MadWifi on GitHub:
https://github.com/proski/madwifi
Here's the summary of the changes I've made so far:
Compilation fixed for Linux 3.10-3.12 and the current linux-next.
ath_info removed, it's should probably be maintained separately.
Removed integration with the official Subversion repository (it's down).
Removed support for Linux 2.6.12 and older, I have no time to compile
test it, let alone test the actual functionality.
Fixed compile errors in rare cases (e.g. SKB debugging and no VLAN).
Fixed some warnings, more fixes coming.
The purpose of the changes is not to make MadWifi work better. The
purpose is to make it compile cleanly and serve as a working reference
for ath5k and ath9k development.
--
Regards,
Pavel Roskin
next reply other threads:[~2013-11-13 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 0:16 Pavel Roskin [this message]
2013-11-14 7:06 ` [ath9k-devel] [Madwifi-devel] MadWifi reference edition Michael Renzmann
2013-11-15 0:33 ` Pavel Roskin
2013-11-14 11:28 ` [ath9k-devel] [ath5k-devel] " Nick Kossifidis
2013-11-14 11:36 ` Nick Kossifidis
2013-11-14 23:52 ` Pavel Roskin
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=20131112191650.32cba01c@IRBT4585 \
--to=proski@gnu.org \
--cc=ath9k-devel@lists.ath9k.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.