Debian Testing: use madwifi driver from non-free or compile with m-a?

[Brazen]

The madwifi documentation says the prefered method is to install the madwifi-source package from contrib and then compile it with module assistant. This doesn't make any sense to me though, if there is a compiled driver for it already in non-free. Is there some technical advantage to compiling madwifi-source over using the binary from non-free, or is it just a political reason?

The binary from non-free sounds better to me, cuz then I don't need to waste space installing build-tools, and I don't need to worry about re-compiling the module every time I get a kernel upgrade.

 

[Brazen]

I may be mistaken (or rather, that website is mistaken). "aptitude search madwifi" only gives madwifi-tools and madwifi-source. It doesn't give any binary from non-free. Here is my sources.list, I don't see I could be missing something

# Debian packages for testing
deb http://debian.mirror.frontiernet.net/debian/ testing main contrib non-free