[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110126193804.GD29268@core.coreip.homeip.net>
Date: Wed, 26 Jan 2011 11:38:05 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Mark Lord <kernel@...savvy.com>
Cc: Mauro Carvalho Chehab <mchehab@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
linux-input@...r.kernel.org, linux-media@...r.kernel.org
Subject: Re: 2.6.36/2.6.37: broken compatibility with userspace input-utils ?
On Wed, Jan 26, 2011 at 02:31:44PM -0500, Mark Lord wrote:
> On 11-01-26 11:44 AM, Dmitry Torokhov wrote:
> > On Wed, Jan 26, 2011 at 10:05:57AM -0500, Mark Lord wrote:
> ..
> >> Nope. Does not work here:
> >>
> >> $ lsinput
> >> protocol version mismatch (expected 65536, got 65537)
> >>
> >
> > It would be much more helpful if you tried to test what has been fixed
> > (hint: version change wasn't it).
>
> It would be much more helpful if you would revert that which was broken
> in 2.6.36. (hint: version was part of it).
>
No, version change will not be reverted as we do not have a way to
validate whether new ioctls are supported. The older kernels are
returning -EINVAL for unknown evdev ioctls so userspace can't know
if ioctl failed because it is unsupported or because arguments are
wrong/not applicable for the underlying device.
> The other part does indeed appear to work with the old binary for input-kbd,
> but the binary for lsinput still fails as above.
>
Great, then I'' include the fix for RC keytables in my next pull
request. I guess it should go to stable as well.
Thanks.
--
Dmitry
--
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/
Powered by blists - more mailing lists