From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Guillaume Chazarain <guichaz@gmail.com>
Cc: ajax@redhat.com, LKML <linux-kernel@vger.kernel.org>,
linux-input@vger.kernel.org
Subject: Re: evdev regression on macbook with 2.6.33-rc5
Date: Mon, 25 Jan 2010 15:25:21 -0800 [thread overview]
Message-ID: <20100125232520.GC30307@core.coreip.homeip.net> (raw)
In-Reply-To: <3d8471ca1001251449g6bdbdb4fn11f566b41691f870@mail.gmail.com>
On Mon, Jan 25, 2010 at 11:49:20PM +0100, Guillaume Chazarain wrote:
> On Sun, Jan 24, 2010 at 10:30 AM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> > DOes the same behavior happens when you try using 'evtest' utility while
> > in console?
>
> Hi Dmitry,
>
> While struggling to make evtest show keyboard events, I discovered
> that the problem is an incompatibility with mouseemu
> (http://packages.ubuntu.com/karmic/mouseemu) as killing it makes the
> keyboard work fine.
>
> So, with mouseemu running, evtest won't print any event at all even if
> I move the mouse, and when mouseemu is off everything works fine and
> evtest prints the expected events.
>
Ah, well, I checked out the sources for this fine specimen. Oh man...
Then we have Debian guys adding their perls to keyboard handler:
++ if (inp.type != EV_KEY && inp.type != EV_REP)
++ return;
Obviously EV_SYN is completely useless message. And who cares about
keyboards with scroll wheels, volume sliders, etc, right?
This package either needs lots of love or it just needs to die...
--
Dmitry
prev parent reply other threads:[~2010-01-25 23:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 18:53 evdev regression on macbook with 2.6.33-rc5 Guillaume Chazarain
2010-01-24 9:30 ` Dmitry Torokhov
2010-01-25 22:49 ` Guillaume Chazarain
2010-01-25 23:25 ` Dmitry Torokhov [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=20100125232520.GC30307@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=ajax@redhat.com \
--cc=guichaz@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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).