Received-SPF: pass (google.com: domain of linux-wireless+bounces-3275-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Message-ID: <240506b19c6671cfce2587f4c1152359066146c7.camel@sipsolutions.net>
Subject: Re: wireless-regdb key change broke crda tests after 37dcea0e6e5
From: Johannes Berg <johannes@sipsolutions.net>
To: Sergei Trofimovich <slyich@gmail.com>
Cc: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org, 
	Chen-Yu Tsai <wens@kernel.org>, Seth Forshee <sforshee@kernel.org>
Date: Wed, 07 Feb 2024 08:58:34 +0100
In-Reply-To: <20240206222757.238a24f8@nz.home>
References: <ZcIXGjzrZrXPCBcp@nz.home>
	 <455bafff0d609eb182ba30a5fbf319888e0e961d.camel@sipsolutions.net>
	 <20240206222757.238a24f8@nz.home>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.50.3 (3.50.3-1.fc39) 
Precedence: bulk
MIME-Version: 1.0

On Tue, 2024-02-06 at 22:27 +0000, Sergei Trofimovich wrote:
>=20
> Great point! `nixpkgs` uses `crda` only as a `hostapd` depend and
> looking at modern `hostapd` it does not use it at all. I'll spend some
> time removing it downstream. Thank you!

Note that hostapd never directly depended on crda, it just needs/wants
it to have the correct regulatory information in the kernel (crda puts
it there) after switching the country (hostapd can do that if possible)
and then hostapd retrieves the information.

But in any case, the whole step with crda is no longer needed if you
have the regulatory file (and possibly signature) in place, the firmware
will load them as firmware files.

johannes