I understand the logic of the of doing this and don't disagree.
However, as this is an entry level device and I believe the only true
64bit O/S advertised for this device, the fact that it does not not
work out of the box may impact on the perception of potential new
Ubuntu users?
Reading Tony's
Thanks guys for all the work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
[SRU] Bluetooth won't activate on the pi 400
Status in bluez package in Ubuntu:
Fix
Test case works perfectly on the Pi400.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
[SRU] Bluetooth won't activate on the pi 400
Status in bluez package in Ubuntu:
Is this the same as: #1903286?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
Bluetooth won't activate on the pi 400
Status in bluez package in Ubuntu:
New
Bug
I can confirm all of the above. Also looking at the Pi OS the in which
the bluetooth works it lists BCM2711-rpi-400.dts. Also unblocking the
soft block has no effect.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
5 matches
Mail list logo