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>
Subject: Re: [PATCH 1/3] ir-kbd-i2c: Allow use of ir-kdb-i2c internal get_key funcs and set ir_type
Date: Sun, 19 Jul 2009 12:31:04 -0700 [thread overview]
Message-ID: <20090719193104.GA17495@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <4A63656D.4070901@rtr.ca>
On Sun, Jul 19, 2009 at 02:26:53PM -0400, 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 ?
>>
>> Where does lsinput get the string from?
> ..
>
> Here's a test program for you:
>
And I think have a fix for that, commit
f936601471d1454dacbd3b2a961fd4d883090aeb
in the for-linus branch of my tree.
--
Dmitry
next prev parent reply other threads:[~2009-07-19 19:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 20:29 [PATCH 0/3] ir-kbd-i2c, cx18: IR devices for CX23418 boards Andy Walls
2009-07-17 20:35 ` [PATCH 1/3] ir-kbd-i2c: Allow use of ir-kdb-i2c internal get_key funcs and set ir_type Andy Walls
2009-07-19 12:47 ` Jean Delvare
2009-07-19 12:52 ` Mark Lord
2009-07-19 12:55 ` Jean Delvare
2009-07-19 13:10 ` Mark Lord
2009-07-19 13:17 ` Mark Lord
2009-07-19 14:38 ` Mark Lord
2009-07-19 17:08 ` Jean Delvare
2009-07-19 18:15 ` Mark Lord
2009-07-19 18:26 ` Mark Lord
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
2009-07-19 20:14 ` Mark Lord
2009-07-20 11:21 ` Andy Walls
2009-07-19 19:40 ` Jean Delvare
2009-07-19 19:31 ` Dmitry Torokhov [this message]
2009-07-19 16:29 ` [PATCH 1/3] ir-kbd-i2c: Allow use of ir-kdb-i2c internal get_key funcs and set ir_type Jean Delvare
2009-07-21 0:07 ` Andy Walls
2009-07-21 9:14 ` Jean Delvare
2009-07-17 20:46 ` [PATCH 2/3] 2/3: cx18: Add i2c initialization for Z8F0811/Hauppage IR transceivers Andy Walls
2009-07-19 13:38 ` Jean Delvare
2009-07-20 18:51 ` Jarod Wilson
2009-07-20 23:40 ` Andy Walls
2009-07-21 0:26 ` Andy Walls
2009-07-17 20:49 ` [PATCH 3/3] ir-kbd-i2c: Add support " Andy Walls
2009-07-19 19:22 ` 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=20090719193104.GA17495@dtor-d630.eng.vmware.com \
--to=dmitry.torokhov@gmail.com \
--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-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