linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mark Lord <lkml@rtr.ca>
Cc: Jean Delvare <khali@linux-fr.org>, Andy Walls <awalls@radix.net>,
	linux-media@vger.kernel.org, Jarod Wilson <jarod@redhat.com>,
	Mike Isely <isely@pobox.com>, Hans Verkuil <hverkuil@xs4all.nl>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Janne Grunau <j@jannau.net>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-input@vger.kernel.org
Subject: Re: Regression 2.6.31:  ioctl(EVIOCGNAME) no longer returns device name
Date: Sun, 19 Jul 2009 12:39:52 -0700	[thread overview]
Message-ID: <20090719193952.GC17495@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <4A637212.2000002@rtr.ca>

On Sun, Jul 19, 2009 at 03:20:50PM -0400, Mark Lord wrote:
> Mark Lord wrote:
>> (resending.. somebody trimmed linux-kernel from the CC: earlier)
>>
>> Jean Delvare wrote:
>>> On Sun, 19 Jul 2009 10:38:37 -0400, Mark Lord wrote:
>>>> I'm debugging various other b0rked things in 2.6.31 here right now,
>>>> so I had a closer look at the Hauppauge I/R remote issue.
>>>>
>>>> The ir_kbd_i2c driver *does* still find it after all.
>>>> But the difference is that the output from 'lsinput' has changed
>>>> and no longer says "Hauppauge".  Which prevents the application from
>>>> finding the remote control in the same way as before.
>>>
>>> OK, thanks for the investigation.
>>>
>>>> I'll hack the application code here now to use the new output,
>>>> but I wonder what the the thousands of other users will do when
>>>> they first try 2.6.31 after release ?
> ..
>
> Mmm.. appears to be a systemwide thing, not just for the i2c stuff.
> *All* of the input devices now no longer show their real names
> when queried with ioctl(EVIOCGNAME).  This is a regression from 2.6.30.
> Note that the real names *are* still stored somewhere, because they
> do still show up correctly under /sys/
>

Should be fixed by f936601471d1454dacbd3b2a961fd4d883090aeb in the
for-linus branch of my tree.

-- 
Dmitry

  reply	other threads:[~2009-07-19 19:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1247862585.10066.16.camel@palomino.walls.org>
     [not found] ` <1247862937.10066.21.camel@palomino.walls.org>
     [not found]   ` <20090719144749.689c2b3a@hyperion.delvare>
     [not found]     ` <4A6316F9.4070109@rtr.ca>
     [not found]       ` <20090719145513.0502e0c9@hyperion.delvare>
     [not found]         ` <4A631B41.5090301@rtr.ca>
     [not found]           ` <4A631CEA.4090802@rtr.ca>
     [not found]             ` <4A632FED.1000809@rtr.ca>
     [not found]               ` <20090719190833.29451277@hyperion.delvare>
     [not found]                 ` <4A63656D.4070901@rtr.ca>
2009-07-19 19:20                   ` Regression 2.6.31: ioctl(EVIOCGNAME) no longer returns device name Mark Lord
2009-07-19 19:39                     ` Dmitry Torokhov [this message]
2009-07-19 20:14                       ` Mark Lord
2009-07-20 11:21                         ` Andy Walls
2009-07-19 19:40                     ` Jean Delvare

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=20090719193952.GC17495@dtor-d630.eng.vmware.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=awalls@radix.net \
    --cc=hverkuil@xs4all.nl \
    --cc=isely@pobox.com \
    --cc=j@jannau.net \
    --cc=jarod@redhat.com \
    --cc=khali@linux-fr.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=mchehab@infradead.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).