From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: Brice Waegeneire <brice@waegenei.re>, 35574@debbugs.gnu.org
Subject: bug#35574: bcm5974 touchpad is not recognized as touchpad
Date: Tue, 28 Apr 2020 11:45:02 +0200 [thread overview]
Message-ID: <20200428094502.cduna7cyerl77ouq@pelzflorian.localdomain> (raw)
In-Reply-To: <87pnbtwi2y.fsf@gmail.com>
On Mon, Apr 27, 2020 at 08:36:37AM +0200, Mathieu Othacehe wrote:
> Thanks for fixing this! This seems like a reasonable choice. However, I
> noticed that on Ubuntu, CONFIG_USB_MOUSE is set to 'M'. So maybe they
> have some special udev/blacklist rules to handle this case?
Interesting. Thank you for checking. So maybe setting
CONFIG_USB_MOUSE=n in the kernel config is the wrong way. I installed
Ubuntu and they just have a file /etc/modprobe.d/blacklist.conf
containing the lines
# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd
I wonder if a default blacklist file would be more like the Guix way.
Or default blacklist kernel-arguments? I remember a discussion by
Danny Milosavljevic and Brice Waegeneire about this at
<https://bugs.gnu.org/40274#128>. All these avoid recompiling the
linux-libre package.
Danny, Brice, I’m putting you in Cc, maybe you have an opinion on
this? I suppose I should not change %default-extra-linux-options.
Regards,
Florian
next prev parent reply other threads:[~2020-04-28 9:50 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) [this message]
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)
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200428094502.cduna7cyerl77ouq@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=35574@debbugs.gnu.org \
--cc=brice@waegenei.re \
--cc=m.othacehe@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).