On Wed, 29 Jun 2005, Johannes Stezenbach wrote: > Patrick Boettcher wrote: >> On Wed, 29 Jun 2005, Ville Mauriala wrote: >>> mauri:~$ dvbtune -f 666000 -qam 64 -gi 8 -cr 2_3 -bv 8 -tm 8 >>> FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI >>> FE_HAS_SYN >>> Event: Frequency: 676600000 >> >> Why does dvbtune is trying 676 MHz, when you requested 666MHz? > > I think the frontend event reports the frequency where > the frontend has actually locked (after zig-zag, and with > AFC offset reported by FE_GET_FRONTEND). The dib3000mc-driver does not read back the frequency in get_frontend, but uses the old value from set_frontend. And in get_tune_settings it does not touch max_drift and step_size + tune_settings is memset to zero before calling get_tune_settings. Not sure if it is a driver-mistake. Patrick. -- Mail: patrick.boettcher@xxxxxxx WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/
