On Wed, Oct 15, 2008 at 7:44 PM, Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx> wrote: > On Wed, Oct 15, 2008 at 05:35:44PM -0700, Tomas Winkler wrote: >> On Wed, Oct 15, 2008 at 7:08 PM, Luis R. Rodriguez >> > The issue was your single band cards do not store 5 GHz band regulatory >> > information. Is this MOW1 or MOW2? >> >> Don't understand the question, the 5GHz channels are disabled that's >> all you can read from there. > > Oh OK so its not just MOW1 and MOW2 but you also *do* take into account > the card's capabilities. > >> > It certainly helps more understand your situation. I had no idea >> > of MOW1 and MOW2. Can this be documented as part of the >> > regulatory_hint() code changes which will be added? >> >> I've just checked current docs and from 5000 on inclusively there are >> only 3 SKU's MOW, ABG (no N) and BG. All others were depreciated. > > Interesting.. Are these SKUs also used on other platforms as well, say > for Windows? Definitely It's not defined specially for Linux market. And you may sense that this is also station mode specific. In AP mode probably the story would be different. > Anyway since you only have 3 this should be very simple to resolve... > Just add the 5 GHz frequency ranges you always support. Obviously the BG > card will not be able to make use of them :) It's ugly but possible w/a but we still have 3945 and 4965 where it is not so simple. Tomas -- 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
