On Thu, Jun 11, 2015 at 05:37:50PM +0800, Kai Hendry wrote:
> On Tue, 9 Jun 2015, at 01:23 PM, Peter Korsgaard wrote:
> > In the likely situation that the touchscreens are of the same type they
> > will have the same device name, so you need to fish out the
> > corresponding /dev/input/event* devic
On Tue, 9 Jun 2015, at 01:23 PM, Peter Korsgaard wrote:
> In the likely situation that the touchscreens are of the same type they
> will have the same device name, so you need to fish out the
> corresponding /dev/input/event* device node and pass it to udevadm info
> (assuming that the server is lo
> "Peter" == Peter Hutterer writes:
Hi,
>> To find the ID reliably. Is this the right way to do it? Is there
>> perhaps a better way with udev/systemd?
> what do you use for configuring and why do you need the ID specifically? if
> you use xinput to configure things, you can use the devi
> "Peter" == Peter Hutterer writes:
Hi,
>> A typical use case is to set the coordinate transformation matrix for
>> touchscreens in multihead setups.
>>
>> In the likely situation that the touchscreens are of the same type they
>> will have the same device name, so you need to fish out
On Tue, Jun 09, 2015 at 07:23:36AM +0200, Peter Korsgaard wrote:
> > "Peter" == Peter Hutterer writes:
>
> Hi,
>
> >> To find the ID reliably. Is this the right way to do it? Is there
> >> perhaps a better way with udev/systemd?
>
> > what do you use for configuring and why do you need th
On Mon, Jun 08, 2015 at 02:53:34PM +0800, Kai Hendry wrote:
> Hi there,
>
> I'm trying to reliably configure a touch input device in X. However the
> IDs can change between reboots.
>
> From doing some googling, it seems that most people script something
> like:
>
> ID=`xinput list | grep -Eo 'o
> On Mon, 8 Jun 2015, at 03:27 PM, Ingo Krabbe wrote:
>> No, I say, you can view/change USB Properties finding the a devices
>> through USB IDs and you can view/change XINPUT Properties addressing the
>> device via xinput and it's XINPUT.ID.
>
> Ok, I think I understand that.
>
> But how do I per
On Mon, 8 Jun 2015, at 03:27 PM, Ingo Krabbe wrote:
> No, I say, you can view/change USB Properties finding the a devices
> through USB IDs and you can view/change XINPUT Properties addressing the
> device via xinput and it's XINPUT.ID.
Ok, I think I understand that.
But how do I permanently set
> On Mon, 8 Jun 2015, at 03:17 PM, Ingo Krabbe wrote:
>> the IDs are a property of the XINPUT extension and the xinput(1) tool can
>> be used to modify XINPUT properties. It's the tool of choice for XINPUT
>> devices. What you might think of is a modification of the kernel (evdev)
>> devices, for e
On Mon, 8 Jun 2015, at 03:17 PM, Ingo Krabbe wrote:
> the IDs are a property of the XINPUT extension and the xinput(1) tool can
> be used to modify XINPUT properties. It's the tool of choice for XINPUT
> devices. What you might think of is a modification of the kernel (evdev)
> devices, for example
Hey Hendry,
the IDs are a property of the XINPUT extension and the xinput(1) tool can be
used to modify XINPUT properties. It's the tool of choice for XINPUT devices.
What you might think of is a modification of the kernel (evdev) devices, for
example USB, which are listed in /sys/bus/usb/devic
Hi there,
I'm trying to reliably configure a touch input device in X. However the
IDs can change between reboots.
From doing some googling, it seems that most people script something
like:
ID=`xinput list | grep -Eo 'ouchpad\s*id\=[0-9]{1,2}' | grep -Eo
'[0-9]{1,2}'`
To find the ID reliably. I
12 matches
Mail list logo
