On Mon, 2013-10-14 at 16:58 +0200, Dennis H Jensen wrote: > > > The commit 59eb21a6504731fc16db4cf9463065dd61093e08 moved those channels > > > to 4.9 GHz but left a hole in the 5.9 Ghz range. > > > > But there was no +/- 15 before, so what gives? > > Well no :) but there also wasn't a special case for that particular > channel set (182 - 196). Yes, but then before 5910 would have been channel 182. Now you're making it channel 197. That doesn't really make sense at all. > So now, when you configure the frequency 5910, it is mapped to channel > 182 which is mapped back to 4910 and nothing works, at least let the > functions be the inverse of the other. > > In case that doesn't do it. What is needed to get channel 182 to be 5910 > MHz as Annex E defines for the US and Europe? Channel to frequency > mapping based on operating class? Annex E is the 802.11 spec, to get something into that ... johannes -- 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
