linux-kernel - [PATCH 0/7] Fixes for ALPS trackstick

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1415993906-13307-1-git-send-email-pali.rohar@gmail.com>
Date:	Fri, 14 Nov 2014 20:38:19 +0100
From:	Pali Rohár <pali.rohar@...il.com>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Hans de Goede <hdegoede@...hat.com>
Cc:	Yunkang Tang <yunkang.tang@...alps.com>,
	Vadim Klishko <vadim@...que.com>, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Pali Rohár <pali.rohar@...il.com>
Subject: [PATCH 0/7] Fixes for ALPS trackstick

This patch series fix detection and identifying trackstick on machines with
ALPS devices. Last patch split trackstick and bare PS/2 mouse packets between
dev2 and dev3 input devices which make sure that driver will send only trackstick
data to trackstick input device.

Pali Rohár (7):
  input: alps: Set correct name of psmouse device in alps_init()
  input: alps: Move trackstick detection to alps_hw_init_*
  input: alps: Move alps_dolphin_get_device_area into
    alps_hw_init_dolphin_v1
  input: alps: Use NULL instead dummy argument for alps_identify
  input: alps: Fix name, product and version of dev2 input device
  input: alps: Add sanity checks for non DualPoint devices
  input: alps: Do not report both trackstick and external PS/2 mouse
    data to one input device

 drivers/input/mouse/alps.c |  361 +++++++++++++++++++++++++++++++-------------
 drivers/input/mouse/alps.h |   14 +-
 2 files changed, 264 insertions(+), 111 deletions(-)

-- 
1.7.9.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/