[RFC] merged void driver

[Peter Hutterer]

On Sat, Nov 06, 2010 at 07:55:10PM -0500, Pat Kane wrote:
> On Sat, Nov 6, 2010 at 5:05 PM, Peter Hutterer <peter.hutterer at who-t.net> wrote:
> ...
>  >  the simple solution is to ditch support for
>  > older X servers (I don't think anyone really cares about void supporting the
>  > last 3 server releases) but exactly at that point it starts making sense
>  > merging the drivers into the server.
> 
> I care about the void drivers for the 1.5.1  server when I need to use VNC.

1.5 has the VCP/VCK already, which should abolish the need for the void
driver as fake input devices. what does VNC need the void driver for?
historically it was useful because at least one device had to be the core
pointer, but since 1.4 that need is gone.
 
> Will VNC, as a loadable module, work with the next release without a
> void driver?

fwiw, it's not going away, the location for it simply changes. so instead of
a separate module, it'll be part of the xserver tree, but still produce the
same void_drv.so.

Cheers,
  Peter