From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Brice Waegeneire <brice@waegenei.re>
Cc: 35574@debbugs.gnu.org
Subject: bug#35574: bcm5974 touchpad is not recognized as touchpad
Date: Fri, 1 May 2020 10:57:19 +0200 [thread overview]
Message-ID: <20200501085719.b2ewxlbgtcl2lhxw@pelzflorian.localdomain> (raw)
In-Reply-To: <a05761af67fe842601dc4f520244c9e5@waegenei.re>
On Wed, Apr 29, 2020 at 06:46:51PM +0000, Brice Waegeneire wrote:
> LGTM! I wonder if, as Ubuntu, we should also blacklist “usbkbd” the
> counterpart of “usbmouse” or just to wait a bug report about it - if
> it ever happen.
I will add usbkbd to the blacklist because
<https://www.willemp.be/cw/usbkbd/> claims there is a race with the
usbhid module and the Linux kernel documentation says usbhid has more
features and “Use usbhid instead if there isn’t any special reason to
use this.”
Thank you!
Regards,
Florian
next prev parent reply other threads:[~2020-05-01 8:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 6:54 bug#35574: bcm5974 touchpad is not recognized as touchpad pelzflorian (Florian Pelz)
2019-05-05 7:41 ` pelzflorian (Florian Pelz)
[not found] ` <20200116233537.myczkgkwnfpn75hu@pelzflorian.localdomain>
2020-04-20 14:47 ` pelzflorian (Florian Pelz)
2020-04-20 15:59 ` pelzflorian (Florian Pelz)
2020-04-20 22:26 ` Bengt Richter
2020-04-27 0:32 ` pelzflorian (Florian Pelz)
2020-04-27 0:28 ` pelzflorian (Florian Pelz)
2020-04-27 6:36 ` Mathieu Othacehe
2020-04-28 9:45 ` pelzflorian (Florian Pelz)
2020-04-28 14:10 ` Brice Waegeneire
2020-04-29 15:27 ` pelzflorian (Florian Pelz)
2020-04-29 15:38 ` Mathieu Othacehe
2020-04-29 16:41 ` pelzflorian (Florian Pelz)
2020-04-29 16:42 ` pelzflorian (Florian Pelz)
2020-04-29 18:31 ` Mathieu Othacehe
2020-04-29 18:46 ` Brice Waegeneire
2020-05-01 8:57 ` pelzflorian (Florian Pelz) [this message]
2020-05-01 8:33 ` pelzflorian (Florian Pelz)
2020-05-01 9:15 ` pelzflorian (Florian Pelz)
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=20200501085719.b2ewxlbgtcl2lhxw@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=35574@debbugs.gnu.org \
--cc=brice@waegenei.re \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.