On 06/11/12 20:31, Johannes Berg wrote:
On Tue, 2012-11-06 at 19:35 +0000, Eddie Chapman wrote:
Right, we're still looking at that. It seems that it's not an ideal
solution, the regulatory change I proposed is probably better. Could you
check if it helps as well? That is, remove this patch, and apply this
one: http://p.sipsolutions.net/8877cbe3440d94b1.txt
OK, so I've removed 0129f39c7d882289.txt, applied 8877cbe3440d94b1.txt,
and I've kept 3a40414f826a8f1096d9b94c4a53ef91b25ba28d applied.
Rebooted, and happy to report throughput is still good, so
8877cbe3440d94b1.txt also "fixes" it for me.
Great, thanks. I'm not really sure which one to apply, and if we apply
the 8877 one we'll also want to update the reg db (that you aren't
using). A lot of people are in Barcelona right now though, so that might
be a week or so until we can close this.
No hurry at all from my point of view.
Thanks for all the testing!
Not at all, it's a pleasure to be able to contribute in some tiny way to
kernel development.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
