Public bug reported:

[Impact]
WCN6856 Bluetooth doesn't work.

[Fix]
Backport firmware blobs and driver support to make it work by loading
correct firmwares.
 
[Test]
Bluetooth scanning and pairing work, and continue to do so after several
suspend/resume cycles.

[Where problems could occur]
The upstream version of btusb_generate_qca_nvm_name() adds several
missing le*_to_cpu() macros, so if this device was ever used on a Big
Endian system, this is a behavioral change.

** Affects: linux (Ubuntu)
     Importance: Low
         Status: Confirmed

** Affects: linux-firmware (Ubuntu)
     Importance: Low
         Status: Confirmed

** Affects: linux-oem-5.14 (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: linux (Ubuntu Focal)
     Importance: Undecided
         Status: Won't Fix

** Affects: linux-firmware (Ubuntu Focal)
     Importance: Low
         Status: Confirmed

** Affects: linux-oem-5.14 (Ubuntu Focal)
     Importance: Low
         Status: Confirmed

** Affects: linux (Ubuntu Jammy)
     Importance: Low
         Status: Confirmed

** Affects: linux-firmware (Ubuntu Jammy)
     Importance: Low
         Status: Confirmed

** Affects: linux-oem-5.14 (Ubuntu Jammy)
     Importance: Undecided
         Status: Invalid

** Also affects: linux-oem-5.14 (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: linux-oem-5.14 (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Also affects: linux-oem-5.14 (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Focal)
       Status: New => Won't Fix

** Changed in: linux (Ubuntu Jammy)
       Status: New => Confirmed

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => Low

** Changed in: linux-oem-5.14 (Ubuntu Focal)
       Status: New => Confirmed

** Changed in: linux-oem-5.14 (Ubuntu Jammy)
       Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Importance: Undecided => Low

** Also affects: linux-firmware (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: linux-firmware (Ubuntu Focal)
       Status: New => Confirmed

** Changed in: linux-firmware (Ubuntu Jammy)
       Status: New => Confirmed

** Changed in: linux-firmware (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: linux-firmware (Ubuntu Jammy)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955689

Title:
  Add Bluetooth support for Qualcomm WCN6856

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-firmware source package in Focal:
  Confirmed
Status in linux-oem-5.14 source package in Focal:
  Confirmed
Status in linux source package in Jammy:
  Confirmed
Status in linux-firmware source package in Jammy:
  Confirmed
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  WCN6856 Bluetooth doesn't work.

  [Fix]
  Backport firmware blobs and driver support to make it work by loading
  correct firmwares.
   
  [Test]
  Bluetooth scanning and pairing work, and continue to do so after several
  suspend/resume cycles.

  [Where problems could occur]
  The upstream version of btusb_generate_qca_nvm_name() adds several
  missing le*_to_cpu() macros, so if this device was ever used on a Big
  Endian system, this is a behavioral change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955689/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to