[PATCH evdev] Export device node as property.

[Peter Korsgaard]

>>>>> "Peter" == Peter Korsgaard <jacmet at sunsite.dk> writes:

Hi,

 Peter>> Ok, I missed that we're trying to solve two different use-cases.
 Peter>> Punting a unique device ID into the properties is be quite
 Peter>> useful, I've been struggling for a while with figuring out how
 Peter>> to make per-device configuration work in a sane manner.

 Peter>> However, is the phys path enough here? Users think in physical
 Peter>> devices and we should (if we can) allow for the same device
 Peter>> being plugged into a different port.

 Peter> Well, it's atleast part of the identification. Again, we
 Peter> basically have 2 use cases:

 Peter> 1: User plugs in USB device to a different port and wants SAME
 Peter> settings applied between sessions

 Peter> 2: User has several of same devices (E.G. my use case is
 Peter> multihead with same type of touchscreens) and want DIFFERENT
 Peter> settings for each (but persistent over sessions).

 Peter> For 1, our best bet is probably using the device name as
 Peter> provided by xinput already, but for 2 we need to look at the
 Peter> phys path (E.G. USB port for usb devices) to be able to handle
 Peter> the common case of USB devices without a unique serial number
 Peter> (so EVIOCGUNIQ doesn't give anything).

 Peter> The question is if we can come up with a sensible logic for
 Peter> choosing between name/phys/uniq?

Any comments on this? Peter?

-- 
Bye, Peter Korsgaard