[RFC] merged void driver

[Alan Coopersmith]

Tiago Vignatti wrote:
> On Fri, Nov 05, 2010 at 10:21:33AM +1000, ext Peter Hutterer wrote:
>> I'm looking at having to fix a number of unmaintained drivers for ABI 12 and
>> because it's hopefully the last time I'll worry about multi-server support
>> for those drivers, I decided to see how much work it is to merge a driver.
>>
>> Current tree is on branch driver-merge in my xserver repo.
>> http://cgit.freedesktop.org/~whot/xserver/log/?h=driver-merge
>> Still rebasing where needed, but it's a start.
>>
>> My main grief at this point is the massive AM_CPPFLAGS define which I'd like
>> to see somewhere more central. In the current drivers, we can just use the
>> sdk directory, but these headers are all over the server's source tree.
>>
>> Any comments appreciated.
> 
> Peter, can you please brief the motivation for merging specifically input void
> driver? I mean, we can start a server without input drivers, so why we would
> care about a void one?

You could watch the video of the discussion at XDS that you slept through
where we discussed this.  8-)

The short summary is:  xf86-input-void & xf86-video-dummy *ONLY* change
when the X server ABI changes - they never have to support new models of
the "null" hardware, so can both serve as examples of driver updates to
new ABI's, and will never need to be separately backported to an older
server by a LTS/enterprise distro that needs to support new hardware
with their existing stable server branch.

-- 
	-Alan Coopersmith-        alan.coopersmith at oracle.com
	 Oracle Solaris Platform Engineering: X Window System