On Thursday 17 Nov 2005 17:22, Johannes Stezenbach wrote: > On Thu, Nov 17, 2005 at 04:33:47PM +0000, Andrew de Quincey wrote: > > On Thursday 17 Nov 2005 15:51, Johannes Stezenbach wrote: > > > One semantic question: With FE_TUNE_MODE_ONESHOT, will the > > > frontend thread still monitor the frontend and generate > > > signal lost and locked events? Because I think that's not > > > useful during scanning, you're better off calling FE_READ_STATUS > > > manually. > > > > Correct - it will not monitor/ generate them. > > OK. Please add a comment to frontend.h which says so. How about: /** * When set, this flag will disable any zigzagging or other "normal" tuning * behaviour. Additionally, there will be no automatic monitoring of the lock * status, and hence no frontend events will be generated. */ #define FE_TUNE_MODE_ONESHOT 0x01
