[Bug 1926378] Re: SRU pi-bluetooth from hirsute to focal to enable all models

[Chris Halse Rogers]

This is apparently fixed in Hirsute, and now the Focal SRU, but that
would seem to leave Groovy without working bluetooth on the Pi 400 and
CM4? Is there any plan for an SRU to Groovy, too?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pi-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1926378

Title:
  SRU pi-bluetooth from hirsute to focal to enable all models

Status in pi-bluetooth package in Ubuntu:
  New
Status in pi-bluetooth source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * Without the pi-bluetooth changes in hirsute, bluetooth will not
  work on the Pi 400 or CM4.

  [Test Case]

   * Boot the Ubuntu Server for Pi 20.04 image on a Raspberry Pi 400.
   * "bluetoothctl"
   * "list" and verify there is no available bluetooth controller
   * Enable proposed (https://wiki.ubuntu.com/Testing/EnableProposed)
   * "sudo apt install pi-bluetooth"
   * "sudo reboot" (required as bluetooth initialization only occurs during
      udev activation)
   * "bluetoothctl"
   * "list" and verify there is a single available bluetooth controller
   * "scan on" and bring another discoverable bluetooth device in range;
      verify it is reported under bluetoothctl
   * Repeat the above steps for the CM4

  [Regression Potential]

  There are multiple changes being SRU'd, but since the linux-firmware-
  raspi2 and bluez packages are also being SRUd, the risk of regression
  should be fairly low. These changes have worked well in hirsute for
  some time. In the past, other updates to this package have caused
  regressions on other Pi models such as the 2, 3, and 4. Though
  unlikely, that could potentially occur with this change as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1926378/+subscriptions