From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 86931] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0
Date: Fri, 19 Dec 2025 01:28:40 +0000 [thread overview]
Message-ID: <bug-86931-62941-JQZHxFo3YA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-86931-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=86931
--- Comment #13 from Kai Krakow (hurikhan77+bko@gmail.com) ---
Randy,
the underlying issue is quite easy to understand:
All Microsoft Xbox controllers are sending a NUL terminated HID descriptor
block. If we strip it away for those devices, the message is gone. This is
probably true for some other vendors (as reported here for Apple Magic Mouse).
We are doing it here around these lines to avoid the warning for Xbox
controllers:
https://github.com/atar-axis/xpadneo/commit/1e6b074506b85d03d2636beca528177f482029b8
So maybe the HID parser should just ignore a single trailing NUL byte and
accept that some device vendors just do that.
OTOH, it may be useful to warn about it, so device developers can properly fix
their HID descriptors. And for that case, rate limiting is the proper
implementation to work around other side effects (like overwhelming an UART
console).
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2025-12-19 1:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-86931-62941@https.bugzilla.kernel.org/>
2016-03-30 17:53 ` [Bug 86931] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 bugzilla-daemon
2018-01-12 9:21 ` bugzilla-daemon
2018-01-12 17:26 ` bugzilla-daemon
2019-01-30 18:27 ` bugzilla-daemon
2020-10-30 10:05 ` bugzilla-daemon
2021-01-08 14:31 ` bugzilla-daemon
2021-07-18 10:47 ` bugzilla-daemon
2021-07-19 6:58 ` bugzilla-daemon
2024-02-22 12:18 ` bugzilla-daemon
2025-12-18 21:49 ` bugzilla-daemon
2025-12-19 1:28 ` 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-86931-62941-JQZHxFo3YA@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 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).