The constant we notice above is that it mainly affects users of mad-wifi, which is one of the last drivers that hasn't been merged into the kernel tree or converted to the unified wifi stack design used since kernel 2.6.24. While I haven't looked at the upstream chnagelog, I wouldn't be surprised if 0.6.6 breaks on madwifi simply because it has migrated to the unified wifi stack as a method of interacting with the interfaces.
The constant we notice above is that it mainly affects users of mad-wifi, which is one of the last drivers that hasn't been merged into the kernel tree or converted to the unified wifi stack design used since kernel 2.6.24. While I haven't looked at the upstream chnagelog, I wouldn't be surprised if 0.6.6 breaks on madwifi simply because it has migrated to the unified wifi stack as a method of interacting with the interfaces.