From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id mA60kmhh023603 for ; Wed, 5 Nov 2008 19:46:48 -0500 Received: from mail.isp.novis.pt (onyx.ip.pt [195.23.92.252]) by mx3.redhat.com (8.13.8/8.13.8) with ESMTP id mA60kZvm022237 for ; Wed, 5 Nov 2008 19:46:35 -0500 From: Ricardo Cerqueira To: hermann pitton In-Reply-To: <1225930171.3338.8.camel@pc10.localdom.local> References: <1225586521.2642.7.camel@pc10.localdom.local> <1225930171.3338.8.camel@pc10.localdom.local> Date: Thu, 06 Nov 2008 00:46:35 +0000 Message-Id: <1225932395.13472.19.camel@frolic> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: video4linux-list@redhat.com Subject: Re: Pinnacle PCTV 310i Remote: i2c 'ERROR: NO_DEVICE' List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: video4linux-list-bounces@redhat.com Errors-To: video4linux-list-bounces@redhat.com List-ID: Hi all; On Thu, 2008-11-06 at 01:09 +0100, hermann pitton wrote: > Hi Matteo, > > Am Dienstag, den 04.11.2008, 15:09 +0100 schrieb picciuX: > > 2008/11/2 hermann pitton : > > > > > don't have that remote, but also enable ir-kbd-i2c debug=1. > > > > > > ir-kbd-i2c: probe 0x7a @ saa7133[0]: no > > > ir-kbd-i2c: probe 0x47 @ saa7133[0]: no > > > ir-kbd-i2c: probe 0x71 @ saa7133[0]: no > > > ir-kbd-i2c: probe 0x2d @ saa7133[0]: no > > > ir-kbd-i2c: probe 0x7a @ saa7133[1]: no > > > ir-kbd-i2c: probe 0x47 @ saa7133[1]: no > > > ir-kbd-i2c: probe 0x71 @ saa7133[1]: no > > > ir-kbd-i2c: probe 0x2d @ saa7133[1]: no > > > Sorry, I missed the rest of the thread; In any case, from the above paste, it looks as if you have 2 saa713x boards in the system, right? I suspect the bug is somehow related to that (ir-kbd-i2c is getting the events, but sending them to the wrong board). Have you tried removing one of them? -- RC > > > You should have the device found at 0x47. > > > > > > > In fact i see: > > > > ir-kbd-i2c: probe 0x47 @ saa7133[0]: yes > > > > So everything seemed to go well. But, same story for the rest: ERROR: > > NO_DEVICE when i press buttons on the remote. > > What seems strange to me is the fact that the driver *reacts* to > > remote key presses, but reacts with an error. > > > > Cheers > > Matteo > > > > since you reported the trouble was already visible for you on earlier > kernels, we might try to get a second confirmation at first. > > Anyone out there? I'm sending a copy to Ricardo too, who added the > support, not sure if he currently has time to read the list. > > Cheers, > Hermann > > > > > -- video4linux-list mailing list Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list