Re: Pinnacle PCTV 310i Remote: i2c 'ERROR: NO_DEVICE'

[Ricardo Cerqueira <v4l@cerqueira.org>]

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 <hermann-pitton@arcor.de>:
> > 
> > > 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