regulatory_hint(9) [centos man page]

REGULATORY_HINT(9)					  Regulatory enforcement infrast					REGULATORY_HINT(9)

NAME

       regulatory_hint - driver hint to the wireless core a regulatory domain

SYNOPSIS

       int regulatory_hint(struct wiphy * wiphy, const char * alpha2);

ARGUMENTS

       wiphy
	   the wireless device giving the hint (used only for reporting conflicts)

       alpha2
	   the ISO/IEC 3166 alpha2 the driver claims its regulatory domain should be in. If rd is set this should be NULL. Note that if you set
	   this to NULL you should still set rd->alpha2 to some accepted alpha2.

DESCRIPTION

       Wireless drivers can use this function to hint to the wireless core what it believes should be the current regulatory domain by giving it
       an ISO/IEC 3166 alpha2 country code it knows its regulatory domain should be in or by providing a completely build regulatory domain. If
       the driver provides an ISO/IEC 3166 alpha2 userspace will be queried for a regulatory domain structure for the respective country.

       The wiphy must have been registered to cfg80211 prior to this call. For cfg80211 drivers this means you must first use wiphy_register, for
       mac80211 drivers you must first use ieee80211_register_hw.

       Drivers should check the return value, its possible you can get an -ENOMEM.

RETURN

       0 on success. -ENOMEM.

AUTHOR

       Johannes Berg <johannes@sipsolutions.net>
	   Author.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014							REGULATORY_HINT(9)

CRDA(8) 							       Linux								   CRDA(8)

NAME

       crda - send to the kernel a wireless regulatory domain for a given ISO / IEC 3166 alpha2

SYNOPSIS

       crda

Description
       crda is the Linux wireless central regulatory domain agent.  crda is intended to be used by udev scripts and should not be run manually
       unless debugging udev scripts.  crda is triggered to run by the kernel by sending a udev event upon a new regulatory domain change. Regula-
       tory domain changes are triggered by the wireless kernel subsystem (upon initialization and on reception of country IEs), wireless drivers,
       or userspace (see iw ). Upon a regulatory domain change the kernel sends a udev change event for the regulatory platform. The kernel
       ignores regulatory domains sent to it if it does not expect them. The regulatory domain is read by crda from the regulatory.bin file.

RSA Digital Signature
       If built with openssl or gcrypt support crda will have embedded into it an RSA digital signature which will prevent it from reading cor-
       rupted or non-authored regulatory.bin files. Authorship is respected by the RSA public key packed into crda.  This specific crda package
       has been built with an RSA public key from John Linville (the Linux wireless kernel maintainer) and as such will only read regulatory.bin
       files signed by him. For further information see the regulatory.bin man page.

UDEV RULE

       A udev regulatory rule must be put in place in order to receive and parse udev events from the kernel in order to get udev to call crda
       with the passed ISO / IEC 3166 alpha2 country code.  An example udev rule which can be used (usually in /lib/udev/rules.d/85-regula-
       tory.rules ):

       KERNEL=="regulatory*", ACTION=="change", SUBSYSTEM=="platform", RUN+="/sbin/crda"

Environment variable
       Set the COUNTRY environment variable with a specific ISO / IEC 3166 alpha2 country code and then run crda without arguments. This will send
       a regulatory domain for that alpha2 to the kernel.

SEE ALSO

       iw(8) regulatory.bin(5)

       http://wireless.kernel.org/en/developers/Regulatory/

crda								  23 January 2009							   CRDA(8)