Ah. Hm. That's the usual problem you get with out-of-kernel drivers.
What I'll do is that when I branch ivtv for 2.6.17 I'll change the
adapter ID back to BT848 in the ivtv-0.7 branch. But for 2.6.18 some
major changes are expected anyway and I'll keep the CX2341X there as
that is really the correct adapter ID for this driver. Hopefully I'll
also have fixed ir-kbd-i2c so that the remote support just works
without needing the lirc drivers.
Hans
On Sunday 09 April 2006 09:23, Martin Dauskardt wrote:
> >I used
> > .id = I2C_HW_B_BT848,
> >instead of
> > .id = I2C_HW_B_CX2341X,
> >
> >and lirc_i2c works!!
>
> I think this is because you reversed the change in ir-kbd-i2c.
>
> >I will make a further test and see if the original rev 3235 works
> > with
>
> ir-kbd-i2c from two weeks ago ... Depending on this, >either
> ivtv-i2c.c or ir-kbd-i2c needs a change.
>
> o.k., it was too late :-) Of course it has nothing to do with
> ir-kbd-i2c, as I am not using it. The key is in lirc_i2c.c:
>
> case 0x18:
> case 0x1a:
> if (adap->id == (I2C_ALGO_BIT | I2C_HW_B_BT848)) {
> strcpy(ir->c.name,"Hauppauge IR");
> ir->l.code_length = 13;
> ir->l.add_to_buf=add_to_buf_haup;
>
>
> _______________________________________________
> 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
