Re: [PATCH] wireless-regdb: Update regulatory rules for Iran (IR) on both 2.4 and 5Ghz for 2019

Ping-Ke Shih <[email protected]> Wed, 19 Feb 2025 10:39:09 +0800
Newsgroups org.infradead.lists.wireless-regdb,org.kernel.vger.linux-wireless
Message-ID <CAHrRpums5Czf8S0QmabsP+CTdeRwhfC49J5Qq_6v5Wgt8dKahg@mail.gmail.com>
Johannes Berg <[email protected]> wrote:
>
> On Tue, 2025-02-18 at 13:29 +0800, Chen-Yu Tsai wrote:
> > There are NO-INDOOR and NO-OUTDOOR flags for the database. The kernel
> > doesn't have a matching IEEE80211_CHAN_OUTDOOR_ONLY flag though.
> > Maybe that should be added?
> >
> > Johannes, what do you think?
>
> Good question. I guess we could have it, though I'm not sure we'd have
> any mechanics to actually _use_ such a thing right now? Something, say
> hostapd (?) would have to promise it's actually outdoors?
>
> More information doesn't hurt and I don't mind adding it at all, but I
> do think we'd probably not be able to use it at this time.
>
> Or we could add it to the db.txt file but ignore it in parsing now and
> skip the band for the binary for now?
>
> The thing is I don't think we have a good way to say "older kernel skips
> this range" - or perhaps we set the NO_IR flag so older kernel cannot
> use it but then allow OUTDOOR_ONLY to override that given some
> conditions?
>

Thanks for the suggestion. I have made a patch to allow NO-INDOOR flag, but
not parse into binary.

Since I'm very not familiar with Python, please review the patch carefully.
Thank you.