Re: regdomain.xml [was also: - Linux wireless-regdb]

> channel was valid. Clearly told me that the organisation does not seem > to be right. > Yup. ath_regdomain. :-) I argued for redoing how the atheros driver did channel representation at QCA when we were doing the 11ac work and .. well, the way I did it in net80211 to at least get someth

Re: regdomain.xml [was also: - Linux wireless-regdb]

e can break up regdomain.xml into multiple files? - One thing I don’t like on the Linux version is that for, say ETSI, the information is basically copied per EU member state.  I love our reference model there.  I don’t mind having etsi, etsi1, etsi2 if I can then say 20 countries it’s etsi2 and be

Re: regdomain.xml [was also: - Linux wireless-regdb]

/channels/.. I made a mistake by accident and the list of combinations we checked in ifconfig exploded to 350.000 for whether a channel was valid. Clearly told me that the organisation does not seem to be right. - I was wondering if for clarity we can break up regdomain.xml into multiple files

Re: regdomain.xml - Linux wireless-regdb

  * Flags.  Once the data's parsed we can get a complete list of these. Right. Is there anything else needed?  And given that each country is a self-contained dataset, what do we need the regulatory domain name for beyond a label? DFS is the main consumer for now. T

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

he labor involved.v > > UCL looks interesting, what level of adoption does it have? If it's > common enough ... > > A single CSV file would be a catastrophe, there are several different > sections to the regdomain.xml file, it would have to be several. JSON > or XML

Re: regdomain.xml

7;m in, it doesn't seem to set that without my intervention.  Where in the software does a particular piece of hardware get assigned to JAPAN-2010 instead of JAPAN-2020? Also ... the regulatory domains have versions?  They don't seem to be present in regdomain.xml.  Should they be ad

Re: regdomain.xml

e. You could perhaps section off /usr/share/regdomain and do all kinds of fun stuff that reduces the labor involved.v UCL looks interesting, what level of adoption does it have?  If it's common enough ... A single CSV file would be a catastrophe, there are several different sections to t

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 I

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

Re: regdomain.xml

ss is > "net80211 regulatory". I read the "regdomain" manpage ... no help there. > Yeah, it's ...old. :-0 > > My assumptions: > > * the data you're looking to clean up/update/refactor is > "/etc/regdomain.xml". > * you have som

Re: regdomain.xml

manpage ... no help there. > Yeah, it's ...old. :-0 > > My assumptions: > > * the data you're looking to clean up/update/refactor is > "/etc/regdomain.xml". > * you have some idea what you want this file to look like afterwards > (an example wou

regdomain.xml

ng to clean up/update/refactor is "/etc/regdomain.xml". * you have some idea what you want this file to look like afterwards (an example would be very helpful) * the information you want added is available somewhere (FCC site, IEEE site, ...) If my assumptions are correct and

[Bug 177688] WiFi regodmains information is inconsistent between "etc/regdomain.xml" and "sys/net80211/ieee80211_regdomain.h"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=177688 Eitan Adler changed: What|Removed |Added Status|In Progress |Open --- Comment #2 from Eitan Adler

Re: misc/177688: WiFi regodmains information is inconsistent between "etc/regdomain.xml" and "sys/net80211/ieee80211_regdomain.h"

Synopsis: WiFi regodmains information is inconsistent between "etc/regdomain.xml" and "sys/net80211/ieee80211_regdomain.h" Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: lev Responsible-Changed-When: Sun Apr 7 10:41:58 UTC 2013 Respons

Re: sys/net80211/ieee80211_regdomain.h is pout of sync with /etc/regdomain.xml

_regdomain.h: SKU_ROW = > 0x81, /* China/Taiwan/Rest of World */ > > > /etc/regdomain.xml: > > ROW > 0x8a > > > And I'm not sure, that all other constants are Ok, it is only value > I've checked, as `bsnmpd' complains a

sys/net80211/ieee80211_regdomain.h is pout of sync with /etc/regdomain.xml

Hello, Freebsd-wireless. It looks like ieee80211_regdomain.h should be regenerated (or fixed?): /data/src/sys/net80211/ieee80211_regdomain.h: SKU_ROW = 0x81, /* China/Taiwan/Rest of World */ /etc/regdomain.xml: ROW 0x8a And I'm not sure, that all