From: Seth Forshee <seth.forshee@canonical.com>
To: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org
Cc: Johannes Berg <johannes@sipsolutions.net>
Subject: [PATCH 0/6] wireless-regdb: Support for new binary database format
Date: Fri, 22 Dec 2017 00:02:57 -0600 [thread overview]
Message-ID: <20171222060303.14478-1-seth.forshee@canonical.com> (raw)
This series starts with Johannes' patch for generating regulatory
databases using the new format and adds various fixes and pieces which
were missing such as installation to the firmware path, manual page
updates, etc. It also restores support for the older database format to
maintain compatibility with using CRDA on older kernels.
I've tested the results with 4.15 and things look to be working. I want
to apply this in the next couple of days and get a new release out, so
please let me know soon if you seen any issues.
Thanks,
Seth
Johannes Berg (1):
regdb: write firmware file format (version code 20)
Seth Forshee (5):
wireless-regdb: Restore generation of old format database files
wireless-regdb: Add sforshee's x509 certificate
wireless-regdb: Better support for generating public certificates
wireless-regdb: Install regulatory.db and regulatory.db.p7s to
/lib/firmware
wireless-regdb: Document regulatory.db in the manual page
Makefile | 37 +++++++++++----
README | 4 +-
db2fw.py | 133 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
gen-pubcert.sh | 18 ++++++++
regulatory.bin.5 | 32 +++++++++----
regulatory.db.5 | 1 +
sforshee.x509.pem | 17 +++++++
7 files changed, 220 insertions(+), 22 deletions(-)
create mode 100755 db2fw.py
create mode 100755 gen-pubcert.sh
create mode 100644 regulatory.db.5
create mode 100644 sforshee.x509.pem
next reply other threads:[~2017-12-22 6:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 6:02 Seth Forshee [this message]
2017-12-22 6:02 ` [PATCH 1/6] regdb: write firmware file format (version code 20) Seth Forshee
2017-12-22 6:02 ` [PATCH 2/6] wireless-regdb: Restore generation of old format database files Seth Forshee
2017-12-22 6:03 ` [PATCH 3/6] wireless-regdb: Add sforshee's x509 certificate Seth Forshee
2017-12-22 6:03 ` [PATCH 4/6] wireless-regdb: Better support for generating public certificates Seth Forshee
2017-12-22 6:03 ` [PATCH 5/6] wireless-regdb: Install regulatory.db and regulatory.db.p7s to /lib/firmware Seth Forshee
2017-12-22 6:03 ` [PATCH 6/6] wireless-regdb: Document regulatory.db in the manual page Seth Forshee
2017-12-22 8:45 ` [PATCH 0/6] wireless-regdb: Support for new binary database format Johannes Berg
2017-12-24 3:24 ` Seth Forshee
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=20171222060303.14478-1-seth.forshee@canonical.com \
--to=seth.forshee@canonical.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.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;
as well as URLs for NNTP newsgroup(s).