From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from zone0.gcu-squad.org ([212.85.147.21]:27903 "EHLO services.gcu-squad.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754837AbZGSQaG (ORCPT ); Sun, 19 Jul 2009 12:30:06 -0400 Date: Sun, 19 Jul 2009 18:29:48 +0200 From: Jean Delvare To: Mark Lord Cc: Andy Walls , linux-media@vger.kernel.org, Jarod Wilson , Mike Isely , Hans Verkuil , Mauro Carvalho Chehab , Janne Grunau Subject: Re: [PATCH 1/3] ir-kbd-i2c: Allow use of ir-kdb-i2c internal get_key funcs and set ir_type Message-ID: <20090719182948.2bfafc67@hyperion.delvare> In-Reply-To: <4A631CEA.4090802@rtr.ca> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-media-owner@vger.kernel.org List-ID: On Sun, 19 Jul 2009 09:17:30 -0400, Mark Lord wrote: > Mark Lord wrote: > > Jean Delvare wrote: > >> Hi Mark, > >> > >> On Sun, 19 Jul 2009 08:52:09 -0400, Mark Lord wrote: > >>> While you folks are looking into ir-kbd-i2c, > >>> perhaps one of you will fix the regressions > >>> introduced in 2.6.31-* ? > >>> > >>> The drive no longer detects/works with the I/R port on > >>> the Hauppauge PVR-250 cards, which is a user-visible regression. > >> > >> This is bad. If there a bugzilla entry? If not, where can I read more > >> details / get in touch with an affected user? > > .. > > > > I imagine there will be thousands of affected users once the kernel > > is released, but for now I'll volunteer as a guinea-pig. > > > > It is difficult to test with 2.6.31 on the system at present, though, > > because that kernel also breaks other things that the MythTV box relies on, > > and the system is in regular use as our only PVR. > > > > Right now, all I know is, that the PVR-250 IR port did not show up > > in /dev/input/ with 2.6.31 after loading ir_kbd_i2c. But it does show > > up there with all previous kernels going back to the 2.6.1x days. > .. > > Actually, I meant to say that it does not show up in the output from > the lsinput command, whereas it did show up there in all previous kernels. Never heard of lsinput, where does it come from? > > > So, to keep the pain level reasonable, perhaps you could send some > > debugging patches, and I'll apply those, reconfigure the machine for > > 2.6.31 again, and collect some output for you. And also perhaps try > > a few things locally as well to speed up the process. > > > > Okay? I'd need additional information first, otherwise I have no clue where to start debugging. Which you just sent in a further post, as I see, so I'll follow-up there... -- Jean Delvare