Hi KP

on 12.10.2014 21:18, kp kirchdoerfer wrote:
> HI Erich;
> 
> I've visited Wroclaw the last days and had no time/access to respond earlier.

Breslau, interesting, I have no clue about Poland.

> 
> Am Freitag, 10. Oktober 2014, 15:21:43 schrieben Sie:
>> Hi KP
>>
....

> 
> But pls explain to me, what's the benefit - I'm ignoring all this just by 
> lack 
> of knowledge.

OK, many Atheros based cards are delivered with an EEPROM country code
of 0x00, e.g. unspecified. The idea is probably that the EOM's should
insert their country specific code there.

The driver is hard coded to insert 'US' if it sees an unspecified
country code, which limits the chip to channels 1-11 but allows for
higher (and illegal) TXPower.

In most European countries we are allowed to use channels 1-13 but at
lower transmit power levels. The way the atheros board is initiated is
that later country selection can only _add_ limits, but not widen them.
So if you insert a country code of 'DE' it will not AND this with the
full register set, but with the previously set limits, which in fact
will result in the above US limitation of channels and the DE limitation
of power, this will make it impossible for you to us an AP which is set
correctly to channels 1-13. The same is valid for the 5 GHz channels.

I ranted about this on the wireless driver list, but could not get
through. If you search the net you will find lots of similar woes about
this issue like for example at
https://bbs.archlinux.org/viewtopic.php?id=124574

So I decided to patch the driver to get a neutral behaviour at
initialization and then be able to set the correct country code. This is
IMHO the most sensible aproach.

cheers

Erich

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to