regulatory.bin(5) [debian man page]

regulatory.bin(5)						       Linux							 regulatory.bin(5)

NAME

       regulatory.bin - The Linux wireless regulatory database

Description
       regulatory.bin is the file used by the Linux wireless subsystem to keep its regulatory database information. It is read by crda upon the
       Linux kernel's request for regulatory information for a specific ISO / IEC 3166 alpha2 country code. The regulatory database is kept in a
       small binary format for size and code efficiency. The regulatory.bin file can be parsed and read in human format by using the regdbdump
       command. The regulatory.bin file should be updated upon regulatory changes or corrections.

Upkeeping
       The regulatory database is maintained by the community as such you are encouraged to send any corrections or updates to the linux-wireless
       mailing list: linux-wireless@vger.kernel.org

SEE ALSO

       regdbdump(8) crda(8) iw(8)

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

regulatory.bin							  23 January 2009						 regulatory.bin(5)

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)