Re: [PATCH evdev] Export device node as property.

2011-02-24 Thread Peter Korsgaard
> "Peter" == Peter Hutterer writes: Hi, >> For a long time we wanted to be able to match up X input devices such as >> the HID keyboards built into USB speakers or USB headsets with their >> particular sound cards, so that pressing the volume button on the device >> actually changes the

Re: [PATCH evdev] Export device node as property.

2011-02-21 Thread Peter Hutterer
On Tue, Feb 08, 2011 at 07:42:31AM +0100, Lennart Poettering wrote: > On Mon, 07.02.11 23:12, Daniel Stone (dan...@fooishbar.org) wrote: > > > Hi, > > > > On Tue, Feb 08, 2011 at 08:32:16AM +1000, Peter Hutterer wrote: > > > CC'ing Lennart, he can contribute more details I supposed. > > > > > >

Re: [PATCH evdev] Export device node as property.

2011-02-16 Thread Peter Korsgaard
> "Peter" == Peter Korsgaard 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 configura

Re: [PATCH evdev] Export device node as property.

2011-02-08 Thread Peter Korsgaard
> "Peter" == Peter Hutterer writes: Hi, >> Maybe another property is needed to satisfy that. What about "Device >> UID", which is string setup by the driver. On evdev, it uses >> EVIOCGPHYS, but it's up to the driver since it has the most details >> about the device. I still think "Devic

Re: [PATCH evdev] Export device node as property.

2011-02-08 Thread Peter Korsgaard
> "Daniel" == Daniel Stone writes: >> We expose a few features of the physical device through the X >> driver, but other information is available only through the kernel >> directly. There is no way of associating an input device with the X >> device it spawned off short of parsing the X.

Re: [PATCH evdev] Export device node as property.

2011-02-07 Thread Lennart Poettering
On Mon, 07.02.11 23:12, Daniel Stone (dan...@fooishbar.org) wrote: > Hi, > > On Tue, Feb 08, 2011 at 08:32:16AM +1000, Peter Hutterer wrote: > > CC'ing Lennart, he can contribute more details I supposed. > > > > On Mon, Feb 07, 2011 at 08:58:22AM +1000, Daniel Stone wrote: > > > On Wed, Feb 02,

Re: [PATCH evdev] Export device node as property.

2011-02-07 Thread Daniel Stone
Hi, On Tue, Feb 08, 2011 at 08:32:16AM +1000, Peter Hutterer wrote: > CC'ing Lennart, he can contribute more details I supposed. > > On Mon, Feb 07, 2011 at 08:58:22AM +1000, Daniel Stone wrote: > > On Wed, Feb 02, 2011 at 03:32:54PM +1000, Peter Hutterer wrote: > > > There is currently no mappin

Re: [PATCH evdev] Export device node as property.

