From: "Peter Tsao (曹珆彰)" <Peter.Tsao@mediatek.com>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"aros@gmx.com" <aros@gmx.com>,
"Chris Lu (陸稚泓)" <Chris.Lu@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Aaron Hou (侯俊仰)" <Aaron.Hou@mediatek.com>,
"Deren Wu (武德仁)" <Deren.Wu@mediatek.com>
Cc: "linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [SPAM]Re: BT_RAM_CODE_MT7961_1a_2_hdr.bin is missing in the firmware tree
Date: Wed, 24 Apr 2024 11:43:07 +0000 [thread overview]
Message-ID: <9bed1f526b5be4a7ae6d89188d7bd46ec7b66e0c.camel@mediatek.com> (raw)
In-Reply-To: <3b983390-110e-4c68-a825-6e811de78919@leemhuis.info>
Dear Thorsten,
Sorry for the misunderstanding.
MT7920 and MT7921 are different chip (hardware) but both use same
chip_id 0x7961 and we distinguish between these two chip through the
8th bit of the "fw_flavor" register.
Therefore, I think we have not violated this rule:
> Users switching to a newer kernel should *not* have to install newer
> firmware files to keep their hardware working.
because MT7921 still be MT7921 and use same FW bin
BT_RAM_MT7961_1_2_hdr.bin.
About MT7920, we will push the stable FW bin after internal test done.
BRs
Peter
On Wed, 2024-04-24 at 08:06 +0200, Linux regression tracking (Thorsten
Leemhuis) wrote:
> On 23.04.24 12:23, Artem S. Tashkinov wrote:
> >
> > Could you please push this firmware ASAP?
> >
> > It's been reported to be missing:
> >
https://urldefense.com/v3/__https://bugzilla.kernel.org/show_bug.cgi?id=218757__;!!CTRNKA9wMg0ARbw!jL88juHMcB9CkhfQy00tGVjWsRXXdMN-_T28ANIP1xdw0C5Yr2dENm0mM3n9Egv5xqdT7oDyEXtOswJ6o2EYZSw9h_v5$
> >
>
> FWIW, that can't be the only solution for that problem, as
> Documentation/driver-api/firmware/firmware-usage-guidelines.rst
> clearly
> states:
>
> """
> Users switching to a newer kernel should *not* have to install newer
> firmware files to keep their hardware working.
> """
>
> Could anyone from mediatek please confirm that this rule is adhered?
>
> Side note: I wonder if Peter's patch
>
https://lore.kernel.org/all/20240415141922.25055-1-peter.tsao@mediatek.com/
> ("Bluetooth: btusb: Fix the patch for MT7920 the affected to MT7921")
> is
> relevant for this.
>
> 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!jL88juHMcB9CkhfQy00tGVjWsRXXdMN-_T28ANIP1xdw0C5Yr2dENm0mM3n9Egv5xqdT7oDyEXtOswJ6o2EYZXhunwKm$
>
> If I did something stupid, please tell me, as explained on that page.
prev parent reply other threads:[~2024-04-24 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 10:23 BT_RAM_CODE_MT7961_1a_2_hdr.bin is missing in the firmware tree Artem S. Tashkinov
2024-04-24 6:06 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-24 11:43 ` Peter Tsao (曹珆彰) [this message]
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=9bed1f526b5be4a7ae6d89188d7bd46ec7b66e0c.camel@mediatek.com \
--to=peter.tsao@mediatek.com \
--cc=Aaron.Hou@mediatek.com \
--cc=Chris.Lu@mediatek.com \
--cc=Deren.Wu@mediatek.com \
--cc=aros@gmx.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).