group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1769980@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package wireless-regdb -
2018.05.09-0ubuntu1~16.04.1

---------------
wireless-regdb (2018.05.09-0ubuntu1~16.04.1) xenial; urgency=medium

  * New upstream release. (LP: #1769980)
  * debian/patches:
    - Drop existing patches.
    - 0001-wireless-regdb-Fix-comparison-of-WmmRule-with-NoneTy.patch,
      0002-wireless-regdb-Fix-iteration-in-create_wmms-for-pyth.patch: Fix
      errors when building regdb with python 3.
  * debian/rules: Change to no longer build from source; use upstream
    binaries instead.
  * debian/control:
    - bump Standards-Version to 3.9.8.
    - update debhelper Build-Depends to (>= 9).
    - Update Build-Depends and maintainer information.
  * debian/compat: bump to compat level 9.

 -- Seth Forshee <seth.forshee@xxxxxxxxxxxxx>  Wed, 23 May 2018 10:38:03
-0500

** Changed in: wireless-regdb (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1769980

Title:
  Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in crda package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in crda source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Won't Fix
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in wireless-regdb source package in Xenial:
  Fix Released
Status in crda source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in wireless-regdb source package in Bionic:
  Fix Released

Bug description:
  Intel wireless driver and firmware require updates in order to meet
  the new ETSI regulation [1] for OEM machines shipped from factories.

  Intel provided us the following information for what are required to
  update:

  1. Kernel driver:

  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/

  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.

  2. linux-firmware
  Requires latest versions from linux-firmware.git

  3. wireless-regdb update

  [1]
  http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf

  -----------------------------------------------------------------------
  == SRU Justification for linux-firmware ==
  [Impact]
  Intel released these firmware updates to support the new ETSI 5GHz Adaptivity Requirement, OEM has to meet it in order to ship.

  [Test Case]
  Check dmesg to confirm the correct firmware is loaded, make sure the revision is correct, and check wifi can functions properly.

  [Regression Potential]
  It is possible that there is regression introduced by Intel's firmware, so should make sure wifi still works properly after the new firmware is used. We have verified the new firmwares of 7260 and 7265D on 4.4
  and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions and will need to confirm with subsequent driver changes.

  ---

  wireless-regdb SRU Justification

  Impact: New regulatory requirements in the EU necessitate updating our
  wireless regulatory database.

  Fix: New upstream release.

  Test Case: Minimal testing would be to reload the regdb (can be done
  with iw built from git or by rebooting) and verifying that you are
  able to change regulatory domains (e.g., sudo iw reg set US; iw reg
  get).

  Regression Potential: Minimal. Biggest risk would be the inability to
  load the new database due to the changes in signing, however testing
  will confirm that appropriate key is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1769980/+subscriptions