Hi Marcel, On Thu, May 13, 2021 at 8:16 AM Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: > > Hi Luiz, > > >> I test this patch no help. rmmod btusb, modprobe btusb. > >> > >> > >> [ 7.661739] Bluetooth: Core ver 2.22 > >> [ 7.661762] NET: Registered protocol family 31 > >> [ 7.661763] Bluetooth: HCI device and connection manager initialized > >> [ 7.661767] Bluetooth: HCI socket layer initialized > >> [ 7.661768] Bluetooth: L2CAP socket layer initialized > >> [ 7.661772] Bluetooth: SCO socket layer initialized > >> [ 7.686106] usbcore: registered new interface driver btusb > >> [ 7.689317] iwlwifi 0000:07:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 > >> [ 7.689789] Bluetooth: hci0: Firmware revision 0.0 build 118 week 15 2021 > >> [ 7.694911] bluetooth hci0: Direct firmware load for intel/ibt-20-0-0.sfi failed with error -2 > >> > >> [ 230.746397] usbcore: registered new interface driver btusb > >> [ 230.750827] Bluetooth: hci0: Firmware revision 0.0 build 118 week 15 2021 > >> [ 230.756450] bluetooth hci0: Direct firmware load for intel/ibt-20-0-0.sfi failed with error -2 > > > > The error shall be ignored in this case since it comes from > > request_firmware we can't prevent it, if you don't see another error > > after that means it can be ignored, that said perhaps we detect it > > sooner by either attempting to stat the file or perhaps check if > > revision comes back as all 0. > > any reason you don’t use firmware_request_nowarn()? Yep, totally missed that one exists, I will send a patch making use of it. -- Luiz Augusto von Dentz
