diff options
Diffstat (limited to 'Documentation/networking/regulatory.txt')
-rw-r--r-- | Documentation/networking/regulatory.txt | 22 |
1 files changed, 9 insertions, 13 deletions
diff --git a/Documentation/networking/regulatory.txt b/Documentation/networking/regulatory.txt index a96989a8ff35..dcf31648414a 100644 --- a/Documentation/networking/regulatory.txt +++ b/Documentation/networking/regulatory.txt | |||
@@ -131,11 +131,13 @@ are expected to do this during initialization. | |||
131 | 131 | ||
132 | r = zd_reg2alpha2(mac->regdomain, alpha2); | 132 | r = zd_reg2alpha2(mac->regdomain, alpha2); |
133 | if (!r) | 133 | if (!r) |
134 | regulatory_hint(hw->wiphy, alpha2, NULL); | 134 | regulatory_hint(hw->wiphy, alpha2); |
135 | 135 | ||
136 | Example code - drivers providing a built in regulatory domain: | 136 | Example code - drivers providing a built in regulatory domain: |
137 | -------------------------------------------------------------- | 137 | -------------------------------------------------------------- |
138 | 138 | ||
139 | [NOTE: This API is not currently available, it can be added when required] | ||
140 | |||
139 | If you have regulatory information you can obtain from your | 141 | If you have regulatory information you can obtain from your |
140 | driver and you *need* to use this we let you build a regulatory domain | 142 | driver and you *need* to use this we let you build a regulatory domain |
141 | structure and pass it to the wireless core. To do this you should | 143 | structure and pass it to the wireless core. To do this you should |
@@ -167,7 +169,6 @@ struct ieee80211_regdomain mydriver_jp_regdom = { | |||
167 | 169 | ||
168 | Then in some part of your code after your wiphy has been registered: | 170 | Then in some part of your code after your wiphy has been registered: |
169 | 171 | ||
170 | int r; | ||
171 | struct ieee80211_regdomain *rd; | 172 | struct ieee80211_regdomain *rd; |
172 | int size_of_regd; | 173 | int size_of_regd; |
173 | int num_rules = mydriver_jp_regdom.n_reg_rules; | 174 | int num_rules = mydriver_jp_regdom.n_reg_rules; |
@@ -178,17 +179,12 @@ Then in some part of your code after your wiphy has been registered: | |||
178 | 179 | ||
179 | rd = kzalloc(size_of_regd, GFP_KERNEL); | 180 | rd = kzalloc(size_of_regd, GFP_KERNEL); |
180 | if (!rd) | 181 | if (!rd) |
181 | return -ENOMEM; | 182 | return -ENOMEM; |
182 | 183 | ||
183 | memcpy(rd, &mydriver_jp_regdom, sizeof(struct ieee80211_regdomain)); | 184 | memcpy(rd, &mydriver_jp_regdom, sizeof(struct ieee80211_regdomain)); |
184 | 185 | ||
185 | for (i=0; i < num_rules; i++) { | 186 | for (i=0; i < num_rules; i++) |
186 | memcpy(&rd->reg_rules[i], &mydriver_jp_regdom.reg_rules[i], | 187 | memcpy(&rd->reg_rules[i], |
187 | sizeof(struct ieee80211_reg_rule)); | 188 | &mydriver_jp_regdom.reg_rules[i], |
188 | } | 189 | sizeof(struct ieee80211_reg_rule)); |
189 | r = regulatory_hint(hw->wiphy, NULL, rd); | 190 | regulatory_struct_hint(rd); |
190 | if (r) { | ||
191 | kfree(rd); | ||
192 | return r; | ||
193 | } | ||
194 | |||