Gerd Knorr writes: > > > 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?
Yes, that is the downside of this method. > > 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? Via i2c client command calls. FE_REGISTER and FE_UNREGISTER call the dvb_(un)register_frontend functions. > > 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. Yes, definitely better for debugging. Ralph
