Peter == Peter Hutterer peter.hutte...@who-t.net 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
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.
On Mon, Feb 07,
Peter == Peter Korsgaard jac...@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
Daniel == Daniel Stone dan...@fooishbar.org 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
Peter == Peter Hutterer peter.hutte...@who-t.net 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
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 by
On Fri, Feb 04, 2011 at 06:04:29AM -0800, Dan Nicholson wrote:
On Fri, Feb 4, 2011 at 5:17 AM, Peter Korsgaard jac...@sunsite.dk wrote:
Peter == Peter Hutterer peter.hutte...@who-t.net writes:
Hi,
I obviously like the concept, but this assumption basically breaks
remote X. What I
On Fri, Feb 04, 2011 at 02:17:18PM +0100, Peter Korsgaard wrote:
Peter == Peter Hutterer peter.hutte...@who-t.net 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
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 mapping
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, 2011 at
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
Peter == Peter Hutterer peter.hutte...@who-t.net 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
On Fri, Feb 4, 2011 at 5:17 AM, Peter Korsgaard jac...@sunsite.dk wrote:
Peter == Peter Hutterer peter.hutte...@who-t.net 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
Dan == Dan Nicholson dbn.li...@gmail.com 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,
On Fri, Feb 4, 2011 at 6:24 AM, Peter Korsgaard jac...@sunsite.dk wrote:
Dan == Dan Nicholson dbn.li...@gmail.com 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
On Wed, Feb 02, 2011 at 09:45:13AM +0100, Peter Korsgaard wrote:
Peter == Peter Hutterer peter.hutte...@who-t.net 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 == Peter Hutterer peter.hutte...@who-t.net 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
On Tue, Feb 1, 2011 at 9:32 PM, Peter Hutterer peter.hutte...@who-t.net 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
On Wed, Feb 02, 2011 at 06:17:22AM -0800, Dan Nicholson wrote:
On Tue, Feb 1, 2011 at 9:32 PM, Peter Hutterer peter.hutte...@who-t.net
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
On Wed, Feb 2, 2011 at 1:21 PM, Peter Hutterer peter.hutte...@who-t.net 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 peter.hutte...@who-t.net
wrote:
There is currently no mapping between XI devices and physical devices
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
21 matches
Mail list logo
