From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: linux-wireless@vger.kernel.org
Cc: wireless-regdb@lists.infradead.org,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: [PATCH v2 0/6] crda: few more updates
Date: Mon, 28 Oct 2013 17:42:00 +0100 [thread overview]
Message-ID: <1382978526-23929-1-git-send-email-mcgrof@do-not-panic.com> (raw)
Here's a second spin, after quite a bit more testing I ran
into a few small issues with the parser and library. This
has these additional fixes / enhancements:
* Lifts the restriction on 32 rules, although the kernel
is limited by this we don't adhere to this limit on our
stream parser or optimizer
* The union code got updated to address two cases that are
invalid for unions
* A few fixes on db2rd and optimizer on using the stream
parser, if its NULL, bail, we weren't checking for it
* The optimizer was not considering band differences as
part of its key broker (when it decides it can use
two rules for optimization), to address this we deduce
the band and add that to the key mixing. Note that this
will need to be updated upon new frequency band additions.
This limits the scope of optimizations between their own
respective bands.
I've also gone ahead and tested this with a huge fluffy
non optimized regulatory domain of 40 rules, and also with
the wireless-regdb db.txt. I'll send some optimizations
based on this for wireless-regdb.
The only patches that go modified are the stream parser
and the optimizer.
Luis R. Rodriguez (6):
crda: relicense under copyleft-next-0.3.0
crda: fix -pedantic gcc compilation
crda: add regulatory domain stream parser
crda: add regulatory domain optimizer
crda: make ssl keys include stdint.h
crda: make reglib a shared library
LICENSE | 14 +-
Makefile | 54 +++-
copyleft-next-0.3.0 | 219 ++++++++++++++
crda.c | 4 +-
db2rd.c | 32 ++
optimize.c | 40 +++
reglib.c | 839 ++++++++++++++++++++++++++++++++++++++++++++++++++++
reglib.h | 60 ++++
utils/key2pub.py | 2 +
9 files changed, 1252 insertions(+), 12 deletions(-)
create mode 100644 copyleft-next-0.3.0
create mode 100644 db2rd.c
create mode 100644 optimize.c
--
1.8.4.rc3
next reply other threads:[~2013-10-28 16:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 16:42 Luis R. Rodriguez [this message]
2013-10-28 16:42 ` [PATCH v2 1/6] crda: relicense under copyleft-next-0.3.0 Luis R. Rodriguez
2013-10-28 16:42 ` [PATCH v2 2/6] crda: fix -pedantic gcc compilation Luis R. Rodriguez
2013-10-28 16:42 ` [PATCH v2 3/6] crda: add regulatory domain stream parser Luis R. Rodriguez
2013-10-28 16:42 ` [PATCH v2 4/6] crda: add regulatory domain optimizer Luis R. Rodriguez
2013-10-28 16:42 ` [PATCH v2 5/6] crda: make ssl keys include stdint.h Luis R. Rodriguez
2013-10-28 16:42 ` [PATCH v2 6/6] crda: make reglib a shared library Luis R. Rodriguez
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=1382978526-23929-1-git-send-email-mcgrof@do-not-panic.com \
--to=mcgrof@do-not-panic.com \
--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).