[PATCH evdev] When building against server 1.8, install 00-evdev.conf.

[Dan Nicholson]

On Wed, Mar 31, 2010 at 6:22 PM, Alan Coopersmith
<alan.coopersmith at oracle.com> wrote:
> Dan Nicholson wrote:
>> Not quite. The hal backend ignores any devices that don't have the
>> input.x11_driver key set. We could change that, but it might be better
>> to keep this behavior for consistency.
>
> So right now, if I start up Xorg from git master on OpenSolaris, where
> we still use HAL since I haven't had a chance to code up the replacement
> code yet, it finds the devices fine via the HAL .fdi file shipped with
> Xorg that maps them to the kbd & mouse driver - is there anything we need
> to do to stick with this for 1.8?   Will any of the settings in the current
> config/x11-input.fdi be moved into xorg.conf.d files?  Should they?

If you're using the hal backend, you don't have to change anything.
The options are still imported from the fdi. What gets tricky is when
you start mixing the fdi and InputClass settings. Since Peter and I
decided that the InputClass settings should take precedence over the
options passed in by the backend, you could have legitimate fdi
settings dropped. The case I think would bite you is where a user has
a custom fdi file setting the driver to synaptics and then you have a
generic InputClass that sets it back to mouse. I don't really know the
best way to handle that besides porting the existing fdi files to
xorg.conf.d files.

--
Dan