2011-02-07 Thread Peter Hutterer
On Fri, Feb 04, 2011 at 02:17:18PM +0100, Peter Korsgaard wrote: > > "Peter" == Peter Hutterer writes: > > Hi, > > >> I obviously like the concept, but this assumption basically breaks > >> remote X. What I think we really need is a unique identifier for XI > >> devices (to be able to rea

Re: [PATCH evdev] Export device node as property.

2011-02-07 Thread Peter Hutterer
On Fri, Feb 04, 2011 at 06:04:29AM -0800, Dan Nicholson wrote: > On Fri, Feb 4, 2011 at 5:17 AM, Peter Korsgaard wrote: > >> "Peter" == Peter Hutterer writes: > > > > Hi, > > > >  >> I obviously like the concept, but this assumption basically breaks > >  >> remote X. What I think we really ne

Re: [PATCH evdev] Export device node as property.

2011-02-07 Thread Peter Hutterer
CC'ing Lennart, he can contribute more details I supposed. On Mon, Feb 07, 2011 at 08:58:22AM +1000, Daniel Stone wrote: > On Wed, Feb 02, 2011 at 03:32:54PM +1000, Peter Hutterer wrote: > > There is currently no mapping between XI devices and physical devices other > > than what can be extracted

Re: [PATCH evdev] Export device node as property.

2011-02-06 Thread Daniel Stone
On Wed, Feb 02, 2011 at 03:32:54PM +1000, Peter Hutterer wrote: > There is currently no mapping between XI devices and physical devices other > than what can be extracted by parsing the Xorg logfile. Add new property > "Device Node" to the driver to export the open device file. > > The client is r

Re: [PATCH evdev] Export device node as property.

2011-02-04 Thread Dan Nicholson
On Fri, Feb 4, 2011 at 6:24 AM, Peter Korsgaard wrote: >> "Dan" == Dan Nicholson writes: > > Hi, > >  >> The question is perhaps what the use case for this property is? To >  >> easily figure out what xinput id corresponds to a config entry in >  >> xorg.conf? The reason I wanted the property

Re: [PATCH evdev] Export device node as property.

2011-02-04 Thread Peter Korsgaard
> "Dan" == Dan Nicholson writes: Hi, >> The question is perhaps what the use case for this property is? To >> easily figure out what xinput id corresponds to a config entry in >> xorg.conf? The reason I wanted the property was slightly different. As >> the xinput ids are not stable, I wa

Re: [PATCH evdev] Export device node as property.

2011-02-04 Thread Dan Nicholson
On Fri, Feb 4, 2011 at 5:17 AM, Peter Korsgaard wrote: >> "Peter" == Peter Hutterer writes: > > Hi, > >  >> I obviously like the concept, but this assumption basically breaks >  >> remote X. What I think we really need is a unique identifier for XI >  >> devices (to be able to reapply propert

Re: [PATCH evdev] Export device node as property.

2011-02-04 Thread Peter Korsgaard
> "Peter" == Peter Hutterer writes: Hi, >> I obviously like the concept, but this assumption basically breaks >> remote X. What I think we really need is a unique identifier for XI >> devices (to be able to reapply properties at next login), and with >> hotplugging, the device node isn't

Re: [PATCH evdev] Export device node as property.

2011-02-03 Thread Peter Hutterer
On Wed, Feb 02, 2011 at 09:45:13AM +0100, Peter Korsgaard wrote: > > "Peter" == Peter Hutterer writes: > > Hi Peter, > > Thanks for picking this up again, I unfortunately have been busy with > other things .. > > Peter> There is currently no mapping between XI devices and physical > Peter

Re: [PATCH evdev] Export device node as property.

2011-02-02 Thread Dan Nicholson
On Wed, Feb 2, 2011 at 1:21 PM, Peter Hutterer wrote: > On Wed, Feb 02, 2011 at 06:17:22AM -0800, Dan Nicholson wrote: >> On Tue, Feb 1, 2011 at 9:32 PM, Peter Hutterer >> wrote: >> > There is currently no mapping between XI devices and physical devices other >> > than what can be extracted by p

Re: [PATCH evdev] Export device node as property.

2011-02-02 Thread Peter Hutterer
On Wed, Feb 02, 2011 at 06:17:22AM -0800, Dan Nicholson wrote: > On Tue, Feb 1, 2011 at 9:32 PM, Peter Hutterer > wrote: > > There is currently no mapping between XI devices and physical devices other > > than what can be extracted by parsing the Xorg logfile. Add new property > > "Device Node" t

Re: [PATCH evdev] Export device node as property.

2011-02-02 Thread Dan Nicholson
On Tue, Feb 1, 2011 at 9:32 PM, Peter Hutterer wrote: > There is currently no mapping between XI devices and physical devices other > than what can be extracted by parsing the Xorg logfile. Add new property > "Device Node" to the driver to export the open device file. > > The client is responsible

Re: [PATCH evdev] Export device node as property.

2011-02-02 Thread Peter Korsgaard
> "Peter" == Peter Hutterer writes: Hi Peter, Thanks for picking this up again, I unfortunately have been busy with other things .. Peter> There is currently no mapping between XI devices and physical Peter> devices other than what can be extracted by parsing the Xorg Peter> logfile. Add

[PATCH evdev] Export device node as property.

2011-02-01 Thread Peter Hutterer
There is currently no mapping between XI devices and physical devices other than what can be extracted by parsing the Xorg logfile. Add new property "Device Node" to the driver to export the open device file. The client is responsible for detecting if the device is on the same host and converting