[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

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
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
Version: 6.0.8-1

Fixed in 6.0, at least.

--- End Message ---
Reply to: