10.04 - HAL -> udev Wacom config

[psyced]

I had a HAL policy for Karmic to change the capture size for my Intuos 2 and, as you might know, HAL was dropped in Lucid..

udev's "rules" are quite different than HAL's policies.. I'm sort of stuck here.

I've Googled and found this, but it is written differently than my HAL policy (see below) - that and my policy has overrides written for each stylus (eraser, stylus, etc.).. I'm not sure how that could be structured within a rule.

Has anyone converted a HAL policy to a udev rule yet (I'll probably just need an example)?

Here's my HAL policy:

<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- -->

<deviceinfo version="0.2">

  <device>
    <match key="input.x11_driver" contains="wacom">
      <match key="input.x11_options.Type" contains="stylus">
        <merge key="input.x11_options.TopX" type="string">7500</merge>
        <merge key="input.x11_options.BottomX" type="string">23000</merge>
        <merge key="input.x11_options.TopY" type="string">4500</merge>
        <merge key="input.x11_options.BottomY" type="string">18200</merge>
      </match>
    </match>
    <match key="input.x11_driver" contains="wacom">
      <match key="input.x11_options.Type" contains="pad">
        <merge key="input.x11_options.TopX" type="string">7500</merge>
        <merge key="input.x11_options.BottomX" type="string">23000</merge>
        <merge key="input.x11_options.TopY" type="string">4500</merge>
        <merge key="input.x11_options.BottomY" type="string">18200</merge>
      </match>
    </match>
    <match key="input.x11_driver" contains="wacom">
      <match key="input.x11_options.Type" contains="eraser">
        <merge key="input.x11_options.TopX" type="string">7500</merge>
        <merge key="input.x11_options.BottomX" type="string">23000</merge>
        <merge key="input.x11_options.TopY" type="string">4500</merge>
        <merge key="input.x11_options.BottomY" type="string">18200</merge>
      </match>
    </match>
    <match key="input.x11_driver" contains="wacom">
      <match key="input.x11_options.Type" contains="cursor">
        <merge key="input.x11_options.TopX" type="string">7500</merge>
        <merge key="input.x11_options.BottomX" type="string">23000</merge>
        <merge key="input.x11_options.TopY" type="string">4500</merge>
        <merge key="input.x11_options.BottomY" type="string">18200</merge>
      </match>
    </match>
  </device>

</deviceinfo>

[Favux]

Hi psyced,

You can use either xorg.conf or 10-wacom.conf in xorg.conf.d which is the preferred method now. In 10-wacom.conf you'd add the options at the bottom of the wacom usb snippet/section. As near as I can tell the syntax for options are the same. See Section 2 c) in the linuxwacom HOW TO.

[psyced]

Favux: I'm not sure how I'm supposed to add my positioning options to 10-wacom.conf.
The three inputclasses in section 2 of your post were already on my config.
Do I just put the options in one of them? So far this has not worked.

[Favux]

Hi psyced,

The syntax for options seems to be the same as in xorg.conf so I would think it should look something like:

Section "InputClass"
	Identifier "Wacom class"
# WALTOP needs a patched kernel driver, that isn't in mainline lk yet,
# so for now just let it fall through and be picked up by evdev instead.
#	MatchProduct "Wacom|WALTOP|WACOM"
	MatchProduct "Wacom|WACOM"
	MatchDevicePath "/dev/input/event*"
	Driver "wacom"
	Option		"TopX"		"7500"
	Option		"TopY"		"4500"
	Option		"BottomX"	"23000"
	Option		"BottomY"	"18200"
EndSection

With the changes just in the usb snippet.

[psyced]

The syntax for options seems to be the same as in xorg.conf so I would think it should look something like:

As I have already said, I've tried that.

[Favux]

Hmmm. I wonder if xf86-input-wacom is automatically setting the coordinates and now over-rides user settings? I know I've seen some discussions about no longer allowing some user settings in linuxwacom-dev. You may want to post in linuxwacom-discuss and ask how to do it. The other option would to be set up your wacom sections in xorg.conf and see if the coordinate options work in xorg.conf.

[psyced]

Huh, that worked. I was a bit against that situation at first because it never worked in Karmic and because fglrx was overwriting the config at times (but it seems it's less so in Lucid).

Thanks.

[Favux]

You are welcome.

That's interesting because it implies some options aren't valid in xorg.conf.d. I have no idea which ones, haven't seen a list or anything.

So in "our" list so far we have:

button options valid in xorg.conf and xorg.conf.d

coordinate options only valid in xorg.conf not xorg.conf.d