Hi Loic,<br><br>The move away from xorg.conf has been to a new hal integration. Please see the documentation in the wiki: <a href="https://wiki.ubuntu.com/X/Config/Input">https://wiki.ubuntu.com/X/Config/Input</a><br>Configuring an fdi for your tablet hardware should not be any more difficult than an xorg and could probably be accomplished by a script. I believe that the move to hal support for input devices will make the autoconfiguration much more robust in the long run and hopefully give xserver the ability to "just work". <br>
<br>--Dan<br><br><div class="gmail_quote">On Sun, Nov 9, 2008 at 12:09 PM, Loïc Martin <span dir="ltr"><<a href="mailto:loic.martin3@gmail.com">loic.martin3@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
Since Hardy, Ubuntu doesn't provides any configuration for Wacom tablets<br>
any more (Gutsy had the lines commented out, but they were there to be<br>
used if necessary). Part of the reason not to provide commented out<br>
lines might have been the abscence of a ServerLayout section in<br>
xorg.conf with new Xorg servers - just uncommenting some lines might<br>
lead to problems.<br>
<br>
The move away from xorg.conf makes it really hard for Wacom tablet and<br>
TabletPC users to configure their hardware. Most documentation they find<br>
isn't valid anymore (one of the problem is creating a ServerLayout with<br>
just the lines for the wacom devices, with X failing to start as a<br>
result), and even with up-to-date documentation users have to figure<br>
themselves what device they should configure, make sure they don't mix<br>
lines between serial and USB tablets (most users would imagine their<br>
TabletPC to be USB, which is most often wrong), and not forget the<br>
special line for TabletPC, which is absent from most howto. We still<br>
maintain the documentation at <a href="https://help.ubuntu.com/community/Wacom" target="_blank">https://help.ubuntu.com/community/Wacom</a>,<br>
but when (if) users find it it's often after their install is messed up.<br>
<br>
Graphic tablets are getting more common due to cheaper models, and even<br>
if you're not a graphic artist, you'll find Wacom devices in many TabletPC.<br>
<br>
With Intrepid, the stylus input is recognised by HAL when the file<br>
10-wacom.fdi is present (comes with xserver-xorg-input-wacom. However,<br>
only the stylus can be configured by this method. No eraser, no pad, no<br>
touch, no cursor.<br>
See<br>
<a href="https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2008-September/005778.html" target="_blank">https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2008-September/005778.html</a><br>
> Note that the wacom driver doesn't fully support input-hotplug, since<br>
> currently you need to initialize the driver multiple times to enable<br>
> stylus/pen/foo, and that's not possible to do with HAL. The wacom fdi file<br>
> configures the device as stylus..<br>
<br>
Traditionnal graphical configuration tools like wacomcpl ("mandatory"<br>
for LCD tablets like TabletPC and Cintiq tablets, it's included in<br>
wacom-tools since Intrepid) don't work anymore since they assume hard<br>
coded device names (stylus, eraser, cursor...) - see<br>
<a href="http://sourceforge.net/mailarchive/message.php?msg_name=9d40e4ef0811072319r51d8b4c5sc3553db2627104c6%40mail.gmail.com" target="_blank">http://sourceforge.net/mailarchive/message.php?msg_name=9d40e4ef0811072319r51d8b4c5sc3553db2627104c6%40mail.gmail.com</a><br>
<br>
********************<br>
Now to the problem at hand for Jaunty:<br>
<br>
Talking about using 3 (or more) different devices for wacom input<br>
(instead of just the stylus like in Intrepid)<br>
<a href="https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2008-September/005780.html" target="_blank">https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2008-September/005780.html</a><br>
On Tue, 30 Sep 2008, Timo Aaltonen wrote:<br>
> It has been confirmed by upstream that what you propose is not possible to<br>
> do with HAL, but instead the driver should use NewInputDeviceRequest() to<br>
> accomplish the same. Unfortunately, that'll take some time, but here's<br>
> hoping that the next six months are enough to have that in time for<br>
> Jaunty. Someone needs to kick^H^H^H^Hask upstream :)<br>
<br>
Where upstream means linuxwacom, see<br>
<a href="https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2008-October/005837.html" target="_blank">https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2008-October/005837.html</a><br>
> I was referring to linuxwacom upstream, which should be aware of the problems<br>
> with input-hotplug, but has not done anything about it AFAIK.<br>
<br>
I contacted upstream, and their answer can be found at:<br>
<a href="http://sourceforge.net/mailarchive/message.php?msg_name=167e8a330811070926n3024605m7bd7baa6e24bfedf%40mail.gmail.com" target="_blank">http://sourceforge.net/mailarchive/message.php?msg_name=167e8a330811070926n3024605m7bd7baa6e24bfedf%40mail.gmail.com</a><br>
Here is an extract:<br>
> Hotplugg is a server-wide issue. It will be resolved for all input devices<br>
> in Xorg, not just for Wacom devices.<br>
><br>
><br>
>> - does wacomcpl support the fdi method? It doesn't recognise anything on my<br>
>> setup, but it could also be a bug in the Ubuntu version.<br>
><br>
><br>
> fdi isn't part of linuxwacom project. It belows to Xorg. The distributor, I<br>
> think, will include it once it is ready.<br>
><br>
> Ping<br>
<br>
So what is Xorg going to do about wacom devices support, and how can we<br>
make sure that, after one year, this support (or a distribution<br>
solution) will at least make it into Jaunty?<br>
Loïc<br>
<font color="#888888"><br>
--<br>
Ubuntu-devel-discuss mailing list<br>
<a href="mailto:Ubuntu-devel-discuss@lists.ubuntu.com">Ubuntu-devel-discuss@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss</a><br>
</font></blockquote></div><br>