wireless-regdb: correct some flag damage...

It seems that commit e56cd9618e3e ("wireless-regdb: remove antenna
gain") accidentally dropped anything beyond the first flag in an entry.
Subsequently, commit d806b5e3ba73 ("wireless-regdb: optimize two of
DE's rules"), commit 788445b48c2e ("wireless-regdb: optimize two of
IL's rules"), and commit 13286f2c259b ("wireless-regdb: optimize two
of NL's rules") dutifully combined the newly/incorrectly compatible
rules with their neighbors...

FWIW, this one-liner was used to find the entries that lost flags:

git show e56cd9618e3e | grep -n '^-[^,]*,[^,]*,[^,]*,[^,]*,'

This patch corrects the damage above, including what is essentially
a revert of the latter three commits.

Reported-by: Christian Sünkenberg <christian.suenkenberg@hfg-karlsruhe.de>
Cc: Luis R. Rodriguez <mcgrof@do-not-panic.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
regdb: Republic of Korea: fix double rule

There's no need to have a 20 MHz and a 40 MHz rule that are
other wise completely the same, remove the 20 MHz one.

Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
wireless-regdb: allow max bandwidth to be AUTO calculated

Allow max bandwidth to be AUTO calculated, base
on contiguous rules. This AUTO ( bw = 0) parameter will be
send to the kernel mode (cfg80211/nl80211) and next maximum
allowed bandwidth will be calculated base on contiguous rules.

Eg.

country PL: DFS-ETSI
	(2402 - 2482 @ 40), (N/A, 20)
	(5170 - 5250 @ AUTO), (N/A, 20)
	(5250 - 5330 @ AUTO), (N/A, 20), DFS
	(5490 - 5710 @ 80), (N/A, 27), DFS

This mean we will calculate maximum bw for rules where
AUTO were set, 160MHz (5330 - 5170) in example above.
So we will get:
	(5170 - 5250 @ 160), (N/A, 20)
	(5250 - 5330 @ 160), (N/A, 20), DFS

In other case:
country FR: DFS-ETSI
	(2402 - 2482 @ 40), (N/A, 20)
	(5170 - 5250 @ AUTO), (N/A, 20)
	(5250 - 5330 @ 80), (N/A, 20), DFS
	(5490 - 5710 @ 80), (N/A, 27), DFS

We will get 80MHz (5250 - 5170):
	(5170 - 5250 @ 80), (N/A, 20)
	(5250 - 5330 @ 80), (N/A, 20), DFS

Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
wireless-regdb: set AUTO bandwidth for world regulatory

Set AUTO bandwidth calculation for world regulatory
domain. This will fix CRDA veryfication issue for
world regulatory domain. This will also allow to set
world regulatory from user mode (using iw/hostapd).

Before we fail when check bandwidth for rule:
2457 - 2482 @ 40 - where (2482 - 2457) < 40

Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
wireless-regdb: add AUTO-BW rule flag

Sync with latest nl80211.h and add AUTO-BW flag.
If this flag set, maximum available bandwidth should
be calculated base on contiguous rules and wider channels
will be allowed to cross multiple contiguous/overlapping
frequency ranges.

Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
wireless-regdb: add channels 52..64 and 100..144 to world regdom

This is a port of what Johannes Berg sent to the
Linux kernel for the static world regulatory domain.

Signed-off-by: Ronald Wahl <ronald.wahl@raritan.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
wireless-regdb: embrace the Developer Certificate of Origin for contributions

The Linux kernel started to embrace a light weight development contribution
agreement process called the Developer Certificate of Origin (DCO) circa
2004. Attorneys all over the planet have conferred a lot of respect and
appreciation for this document and it provides a light weight alternative to
cumbersome and controversial Contribution License Agreements (CLAs).

Similar to streamlining FOSS licenses we also all stand to gain from
streamlining a light weight contribution agreement process for development
and in light of this the the Linux Foundation recently has made the DCO a
standalone project [0] so that any FOSS project under any FOSS license can
take advantage of the same gains. The motivation and intent is documented
only currently on my blog post [1].

Lets take advantage of the new shiny DCO and embrace it for contributions.

[0] http://developercertificate.org/
[1] http://www.do-not-panic.com/2014/02/developer-certificate-of-origin.html

Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
wireless-regdb: update NO's regulatory rules

This aligns the regdb entry with the current Norwegian
regulations.

 o Adding a reference to the authoritative source

 o Adding a note about TPC

 o Adjusting band edges to match the text of the regulations,
   except for merging 5470 - 5725 and 5725 – 5795 MHz using
   the lowest common EIRP limit

 o Syncronizing EIRP limits with the regulation text, fixing
   values, using mW instead of dBm, and adjusting for "no TPC"
   where applicable

 o Adding the bands 5710 – 5795 MHz, 5815 – 5850 MHz and
   17.1 - 17.3 GHz

An unofficial English translation of the regulations is available
from (attachment link on the right):
http://eng.npt.no/technical/frequency-management/frequency-licenses/permission-to-use-radio-frequencies
The relevant part is "Section 11. Wireless networks"

The reference in the db.txt comment is the actual authoritative
publication of these regulations, in Norwegian only.

Signed-off-by: Bjørn Mork <bjorn@mork.no>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
wireless-regdb: update regulatory.bin based on preceding changes.

Signed-off-by: John W. Linville <linville@tuxdriver.com>