Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #76533 > unrolled thread

Bug#1022022: New btusb hardware IDs (MT7922, MT7921, others)

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1022022: New btusb hardware IDs (MT7922, MT7921, others) Chris Hofstaedtler <zeha@debian.org> - 2022-10-18 23:50 +0200
    Bug#1022022: New btusb hardware IDs (MT7922, MT7921, others) Diederik de Haas <didi.debian@cknow.org> - 2022-10-19 00:10 +0200
      Bug#1022022: New btusb hardware IDs (MT7922, MT7921, others) Chris Hofstaedtler <zeha@debian.org> - 2022-10-19 01:10 +0200
    Bug#1022022: New btusb hardware IDs (MT7922, MT7921, others) Bjørn Mork <bjorn@mork.no> - 2022-10-19 09:20 +0200
    Bug#1022022: marked as done (New btusb hardware IDs (MT7922,  MT7921, others)) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-11-29 10:40 +0100

#76533 — Bug#1022022: New btusb hardware IDs (MT7922, MT7921, others)

Source: linux
Version: 5.19.11-1

Hi,

it appears quite some new btusb hardware was released recently.
linux-next has a lot of simple "Add xyz ID" patches for btusb.c:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/drivers/bluetooth/btusb.c

Personally I have an Asus PN52 mini PC, with an MT7922 wifi/bt card.
It sports this hwid:
Bus 005 Device 003: ID 0489:e0e2 Foxconn / Hon Hai Wireless_Device
  idVendor           0x0489 Foxconn / Hon Hai
  idProduct          0xe0e2
  bcdDevice            1.00
  iManufacturer           5 MediaTek Inc.
  iProduct                6 Wireless_Device

I'll try applying 57117d7234dadfba2a83615b2a9369f6f2f9914f on top of
5.19.11-1 and report if that works, but I would expect it to.

Please consider applying 57117d7234dadfba2a83615b2a9369f6f2f9914f
and/or the other patches adding new hwids to btusb.c for the
bookworm kernel.

Thanks,
Chris

[toc] | [next] | [standalone]

#76534

[Multipart message — attachments visible in raw view] — view raw

On dinsdag 18 oktober 2022 23:44:17 CEST Chris Hofstaedtler wrote:
> it appears quite some new btusb hardware was released recently.
> linux-next has a lot of simple "Add xyz ID" patches for btusb.c:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/driv
> ers/bluetooth/btusb.c
> 
> Please consider applying 57117d7234dadfba2a83615b2a9369f6f2f9914f
> and/or the other patches adding new hwids to btusb.c for the
> bookworm kernel.

It's already part of Linux 6.1-rc1 and it is expected that 6.1 will be the
next LTS release and I'd guess thus also the Bookworm kernel.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/drivers/bluetooth?h=v6.1-rc1

[toc] | [prev] | [next] | [standalone]

#76535

* Diederik de Haas <didi.debian@cknow.org> [221019 00:07]:
> On dinsdag 18 oktober 2022 23:44:17 CEST Chris Hofstaedtler wrote:
> > it appears quite some new btusb hardware was released recently.
> > linux-next has a lot of simple "Add xyz ID" patches for btusb.c:
> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/driv
> > ers/bluetooth/btusb.c
> > 
> > Please consider applying 57117d7234dadfba2a83615b2a9369f6f2f9914f
> > and/or the other patches adding new hwids to btusb.c for the
> > bookworm kernel.
> 
> It's already part of Linux 6.1-rc1 and it is expected that 6.1 will be the
> next LTS release and I'd guess thus also the Bookworm kernel.
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/drivers/bluetooth?h=v6.1-rc1

Right, that'd be good. I've manually applied
57117d7234dadfba2a83615b2a9369f6f2f9914f against 5.9.11-1, and that
works for me; but only after making available
BT_RAM_CODE_MT7922_1_1_hdr.bin from linux-firmware.git.

Chris

[toc] | [prev] | [next] | [standalone]

#76538

Chris Hofstaedtler <zeha@debian.org> writes:
> * Diederik de Haas <didi.debian@cknow.org> [221019 00:07]:
>> On dinsdag 18 oktober 2022 23:44:17 CEST Chris Hofstaedtler wrote:
>> > it appears quite some new btusb hardware was released recently.
>> > linux-next has a lot of simple "Add xyz ID" patches for btusb.c:
>> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/driv
>> > ers/bluetooth/btusb.c
>> > 
>> > Please consider applying 57117d7234dadfba2a83615b2a9369f6f2f9914f
>> > and/or the other patches adding new hwids to btusb.c for the
>> > bookworm kernel.
>> 
>> It's already part of Linux 6.1-rc1 and it is expected that 6.1 will be the
>> next LTS release and I'd guess thus also the Bookworm kernel.
>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/drivers/bluetooth?h=v6.1-rc1
>
> Right, that'd be good. I've manually applied
> 57117d7234dadfba2a83615b2a9369f6f2f9914f against 5.9.11-1, and that
> works for me; but only after making available
> BT_RAM_CODE_MT7922_1_1_hdr.bin from linux-firmware.git.

If this is a simple device ID addition without any other dependencies,
then it qualifies for Linux stable.  And you'll get it in Debian stable
for free.

New device ID patches are regularily backported to the maintained stable
kernels, and usually picked up automatically by the stable maintainers.
You can request a backport of a specific commit in mainline by sending
an email to stable@vger.kernel.org

See https://docs.kernel.org/process/stable-kernel-rules.html


Bjørn

[toc] | [prev] | [next] | [standalone]

#77386 — Bug#1022022: marked as done (New btusb hardware IDs (MT7922, MT7921, others))

[Multipart message — attachments visible in raw view] — view raw

Your message dated Tue, 29 Nov 2022 10:28:34 +0100
with message-id <20221129092834.tv5tzoxm7mkttfph@zeha.at>
and subject line Re: #1022022: New btusb hardware IDs (MT7922, MT7921, others)
has caused the Debian Bug report #1022022,
regarding New btusb hardware IDs (MT7922, MT7921, others)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1022022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022022
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web