regdomain.xml

[Aaron]

On 7/21/2020 5:52 PM, Adrian Chadd wrote:
> On Tue, 21 Jul 2020 at 14:48, Aaron <notjanedeere at gmail.com 
> <mailto:notjanedeere at gmail.com>> wrote:
>
>     On 7/21/2020 5:41 PM, Adrian Chadd wrote:
>>     (cc'ing the list again, hehe :-)
>>     On Tue, 21 Jul 2020 at 14:35, Aaron <notjanedeere at gmail.com
>>     <mailto:notjanedeere at gmail.com>> wrote:
>>
>>         On 7/21/2020 5:33 PM, Adrian Chadd wrote:
>>
>>>         Ok. Please do dig into it.
>>>
>>>         Do try to treat the regdomain code as a black box - input is
>>>         "what regulatory domain do we want" and the output is "a
>>>         list of channels and properties of those channels that we
>>>         currently program into net80211." Hopefully we don't have to
>>>         change the net80211 channel API!
>>         This is the sort of information I'm looking for!  So far all
>>         I'm looking at is an XML file. Where would I find the
>>         "regdomain code"?
>>
>>
>>     (We really should write a page in the wiki about regdomain stuff.)
>>
>>     So, here's my suggestion:
>>
>>     * get freebsd with a supported wifi card
>>     * look at what happens when you type "ifconfig wlan0 create
>>     wlandev XXX"; and then "ifconfig wlan0 regdomain FCC3"
>>     * .. see what it does with the channel programming in
>>     src/sbin/ifconfig/ and src/lib/lib80211/
>>     * Also 'ifconfig wlan0 list sta" and "ifconfig -v wlan0 list sta"
>>
>>     in src/sbin/ifconfig/ifieee80211.c look at
>>     setdefregdomain(), setregdomain_cb(), print_channels() and
>>     list_channels()
>>
>>     * print_channels() queries net80211 for the list of channels
>>     * list_channels() calls it :-)
>>     * setregdomain_cb() sucks in the lib80211 regdomain code, does a
>>     bunch of hijinx, and then calls into net80211 using the
>>     IEEE80211_IOC_REGDOMAIN ioctl to set the sku/country and the
>>     channel list.
>>
>>
>>
>>     -adrian
>
>     So much for limiting myself to XML parsing.  I'll grab some source
>     files and take a look, I can code but might be too removed from
>     what's being done here to get my ahead around it.  Thanks all.
>
>
> Oh! It's ok! If this is too big a thing then we can look around for 
> other bits and pieces that need doing. :-)
>
> I'd still like to get the regdomain stuff discussed!
>
>
>
> -a
No, I'm down - until I see what the code looks like of course.  If it's 
modular enough to be understood without too many adjacent systems I 
might be alright.  At present I'm less interested in changing the code 
that operates on the XML file and more interested in a refactoring.  
(Which will necessitate code changes, but I expect I'll be less involved 
there.)  I'm good at data design work, I'll try and stay in my lane.