linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kai-Heng Feng <kai.heng.feng@canonical.com>
To: "open list:HID CORE LAYER" <linux-input@vger.kernel.org>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Peter Hutterer <peter.hutterer@who-t.net>,
	ray.chen@canonical.com,
	You-Sheng Yang <vicamo.yang@canonical.com>
Subject: How to make sure touchpad doesn't use psmouse.ko?
Date: Mon, 7 Oct 2019 15:45:19 +0800	[thread overview]
Message-ID: <7DD64ADB-478C-408C-873D-C07186FEB65F@canonical.com> (raw)

Hi,

When we are enabling a new hardware, sometimes touchpad may still use psmouse.ko due to bugs or missing IDs.
Is there a way to quickly to determine the touchpad doesn't use psmouse but something like SMBus or HID over I2C?

Kai-Heng

             reply	other threads:[~2019-10-07  7:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07  7:45 Kai-Heng Feng [this message]
2019-10-11  9:35 ` How to make sure touchpad doesn't use psmouse.ko? Benjamin Tissoires
2019-10-16 10:58   ` Kai-Heng Feng

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=7DD64ADB-478C-408C-873D-C07186FEB65F@canonical.com \
    --to=kai.heng.feng@canonical.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=peter.hutterer@who-t.net \
    --cc=ray.chen@canonical.com \
    --cc=vicamo.yang@canonical.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.
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).