On Tue, 2013-10-15 at 11:40 +0200, Dennis H Jensen wrote: > > 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. > > OK, fair enough, but the fact is that there is a hole in the frequencies > that were added in 802.11p. 802.11p ... yeah, that's an issue. > > > 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 ... > > You misunderstood me; the European operating class 14, for example, > states that channel 182 is to be 5910. That's a 10MHz channel only. In any case, I don't see a good way out. Pretending that the channel number is something else like you did in this patch is clearly wrong and will obviously lead to interoperability issues. I think we need to actually start taking the operating class (or maybe just the starting frequency) into account in the kernel. How we do that I don't really know. 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
