Re: regdomain.xml - Linux wireless-regdb

On 7/21/2020 11:39 PM, Adrian Chadd wrote: On Tue, 21 Jul 2020 at 20:36, Aaron > wrote: Still working on my mailing list etiquette ... On 7/21/2020 11:11 PM, Adrian Chadd wrote: > On Tue, 21 Jul 2020 at 20:03, Aaron mailto:notjanede...@gmail.com>

Re: Re: regdomain.xml - Linux wireless-regdb

On Tue, 21 Jul 2020 at 20:36, Aaron wrote: > Still working on my mailing list etiquette ... > > On 7/21/2020 11:11 PM, Adrian Chadd wrote: > > > On Tue, 21 Jul 2020 at 20:03, Aaron > > wrote: > > > > On 7/21/2020 10:53 PM, Adrian Chadd wrote: > > > As a dat

Fwd: Re: regdomain.xml - Linux wireless-regdb

Still working on my mailing list etiquette ... On 7/21/2020 11:11 PM, Adrian Chadd wrote: On Tue, 21 Jul 2020 at 20:03, Aaron > wrote: On 7/21/2020 10:53 PM, Adrian Chadd wrote: > As a data source yes, but I'd /love/ ours to be more structured. > Pars

Re: regdomain.xml - Linux wireless-regdb

On Tue, 21 Jul 2020 at 20:03, Aaron wrote: > On 7/21/2020 10:53 PM, Adrian Chadd wrote: > > As a data source yes, but I'd /love/ ours to be more structured. > > Parsing the wireless-regdb format is ... lol. > > > > > > -a > Fair enough. This data also has a 1:1 mapping between country and > regu

Re: regdomain.xml - Linux wireless-regdb

On 7/21/2020 10:53 PM, Adrian Chadd wrote: As a data source yes, but I'd /love/ ours to be more structured. Parsing the wireless-regdb format is ... lol. -a Fair enough.  This data also has a 1:1 mapping between country and regulatory domain.  You mentioned Atheros earlier, is this 1:many co

Re: regdomain.xml - Linux wireless-regdb

As a data source yes, but I'd /love/ ours to be more structured. Parsing the wireless-regdb format is ... lol. -a ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to

regdomain.xml - Linux wireless-regdb

For reference, found this: https://mirrors.edge.kernel.org/pub/software/network/wireless-regdb/ Contains current (2020-04) regulatory information.  Format appears to be: country [ISO3166 2-character country code]: [regulatory domain code]     ([start freq in MHz] - [end freq in MHZ] @ [channel

Re: regdomain.xml

On 7/21/2020 5:52 PM, Adrian Chadd wrote: On Tue, 21 Jul 2020 at 14:48, Aaron > 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 mailto:notjanede...@gmail.com>> wrote: On 7/2

Re: regdomain.xml

On Tue, 21 Jul 2020 at 14:48, Aaron 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 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 bl

Re: regdomain.xml

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 > 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

Re: regdomain.xml

(cc'ing the list again, hehe :-) On Tue, 21 Jul 2020 at 14:35, Aaron 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 channe

Re: regdomain.xml

On Tue, 21 Jul 2020 at 14:31, Aaron wrote: > > What do others think? What should we do? > >>> I vote for recreating it as a CSV file. Would then be easier to work > with > >>> and easy to convert to other formats -- json/xml/... > >> Lol, if anything we'd likely use a format that we already

Re: regdomain.xml

Sent this to Adrian instead of the list: --- I preface this with the realisation that I'm using 12.1-RELEASE and should switch to one of the dev releases.  13-CURRENT? I read the "regdomain" manpage ... no help there. Yeah, it's ...old. :-0 Stick that on the TODO?  Once everything else

Re: regdomain.xml

What do others think? What should we do? I vote for recreating it as a CSV file. Would then be easier to work with and easy to convert to other formats -- json/xml/... Lol, if anything we'd likely use a format that we already use inside the tree, so json or xml. I don't MIND xml, but I mind ho

Re: regdomain.xml

On Tue, Jul 21, 2020 at 3:13 PM Adrian Chadd wrote: > > On Tue, 21 Jul 2020 at 12:59, Chris wrote: > > > > > So, I'd really like to figure out how to simplify the regdomain.xml file. > > > But - we should come up with a firm plan first. Luckily this IS basically > > > all userland work. :-) > > >

Re: regdomain.xml

On Tue, 21 Jul 2020 at 12:59, Chris wrote: > > So, I'd really like to figure out how to simplify the regdomain.xml file. > > But - we should come up with a firm plan first. Luckily this IS basically > > all userland work. :-) > > > +1 for the offer to dig in, Aaron! > > > What do others think? W

Re: regdomain.xml

On Tue, 21 Jul 2020 09:02:07 -0700 Adrian Chadd adrian.ch...@gmail.com said hi! On Tue, 21 Jul 2020 at 02:06, Aaron wrote: > Howdy FreeBSD wireless mailing list, > > Looking to help, only item on this list > (https://wiki.freebsd.org/WiFi/TodoStuff) I'm competent to address is > "net80211 reg

Re: regdomain.xml

hi! On Tue, 21 Jul 2020 at 02:06, Aaron wrote: > Howdy FreeBSD wireless mailing list, > > Looking to help, only item on this list > (https://wiki.freebsd.org/WiFi/TodoStuff) I'm competent to address is > "net80211 regulatory". I read the "regdomain" manpage ... no help there. > Yeah, it's ...o

regdomain.xml

Howdy FreeBSD wireless mailing list, Looking to help, only item on this list (https://wiki.freebsd.org/WiFi/TodoStuff) I'm competent to address is "net80211 regulatory".  I read the "regdomain" manpage ... no help there. My assumptions: * the data you're looking to clean up/update/refactor