Weekly Engineering News 37/2008

[Andy Green]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:

| They also just announced (literally in the past hour or two) and new
| list "madwifi-project" [2] for big picture coordination the drivers,
| developers and resources.  It meant to be a more open version of
| madwifi-team...
|
| In these threads, I've seen _no_ mention of ar6k...  Perhaps it should
| be integrated into the madwifi project effort?

Like Harald says, ar6000 is a bit of a different beast.

The firmware in there is basically doing everything internally, it has
advantages in power that we don't need the CPU to deal with stuff unless
it is necessary.  But, it means we totally rely on what the currently
unchangable firmware offers for the effective functionality of the
device, bugs and lacks included.

The current ar6000 driver itself is not that huge (because lots is done
in the firmware) and again does not need mac80211 or old 80211 stacks in
Linux because it's all in the firmware.

The ar6000 driver has quite a big footprint mainly because of the
Atheros non-mainline SDIO stack that it is tied to at the moment.  I
don't think it's going to be that interesting for Madwifi folks when you
consider these angles.

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkjSpsEACgkQOjLpvpq7dMqcuwCdH8RxXcVOewLfQXysNIvV8efZ
GckAniPOUFB770a6bZr5uvoZv42z4CJN
=zSJV
-----END PGP SIGNATURE-----