All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Benjamin Beichler <Benjamin.Beichler@uni-rostock.de>,
	Seth Forshee <seth.forshee@canonical.com>
Cc: 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:36:53 +0100	[thread overview]
Message-ID: <1510583813.30497.44.camel@sipsolutions.net> (raw)
In-Reply-To: <fffbdcf1-631e-d0de-836d-e95266afa686@uni-rostock.de>

On Mon, 2017-11-13 at 15:34 +0100, Benjamin Beichler wrote:
> Am 13.11.2017 um 14:36 schrieb Seth Forshee:
> > On Mon, Nov 13, 2017 at 10:23:09AM +0100, Johannes Berg wrote:
> > > On Mon, 2017-11-13 at 10:19 +0100, Benjamin Beichler wrote:
> > > > Is there already an example regulatory.db file available? 
> > > 
> > > There isn't yet, Seth?
> > 
> > Not yet. I've done some work on the patch you sent to make it generate
> > db files in both formats, not sure I'm ready to start actually releasing
> > files in the new format yet though. I suppose I could push it to a
> > testing branch with a signed regulatory.db file.
> 
> I would really appreciate this, since my current tool chain is not
> appropriate for this whole signing stuff and hwsim is failing to set my
> standard frequencies, because of the missing regdb.

You should be able to continue to use CRDA?

And if you don't, you can just disable signature checking and build the
binary yourself?

johannes

  reply	other threads:[~2017-11-13 14:36 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 [this message]
     [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
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=1510583813.30497.44.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=Benjamin.Beichler@uni-rostock.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=seth.forshee@canonical.com \
    /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.