<div class="gmail_quote">On Mon, Dec 14, 2009 at 2:59 PM, Ping <span dir="ltr"><<a href="mailto:pinglinux@gmail.com">pinglinux@gmail.com</a>></span> wrote:<br> <blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote"> <div class="im">On Mon, Dec 14, 2009 at 7:36 AM, Dan Nicholson <span dir="ltr"><<a href="mailto:dbn.lists@gmail.com" target="_blank">dbn.lists@gmail.com</a>></span> wrote:<br></div> <div class="gmail_quote"> <div class="im"> <blockquote style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote"> <div> <div></div> <div>I think it will work the way you envision, but with the caveat that<br></div></div>there isn't any parsing of ~/.xorg.conf and never has been. After<br>that, it would work similarly to how you describe. xorg.conf is parsed<br> first and then the xorg.conf.d files are parsed afterwards, but their<br>contents are all mashed into one configuration structure. There is no<br>on-the-fly parsing of config files, but there doesn't need to be.<br>Earlier matches take precedence, so if the input device is fully<br> specified in xorg.conf, nothing happening in xorg.conf.d would have<br>any effect.<br></blockquote></div> <div><br>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. <br> <br>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.</div> </div></blockquote> <div> </div> <div>Hi Dan,</div> <div> </div> <div>While sorting through my customers' requests for wacom X driver related issues, I encountered another "unusual" situation:</div> <div> </div> <div>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. </div> <div> </div> <div>Do we have an existing option to disable hotplugging for a device?</div> <div> </div> <div>Ping</div> <div> </div></div>