linux.git/net/wireless/reg.h, branch v3.4

cfg80211: relicense reg.c reg.h and genregdb.awk to ISC

2012-01-04T19:30:41+00:00

Following the tradition we have had with ath5k, ath9k, CRDA,
wireless-regdb I'd like to license this code under the permissive ISC
license for the code sharing purposes with other OSes, it'd sure be nice
to help the landscape in this area. Although I am %82.89 owner of the
regulatory code I have asked every contributor to the regulatory code
and have receieved positive Acked-bys from everyone except two deceased
entities:

 o Frans Pop RIP 2010 [0]
	- Frans Pop 
	- Frans Pop 
 o Nokia     RIP February, 11, 2011 [1], [2]
	- ext-yuri.ershov@nokia.com
	- kalle.valo@nokia.com

Frans Pop's contribution was a simple patch 55f98938, titled,
"wireless: remove trailing space in messages" which just add a \n
to some printk lines. I'm going to treat these additions as
uncopyrightable.

As for the contributions made by employees on behalf of Nokia
my contact point was Petri Karhula  but
after one month he noted he had not been able to get traction from the
legal department on this request, as such it I proceeded by replacing
their contributions in previous patches.

The end goal is to help a clean rewrite that starts in userspace
that is shared under ISC license which currently is taking place with
the regulatory simulator [3].

[0] http://lists.debian.org/debian-devel/2011/12/msg00263.html
[1] http://press.nokia.com/2011/02/11/nokia-outlines-new-strategy-introduces-new-leadership-operational-structure/
[2] http://NokiaPlanB.com
[3] git://github.com/mcgrof/regsim.git

Acked-by: Thadeu Lima de Souza Cascardo 
Acked-by: Dan Carpenter 
Acked-by: Mihai Moldovan 
Acked-by: Uwe Kleine-König 
Acked-by: Sven Neumann 
Acked-by: Johannes Berg 
Acked-by: Tomas Winkler 
Acked-by: Tony Vroon 
Acked-by: Pavel Roskin 
Acked-by: Bob Copeland 
Acked-by: Lucas De Marchi 
Acked-by: Pat Erley 
Acked-by: Tejun Heo 
Acked-by: John W. Linville 
Acked-by: Chris Wright 
Acked-by: Joe Perches 
Acked-by: Paul Gortmaker 
Acked-by: John Gordon 
Acked-by: Simon Barber 
Acked-by: Rajkumar Manoharan 
Acked-by: Jiri Benc 
Acked-by: Bruno Randolf 
Acked-by: Scott James Remnant 
Acked-by: Roel Kluin 
Signed-off-by: Luis R. Rodriguez 
Signed-off-by: John W. Linville

cfg80211: process regulatory DFS region for countries

2011-11-21T21:20:41+00:00

The wireless-regdb now has support for mapping a country to
one DFS region. CRDA sends this to us now so process it
so we can provide that hint to drivers. This will later be
used by code for processing DFS in a way that meets the
criteria for the DFS region the country belongs to.

Signed-off-by: Luis R. Rodriguez 
Signed-off-by: John W. Linville

cfg80211: hold reg_mutex when updating regulatory

2011-09-14T17:26:39+00:00

The function wiphy_update_regulatory() uses the static variable
last_request and thus needs to be called with reg_mutex held.
This is the case for all users in reg.c, but the function was
exported for use by wiphy_register(), from where it is called
without the lock being held.

Fix this by making wiphy_update_regulatory() private and introducing
regulatory_update() as a wrapper that acquires and holds the lock.

Signed-off-by: Sven Neumann 
Cc: John W. Linville 
Cc: Luis R. Rodriguez 
Cc: Daniel Mack 
Cc: linux-wireless@vger.kernel.org
Acked-by:  Luis R. Rodriguez 
Signed-off-by: John W. Linville

net/wireless: add COUNTRY to to regulatory device uevent

2011-03-09T21:10:57+00:00

Regulatory devices issue change uevents to inform userspace of a need
to call the crda tool; however these can often be sent before udevd is
running, and were not previously included in the results of
udevadm trigger (which requests a new change event using the /uevent
attribute of the sysfs object).

Add a uevent function to the device type which includes the COUNTRY
information from the last request if it has yet to be processed, the
case of multiple requests is already handled in the code by checking
whether an unprocessed one is queued in the same manner and refusing
to queue a new one.

The existing udev rule continues to work as before.

