From: Kalle Valo <kvalo@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Sergei Trofimovich <slyich@gmail.com>,
linux-wireless@vger.kernel.org,
wireless-regdb@lists.infradead.org,
Chen-Yu Tsai <wens@kernel.org>,
Seth Forshee <sforshee@kernel.org>
Subject: Re: wireless-regdb key change broke crda tests after 37dcea0e6e5
Date: Wed, 07 Feb 2024 11:19:11 +0200 [thread overview]
Message-ID: <87v870hbsg.fsf@kernel.org> (raw)
In-Reply-To: <240506b19c6671cfce2587f4c1152359066146c7.camel@sipsolutions.net> (Johannes Berg's message of "Wed, 07 Feb 2024 08:58:34 +0100")
Johannes Berg <johannes@sipsolutions.net> writes:
> On Tue, 2024-02-06 at 22:27 +0000, Sergei Trofimovich wrote:
>>
>> 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.
I assume you mean: the kernel will load them as firmware files.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-02-07 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 11:25 wireless-regdb key change broke crda tests after 37dcea0e6e5 Sergei Trofimovich
2024-02-06 11:47 ` Johannes Berg
2024-02-06 22:27 ` Sergei Trofimovich
2024-02-07 7:58 ` Johannes Berg
2024-02-07 9:19 ` Kalle Valo [this message]
2024-02-07 9:22 ` Johannes Berg
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=87v870hbsg.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=sforshee@kernel.org \
--cc=slyich@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