>>>> I have not yet had time to check with the latest driver, but >>>> probably the original poster could try removing the FE_CAN_RECOVER >>>> flag from ves1820.c, and if it does not help, Kaihola's "patch" on >>>> the this list. >>>> >>> I have been trying to test without FE_CAN_RECOVER but when I tried >>> to compile dvb-kernel drivers it complains about not being able to >>> find V4L2_BUF_FLAG_INPUT >>> >>> I'm using a 2.4.24 kernel with the patch from >>> http://bytesex.org/bttv. I don't know if this compile problem is >>> caused by that patch since it also includes v4l2 support. I think >>> it's trying to use the videodev2.h file from the kernel directory >>> instead of the one from dvb-kernel. >>> The kernel version doesn't have that define. >> >> I did a cvs co a couple of minutes ago and compiled without >> FE_CAN_RECOVER using the 2.6.3 kernel and the preliminary tests >> looks very promising, i will report back when i have done more tests. > > I wonder hat exactly FE_CAN_CLEAN_SETUP and FE_CAN_RECOVER mean > and whether they really apply to ves1820... >
Removing FE_CAN_RECOVER from ves1820 is a big improvement, I no longer need to tune more that one time to get a lock. So I sugest that it's removed. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
