From: Pavel Machek <pavel@ucw.cz>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
kernel list <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-input@vger.kernel.org
Subject: Re: 3.7-rc3: mouses stopped working
Date: Sun, 18 Nov 2012 19:53:17 +0100 [thread overview]
Message-ID: <20121118185316.GA2844@elf.ucw.cz> (raw)
In-Reply-To: <20121118085638.GA2331@core.coreip.homeip.net>
Hi!
> > That is correct and expected behavior.
> >
> > > So it seems to be "/dev/input/mice" issue. Does it work for you?
> >
> > Yes, it works for me properly (testing with rc4+, 1b42fc4 more precisely).
> > Even after disconnect/reconnect cycle of USB mouse, I am getting events
> > properly from /dev/input/mice (frankly I am surprised that you noticed ...
> > Xorg has been using evdev driver for ages already by default, right?)
> >
> > What was the last kernel version that worked for you in this respect?
> >
> > Adding Dmitry and linux-input.
>
> Does the patch below help?
Yes. With this patch, my mice are back.
Tested-by: Pavel Machek <pavel@ucw.cz>
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2012-11-18 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121115132849.GA4062@elf.ucw.cz>
[not found] ` <alpine.LNX.2.00.1211151429240.15877@pobox.suse.cz>
[not found] ` <20121115140736.GA2651@elf.ucw.cz>
[not found] ` <alpine.LNX.2.00.1211151508350.15877@pobox.suse.cz>
[not found] ` <20121116013405.GA2002@elf.ucw.cz>
[not found] ` <alpine.LNX.2.00.1211161153290.20577@pobox.suse.cz>
[not found] ` <20121116122400.GA10994@elf.ucw.cz>
2012-11-16 12:37 ` 3.7-rc3: mouses stopped working Jiri Kosina
2012-11-18 8:56 ` Dmitry Torokhov
2012-11-18 13:34 ` Krzysztof Mazur
2012-11-18 18:53 ` Pavel Machek [this message]
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=20121118185316.GA2844@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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).