[linux-dvb] Re: NEWSTRUCT questions

[Gerd Knorr <kraxel@bytesex.org>]

> > The DVB driver should be able to tell the I2C subsystem to probe for
> > frontends only on a specific I2C bus. (The frontend drivers are
> > the same for all systems, so they know nothing about the busses.)
>  
>  Thats true. At least it would be fine to have such a situation ;)

Easily doable in the i2c_driver->attach_adapter() function, just check
i2c_adapter->id before calling the i2c_probe() function.

>  My idea is to extend the dvb_i2c layer with some kind of
>  gateway/bridge to the linux i2c layer. dvb_i2c will try to probe its
>  internal busses first and then fallback to linux i2c if no devices
>  could be attached.

What exactly is the point of having two different i2c layers?  Why don't
you simply use the linux i2c layer for everything?

>  This opens up another question: Is there a required module load
>  order? Frist fe's then adapters or the other way round? Or no
>  required order at all?

module loading should work in any order (unless symbol dependences
force some specific ordering).

  Gerd

-- 
You can't please everybody.  And usually if you _try_ to please
everybody, the end result is one big mess.
				-- Linus Torvalds, 2002-04-20


-- 
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe linux-dvb" as subject.