On Friday 16 May 2008 21:34, Andy Walls wrote:
...
> It looks like cx18_reset_tuner_gpio() is being passed a bad callback
> pointer as the code to fetch cx->num from the callback pointer is
> correct.  In this function, we don't actually have the real data we
> need to work with.  We won't be able to reset the xc3028 tuner chip
> until this is resolved.
>
> That would also imply that the tuner-xc2028 driver has stored away
> the wrong data or corrupted the callback data we gave it to store.

Just to pitch in: last Tuesday my cx18 xceive tuner code was merged in 
the v4l-dvb tree, so I know that in that tree this tuner works well 
(analog only). The xceive_pin field in the card definition of 
cx18-cards.c probably needs adjusting for the xceive firmware load to 
work, though. The full range is 0-31, but I would test the range 8-15 
first. Basically a matter of 'rmmod cx18', edit/make/install 
cx18, 'modprobe cx18' and check if the fw is now loaded correctly.

Regards,

        Hans

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

Reply via email to