€•pc      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ)/translations/zh_CN/networking/regulatory”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/zh_TW/networking/regulatory”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/it_IT/networking/regulatory”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/ja_JP/networking/regulatory”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/ko_KR/networking/regulatory”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/sp_SP/networking/regulatory”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1h¡hhhžhhŸŒC/var/lib/git/docbuild/linux/Documentation/networking/regulatory.rst”h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ'Linux wireless regulatory documentation”h]”hŒ'Linux wireless regulatory documentation”…””}”(hh»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh¶hžhhŸh³h KubhŒ	paragraph”“”)”}”(hŒ_This document gives a brief review over how the Linux wireless
regulatory infrastructure works.”h]”hŒ_This document gives a brief review over how the Linux wireless
regulatory infrastructure works.”…””}”(hhËhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶hžhubhÊ)”}”(hŒFMore up to date information can be obtained at the project's web page:”h]”hŒHMore up to date information can be obtained at the projectâ€™s web page:”…””}”(hhÙhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K
hh¶hžhubhÊ)”}”(hŒ9https://wireless.wiki.kernel.org/en/developers/Regulatory”h]”hŒ	reference”“”)”}”(hhéh]”hŒ9https://wireless.wiki.kernel.org/en/developers/Regulatory”…””}”(hhíhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”héuh1hëhhçubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶hžhubhµ)”}”(hhh]”(hº)”}”(hŒ'Keeping regulatory domains in userspace”h]”hŒ'Keeping regulatory domains in userspace”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj  hžhhŸh³h KubhÊ)”}”(hŒõDue to the dynamic nature of regulatory domains we keep them
in userspace and provide a framework for userspace to upload
to the kernel one regulatory domain to be used as the central
core regulatory domain all wireless devices should adhere to.”h]”hŒõDue to the dynamic nature of regulatory domains we keep them
in userspace and provide a framework for userspace to upload
to the kernel one regulatory domain to be used as the central
core regulatory domain all wireless devices should adhere to.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj  hžhubeh}”(h]”Œ'keeping-regulatory-domains-in-userspace”ah ]”h"]”Œ'keeping regulatory domains in userspace”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒ+How to get regulatory domains to the kernel”h]”hŒ+How to get regulatory domains to the kernel”…””}”(hj+  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj(  hžhhŸh³h KubhÊ)”}”(hŒßWhen the regulatory domain is first set up, the kernel will request a
database file (regulatory.db) containing all the regulatory rules. It
will then use that database when it needs to look up the rules for a
given country.”h]”hŒßWhen the regulatory domain is first set up, the kernel will request a
database file (regulatory.db) containing all the regulatory rules. It
will then use that database when it needs to look up the rules for a
given country.”…””}”(hj9  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj(  hžhubeh}”(h]”Œ+how-to-get-regulatory-domains-to-the-kernel”ah ]”h"]”Œ+how to get regulatory domains to the kernel”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒ?How to get regulatory domains to the kernel (old CRDA solution)”h]”hŒ?How to get regulatory domains to the kernel (old CRDA solution)”…””}”(hjR  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjO  hžhhŸh³h KubhÊ)”}”(hŒ°Userspace gets a regulatory domain in the kernel by having
a userspace agent build it and send it via nl80211. Only
expected regulatory domains will be respected by the kernel.”h]”hŒ°Userspace gets a regulatory domain in the kernel by having
a userspace agent build it and send it via nl80211. Only
expected regulatory domains will be respected by the kernel.”…””}”(hj`  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K!hjO  hžhubhÊ)”}”(hŒA currently available userspace agent which can accomplish this
is CRDA - central regulatory domain agent. Its documented here:”h]”hŒA currently available userspace agent which can accomplish this
is CRDA - central regulatory domain agent. Its documented here:”…””}”(hjn  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K%hjO  hžhubhÊ)”}”(hŒ>https://wireless.wiki.kernel.org/en/developers/Regulatory/CRDA”h]”hì)”}”(hj~  h]”hŒ>https://wireless.wiki.kernel.org/en/developers/Regulatory/CRDA”…””}”(hj€  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j~  uh1hëhj|  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K(hjO  hžhubhÊ)”}”(hŒÚEssentially the kernel will send a udev event when it knows
it needs a new regulatory domain. A udev rule can be put in place
to trigger crda to send the respective regulatory domain for a
specific ISO/IEC 3166 alpha2.”h]”hŒÚEssentially the kernel will send a udev event when it knows
it needs a new regulatory domain. A udev rule can be put in place
to trigger crda to send the respective regulatory domain for a
specific ISO/IEC 3166 alpha2.”…””}”(hj”  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K*hjO  hžhubhÊ)”}”(hŒ0Below is an example udev rule which can be used:”h]”hŒ0Below is an example udev rule which can be used:”…””}”(hj¢  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K/hjO  hžhubhÊ)”}”(hŒ•# Example file, should be put in /etc/udev/rules.d/regulatory.rules
KERNEL=="regulatory*", ACTION=="change", SUBSYSTEM=="platform", RUN+="/sbin/crda"”h]”hŒ¥# Example file, should be put in /etc/udev/rules.d/regulatory.rules
KERNEL==â€regulatory*â€, ACTION==â€changeâ€, SUBSYSTEM==â€platformâ€, RUN+=â€/sbin/crdaâ€”…””}”(hj°  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K1hjO  hžhubhÊ)”}”(hŒKThe alpha2 is passed as an environment variable under the variable COUNTRY.”h]”hŒKThe alpha2 is passed as an environment variable under the variable COUNTRY.”…””}”(hj¾  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K4hjO  hžhubeh}”(h]”Œ=how-to-get-regulatory-domains-to-the-kernel-old-crda-solution”ah ]”h"]”Œ?how to get regulatory domains to the kernel (old crda solution)”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒ Who asks for regulatory domains?”h]”hŒ Who asks for regulatory domains?”…””}”(hj×  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjÔ  hžhhŸh³h K7ubhŒbullet_list”“”)”}”(hhh]”hŒ	list_item”“”)”}”(hŒUsers
”h]”hÊ)”}”(hŒUsers”h]”hŒUsers”…””}”(hjð  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K9hjì  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jê  hjç  hžhhŸh³h Nubah}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ*”uh1jå  hŸh³h K9hjÔ  hžhubhÊ)”}”(hŒUsers can use iw:”h]”hŒUsers can use iw:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K;hjÔ  hžhubhÊ)”}”(hŒ:https://wireless.wiki.kernel.org/en/users/Documentation/iw”h]”hì)”}”(hj  h]”hŒ:https://wireless.wiki.kernel.org/en/users/Documentation/iw”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j  uh1hëhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K=hjÔ  hžhubhÊ)”}”(hŒAn example::”h]”hŒAn example:”…””}”(hj2  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K?hjÔ  hžhubhŒliteral_block”“”)”}”(hŒ5# set regulatory domain to "Costa Rica"
iw reg set CR”h]”hŒ5# set regulatory domain to "Costa Rica"
iw reg set CR”…””}”hjB  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j@  hŸh³h KAhjÔ  hžhubhÊ)”}”(hŒÖThis will request the kernel to set the regulatory domain to
the specified alpha2. The kernel in turn will then ask userspace
to provide a regulatory domain for the alpha2 specified by the user
by sending a uevent.”h]”hŒÖThis will request the kernel to set the regulatory domain to
the specified alpha2. The kernel in turn will then ask userspace
to provide a regulatory domain for the alpha2 specified by the user
by sending a uevent.”…””}”(hjP  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KDhjÔ  hžhubjæ  )”}”(hhh]”jë  )”}”(hŒ5Wireless subsystems for Country Information elements
”h]”hÊ)”}”(hŒ4Wireless subsystems for Country Information elements”h]”hŒ4Wireless subsystems for Country Information elements”…””}”(hje  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KIhja  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jê  hj^  hžhhŸh³h Nubah}”(h]”h ]”h"]”h$]”h&]”j
  j  uh1jå  hŸh³h KIhjÔ  hžhubhÊ)”}”(hŒŒThe kernel will send a uevent to inform userspace a new
regulatory domain is required. More on this to be added
as its integration is added.”h]”hŒŒThe kernel will send a uevent to inform userspace a new
regulatory domain is required. More on this to be added
as its integration is added.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KKhjÔ  hžhubjæ  )”}”(hhh]”jë  )”}”(hŒDrivers
”h]”hÊ)”}”(hŒDrivers”h]”hŒDrivers”…””}”(hj”  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KOhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jê  hj  hžhhŸh³h Nubah}”(h]”h ]”h"]”h$]”h&]”j
  j  uh1jå  hŸh³h KOhjÔ  hžhubhÊ)”}”(hXj  If drivers determine they need a specific regulatory domain
set they can inform the wireless core using regulatory_hint().
They have two options -- they either provide an alpha2 so that
crda can provide back a regulatory domain for that country or
they can build their own regulatory domain based on internal
custom knowledge so the wireless core can respect it.”h]”hXj  If drivers determine they need a specific regulatory domain
set they can inform the wireless core using regulatory_hint().
They have two options -- they either provide an alpha2 so that
crda can provide back a regulatory domain for that country or
they can build their own regulatory domain based on internal
custom knowledge so the wireless core can respect it.”…””}”(hj®  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KQhjÔ  hžhubhÊ)”}”(hXà  *Most* drivers will rely on the first mechanism of providing a
regulatory hint with an alpha2. For these drivers there is an additional
check that can be used to ensure compliance based on custom EEPROM
regulatory data. This additional check can be used by drivers by
registering on its struct wiphy a reg_notifier() callback. This notifier
is called when the core's regulatory domain has been changed. The driver
can use this to review the changes made and also review who made them
(driver, user, country IE) and determine what to allow based on its
internal EEPROM data. Devices drivers wishing to be capable of world
roaming should use this callback. More on world roaming will be
added to this document when its support is enabled.”h]”(hŒemphasis”“”)”}”(hŒ*Most*”h]”hŒMost”…””}”(hjÂ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÀ  hj¼  ubhXÜ   drivers will rely on the first mechanism of providing a
regulatory hint with an alpha2. For these drivers there is an additional
check that can be used to ensure compliance based on custom EEPROM
regulatory data. This additional check can be used by drivers by
registering on its struct wiphy a reg_notifier() callback. This notifier
is called when the coreâ€™s regulatory domain has been changed. The driver
can use this to review the changes made and also review who made them
(driver, user, country IE) and determine what to allow based on its
internal EEPROM data. Devices drivers wishing to be capable of world
roaming should use this callback. More on world roaming will be
added to this document when its support is enabled.”…””}”(hj¼  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KXhjÔ  hžhubhÊ)”}”(hŒÔDevice drivers who provide their own built regulatory domain
do not need a callback as the channels registered by them are
the only ones that will be allowed and therefore *additional*
channels cannot be enabled.”h]”(hŒ¬Device drivers who provide their own built regulatory domain
do not need a callback as the channels registered by them are
the only ones that will be allowed and therefore ”…””}”(hjÚ  hžhhŸNh NubjÁ  )”}”(hŒ*additional*”h]”hŒ
additional”…””}”(hjâ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÀ  hjÚ  ubhŒ
channels cannot be enabled.”…””}”(hjÚ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KdhjÔ  hžhubeh}”(h]”Œwho-asks-for-regulatory-domains”ah ]”h"]”Œ who asks for regulatory domains?”ah$]”h&]”uh1h´hh¶hžhhŸh³h K7ubhµ)”}”(hhh]”(hº)”}”(hŒ)Example code - drivers hinting an alpha2:”h]”hŒ)Example code - drivers hinting an alpha2:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj  hžhhŸh³h KjubhÊ)”}”(hŒ¯This example comes from the zd1211rw device driver. You can start
by having a mapping of your device's EEPROM country/regulatory
domain value to a specific alpha2 as follows::”h]”hŒ°This example comes from the zd1211rw device driver. You can start
by having a mapping of your deviceâ€™s EEPROM country/regulatory
domain value to a specific alpha2 as follows:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Klhj  hžhubjA  )”}”(hXX  static struct zd_reg_alpha2_map reg_alpha2_map[] = {
      { ZD_REGDOMAIN_FCC, "US" },
      { ZD_REGDOMAIN_IC, "CA" },
      { ZD_REGDOMAIN_ETSI, "DE" }, /* Generic ETSI, use most restrictive */
      { ZD_REGDOMAIN_JAPAN, "JP" },
      { ZD_REGDOMAIN_JAPAN_ADD, "JP" },
      { ZD_REGDOMAIN_SPAIN, "ES" },
      { ZD_REGDOMAIN_FRANCE, "FR" },”h]”hXX  static struct zd_reg_alpha2_map reg_alpha2_map[] = {
      { ZD_REGDOMAIN_FCC, "US" },
      { ZD_REGDOMAIN_IC, "CA" },
      { ZD_REGDOMAIN_ETSI, "DE" }, /* Generic ETSI, use most restrictive */
      { ZD_REGDOMAIN_JAPAN, "JP" },
      { ZD_REGDOMAIN_JAPAN_ADD, "JP" },
      { ZD_REGDOMAIN_SPAIN, "ES" },
      { ZD_REGDOMAIN_FRANCE, "FR" },”…””}”hj!  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j@  hŸh³h Kphj  hžhubhÊ)”}”(hŒVThen you can define a routine to map your read EEPROM value to an alpha2,
as follows::”h]”hŒUThen you can define a routine to map your read EEPROM value to an alpha2,
as follows:”…””}”(hj/  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kyhj  hžhubjA  )”}”(hX×  static int zd_reg2alpha2(u8 regdomain, char *alpha2)
{
      unsigned int i;
      struct zd_reg_alpha2_map *reg_map;
              for (i = 0; i < ARRAY_SIZE(reg_alpha2_map); i++) {
                      reg_map = &reg_alpha2_map[i];
                      if (regdomain == reg_map->reg) {
                      alpha2[0] = reg_map->alpha2[0];
                      alpha2[1] = reg_map->alpha2[1];
                      return 0;
              }
      }
      return 1;
}”h]”hX×  static int zd_reg2alpha2(u8 regdomain, char *alpha2)
{
      unsigned int i;
      struct zd_reg_alpha2_map *reg_map;
              for (i = 0; i < ARRAY_SIZE(reg_alpha2_map); i++) {
                      reg_map = &reg_alpha2_map[i];
                      if (regdomain == reg_map->reg) {
                      alpha2[0] = reg_map->alpha2[0];
                      alpha2[1] = reg_map->alpha2[1];
                      return 0;
              }
      }
      return 1;
}”…””}”hj=  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j@  hŸh³h K|hj  hžhubhÊ)”}”(hŒÃLastly, you can then hint to the core of your discovered alpha2, if a match
was found. You need to do this after you have registered your wiphy. You
are expected to do this during initialization.”h]”hŒÃLastly, you can then hint to the core of your discovered alpha2, if a match
was found. You need to do this after you have registered your wiphy. You
are expected to do this during initialization.”…””}”(hjK  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K‹hj  hžhubjA  )”}”(hŒ^r = zd_reg2alpha2(mac->regdomain, alpha2);
if (!r)
        regulatory_hint(hw->wiphy, alpha2);”h]”hŒ^r = zd_reg2alpha2(mac->regdomain, alpha2);
if (!r)
        regulatory_hint(hw->wiphy, alpha2);”…””}”hjY  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j@  hŸh³h K‘hj  hžhubeh}”(h]”Œ&example-code-drivers-hinting-an-alpha2”ah ]”h"]”Œ)example code - drivers hinting an alpha2:”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kjubhµ)”}”(hhh]”(hº)”}”(hŒ>Example code - drivers providing a built in regulatory domain:”h]”hŒ>Example code - drivers providing a built in regulatory domain:”…””}”(hjr  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjo  hžhhŸh³h K–ubhÊ)”}”(hŒJ[NOTE: This API is not currently available, it can be added when required]”h]”hŒJ[NOTE: This API is not currently available, it can be added when required]”…””}”(hj€  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K˜hjo  hžhubhÊ)”}”(hX  If you have regulatory information you can obtain from your
driver and you *need* to use this we let you build a regulatory domain
structure and pass it to the wireless core. To do this you should
kmalloc() a structure big enough to hold your regulatory domain
structure and you should then fill it with your data. Finally you simply
call regulatory_hint() with the regulatory domain structure in it.”h]”(hŒKIf you have regulatory information you can obtain from your
driver and you ”…””}”(hjŽ  hžhhŸNh NubjÁ  )”}”(hŒ*need*”h]”hŒneed”…””}”(hj–  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÀ  hjŽ  ubhX?   to use this we let you build a regulatory domain
structure and pass it to the wireless core. To do this you should
kmalloc() a structure big enough to hold your regulatory domain
structure and you should then fill it with your data. Finally you simply
call regulatory_hint() with the regulatory domain structure in it.”…””}”(hjŽ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kšhjo  hžhubhÊ)”}”(hŒ’Below is a simple example, with a regulatory domain cached using the stack.
Your implementation may vary (read EEPROM cache instead, for example).”h]”hŒ’Below is a simple example, with a regulatory domain cached using the stack.
Your implementation may vary (read EEPROM cache instead, for example).”…””}”(hj®  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K¡hjo  hžhubhÊ)”}”(hŒ)Example cache of some regulatory domain::”h]”hŒ(Example cache of some regulatory domain:”…””}”(hj¼  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K¤hjo  hžhubjA  )”}”(hXr  struct ieee80211_regdomain mydriver_jp_regdom = {
      .n_reg_rules = 3,
      .alpha2 =  "JP",
      //.alpha2 =  "99", /* If I have no alpha2 to map it to */
      .reg_rules = {
              /* IEEE 802.11b/g, channels 1..14 */
              REG_RULE(2412-10, 2484+10, 40, 6, 20, 0),
              /* IEEE 802.11a, channels 34..48 */
              REG_RULE(5170-10, 5240+10, 40, 6, 20,
                      NL80211_RRF_NO_IR),
              /* IEEE 802.11a, channels 52..64 */
              REG_RULE(5260-10, 5320+10, 40, 6, 20,
                      NL80211_RRF_NO_IR|
                      NL80211_RRF_DFS),
      }
};”h]”hXr  struct ieee80211_regdomain mydriver_jp_regdom = {
      .n_reg_rules = 3,
      .alpha2 =  "JP",
      //.alpha2 =  "99", /* If I have no alpha2 to map it to */
      .reg_rules = {
              /* IEEE 802.11b/g, channels 1..14 */
              REG_RULE(2412-10, 2484+10, 40, 6, 20, 0),
              /* IEEE 802.11a, channels 34..48 */
              REG_RULE(5170-10, 5240+10, 40, 6, 20,
                      NL80211_RRF_NO_IR),
              /* IEEE 802.11a, channels 52..64 */
              REG_RULE(5260-10, 5320+10, 40, 6, 20,
                      NL80211_RRF_NO_IR|
                      NL80211_RRF_DFS),
      }
};”…””}”hjÊ  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j@  hŸh³h K¦hjo  hžhubhÊ)”}”(hŒEThen in some part of your code after your wiphy has been registered::”h]”hŒDThen in some part of your code after your wiphy has been registered:”…””}”(hjØ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K·hjo  hžhubjA  )”}”(hX0  struct ieee80211_regdomain *rd;
int size_of_regd;
int num_rules = mydriver_jp_regdom.n_reg_rules;
unsigned int i;

size_of_regd = sizeof(struct ieee80211_regdomain) +
        (num_rules * sizeof(struct ieee80211_reg_rule));

rd = kzalloc(size_of_regd, GFP_KERNEL);
if (!rd)
        return -ENOMEM;

memcpy(rd, &mydriver_jp_regdom, sizeof(struct ieee80211_regdomain));

for (i=0; i < num_rules; i++)
        memcpy(&rd->reg_rules[i],
               &mydriver_jp_regdom.reg_rules[i],
               sizeof(struct ieee80211_reg_rule));
regulatory_struct_hint(rd);”h]”hX0  struct ieee80211_regdomain *rd;
int size_of_regd;
int num_rules = mydriver_jp_regdom.n_reg_rules;
unsigned int i;

size_of_regd = sizeof(struct ieee80211_regdomain) +
        (num_rules * sizeof(struct ieee80211_reg_rule));

rd = kzalloc(size_of_regd, GFP_KERNEL);
if (!rd)
        return -ENOMEM;

memcpy(rd, &mydriver_jp_regdom, sizeof(struct ieee80211_regdomain));

for (i=0; i < num_rules; i++)
        memcpy(&rd->reg_rules[i],
               &mydriver_jp_regdom.reg_rules[i],
               sizeof(struct ieee80211_reg_rule));
regulatory_struct_hint(rd);”…””}”hjæ  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j@  hŸh³h K¹hjo  hžhubeh}”(h]”Œ;example-code-drivers-providing-a-built-in-regulatory-domain”ah ]”h"]”Œ>example code - drivers providing a built in regulatory domain:”ah$]”h&]”uh1h´hh¶hžhhŸh³h K–ubhµ)”}”(hhh]”(hº)”}”(hŒ'Statically compiled regulatory database”h]”hŒ'Statically compiled regulatory database”…””}”(hjÿ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjü  hžhhŸh³h KÎubhÊ)”}”(hŒ‰When a database should be fixed into the kernel, it can be provided as a
firmware file at build time that is then linked into the kernel.”h]”hŒ‰When a database should be fixed into the kernel, it can be provided as a
firmware file at build time that is then linked into the kernel.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KÐhjü  hžhubeh}”(h]”Œ'statically-compiled-regulatory-database”ah ]”h"]”Œ'statically compiled regulatory database”ah$]”h&]”uh1h´hh¶hžhhŸh³h KÎubeh}”(h]”Œ'linux-wireless-regulatory-documentation”ah ]”h"]”Œ'linux wireless regulatory documentation”ah$]”h&]”uh1h´hhhžhhŸh³h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h³uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¹NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jN  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h³Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j(  j%  j%  j"  jL  jI  jÑ  jÎ  jÿ  jü  jl  ji  jù  jö  j   j  uŒ	nametypes”}”(j(  ‰j%  ‰jL  ‰jÑ  ‰jÿ  ‰jl  ‰jù  ‰j   ‰uh}”(j%  h¶j"  j  jI  j(  jÎ  jO  jü  jÔ  ji  j  jö  jo  j  jü  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.