Source: firmware-nonfree Followup-For: Bug #962038 Dear Maintainer and reporter,
I spoke to Phil and Serge about this issue as a bluez-firmware maintainer. As written here[0], they seem like no plan to manage with linux-firmware. (I think it is a good choice to manage with linux-firmware with upstream...) Therefore, I'm thinking of importing firmware to bluez-firmware package. Do you have any other opinion? Best regards, Nobuhiro [0]: https://github.com/RPi-Distro/bluez-firmware/issues/7 -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: armhf, arm64, i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/16 CPU threads) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled