On 7/10/07, Ron <[EMAIL PROTECTED]> wrote:
>
> But I guess if we can't convince the hardware crew to add a unique
> identifier of some sort to new tablets (and even if we could, that
> doesn't help anyone today), then we'll just need to make the by-path
> configuration more friendly to users somehow...
>
> We should be able to concoct a reasonable by-path rule specific
> to wacom devices that auto-configuration tools can fairly easily
> pattern match, but which will remain the same until the device
> is moved to a different port...
>
> It will probably depend on a relatively recent udev, but starting
> from the set of rules I posted earlier, try something like:
>
> ----- psuedo patch ----
> # Convenience link for the common case of a single tablet.
> KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYMLINK="input/wacom"
>
> + # You probably won't need this IMPORT rule, since an earlier file is
> + # likely to have already done it, but the rule that follows it does
> + # depend on that having happened to set ID_PATH.
> + # IMPORT{program}="path_id %p"
> +
> + # Port specific link for users of multiple tablets of the same type.
> + KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", ENV{ID_PATH}=="?*",
> SYMLINK+="input/by-path/$env{ID_PATH}-wacom"
I tested this rule. It works for kernel 2.6.21 or later. But not for
2.6.20 or earlier.
Ron, I agree to add this rule for tablets of the same type.
Thanks,
Ping
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
