Quoting Simon Geard <[EMAIL PROTECTED]>: > On Tue, 2008-04-22 at 22:46 +0200, alban wrote:
> Indeed, that fixes most of the problem. Scanning now finds the same > access points as madwifi did, making the new drivers usable. It's still > relatively slow though - a second or so to return results, where madwifi > was instantaneous. > > Also, any idea when whatever changes now in compat-wireless might get > merged to the kernel tree? It'd be nice if 2.6.25.1 would make things > work out-of-the-box... As far as I know, all changes made before 2.6.25 release will be queued for 2.6.26. 2.6.25.x is only for hotfixes, i.e. for simple patches that fix something important (especially regressions) but are unlikely to cause any problems. If you find the exact patch that fixes the problem with your card (you can do it by bisecting the wireless-testing git repository), and it turns out to be something simple and independent from other patches, then it may go to 2.6.25.1. But chances are, all simple fixes are in 2.6.25 already. -- Regards, Pavel Roskin _______________________________________________ ath5k-users mailing list [email protected] https://lists.ath5k.org/mailman/listinfo/ath5k-users
