naming of DDXen.

[Luc Verhaegen]

On Wed, Jun 15, 2005 at 10:33:53AM +0200, Egbert Eich wrote:
>  > And done.  I skipped two directories under hw/xfree86/drivers/, v4l and i2c.  
>  > I've never actually seen v4l to work so I have no idea what it should be 
>  > classed as.  And i2c I don't know if it's worth our time to split out into 40 
>  > submodules, but probably not.
> 
> v4l is an independent module that works with any driver that 
> supports specific Xv features.
> It currently behaves like a driver (it calls AddDriver() and uses
> the Probe() function to register itself with the XV extension).
> That's probably the only reason why it lives among the drivers.
> 
>  > 
>  > So, what do we think about the following options?
>  > 
>  >     xf86-v4l versus xf86-video-v4l
>  >     xf86-i2c versus xf86-i2c-*
>  > 
> 
> What do you plan to put in xf86-i2c? The i2c module in xfree86/i2c
> is generic and uniq across all drivers. However contrary to the
> v4l module it is not a driver. 
> It makes only sense in
> an XFree86 DDX context. Why don't we keep these kind of modules
> together with the core part of the XFree86 DDX? 
> 
> Egbert.
xf86-i2c-<device> makes sense.

Output devices (or whatever they should be named) are, in the end, going 
to have to sit there. Stuff like brooktree/conexant, chrontel, 
philips etc. The stuff currently in the i2c directory is very ati 
specific, but it's a start for something that needs to be shared between 
many video drivers.

I expect stuff like:
xf86-i2c-bt86x (tv encoders BT868/869)
xf86-i2c-ch7xxx
xf86-i2c-fs45x
xf86-i2c-sil16x
xf86-i2c-saa711x
xf86-i2x-sis30x
xf86-i2c-vt162x
xf86-i2c-vt163x
etc.

I have a voodoo3 here and a prosavage board and nv card on their way, 
all have the bt869. So that will probably be the first.

vt162x needs to be shared between via (unichrome), savage and trident.

sil16x is possible for i8xx, via and nv.

And on and on :)

Luc Verhaegen.