[PATCH] xfree86: Allow a config directory for multiple config files

Ping pinglinux at gmail.com
Wed Dec 16 17:14:04 PST 2009


On Mon, Dec 14, 2009 at 2:59 PM, Ping <pinglinux at gmail.com> wrote:

> On Mon, Dec 14, 2009 at 7:36 AM, Dan Nicholson <dbn.lists at gmail.com>wrote:
>
>>  I think it will work the way you envision, but with the caveat that
>> there isn't any parsing of ~/.xorg.conf and never has been. After
>> that, it would work similarly to how you describe. xorg.conf is parsed
>> first and then the xorg.conf.d files are parsed afterwards, but their
>> contents are all mashed into one configuration structure. There is no
>> on-the-fly parsing of config files, but there doesn't need to be.
>> Earlier matches take precedence, so if the input device is fully
>> specified in xorg.conf, nothing happening in xorg.conf.d would have
>> any effect.
>>
>
> Sounds very reasonable.  My concern was it looked to me like that you have
> to manually disable the options in xorg.conf if there is a local/custom/user
> defined (whatever you call it :) .conf file.  So, my suggestion was to
> disable everything else after the first .conf is used by default.  Sorry for
> my misunderstanding.  You are doing exactly the way that I'd like it to be
> except I thought we want to process xorg.conf.d before xorg.conf.  But, your
> approach makes more sense since it follows the old HAL way.
>
> Another thing that I'd like to make sure I understand it correctly is:  we
> can define just a few sections, such as just one InputDevice section,
> without defining anything else in xorg.conf, and X server will start without
> problem.  That is, the default drivers will catch all undefined devices by
> default.
>

Hi Dan,

While sorting through my customers' requests for wacom X driver related
issues, I encountered another "unusual" situation:

How can we explicitly let X server ignore a device on a hotplugging enabled
system?  Some users want to run X server. But they don't want wacom_drv.so
to grad the device.  They want to process the data directly from the kernel
themselves.  When we discussed the "true hotplugging" X server, we kinda
assumed that at least one driver will pick up the device in X server by
default.

Do we have an existing option to disable hotplugging for a device?

Ping
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.x.org/archives/xorg-devel/attachments/20091216/76ff049c/attachment.html 


More information about the xorg-devel mailing list