public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: wireless-regdb@lists.infradead.org
Cc: linux-wireless@vger.kernel.org,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: [ANN] wireless-regdb: master-2017-12-23
Date: Sat, 23 Dec 2017 21:54:31 -0600	[thread overview]
Message-ID: <20171224035431.GA5626@ubuntu-xps13> (raw)

A new release of wireless-regdb (master-2017-12-23) is available at:

https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2017.12.23.tar.gz

Note that this is the first release to include the new regulatory
database format, supporting direct loading of the database by the
kernel. The short log of changes since the 2017-03-07 release is below.

Thanks,
Seth

---

Andreas Mohr (1):
      wireless-regdb: reduce power level limit of KR (Korea) 802.11b/g/n to the certification-requested "20mW" (13dBm).

Aron Rosenberg (1):
      Set NO-OUTDOOR Flag on Canada 5Ghz 5150 to 5250

Chen-Yu Tsai (2):
      wireless-regdb: Update regulatory document references for Taiwan (TW)
      wireless-regdb: Add 60 GHz rule for Taiwan (TW)

Edwin Steele (1):
      wireless-regdb: Update rules for Turkey 5ghz

Johannes Berg (1):
      regdb: write firmware file format (version code 20)

Seth Forshee (8):
      wireless-regdb: Add 5 Ghz rules for Kazakhstan (KZ)
      wireless-regdb: Update rules for Denmark (DK)
      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
      wireless-regdb: update regulatory database based on preceding changes

Sven Eckelmann (1):
      wireless-regdb: Update regulatory rules for Singapore (SG)

Xose Vazquez Perez (1):
      wireless-regdb: add Short Range Devices (SRD) (ETSI EN 300 440) for Spain

                 reply	other threads:[~2017-12-24  3:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20171224035431.GA5626@ubuntu-xps13 \
    --to=seth.forshee@canonical.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --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