<div>Thank you, Matthew, for picking up this topic for Wacom. Please see my comments in line.</div>
<div> </div>
<div>Ping <br></div>
<div class="gmail_quote">On Tue, Oct 6, 2009 at 11:25 AM, Matthew Garrett <span dir="ltr"><<a href="mailto:mjg59@srcf.ucam.org">mjg59@srcf.ucam.org</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">I think that this will currently break wacom. Wacom is set up to provide<br>one input device per input mechanism - so typically we may have pen,<br>
stylus and eraser. The driver insists on each of these being declared as<br>separate instances, so in hal we have a callout for wacoms that<br>generates extra devices in the hal namespace. Each of these devices then<br>corresponds to one of the input mechanisms. For this to work in a udev<br>
world, we either need to have a mechanism for a single udev event to<br>generate (or remove) multiple input devices </blockquote>
<div> </div>
<div>If we go with this approach, I'd expect that requires more work on server side. But xf86-input-wacom could stay unchanged. </div>
<div> </div>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">or alternatively to fix up<br>wacom so it can be told to create multiple X input devices in a single<br>instance.</blockquote>
<div> </div>
<div>Does xserver have mechanism to create multiple X input devices in a single instance now? If not, this approach would need both server and driver work. With the driver's current status (I mean out of sync with xserver), adding more work now would not make too big a difference. We could design this support into the current rework. </div>
<div> </div>
<div>So, I don't have a preference for which way to go. I hope we choose an approach that would have a longer lifespan.</div></div>