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: Wed, 29 Apr 2020 18:41:20 +0200 [thread overview]
Message-ID: <20200429164120.fousoswocdgsralr@pelzflorian.localdomain> (raw)
In-Reply-To: <87zhauwbdx.fsf@gmail.com>
On Wed, Apr 29, 2020 at 05:38:02PM +0200, Mathieu Othacehe wrote:
> I know that (for now) having a mouse in the installer is not very
> useful. But maybe `kernel-arguments' in (gnu system install) should
> inherit from this field?
Actually in my tests I no longer need the modprobe.blacklist=radeon on
my AMD PC. I suggest the attached revert instead and will push it if
there are no objections.
Regards,
Florian
next prev parent reply other threads:[~2020-04-29 16:42 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) [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200429164120.fousoswocdgsralr@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 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.