On 05.04.24 11:15, Deren Wu (武德仁) wrote: > > Thanks for the note. We are looking for solution for this issue. Peter > would post the new patch. :) Anyone still working on this, as that afaics did not happen -- or was there progress and I just missed it? Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr If I did something stupid, please tell me, as explained on that page. #regzbot poke > On Fri, 2024-04-05 at 10:34 +0200, Linux regression tracking (Thorsten > Leemhuis) wrote: >> [CCing the regression list, as it should be in the loop for >> regressions: >> > https://urldefense.com/v3/__https://docs.kernel.org/admin-guide/reporting-regressions.html__;!!CTRNKA9wMg0ARbw!n9OQDQtfMiQdddzNLvMEOMLnnEHhw12KRY5W5YPscQJTiNQtuIVuJufNc2UYpy-rUlRtMUwZsL5NDERIf1CoGox8J2I$ >> ] >> >> On 01.04.24 17:20, Mike Lothian wrote: >>> On Mon, 1 Apr 2024 at 15:44, Mike Lothian <mike@xxxxxxxxxxxxxx> >>> wrote: >>>> >>>> I think this patch is causing issues with older firmware >>>> >>>> Bus 003 Device 002: ID 13d3:3563 IMC Networks Wireless_Device >>>> >>>> [ 0.315064] Bluetooth: Core ver 2.22 >>>> [ 0.315064] NET: Registered PF_BLUETOOTH protocol family >>>> [ 0.315064] Bluetooth: HCI device and connection manager >>>> initialized >>>> [ 0.315064] Bluetooth: HCI socket layer initialized >>>> [ 0.315064] Bluetooth: L2CAP socket layer initialized >>>> [ 0.315064] Bluetooth: SCO socket layer initialized >>>> [ 4.670811] Bluetooth: RFCOMM TTY layer initialized >>>> [ 4.671029] Bluetooth: RFCOMM socket layer initialized >>>> [ 4.671790] Bluetooth: RFCOMM ver 1.11 >>>> [ 4.673416] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 >>>> [ 4.673659] Bluetooth: BNEP filters: protocol multicast >>>> [ 4.673895] Bluetooth: BNEP socket layer initialized >>>> [ 4.674125] Bluetooth: HIDP (Human Interface Emulation) ver >>>> 1.2 >>>> [ 4.674360] Bluetooth: HIDP socket layer initialized >>>> [ 5.016365] bluetooth hci0: Direct firmware load for >>>> mediatek/BT_RAM_CODE_MT7961_1a_2_hdr.bin failed with error -2 >>>> [ 5.017163] Bluetooth: hci0: Failed to load firmware file (-2) >>>> [ 5.017557] Bluetooth: hci0: Failed to set up firmware (-2) >>>> [ 5.018129] Bluetooth: hci0: HCI Enhanced Setup Synchronous >>>> Connection command is advertised, but not supported. >>>> >>>> The correct name should be >>>> mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin >>>> >>>> Reverting this patch fixes things >>> >>> If it helps, the device ID is 0x7961 and the fw_flavour is 24 or >>> 0x18 in hex >> >> Thanks for the report! >> >> Peter, did you look into this? >> >> Anyway: To be sure the issue doesn't fall through the cracks >> unnoticed, >> I'm adding it to regzbot, the Linux kernel regression tracking bot: >> >> #regzbot report: >> > https://lore.kernel.org/all/20240401144424.1714-1-mike@xxxxxxxxxxxxxx/ >> #regzbot introduced: 1cb63d80fff6c4 >> #regzbot title: net: Bluetooth: firmware loading problems with older >> firmware >> #regzbot ignore-activity >> >> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' >> hat) >> -- >> Everything you wanna know about Linux kernel regression tracking: >> > https://urldefense.com/v3/__https://linux-regtracking.leemhuis.info/about/*tldr__;Iw!!CTRNKA9wMg0ARbw!n9OQDQtfMiQdddzNLvMEOMLnnEHhw12KRY5W5YPscQJTiNQtuIVuJufNc2UYpy-rUlRtMUwZsL5NDERIf1CoQcaol0s$ >> >> That page also explains what to do if mails like this annoy you.
