From: Johannes Berg <johannes@sipsolutions.net>
To: Benjamin Beichler <Benjamin.Beichler@uni-rostock.de>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 3/4] cfg80211: reg: remove support for built-in regdb
Date: Mon, 13 Nov 2017 15:53:30 +0100 [thread overview]
Message-ID: <1510584810.30497.47.camel@sipsolutions.net> (raw)
In-Reply-To: <40a4b97b-7711-43d1-b0fb-3cfb7b8bca88@uni-rostock.de>
On Mon, 2017-11-13 at 15:48 +0100, Benjamin Beichler wrote:
>
> Then this may be a bug, since the loading the regulatory.db fails
> (platform regulatory.0: Direct firmware load for regulatory.db failed
> with error -2) also, when CONFIG_CFG80211_REQUIRE_SIGNED_REGDB is not
> set (and of course CONFIG_CFG80211_CERTIFICATION_ONUS is set)
Well that just means you don't have the file (in the right place)
johannes
next prev parent reply other threads:[~2017-11-13 14:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 9:50 [PATCH v2 0/4] built-in regulatory database Johannes Berg
2017-10-09 9:50 ` [PATCH v2 1/4] cfg80211: support loading regulatory database as firmware file Johannes Berg
2017-10-09 9:50 ` [PATCH v2 2/4] cfg80211: support reloading regulatory database Johannes Berg
2017-10-09 9:50 ` [PATCH v2 3/4] cfg80211: reg: remove support for built-in regdb Johannes Berg
2017-11-13 9:19 ` Benjamin Beichler
2017-11-13 9:23 ` Johannes Berg
2017-11-13 13:36 ` Seth Forshee
2017-11-13 14:34 ` Benjamin Beichler
2017-11-13 14:36 ` Johannes Berg
[not found] ` <b2023534-0ea0-b3b5-f6ef-40e5dd239d38@uni-rostock.de>
[not found] ` <1510584253.30497.45.camel@sipsolutions.net>
2017-11-13 14:48 ` Benjamin Beichler
2017-11-13 14:53 ` Johannes Berg [this message]
2017-10-09 9:50 ` [PATCH v2 4/4] cfg80211: implement regdb signature checking 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=1510584810.30497.47.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Benjamin.Beichler@uni-rostock.de \
--cc=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.