On Sunday 14 March 2004 23:15, Klaus Schmidinger wrote: > Andreas Oberritter wrote: > > Hi, > > > > On Sun, 2004-03-14 at 23:46, Andrew de Quincey wrote: > > > I suppose its a matter of how tolerant we want to be of userspace > > > programs.. I mean, we already turn OFF the LNB power automatically, why > > > not turn it on as well? > > > > I don't care much, but please don't change the voltage setting in the > > inittab, because it breaks support for the ves1893 and ves1993 on the > > other (non-pci) boards, where the gpio pins toggled by this register > > have a different meaning. > > > > If you decide to set the voltage of all frontends to 13V at open(), then > > checking for O_RDWR should be sufficient to decide, because only one > > writer is allowed. > > > > However, I don't like that idea. It makes it impossible to stay at 0V, > > when the frontend is connected to a loop through output of another > > receiver, which shall not be disturbed. Userspace apps can choose the > > desired voltage anyway after opening the device. > > Ok, if it is defined behaviour that the driver does _not_ turn on LNB > power when opening the frontend, that's fine with me - I have a workaround > in VDR now. I just wasn't aware of this change, and apparently it has > nothing to do with the actual problem of DiSEqC switching being unreliable > with dvb-kernel.
So there must still be a change in the av7110 code, which does the DISEQC on your card. As far as I can see none of the other changes to ves1x83 should break anything. Just that there were _two_ driver issues here complicated the matter. Dunno much about the av7110 myself... does the firmware have anything to do with DISEQC? Was there a firmware change between 1.0.1 and 1.1.0? -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
