Lines Matching refs:regulatory
4 Linux wireless regulatory documentation
8 regulatory infrastructure works.
14 Keeping regulatory domains in userspace
17 Due to the dynamic nature of regulatory domains we keep them
19 to the kernel one regulatory domain to be used as the central
20 core regulatory domain all wireless devices should adhere to.
22 How to get regulatory domains to the kernel
25 When the regulatory domain is first set up, the kernel will request a
26 database file (regulatory.db) containing all the regulatory rules. It
30 How to get regulatory domains to the kernel (old CRDA solution)
33 Userspace gets a regulatory domain in the kernel by having
35 expected regulatory domains will be respected by the kernel.
38 is CRDA - central regulatory domain agent. Its documented here:
43 it needs a new regulatory domain. A udev rule can be put in place
44 to trigger crda to send the respective regulatory domain for a
49 # Example file, should be put in /etc/udev/rules.d/regulatory.rules
50 KERNEL=="regulatory*", ACTION=="change", SUBSYSTEM=="platform", RUN+="/sbin/crda"
54 Who asks for regulatory domains?
65 # set regulatory domain to "Costa Rica"
68 This will request the kernel to set the regulatory domain to
70 to provide a regulatory domain for the alpha2 specified by the user
76 regulatory domain is required. More on this to be added
81 If drivers determine they need a specific regulatory domain
84 crda can provide back a regulatory domain for that country or
85 they can build their own regulatory domain based on internal
89 regulatory hint with an alpha2. For these drivers there is an additional
91 regulatory data. This additional check can be used by drivers by
93 is called when the core's regulatory domain has been changed. The driver
100 Device drivers who provide their own built regulatory domain
109 by having a mapping of your device's EEPROM country/regulatory
149 Example code - drivers providing a built in regulatory domain:
154 If you have regulatory information you can obtain from your
155 driver and you *need* to use this we let you build a regulatory domain
157 kmalloc() a structure big enough to hold your regulatory domain
159 call regulatory_hint() with the regulatory domain structure in it.
161 Bellow is a simple example, with a regulatory domain cached using the stack.
164 Example cache of some regulatory domain::
205 Statically compiled regulatory database