On Monday 01 March 2004 12:09, Andrew de Quincey wrote: > I only have access to a few sat dishes, all of which are professional quality > with quad LNBs. I haven't ever actually experienced LNB drift. Currently the
Same here. > only use I have for the zigzagging code is to finetune during the initial > lock. Ideally, that would be done in a userspace library. Full ack. IMHO the driver should return the frequency offset (if possible). An application could use this offset and save the info. This could improve tuning speed... > _However_, from what Johannes and Holger were saying, removing zigzag from the > dirver has been tried before, but had to be re-added because it just didn't > work right without it. Some frontends may need it, others don't. > I suggest we implement my IOCTL suggestion, _as well as_ equivalent module > parameters, which by default will be set on, so as not to break people who do > need the current beheviour. The module parameters can then be used to > override everything else by those who know for sure that they don't need any > of the fancier stuff. If the application developers will implement these options, it will be fine. For me, module parameters are sufficient (maybe zigzag range + step size). Oliver P.S.: No need to CC me. I'm reading the ML. ;-) -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
