On Saturday 20 March 2004 23:07, Johannes Stezenbach wrote: > Andrew de Quincey wrote: > > > > But why does it break DISEQC as well? > > DiSEqC is implemented using a timer irq in the firmware.
Well, this will work only if there is no other interrupt load. Otherwise the timer interrupt processing might be delayed and timing is off. > And "hardware" section filters cause some ARM CPU load > (as do TS filters). > > Of course, while tuning there is no signal and the load > should be zero. But some frontends just output garbage > instead of muting their output. Hmm, why should the load be zero if you are switching from one channel to another one? In this case there is a valid signal. Oliver -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
