Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755154AbZGSS04 (ORCPT ); Sun, 19 Jul 2009 14:26:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752253AbZGSS0z (ORCPT ); Sun, 19 Jul 2009 14:26:55 -0400 Received: from rtr.ca ([76.10.145.34]:37069 "EHLO mail.rtr.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751663AbZGSS0y (ORCPT ); Sun, 19 Jul 2009 14:26:54 -0400 Message-ID: <4A63656D.4070901@rtr.ca> Date: Sun, 19 Jul 2009 14:26:53 -0400 From: Mark Lord Organization: Real-Time Remedies Inc. User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: Jean Delvare Cc: Andy Walls , linux-media@vger.kernel.org, Jarod Wilson , Mike Isely , Hans Verkuil , Mauro Carvalho Chehab , Janne Grunau , Linux Kernel Subject: Re: [PATCH 1/3] ir-kbd-i2c: Allow use of ir-kdb-i2c internal get_key funcs and set ir_type References: <1247862585.10066.16.camel@palomino.walls.org> <1247862937.10066.21.camel@palomino.walls.org> <20090719144749.689c2b3a@hyperion.delvare> <4A6316F9.4070109@rtr.ca> <20090719145513.0502e0c9@hyperion.delvare> <4A631B41.5090301@rtr.ca> <4A631CEA.4090802@rtr.ca> <4A632FED.1000809@rtr.ca> <20090719190833.29451277@hyperion.delvare> In-Reply-To: <20090719190833.29451277@hyperion.delvare> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1656 Lines: 56 (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: #include #include #include #include #include #include #include // Invoke with "/dev/input/event4" as argv[1] // // On 2.6.30, this gives the real name, eg. "i2c IR (Hauppauge)". // On 2.6.31, it simply gives "event4" as the "name". int main(int argc, char *argv[]) { char buf[32]; int fd, rc; fd = open(argv[1], O_RDONLY); if (fd == -1) { perror(argv[1]); exit(1); } rc = ioctl(fd,EVIOCGNAME(sizeof(buf)),buf); if (rc >= 0) fprintf(stderr," name : \"%.*s\"\n", rc, buf); return 0; } -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/