Message-ID: <d9181baa0f9d6f33a3323f6663eefb97141c9ebc.camel@sipsolutions.net>
Subject: Re: wireless-regdb for automotive
From:   Johannes Berg <johannes@sipsolutions.net>
To:     Marcin Sielski <marcin.sielski@gmail.com>
Cc:     linux-wireless@vger.kernel.org
Date:   Tue, 15 Jan 2019 14:29:08 +0100
In-Reply-To: <CANWiEci5fFFr0n4Eu7N=ox7djf9KSXnma77+N=vRNc1=U997FQ@mail.gmail.com> (sfid-20181217_191421_830793_5C380D7B)
References: <CANWiEciGLPxDc5JT0+gVrzEyEC6GOcUJUf8XR4PrYHj4TysHpA@mail.gmail.com>
         <112ca7a8933b6113edf29e874d95207a22ccb790.camel@sipsolutions.net>
         <CANWiEci5fFFr0n4Eu7N=ox7djf9KSXnma77+N=vRNc1=U997FQ@mail.gmail.com>
         (sfid-20181217_191421_830793_5C380D7B)
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

On Mon, 2018-12-17 at 19:14 +0100, Marcin Sielski wrote:
> Hi,
> 
> > > Do you possibly have ideas how to adjust wireless-regdb package
> > > to support also automotive use cases as described in:
> > > https://www.efis.dk/documents/44659
> > 
> > You might want to explain what changes this requires ...
> 
> Let's take 5150 - 5250 MHz as an example. It is ok to use it in in the
> Cars if EIRP is limited to 25mW,
> These regulations applies to EU countries as well as all the countries
> which recognize EU rules.
> Currently the only solution is to update db.txt to reflect these
> regulations by OEM/Tier 1. There is no
> generic solution that would cover various applications (e.g. in
> automotive) where Linux kernel is used.

Yes, ok, hmm. No good ideas here.

But DE for example specifies

        (5150 - 5250 @ 80), (100 mW), NO-OUTDOOR, AUTO-BW

now?

Perhaps it might make sense to have the db.txt processed by the (C)
preprocessor, and add something like

#ifdef COMPILE_FOR_CAR
...
#else
...
#endif

and then you can build your own binary for the in-car environment, yet
share the sources with the community?

johannes