Re: cosmetic udev glitches

2010-03-03 Thread Thomas Jaeger
On 03/03/2010 08:25 PM, Dan Nicholson wrote: > On Wed, Mar 3, 2010 at 4:59 PM, Thomas Jaeger wrote: >> On 03/03/2010 07:48 PM, Dan Nicholson wrote: >>> On Wed, Mar 3, 2010 at 4:00 PM, Thomas Jaeger wrote: The attribute 'name' might not exist (as in the case of serial wacom devices) and

Re: cosmetic udev glitches

2010-03-03 Thread Dan Nicholson
On Wed, Mar 3, 2010 at 4:59 PM, Thomas Jaeger wrote: > On 03/03/2010 07:48 PM, Dan Nicholson wrote: >> On Wed, Mar 3, 2010 at 4:00 PM, Thomas Jaeger wrote: >>> The attribute 'name' might not exist (as in the case of serial wacom >>> devices) and it's impossible to set it in an udev rule, I believ

Re: cosmetic udev glitches

2010-03-03 Thread Thomas Jaeger
On 03/03/2010 07:48 PM, Dan Nicholson wrote: > On Wed, Mar 3, 2010 at 4:00 PM, Thomas Jaeger wrote: >> The attribute 'name' might not exist (as in the case of serial wacom >> devices) and it's impossible to set it in an udev rule, I believe, so we >> should at least fall back to the NAME property

Re: cosmetic udev glitches

2010-03-03 Thread Dan Nicholson
On Wed, Mar 3, 2010 at 4:00 PM, Thomas Jaeger wrote: > The attribute 'name' might not exist (as in the case of serial wacom > devices) and it's impossible to set it in an udev rule, I believe, so we > should at least fall back to the NAME property if the attribute is not > available. Not for the

Re: cosmetic udev glitches

2010-03-03 Thread Thomas Jaeger
The attribute 'name' might not exist (as in the case of serial wacom devices) and it's impossible to set it in an udev rule, I believe, so we should at least fall back to the NAME property if the attribute is not available. Tom On 03/02/2010 05:47 PM, Dan Nicholson wrote: > On Tue, Mar 02, 2010 a

Re: cosmetic udev glitches

2010-03-03 Thread Julien Cristau
On Tue, Mar 2, 2010 at 14:47:22 -0800, Dan Nicholson wrote: > From: Dan Nicholson > Date: Tue, 2 Mar 2010 14:42:22 -0800 > Subject: [PATCH] config/udev: Get product name from attribute instead of > uevent > > The input device product name in the kernel uevent has embedded quotes > that aren't

Re: cosmetic udev glitches

2010-03-03 Thread Simon Thum
Julien Cristau wrote: > This is also expected at the moment. The enumeration of devices gives > us /dev/input/event* (which evdev can handle), and > /dev/input/{mouse,kbd}* (which it doesn't). This results in a couple > error messages for the latter. It should be possible to tone those down > so

Re: cosmetic udev glitches

2010-03-02 Thread Dan Nicholson
On Wed, Mar 03, 2010 at 10:40:16AM +1000, Peter Hutterer wrote: > On Tue, Mar 02, 2010 at 04:29:41PM -0800, Dan Nicholson wrote: > > On Tue, Mar 2, 2010 at 4:16 PM, Peter Hutterer > > wrote: > > > On Tue, Mar 02, 2010 at 02:47:22PM -0800, Dan Nicholson wrote: > > >> Can you try the patch below th

Re: cosmetic udev glitches

2010-03-02 Thread Peter Hutterer
On Tue, Mar 02, 2010 at 04:29:41PM -0800, Dan Nicholson wrote: > On Tue, Mar 2, 2010 at 4:16 PM, Peter Hutterer > wrote: > > On Tue, Mar 02, 2010 at 02:47:22PM -0800, Dan Nicholson wrote: > >> Can you try the patch below that uses the name attribute instead of the > >> value from the uevent? I ra

Re: cosmetic udev glitches

2010-03-02 Thread Dan Nicholson
On Tue, Mar 2, 2010 at 4:16 PM, Peter Hutterer wrote: > On Tue, Mar 02, 2010 at 02:47:22PM -0800, Dan Nicholson wrote: >> Can you try the patch below that uses the name attribute instead of the >> value from the uevent? I ran it through a little test app, but not in X. >> >> From c01a4e6dce7196a60

Re: cosmetic udev glitches

2010-03-02 Thread Peter Hutterer
On Tue, Mar 02, 2010 at 02:47:22PM -0800, Dan Nicholson wrote: > Can you try the patch below that uses the name attribute instead of the > value from the uevent? I ran it through a little test app, but not in X. > > From c01a4e6dce7196a60b5247dde78054b27e004494 Mon Sep 17 00:00:00 2001 > From: Dan

Re: cosmetic udev glitches

2010-03-02 Thread Dan Nicholson
On Tue, Mar 02, 2010 at 05:57:04PM +0100, Simon Thum wrote: > Hi all, > > I just upgraded my X to use udev. It generally went fine, but I noticed > two minor issues: > > At first, the device names have quotation marks. As in > > xinput list > ... > ⎜ "ImExPS/2 Logitech Wheel Mouse"

Re: cosmetic udev glitches

2010-03-02 Thread Peter Hutterer
On Tue, Mar 02, 2010 at 01:01:53PM -0800, Dan Nicholson wrote: > On Tue, Mar 2, 2010 at 9:28 AM, Julien Cristau wrote: > > On Tue, Mar  2, 2010 at 17:57:04 +0100, Simon Thum wrote: > > > >> Hi all, > >> > >> I just upgraded my X to use udev. It generally went fine, but  I noticed > >> two minor is

Re: cosmetic udev glitches

2010-03-02 Thread Dan Nicholson
On Tue, Mar 2, 2010 at 9:28 AM, Julien Cristau wrote: > On Tue, Mar  2, 2010 at 17:57:04 +0100, Simon Thum wrote: > >> Hi all, >> >> I just upgraded my X to use udev. It generally went fine, but  I noticed >> two minor issues: >> >> At first, the device names have quotation marks. As in >> >> xinp

Re: cosmetic udev glitches

2010-03-02 Thread Julien Cristau
On Tue, Mar 2, 2010 at 17:57:04 +0100, Simon Thum wrote: > Hi all, > > I just upgraded my X to use udev. It generally went fine, but I noticed > two minor issues: > > At first, the device names have quotation marks. As in > > xinput list > ... > ⎜ "ImExPS/2 Logitech Wheel Mouse"

cosmetic udev glitches

2010-03-02 Thread Simon Thum
Hi all, I just upgraded my X to use udev. It generally went fine, but I noticed two minor issues: At first, the device names have quotation marks. As in xinput list ... ⎜ "ImExPS/2 Logitech Wheel Mouse" id=7[slave pointer (2)] I looked up the source, but found nothing obvio