From: ryanm0 <ryanm0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Race condition between bcm5974 and usbmouse kernel modules
Date: Mon, 08 Feb 2021 04:30:55 +0100 [thread overview]
Message-ID: <20210208033055.0izuqAAZSvbGNF_b1mhXRNoIr1zWcEmdko4JwxLiu6E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27465@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]
New comment by ryanm0 on void-packages repository
https://github.com/void-linux/void-packages/issues/27465#issuecomment-774841514
Comment:
I agree, it probably would be best to avoid disabling that feature if it can be avoided.
Regarding the mouse_ignore list: It looks like the device ID (at least for my trackpad) is already in the hid_mouse_ignore_list (my trackpad has an ID of 05ac:0252 which corresponds to USB_DEVICE_ID_APPLE_WELLSPRING5A_ANSI). If my understanding of what's happening is correct, I think the mouse_ignore list might only be used by the usbhid module, and not by the usbmouse module that we're having a conflict with. I looked through <https://github.com/torvalds/linux/blob/master/drivers/hid/usbhid/hid-core.c> (for the regular usbhid module), and that looks to have code to handle device quirks, including ignoring the device, whereas <https://github.com/torvalds/linux/blob/master/drivers/hid/usbhid/usbmouse.c> (for usbmouse) looks like it doesn't have any of that. I guess that would explain why a lot of other distros blacklist the usbmouse module by default. That being said, I've never touched kernel or driver code, so I could definitely be overlooking something.
If creating a void docs page for this turns out to be the best solution, I could try working on a macbook page like the one @ericonr linked. However, since I have a different model of macbook than the original author of that PR, I've only experienced the trackpad issue and none of the other issues mentioned there.
next prev parent reply other threads:[~2021-02-08 3:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-27 1:07 [ISSUE] " ryanm00
2020-12-31 1:32 ` fosslinux
2020-12-31 1:33 ` fosslinux
2021-02-05 3:07 ` ahesford
2021-02-05 3:14 ` ericonr
2021-02-05 3:43 ` ahesford
2021-02-08 3:30 ` ryanm0 [this message]
2021-02-08 3:34 ` ryanm0
2021-02-08 3:35 ` ryanm0
2022-05-01 2:14 ` github-actions
2022-05-16 2:07 ` [ISSUE] [CLOSED] " github-actions
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=20210208033055.0izuqAAZSvbGNF_b1mhXRNoIr1zWcEmdko4JwxLiu6E@z \
--to=ryanm0@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).