I've commented this code, so please get the latest trunk and test again. 
I'd completely forgotten about adding this code :-)

        Hans

On Thursday 06 April 2006 08:30, Martin Dauskardt wrote:
> > From: Hans Verkuil <[EMAIL PROTECTED]>
> > - Better Hauppauge remote support: it seems it is broken in the
> > latest v4l-dvb repository. I'd appreciate it if someone can track
> > down the exact problem. I know how to tell the various Hauppauge
> > remotes apart, so that may help to fix this issue correctly. This
> > is a kernel problem, not an ivtv one. So you need to hack the
> > v4l-dvb sources.
>
> I am using v4l-dvb-mercurial from 03.04.06 both for a 2.6.15 kernel
> with ivtv 0.4.4 and for a 2.6.16 with ivtv 0.7.0
> With ivtv 0.4.4 ir-kbd-i2c does not load automatically, and the
> remote works with lirc_i2c perfectly.
>
> With ivtv 0.7.0 the same version of ir-kbd-i2c loads automatically
> after "modprobe ivtv"  and can`t be unloaded. So I don`t think it`s a
> kernel problem.
>
>
> Could this be the problem:
>
> ivtv/trunk/driver/ivtv-i2c.c
> Revision 3207 - (view) (download) - [select for diffs]
> Modified Thu Mar 23 22:53:32 2006 UTC (13 days, 7 hours ago) by
> hverkuil File length: 17440 byte(s)
> Diff to previous 3140
> Update driver for latest v4l-dvb repository containing the
> new routing changes.
>
> #include <media/ir-kbd-i2c.h>
>
> if (client->addr == 0x7a) {
>                    struct IR_i2c *ir = i2c_get_clientdata(client);
>                    IVTV_INFO("%s i2c IR detected (%s).\n",
>    #if LINUX_VERSION_CODE <=  KERNEL_VERSION(2,6,15)
>                                    client->driver->name,ir->phys);
>    #else
>                    client->driver->driver.name, ir->phys);
>    #endif
>                    ir->get_key   = get_key_pinnacle;
>                    ir->ir_codes  = ir_codes_pinnacle;
>            }
>
>
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel

_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to