On Sun, Jan 10, 2010 at 9:22 PM, Peter Hutterer <[email protected]> wrote: > On Sun, Jan 10, 2010 at 08:41:26PM -0800, Ping wrote: >> On Sun, Jan 10, 2010 at 8:23 PM, Ron <[email protected]> wrote: >> > The ID's are a property of the tool/device, we could ignore them, but I >> > don't actually see any other way to address a tool in the case where >> > I had 2 identical tablets plugged in, as the long device names are going >> > to be the same, no? (I don't have 2 tablets the same, so I may be wrong) >> >> They are different (I don't have two identical ones at home). But I >> know they are different since I tested before (I don't trust my memory >> so much now once you asked :). I'll be sure tomorrow. > > AFAICT, neither the driver nor the server expose any API that can be used to > identify different tablets. Since the naming is identical for hotplugged > devices, you'll get overlap for multiple devices of the same type.
Peter is right (as always :). Identical devices get the same names. The logical port, as it used to be, is not a static source to identify the identical devices either. The ID can be used by xsetwacom to distinguish one tool from the other of two identical devices. But, it is not static among reboots. So, end users (I know there are quite a few) who have two or more identical devices would have to use Ron's linuxwacom.rules and to setup their specific options for each device/tool in /etc/X11/xorg.conf to get a static performance. Not a pretty solution for hotplogging. But it is a solution. I have to test the identical device case on the newer systems (with HAL now and udev in the future) to see how it works (don't have time to run these kind of testing now). >> > But I don't think we have much risk of overlap in those 3 namespaces >> > do we? If not, it doesn't really matter what order we search them, >> > if we do, well ++eww, I agree, but I'm sure we'll figure something out .... >> >> I am with you - there is always a solution no matter which way we >> choose. We hope we could find and choose the better one instead of >> the ugly one as much as we could afford. > > we do not have to work around every possible configuration combination or > we'll be here all night. if we have a documented matching order, that will > be enough. > e.g. xsetwacom --get "stylus" ... > should first match a device named "stylus" or, if none exists, then a device > of the type stylus. If there are two devices of name "stylus", complain and > require the device id. if there are two stylus devices, complain and require > the device name or the device id. > I daresay, for the most setups where a single device is plugged in without > any funky configuration, the type match will work fine. I agree with you guys for this plan since special settings of identical devices would (probably) have to be dealt separately in xorg.conf, which would have a different dev_name for each tool anyway. Ping ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