Signed-off-by: Scott James Remnant 
Acked-By: Kay Sievers 
Acked-by: Greg Kroah-Hartman 
Signed-off-by: John W. Linville

wireless: move regulatory_init to .init.text

2010-06-18T19:11:13+00:00

regulatory_init is only called by cfg80211_init which is in .init.text,
too.

Signed-off-by: Uwe Kleine-König 
Signed-off-by: John W. Linville

cfg80211: add regulatory hint disconnect support

2010-02-01T20:40:06+00:00

This adds a new regulatory hint to be used when we know all
devices have been disconnected and idle. This can happen
when we suspend, for instance. When we disconnect we can
no longer assume the same regulatory rules learned from
a country IE or beacon hints are applicable so restore
regulatory settings to an initial state.

Since driver hints are cached on the wiphy that called
the hint, those hints are not reproduced onto cfg80211
as the wiphy will respect its own wiphy->regd regardless.

Signed-off-by: Luis R. Rodriguez 
Signed-off-by: John W. Linville

cfg80211: make regulatory_hint_11d() band specific

2010-01-15T22:02:06+00:00

In practice APs do not send country IE channel triplets for channels
the AP is not operating on and if they were to do so they would have
to use the regulatory extension which we currently do not process.
No AP has been seen in practice that does this though so just drop
those country IEs.

Additionally it has been noted the first series of country IE
channels triplets are specific to the band the AP sends. Propagate
the band on which the country IE was found on reject the country
IE then if the triplets are ever oustide of the band.

Although we now won't process country IE information with multiple
band information we leave the intersection work as is as it is
technically possible for someone to want to eventually process these
type of country IEs with regulatory extensions.

Cc: Jouni Malinen 
Cc: Johannes Berg 
Signed-off-by: Luis R. Rodriguez 
Signed-off-by: John W. Linville

Merge branch 'master' of master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6

2009-08-13T00:44:53+00:00

Conflicts:
	arch/microblaze/include/asm/socket.h

cfg80211: enable country IE support to all cfg80211 drivers

2009-08-04T20:44:19+00:00

Since the bss is always set now once we are connected, if the
bss has its own information element we refer to it and pass that
instead of relying on mac80211's parsing.

Now all cfg80211 drivers get country IE support, automatically and
we reduce the call overhead that we had on mac80211 which called this
upon every beacon and instead now call this only upon a successfull
connection by a STA on cfg80211.

Acked-by: Johannes Berg 
Signed-off-by: Luis R. Rodriguez 
Signed-off-by: John W. Linville

cfg80211: fix regression on beacon world roaming feature

2009-08-03T20:31:21+00:00

A regression was added through patch a4ed90d6:

"cfg80211: respect API on orig_flags on channel for beacon hint"

We did indeed respect _orig flags but the intention was not clearly
stated in the commit log. This patch fixes firmware issues picked
up by iwlwifi when we lift passive scan of beaconing restrictions
on channels its EEPROM has been configured to always enable.

By doing so though we also disallowed beacon hints on devices
registering their wiphy with custom world regulatory domains
enabled, this happens to be currently ath5k, ath9k and ar9170.
The passive scan and beacon restrictions on those devices would
never be lifted even if we did find a beacon and the hardware did
support such enhancements when world roaming.

Since Johannes indicates iwlwifi firmware cannot be changed to
allow beacon hinting we set up a flag now to specifically allow
drivers to disable beacon hints for devices which cannot use them.

We enable the flag on iwlwifi to disable beacon hints and by default
enable it for all other drivers. It should be noted beacon hints lift
passive scan flags and beacon restrictions when we receive a beacon from
an AP on any 5 GHz non-DFS channels, and channels 12-14 on the 2.4 GHz
band. We don't bother with channels 1-11 as those channels are allowed
world wide.

This should fix world roaming for ath5k, ath9k and ar9170, thereby
improving scan time when we receive the first beacon from any AP,
and also enabling beaconing operation (AP/IBSS/Mesh) on cards which
would otherwise not be allowed to do so. Drivers not using custom
regulatory stuff (wiphy_apply_custom_regulatory()) were not affected
by this as the orig_flags for the channels would have been cleared
upon wiphy registration.

I tested this with a world roaming ath5k card.

Cc: Jouni Malinen 
Signed-off-by: Luis R. Rodriguez 
Reviewed-by: Johannes Berg 
Signed-off-by: John W. Linville