mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Deren Wu (武德仁)" <Deren.Wu@mediatek.com>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	"Peter Tsao (曹珆彰)" <Peter.Tsao@mediatek.com>,
	"mike@fireburn.co.uk" <mike@fireburn.co.uk>
Cc: "marcel@holtmann.org" <marcel@holtmann.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Chris Lu (陸稚泓)" <Chris.Lu@mediatek.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	"johan.hedberg@gmail.com" <johan.hedberg@gmail.com>,
	"Steve Lee (李視誠)" <steve.lee@mediatek.com>,
	"Sean Wang" <Sean.Wang@mediatek.com>,
	"Aaron Hou (侯俊仰)" <Aaron.Hou@mediatek.com>,
	"luiz.dentz@gmail.com" <luiz.dentz@gmail.com>
Subject: Re: [SPAM]Re: [PATCH] [PATCH] Bluetooth: btusb: Add support Mediatek MT7920
Date: Fri, 5 Apr 2024 09:15:20 +0000	[thread overview]
Message-ID: <11f098c7cc3a063fd20c02f1a66372e3444cb272.camel@mediatek.com> (raw)
In-Reply-To: <2d822b6c-8b55-443d-ad9e-03e97ce7b99b@leemhuis.info>

Hi Thorsten,

Thanks for the note. We are looking for solution for this issue. Peter
would post the new patch. :)

Regards,
Deren

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@fireburn.co.uk>
> > 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@fireburn.co.uk/
> #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.

  reply	other threads:[~2024-04-05  9:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 14:48 Peter Tsao
2024-03-04 21:30 ` patchwork-bot+bluetooth
2024-04-01 14:44 ` Mike Lothian
2024-04-01 15:20   ` Mike Lothian
2024-04-05  8:34     ` Linux regression tracking (Thorsten Leemhuis)
2024-04-05  9:15       ` Deren Wu (武德仁) [this message]
2024-04-15 12:30         ` Linux regression tracking (Thorsten Leemhuis)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=11f098c7cc3a063fd20c02f1a66372e3444cb272.camel@mediatek.com \
    --to=deren.wu@mediatek.com \
    --cc=Aaron.Hou@mediatek.com \
    --cc=Chris.Lu@mediatek.com \
    --cc=Peter.Tsao@mediatek.com \
    --cc=Sean.Wang@mediatek.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=mike@fireburn.co.uk \
    --cc=regressions@lists.linux.dev \
    --cc=steve.lee@mediatek.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®