Hi, > That only gives access to the already registered i2c_adapter (but > a lot cleaner than the present method used to do this).
Making it cleaner was exactly the point ;) > What one needs for properly registering the frontend is access to the > dvb_adapter and the i2c_client pointers at the same time. Ok, I see. > The only place where this happens is in the attach_inform > function of the bttv driver. Currently, only the analog tuners and audio > controllers are initialized there. So, that's the natural place to > also initialize DVB frontends. Of course the dvb_adapter pointer would > also have to be part of the bttv structure. I don't like the idea to make bttv depend on the dvb core, I think that will happen when doing it this way? > Alternative: get the i2c_adapter pointer via sub_device, > lock it, (in case of linuxtv driver, change i2c adapter name), > scan it for already present clients, init them, How the initialization is done? > somehow add a callback for sub_devices in attach_inform > for future attachments, do the same for detachments (if one > allows it at all), unlock i2c_adapter. We'll need both attach and detach I think. "rmmod $frontend" should work, even if it is only for small driver development turnaround times. Gerd PS: anyone at OLS? -- return -ENOSIG;
