Re: [Linuxwacom-devel] painless multiple tablets, end of hid_blacklist'ing ... film at 11

[Andrew Z. <za...@ho...>]

On Mon, 17 Apr 2006 22:54:45 +0930
Ron <ro...@de...> wrote:

> It will also create a /dev/input/<TabletType> node, pointing to the
> last attached device of that type (in my case graphire3).  For users
> with multiple devices of different types, you may use the name of each
> tablet without ever needing to worry about where or what order you
> connect them in.
As long as we're at it... maybe it would make sense to create the links
named input/tablet/graphire3 and so on, instead of input/graphire3? The
reason is that if somebody wants to see all the tablets, it just gets
the content of the /dev/input/tablet/ directory. A similar thing
could be done for mouses, e.g. /dev/input/mouse/mx1000 and such.

Now about BlueTooth tablets. Alas, they don't provide idVendor/
idProduct, so they can be identified only by SYSFS{name}. I would
propose to change the line 

... SYSFS{idVendor}=="056a", SYMLINK="input/tablet/wacom"

to:

... SUBSYSTEM="input", SYSFS{name}=="Wacom*", SYMLINK="input/ tablet/
wacom"

(I presume USB devices also set the "name" field); and same for the
check_driver line. Here's what udevinfo says about my tablet:

  looking at device '/class/input/input4/event3':
    KERNEL=="event3"
    SUBSYSTEM=="input"
    SYSFS{dev}=="13:67"

  looking at device '/class/input/input4':
    ID=="input4"
    BUS=="input"
    DRIVER==""
    SYSFS{uniq}==""
    SYSFS{phys}==""
    SYSFS{name}=="Wacom Graphire 6x8 BlueTooth"

> For the case where a user has multiple tablets of the same type,
> things get just a little harder.  There does not seem to be any
> serial number or similar which we could use to discriminate between
> them (if there is, making it available may prove useful) -- but this
Well, if someone has more than one tablet, he can just point to the
eventX node directly.

-- 
Greetings,
   Andrew