Re: ipw2200 GEO identification code
Paolo <oopla <at> users.sf.net>
2005-08-02 20:24:55 GMT
On Mon, Aug 01, 2005 at 10:05:56AM -0500, James Ketrenos wrote:
> As you are probably aware, we can not incorporate the patch into the
yep, that wasn't the target, only to hopefully help those like me that
got 1.0.4 working in chan>11 but got stuck w/ 1.0.6, finding themselves
suddenly and unknowingly thrown into FCC domain by upgrading to
80211-1.0.3+2200-1.0.6, until ipw2x00 devs get it right.
BTW, not much from me there in, I did mostly cut'n'paste from 1.0.4.
> driver as it bypasses the checks to determine the geography for which
> your wireless cards was tested to function. I do appreciate your use of
Not exaclty, if you don't set geography you get what EEPROM says.
Anyway, either the check is wrong, or the EEPROM content for that is
meaningless: 1.0.3+1.0.6 above + EEPROM in my card would state that I'm in
GEO_000, ie even smaller domain than FCC rules.
Which is wrong, as I'm in EU, and paid for a wlan embedded in a product
intended for and sold in EU. We have private/public CE-compliant
APs around on chans 12,13, which I'm supposed to be able to connect to
with no special tinkering w/ either the card or it's driver.
Likewise, I guess you guys from Intel, while travelling in eg Japan w/
your stock FCC-compliant notebook, do expect to connect to eg. Tokyo
airport's WiFi service in a snap, w/out need to ask netadmin over there
to switch their chan-14 service over to an FCC-blessed chan ;)
My bet is that, if we all look at what's in EEPROM->country, we find most
of us nowhere, ie GEO_000, like seems the case w/ eg madwifi (regdomain=0).