From: vivi@mage.me.uk (Reza)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Newest kernel appears to break tap feature - good starting point for kernel development?
Date: Fri, 03 Feb 2012 22:11:21 +0000 [thread overview]
Message-ID: <4F2C5B89.8060900@mage.me.uk> (raw)
Hi all,
I'm interested in getting involved in kernel development. I compiled the
latest kernel and found that it broke the tap feature on my asus x54h
k54l. I had a look at the way the devices were interpreted and
/proc/bus/input/devices gave different results. This seems like it may
be a good starting point but I'm not sure where to go from here or
whether it's an issue with the kernel. I presume it is as switching back
to the older kernel fixes the tapping for left click. Any advice on
where to go from here would be greatly appreciated. Thanks.
Reza
-works fine-
Linux laptop 3.1.0-1-amd64 #1 SMP Tue Jan 10 05:01:58 UTC 2012 x86_64
GNU/Linux
I: Bus=0011 Vendor=0002 Product=0001 Version=0063
N: Name="PS/2 Logitech Wheel Mouse"
P: Phys=isa0060/serio4/input0
S: Sysfs=/devices/platform/i8042/serio4/input/input6
U: Uniq=
H: Handlers=mouse0 event6
B: PROP=0
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=103
-latest kernel where the tap feature breaks-
Linux laptop 3.3.0-rc2+ #5 SMP Fri Feb 3 21:05:27 GMT 2012 x86_64 GNU/Linux
I: Bus=0011 Vendor=0002 Product=000e Version=0000
N: Name="ETPS/2 Elantech Touchpad"
P: Phys=isa0060/serio4/input0
S: Sysfs=/devices/platform/i8042/serio4/input/input6
U: Uniq=
H: Handlers=mouse0 event6
B: PROP=0
B: EV=b
B: KEY=6420 30000 0 0 0 0
B: ABS=260800011000003
next reply other threads:[~2012-02-03 22:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 22:11 Reza [this message]
2012-02-04 7:03 ` Newest kernel appears to break tap feature - good starting point for kernel development? Mulyadi Santosa
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=4F2C5B89.8060900@mage.me.uk \
--to=vivi@mage.me.uk \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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 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.