All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219387] Bluetooth: hci0: Reading supported features failed (-16)
Date: Fri, 20 Nov 2026 05:15:43 +0000	[thread overview]
Message-ID: <bug-219387-62941-fKFbbyJFZA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219387-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=219387

--- Comment #16 from cheako+kernel_org@mikemestnik.net ---
The issue with this bug was that if your vend/prod ID was not in the list, it
wouldn't work and there was no way to tell the driver to "Force detection for
this `new` product ID."  As I've said, instead of recompiling with a new table
of IDs...  I just edited the binary module replacing one of the other IDs and
now I'm just not updating the kernel until a driver with the aforementioned
module option is added, or my ID is added to the table.

-- 
You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2026-11-20  5:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14 16:40 [Bug 219387] New: Bluetooth: hci0: Reading supported features failed (-16) bugzilla-daemon
2024-10-14 16:42 ` [Bug 219387] " bugzilla-daemon
2024-10-16  5:51 ` bugzilla-daemon
2024-10-16 20:44 ` bugzilla-daemon
2024-10-16 21:02 ` bugzilla-daemon
2024-10-17  0:35 ` bugzilla-daemon
2024-11-03 14:04 ` bugzilla-daemon
2024-11-04 13:02 ` bugzilla-daemon
2024-11-04 13:04 ` bugzilla-daemon
2024-11-04 13:07 ` bugzilla-daemon
2025-01-27 19:02 ` bugzilla-daemon
2025-01-27 19:09 ` bugzilla-daemon
2025-01-28  4:02 ` bugzilla-daemon
2025-07-08  4:46 ` bugzilla-daemon
2025-12-24 15:04 ` bugzilla-daemon
2025-12-24 15:45 ` bugzilla-daemon
2026-11-20  0:38 ` bugzilla-daemon
2026-11-20  5:15 ` bugzilla-daemon [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=bug-219387-62941-fKFbbyJFZA@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.