> i have tested this last week, only one clr_bit is needed after tuning. So, > if you "FE_RESET" after tuning in the core frontend stuff with FE_POLL (if > i have understand this correct), there is no need for doing this after > setting the symbolrate. > > Or, possilbe the better way, we don�t do a "RESET" in the core stuff for > the ves1x93 and let the clr_bit stay as is in the symbolrate routine. This > is maybe better, because the tuxbox project share the ves1x93 driver with > "us"; the dbox2 uses the same demod. So the frontend driver have a chance > to differ between ves1893 who need the "reset" and the ves1993 who will > irritate by this. > > Maybe Andreas Oberritter could say anything about this...
Weird, I see what you mean; the code doesn't do the clr_bit() if its a ves1993... although it _will_ have been having it done previously because of the old call to FE_RESET. Why then would there need to be multiple clr_bit() calls for the ves1893 then I wonder if only one is really needed? -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
