From: Johannes Berg <johannes@sipsolutions.net>
To: wens@kernel.org, "Taavi Eomäe" <taavieomae@gmail.com>
Cc: wireless-regdb@lists.infradead.org,
linux-wireless <linux-wireless@vger.kernel.org>,
Kalle Valo <kvalo@kernel.org>
Subject: Re: S1G and 6GHz channels in Estonia (and EU)
Date: Mon, 03 Jun 2024 09:10:08 +0200 [thread overview]
Message-ID: <234e631d44001c22368b8ddad916d9a0f13604f6.camel@sipsolutions.net> (raw)
In-Reply-To: <CAGb2v66xjwgcMZ2-N9CEg055Q+mLQKm20Nvo9mmHD3LY=C=Vjw@mail.gmail.com>
On Mon, 2024-06-03 at 14:39 +0800, Chen-Yu Tsai wrote:
> (Resend to Kalle's correct email address)
>
> On Mon, Jun 3, 2024 at 2:36 PM Chen-Yu Tsai <wens@kernel.org> wrote:
> >
> > (Adding linux-wireless ML, Kalle and Johannes)
> >
> > On Mon, Jun 3, 2024 at 1:13 AM Taavi Eomäe <taavieomae@gmail.com> wrote:
> > >
> > > Hi!
> > >
> > > I have a few questions about the current regdb values for Estonia/EE and EU:
> > >
> > > 1) There are no allowed S1G/HaLow/802.11ah EE (or EU) bands:
> > >
> > > Based on resources online and Estonian law
> > > (https://www.riigiteataja.ee/akt/117052024018?leiaKehtiv - Extra 6)
> > > these two additions should be correct:
> > >
> > > + (863 - 868 @ 1), (25 mW)
> > > + (915.8 - 919.4 @ 1), (25 mW)
> > >
> > > (Note: I don't see a way to define duty-cycle limitations, but that
> > > should be okay?)
> >
> > I'm not sure if there are plans to support S1G in Linux. If not then
> > the information would go unused and untested. If it is supported, then
> > patches are more than welcome.
There's some S1G support, but perhaps only in hwsim right now.
johannes
prev parent reply other threads:[~2024-06-03 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALfTr+pXU_=ORh2w3GE+YiU9igh61uWZS-zdG1GyKFb5Qs6fTg@mail.gmail.com>
2024-06-03 6:36 ` S1G and 6GHz channels in Estonia (and EU) Chen-Yu Tsai
2024-06-03 6:39 ` Chen-Yu Tsai
2024-06-03 7:10 ` Johannes Berg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=234e631d44001c22368b8ddad916d9a0f13604f6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=taavieomae@gmail.com \
--cc=wens@kernel.org \
--cc=wireless-regdb@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).