On 2011-05-04 1:57 AM, Javier Cardona wrote:
Mesh beaconing on ath9k was broken by this commit:
commit 4801416c76a3a355076d6d371c00270dfe332e1c
Author: Ben Greear<greearb@xxxxxxxxxxxxxxx>
Date: Sat Jan 15 19:13:48 2011 +0000
This patch assigns the right opmode when the device is used in mesh
mode.
Reported-by: Fabrice Deyber fabricedeyber@xxxxxxxxxxxxx
Signed-off-by: Javier Cardona<javier@xxxxxxxxxxx>
Any idea why exactly ath9k needs to use this opmode? If I understand the
specs correctly, 802.11s does not use distributed beacons like ad-hoc
mode, so theoretically it should be fine with using the AP iftype.
If beacons don't work at all in this opmode for 802.11s then this patch
may just be covering up an underlying bug rather than fixing the real issue.
- Felix
--
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
