From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Lord Subject: Re: 2.6.36/2.6.37: broken compatibility with userspace input-utils ? Date: Wed, 26 Jan 2011 14:33:17 -0500 Message-ID: <4D4076FD.6070207@teksavvy.com> References: <4D3E59CA.6070107@teksavvy.com> <4D3E5A91.30207@teksavvy.com> <20110125053117.GD7850@core.coreip.homeip.net> <4D3EB734.5090100@redhat.com> <20110125164803.GA19701@core.coreip.homeip.net> <20110125205453.GA19896@core.coreip.homeip.net> <4D3F4804.6070508@redhat.com> <4D3F4D11.9040302@teksavvy.com> <20110125232914.GA20130@core.coreip.homeip.net> <20110126020003.GA23085@core.coreip.homeip.net> <4D403855.4050706@teksavvy.com> <4D405A9D.4070607@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4D405A9D.4070607@redhat.com> Sender: linux-media-owner@vger.kernel.org To: Mauro Carvalho Chehab Cc: Dmitry Torokhov , Linus Torvalds , Linux Kernel , linux-input@vger.kernel.org, linux-media@vger.kernel.org List-Id: linux-input@vger.kernel.org On 11-01-26 12:32 PM, Mauro Carvalho Chehab wrote: > Em 26-01-2011 13:05, Mark Lord escreveu: .. >> Nope. Does not work here: >> >> $ lsinput >> protocol version mismatch (expected 65536, got 65537) > > You need to relax the version test at the tree. As I said before, this is > a development tool from the early RC days, bound to work with one specific > version of the API, and programmed by purpose to fail if there would by any > updates at the Input layer. .. As I said before, I personally have done that on my copy here. But that's not what this thread is about. This thread is about broken userspace courtesy of these changes. So I am testing with the original userspace binary here, and it still fails. And will continue to fail until that regression is fixed. Cheers