On Thu, Apr 09, 2020 at 02:28:13PM +0300, Pekka Paalanen wrote:
> On Thu, 9 Apr 2020 13:01:56 +0200
> Michał Zegan wrote:
>
> > W dniu 09.04.2020 o 10:23, Pekka Paalanen pisze:
> > > On Thu, 9 Apr 2020 09:46:08 +0200
> > > Lennart Poettering wrote:
> > >
> > >> On Fr, 03.04.20 10:28, Pekka
On Tue, Feb 06, 2018 at 09:14:46AM +0200, Mantas Mikulėnas wrote:
> On Tue, Feb 6, 2018 at 1:21 AM, Peter Hutterer <peter.hutte...@who-t.net>
> wrote:
>
> > On Mon, Feb 05, 2018 at 11:51:30AM +0200, Mantas Mikulėnas wrote:
> > > On Mon, Feb 5, 2018 at 8:02 AM, Pete
On Mon, Feb 05, 2018 at 11:51:30AM +0200, Mantas Mikulėnas wrote:
> On Mon, Feb 5, 2018 at 8:02 AM, Peter Hutterer <peter.hutte...@who-t.net>
> wrote:
>
> > Hi all,
> >
> > I think there is some race conditions between the udev rules and the hwdb
> > and I
Hi all,
I think there is some race conditions between the udev rules and the hwdb
and I cannot rely that udev rules are applied consistently on a device.
For reference, after building libinput run
sudo ./build/libinput-test-suite-runner
--filter-test=lid_update_hw_on_key_multiple_keyboards
On Thu, Jun 15, 2017 at 07:33:58AM +, Zheng, Lv wrote:
> Hi, Peter
>
> > From: Peter Hutterer [mailto:peter.hutte...@who-t.net]
> > Subject: Re: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable LID
> > switch exported by ACPI
> >
> > On Thu, Jun 15,
On Thu, Jun 15, 2017 at 02:52:57AM +, Zheng, Lv wrote:
> Hi, Benjamin
>
> > From: Benjamin Tissoires [mailto:benjamin.tissoi...@redhat.com]
> > Subject: Re: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable LID
> > switch exported by ACPI
> >
> > Hi,
> >
> > [Sorry for the delay, I
On Tue, Jun 06, 2017 at 12:22:09PM +0200, Benjamin Tissoires wrote:
[...]
> > This is because the aml table puts many Notify(LID, 0x80) in various
> > control methods.
> > And not one of them but multiple of them will be invoked by various OS
> > drivers during suspend/resume period.
> > I think
The hwdb behaviour is a bit hard to predict when multiple matches with globs
apply to a device so I'm wondering whether this is just an implementation
result or intended behaviour.
Example 1:
$> cat 99-test.hwdb
test:*
match=generic
test:specific*
match=specific
$> systemd-hwdb query
On Fri, May 29, 2015 at 02:54:54PM +0200, Andreas Pokorny wrote:
Require touch screens to have a ABS_MT_SLOT axis while exclude devices
that overlap with the MT range of axes.
---
src/udev/udev-builtin-input_id.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
On Fri, May 29, 2015 at 12:32:44PM +0200, Andreas Pokorny wrote:
Hi,
On Fri, May 29, 2015 at 2:07 AM, Peter Hutterer peter.hutte...@who-t.net
wrote:
On Thu, May 28, 2015 at 02:47:35PM +0200, Andreas Pokorny wrote:
There are touch screens that do not provide 'BTN_TOUCH' and hence
On Thu, May 28, 2015 at 02:47:35PM +0200, Andreas Pokorny wrote:
There are touch screens that do not provide 'BTN_TOUCH' and hence no
'EV_KEY'. Previously those would not get any properties assigned and
note: I consider this a kernel bug. From the kernel's documentation:
* BTN_TOUCH:
On Mon, Apr 20, 2015 at 10:24:35AM +0200, David Herrmann wrote:
Hi
On Fri, Apr 17, 2015 at 4:48 PM, Hans de Goede hdego...@redhat.com wrote:
Hi All,
Here is v4 of my pointstick set.
Changes since v3:
-Use the existing evdev matching rules
-Make setting the sensitivity part of the
On Mon, Apr 20, 2015 at 06:01:53PM -0400, Benjamin Tissoires wrote:
The atmel driver sets a default resolution of 20 for each touchpads it
creates. On this model, 10 is more appropriate.
The resolution is not set for the touchscreen by the kernel, so match
the name to both touchpad and
On Mon, Apr 13, 2015 at 03:08:53PM +0200, Hans de Goede wrote:
Hi,
On 13-04-15 14:41, Zbigniew Jędrzejewski-Szmek wrote:
On Mon, Apr 13, 2015 at 11:15:00AM +0200, Hans de Goede wrote:
Make test_pointer / test_keys return a boolean indicating whether or not
they've set any properties on the
On Tue, Apr 07, 2015 at 12:08:00PM +0200, David Herrmann wrote:
Hi
On Mon, Mar 23, 2015 at 2:30 AM, Peter Hutterer
peter.hutte...@who-t.net wrote:
Verified for the 5,1 Macbook, the others are guesses based on the list of
supported devices of the moshi trackpad protector.
http
On Sat, Apr 11, 2015 at 03:27:46PM +0200, Hans de Goede wrote:
The Trust TB7300 (relabelled Waltop?) tablet has a scrollwheel which shows
up as a /dev/input/event# node all by itself. Currently input_id does not
set any ID_INPUT_FOO attr on this causing it it to not be recognized by
Xorg /
On Wed, Apr 08, 2015 at 07:41:06PM +0200, Lennart Poettering wrote:
On Mon, 23.03.15 11:30, Peter Hutterer (peter.hutte...@who-t.net) wrote:
No point parsing the properties if we can't get the devnode to apply them
later. Plus, this makes future additions easier to slot in.
Hmm, Peter
On Tue, Apr 07, 2015 at 11:37:09AM +0200, Hans de Goede wrote:
Hi,
On 07-04-15 07:07, Peter Hutterer wrote:
On Fri, Apr 03, 2015 at 04:11:59PM +0200, Hans de Goede wrote:
Lenovo has changed the sensitity of the trackpoint on the x240 / T440s /
T540
s/sensitity/sensitivity/
generation
On Tue, Apr 07, 2015 at 02:06:33PM +0200, David Herrmann wrote:
Hi
On Tue, Apr 7, 2015 at 1:52 PM, Hans de Goede hdego...@redhat.com wrote:
Hi,
On 07-04-15 13:46, David Herrmann wrote:
Hi
On Tue, Apr 7, 2015 at 1:40 PM, Hans de Goede hdego...@redhat.com wrote:
The series
On Fri, Mar 27, 2015 at 12:54:50PM +0100, Martin Pitt wrote:
Hey Peter,
thanks for these! Patches 1 to 4 look good to me, but I have some
questions/comments on this one.
Peter Hutterer [2015-03-23 11:30 +1000]:
--- /dev/null
+++ b/rules/60-evdev.rules
@@ -0,0 +1,14 @@
+# do
Separate patch for ease of review, will be merged into
udev: builtin-keyboard: add support for EV_ABS_OVERRIDE
Replace the hwdb keyboard: prefix with evdev: and drop the separate
60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes
anyway, we don't need a separate rules
On Sat, Apr 04, 2015 at 02:07:27PM +0200, David Herrmann wrote:
Hi
On Fri, Apr 3, 2015 at 8:55 PM, Hans de Goede hdego...@redhat.com wrote:
[...]
I don't think we should return when we see INPUT_PROP_ACCEL. If a
keyboard embeds an accelerometer, we will miss it. I think I went too
deep
On Fri, Apr 03, 2015 at 04:12:00PM +0200, Hans de Goede wrote:
The pointingstick of the Dell Latitude E6400 is somewhat slow by default,
where as the pointingstick of the Dell Latitude D620 is much too fast by
s/where as/whereas/
ACK otherwise.
Cheers,
Peter
default, set
On Fri, Apr 03, 2015 at 04:11:59PM +0200, Hans de Goede wrote:
Lenovo has changed the sensitity of the trackpoint on the x240 / T440s / T540
s/sensitity/sensitivity/
generation of Thinkpads, making them somewhat unsensitive by default, add a
I think it's insensitive, not unsensitive.
hwdb
On Fri, Apr 03, 2015 at 04:11:57PM +0200, Hans de Goede wrote:
There is quite a wide spread in the delta events generated by pointingsticks,
some generate deltas of 1-2 under normal use, while others generate deltas
from 1-20.
This commit adds a set of rules + a hwdb file which allows
On Fri, Apr 03, 2015 at 04:11:58PM +0200, Hans de Goede wrote:
The IBM / Lenovo trackpoints are special, they allow specifying a sensitivity
s/are special, they//
setting through a ps/2 command, which changes the range of the deltas send
when
s/send/sent/
using the trackpoint. One some
On Mon, Mar 23, 2015 at 09:15:02AM +0300, Reverend Homer wrote:
[...]
+static void override_abs(int fd, const char *devnode,
+ unsigned evcode, const char *value) {
+struct input_absinfo absinfo;
+int rc;
+char *next;
+
+rc = ioctl(fd,
No changes in the mapping, but previously we opened the device only on
successful parsing. Now we open the mapping as soon as we have a value that
looks interesting. Since errors are supposed to be the exception, not the
rule, this is probably fine.
---
src/udev/udev-builtin-keyboard.c | 59
No point parsing the properties if we can't get the devnode to apply them
later. Plus, this makes future additions easier to slot in.
---
src/udev/udev-builtin-keyboard.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/src/udev/udev-builtin-keyboard.c
Parse properties in the form
EV_ABS_OVERRIDE_00=min:max:res:fuzz:flat
and apply them to the kernel device. Future processes that open that device
will see the updated EV_ABS range.
This is particularly useful for touchpads that don't provide a resolution in
the kernel driver but can be fixed up
Rather than building a map and looping through the map, immediately call the
ioctl when we have a successfully parsed property.
This has a side-effect: before the maximum number of ioctls was limited to the
size of the map (1024), now it is unlimited.
---
src/udev/udev-builtin-keyboard.c | 46
No functional changes, just to make the next patch easier to review
---
src/udev/udev-builtin-keyboard.c | 62
1 file changed, 31 insertions(+), 31 deletions(-)
diff --git a/src/udev/udev-builtin-keyboard.c b/src/udev/udev-builtin-keyboard.c
index
size. This is probably slightly off, but still better
than no resolution at all.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
hwdb/60-evdev.hwdb | 40
1 file changed, 40 insertions(+)
diff --git a/hwdb/60-evdev.hwdb b/hwdb/60-evdev.hwdb
index
On Thu, Mar 19, 2015 at 01:54:46PM +0100, David Herrmann wrote:
Hi
On Thu, Mar 19, 2015 at 10:52 AM, Peter Hutterer
peter.hutte...@who-t.net wrote:
This builtin parses properties in the form
EV_ABS_OVERRIDE_00=min:max:res:fuzz:flat
The concept sounds good. hwdb is definitely the place
This builtin parses properties in the form
EV_ABS_OVERRIDE_00=min:max:res:fuzz:flat
and applies them to the kernel device. Future processes that open that device
will see the updated EV_ABS range.
This is particularly useful for touchpads that don't provide a resolution in
the kernel driver but
On Wed, Feb 11, 2015 at 02:18:12PM +, Colin Guthrie wrote:
CC'ing Peter Hutterer as the xorg input guy for his thoughts :)
Lennart Poettering wrote on 11/02/15 11:46:
On Wed, 11.02.15 10:43, Colin Guthrie (gm...@colin.guthr.ie) wrote:
Hi,
I've recently run into an annoying
On Mon, Feb 02, 2015 at 12:57:24PM +0100, Lennart Poettering wrote:
On Fri, 30.01.15 08:12, Peter Hutterer (peter.hutte...@who-t.net) wrote:
Hi,
I need some sort of way of assigning udev properties on the fly to a device,
but I'm short of ideas how to do this sensibly
On Fri, Jan 30, 2015 at 09:22:51AM +0100, Martin Pitt wrote:
Tomasz Torcz [2015-01-29 23:42 +0100]:
Have you seen umockdev? https://github.com/martinpitt/umockdev/
Right, with that you can run your tests as normal user, completely
isolated from the actual system, and you can set up/change
Hi,
I need some sort of way of assigning udev properties on the fly to a device,
but I'm short of ideas how to do this sensibly.
A bit more context:
The libinput test suite works by setting up uinput devices for each test
case, then hooking libinput contexts up to those devices. libinput itself
Currently used to tag devices in the new Lenovo *50 series and the X1 Carbon
3rd. These laptops re-introduced the physical trackpoint buttons that were
missing from the *40 series but those buttons are now wired up to the
touchpad.
The touchpad now sends BTN_0, BTN_1 and BTN_2 for the trackpoint.
On Thu, Jan 29, 2015 at 03:04:29AM +0100, Lennart Poettering wrote:
On Thu, 29.01.15 11:58, Peter Hutterer (peter.hutte...@who-t.net) wrote:
Currently used to tag devices in the new Lenovo *50 series and the X1 Carbon
3rd. These laptops re-introduced the physical trackpoint buttons
On Wed, Jan 14, 2015 at 01:07:40PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jan 14, 2015 at 03:57:03PM +1000, Peter Hutterer wrote:
On Mon, Jan 12, 2015 at 09:48:55AM +1000, Peter Hutterer wrote:
Most mice have a wheel click angle of 15 degrees, i.e. 24 clicks per full
wheel
On Wed, Jan 14, 2015 at 10:50:12PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Jan 15, 2015 at 07:21:31AM +1000, Peter Hutterer wrote:
On Wed, Jan 14, 2015 at 01:07:40PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jan 14, 2015 at 03:57:03PM +1000, Peter Hutterer wrote:
On Mon
On Mon, Jan 12, 2015 at 09:48:55AM +1000, Peter Hutterer wrote:
Most mice have a wheel click angle of 15 degrees, i.e. 24 clicks per full
wheel rotation. Some mice, like the Logitech M325 have a larger angle. To
allow userspace to make use of that knowledge, add a property to the hwdb
Most mice have a wheel click angle of 15 degrees, i.e. 24 clicks per full
wheel rotation. Some mice, like the Logitech M325 have a larger angle. To
allow userspace to make use of that knowledge, add a property to the hwdb.
---
libinput patches to read this are here:
On Tue, Dec 23, 2014 at 02:16:15PM +0100, David Herrmann wrote:
(CC'ing sd-devel this time.. sorry)
On Tue, Dec 23, 2014 at 1:19 AM, Peter Hutterer
peter.hutte...@who-t.net wrote:
https://bugs.freedesktop.org/show_bug.cgi?id=87037
---
some feedback on the rule would be appreciated
https://bugs.freedesktop.org/show_bug.cgi?id=87037
---
some feedback on the rule would be appreciated, in case there's a better
approach to matching.
hwdb/70-mouse.hwdb | 4
rules/70-mouse.rules | 3 +++
2 files changed, 7 insertions(+)
diff --git a/hwdb/70-mouse.hwdb
On Thu, Nov 27, 2014 at 12:39:08PM +0100, David Herrmann wrote:
Hi
On Thu, Nov 27, 2014 at 7:06 AM, Peter Hutterer
peter.hutte...@who-t.net wrote:
On Wed, Nov 26, 2014 at 01:10:10AM +0100, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Nov 26, 2014 at 01:01:30AM +0100, Zbigniew Jędrzejewski
---
hwdb/60-keyboard.hwdb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hwdb/60-keyboard.hwdb b/hwdb/60-keyboard.hwdb
index 533ad5b..46348b9 100644
--- a/hwdb/60-keyboard.hwdb
+++ b/hwdb/60-keyboard.hwdb
@@ -42,7 +42,7 @@
# an input device use the commonly available tool:
Pointer acceleration for relative input devices (mice, trackballs, etc.)
applies to the deltas of the device. Alas, those deltas have no physical
reference point - a delta of 10 may be caused by a large movement of a low-dpi
mouse or by a minute movement of a high-dpi mouse.
Which makes pointer
On Tue, Nov 25, 2014 at 09:30:07PM +1000, Peter Hutterer wrote:
Pointer acceleration for relative input devices (mice, trackballs, etc.)
applies to the deltas of the device. Alas, those deltas have no physical
reference point - a delta of 10 may be caused by a large movement of a low-dpi
mouse
On Sun, Nov 23, 2014 at 02:40:29AM +0100, Zbigniew Jędrzejewski-Szmek wrote:
On Sun, Nov 23, 2014 at 12:14:32AM +0100, Zbigniew Jędrzejewski-Szmek wrote:
On Sat, Nov 22, 2014 at 02:47:49PM +0100, David Herrmann wrote:
Hi
On Fri, Nov 21, 2014 at 5:00 AM, Peter Hutterer
peter.hutte
I was playing around with systemd-nspawn and systemd-run. The latter doesn't
seem to let me run a command that solely exists on the container.
simple way of reproducing: drop a file foo into the container, then on the
host run
systemd-run -M mycontainer /path/to/foo
I expected this to run
I can't seem to find this in the documentation, so I do wonder if it exists:
is there an equivalent to journalctl -b -1 that lists the log of the most
recent pid?
Specifically I'd like to run journalctl /usr/bin/Xorg --pid -1 or similar to
get users to attach the most recent log file instead of
On 15/03/2014 07:11 , Lennart Poettering wrote:
On Fri, 14.03.14 08:53, Peter Hutterer (peter.hutte...@who-t.net) wrote:
Hey,
I have a service file wacom-inputattach@.service that is started from a udev
rule:
SUBSYSTEM==tty|pnp, KERNEL==ttyS[0-9]*, ATTRS{id}==WACf*,
TAG+=systemd, ENV
On Fri, Mar 14, 2014 at 06:27:26AM +0400, Andrey Borzenkov wrote:
В Fri, 14 Mar 2014 08:53:45 +1000
Peter Hutterer peter.hutte...@who-t.net пишет:
Hey,
I have a service file wacom-inputattach@.service that is started from a udev
rule:
SUBSYSTEM==tty|pnp, KERNEL==ttyS[0-9
On 15/02/2014 01:52 , Laércio de Sousa wrote:
This rules file tells udev to create symlinks for input devices
(keyboard and mouse, at this moment) separated by seat, so it could
be easier for one to get quickly the devpath of a given input
device attached to a given seat.
Example: the keyboard
On Tue, Dec 10, 2013 at 08:20:17PM +0100, Lennart Poettering wrote:
On Mon, 09.12.13 12:18, Peter Hutterer (peter.hutte...@who-t.net) wrote:
On Fri, Dec 06, 2013 at 04:10:02PM +0100, Kay Sievers wrote:
On Fri, Dec 6, 2013 at 7:20 AM, Peter Hutterer peter.hutte...@who-t.net
wrote
On Fri, Dec 06, 2013 at 04:10:02PM +0100, Kay Sievers wrote:
On Fri, Dec 6, 2013 at 7:20 AM, Peter Hutterer peter.hutte...@who-t.net
wrote:
It also depends on the wacom_w8001 and how it reacts when it's loaded
and no hardware is present.
Peter, couldn't this module be autoloaded
On Thu, Dec 05, 2013 at 01:24:10PM +, Jóhann B. Guðmundsson wrote:
[...]
So we need an udev wacom-serial-driver rule that might look like
this for the wacom serial devices
ACTION==remove, GOTO=drivers_end
ENV{MODALIAS}==?*, RUN{builtin}=kmod load $env{MODALIAS}
SUBSYSTEM==tty|pnp,
On Thu, Dec 05, 2013 at 04:38:45PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Dec 05, 2013 at 04:27:51PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Dec 05, 2013 at 04:50:54PM +1000, Peter Hutterer wrote:
the new rule now is:
SUBSYSTEM==tty|pnp, KERNEL==ttyS[0-9]*, ATTRS
On Thu, Dec 05, 2013 at 01:24:10PM +, Jóhann B. Guðmundsson wrote:
On 12/05/2013 12:28 PM, Michael Biebl wrote:
2013/12/5 Jóhann B. Guðmundssonjohan...@gmail.com:
On 12/05/2013 06:50 AM, Peter Hutterer wrote:
ExecStartPre=/usr/sbin/modprobe wacom_w8001
Add a configuration file called
When I fired up F20 on one of my laptops here I noticed that inputattach
doesn't work anymore for serial Wacom devices. It used to be started through
udev, but that doesn't work anymore. So moving to a systemd service it is,
but I'd like a review of the changes please.
The goal is to start
63 matches
Mail list logo
