> What about a writeable complete register dump for each dvb_i2c device? > Then you don't have to reimplement this for every new frontend driver.
Sounds interesting. But right now I don't need to change any registers on the device directly, but rather specify that when new frontend parameters are set, register values XXX are used to program the frontend demodulator. I.e. the register values used by the driver need to be modified, so that the driver will use the new values instead of the default (as opposed to changing a register value, then having the driver write the default one again in the next frontend change). I hope that made sense :-) Sorry if I misunderstood you. > Yes, to make it simple you can add a two proc files: one that takes a > binary dvb_frontend_parameters struct and one that takes one in ascii > format like generated by the scan utility and czap/tzap. > The dump and parser code you can take from czap.c, tzap.c and scan/dump.c In addition to the existing ones, or to replace them? Sounds like a good idea, just wasn't sure if you'd be happy with the added complexity inside the kernel (i.e. parsers and pre/post processors). But I will add them :) Cheers, Dennis -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
