From: Bengt Richter <bokr@bokr.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 35574@debbugs.gnu.org
Subject: bug#35574: bcm5974 touchpad is not recognized as touchpad
Date: Tue, 21 Apr 2020 00:26:07 +0200 [thread overview]
Message-ID: <20200420222607.GA4620@LionPure> (raw)
In-Reply-To: <20200420155908.ulewy4c2vqkuzgfr@pelzflorian.localdomain>
Hi Fllorian,
On +2020-04-20 17:59:08 +0200, pelzflorian (Florian Pelz) wrote:
> On Mon, Apr 20, 2020 at 04:47:18PM +0200, pelzflorian (Florian Pelz) wrote:
> > However I also cannot find the reason why this usbmouse loadable
> > kernel module gets loaded at all. How can I debug what loads this
Could the module be needed "just in case" in an initrd
but should be unloaded before pivoting in a normal case?
> > kernel module? Debian does not show usbmouse in lsmod, and I think
> > usbmouse should not get loaded in Guix either. usbmouse is not
> > required for my external USB mouse to work.
>
> Debian 10’s /boot/config-4.19.0-6-amd64 has
>
> # USB HID Boot Protocol drivers
> #
> # CONFIG_USB_KBD is not set
> # CONFIG_USB_MOUSE is not set
>
> while Guix has in /tmp/guix-build-linux-libre-5.4.32.drv-0/linux-5.4.32/.config
>
> CONFIG_USB_MOUSE=m
>
> I will write and test a patch to disable the module in
> %default-extra-linux-options, like the description in linux-5.4.11
> source file drivers/hid/usbhid/Kconfig recommends:
>
> config USB_MOUSE
> tristate "USB HIDBP Mouse (simple Boot) support"
> depends on USB && INPUT
> ---help---
> Say Y here only if you are absolutely sure that you don't want
> to use the generic HID driver for your USB mouse and prefer
> to use the mouse in its limited Boot Protocol mode instead.
>
> This is almost certainly not what you want. This is mostly
> useful for embedded applications or simple mice.
>
> To compile this driver as a module, choose M here: the
> module will be called usbmouse.
>
> If even remotely unsure, say N.
>
> Regards,
> Florian
>
>
>
--
Regards,
Bengt Richter
next prev parent reply other threads:[~2020-04-20 22:27 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 [this message]
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)
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=20200420222607.GA4620@LionPure \
--to=bokr@bokr.com \
--cc=35574@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).