Hi,
On 6/27/22 21:50, Gwendal Grignou wrote:
> In 60-sensor.hwdb, we can specify a matrix to rotate sensor output to
> match the expected 'natural' orientation [1].
>
> When behind a screen, accelerometers are usually soldered upside down,
> so a rotation matrix is needed to rotate their raw outp
Hi All,
I'm sending this to both systemd-devel and lkml since I'm not sure
what is causing this.
For some reason the msi-laptop module is not autoloading on a
MSI S270 (yes that is a very old laptop).
Here is some debugging info:
$ cat /sys/class/dmi/id/modalias
dmi:bvnAmericanMegatrendsInc.:bv
Hi All,
As part of improving the boot experience:
https://fedoraproject.org/wiki/Changes/FlickerFreeBoot
https://hansdegoede.livejournal.com/20119.html
I took a look at how applying offline updates looks
when pressing ESC to get the detailed view, pk-offline-update
then prints "dnf update" like
Hi,
On 27-02-19 12:50, Lennart Poettering wrote:
On Mi, 27.02.19 10:40, Mantas Mikulėnas (graw...@gmail.com) wrote:
On Tue, Feb 26, 2019 at 7:29 PM Hans de Goede wrote:
Hi All,
As part of improving the boot experience:
https://fedoraproject.org/wiki/Changes/FlickerFreeBoot
https
Hi,
On 27-02-19 17:04, Lennart Poettering wrote:
On Mi, 27.02.19 15:56, Hans de Goede (hdego...@redhat.com) wrote:
Hi,
On 27-02-19 12:50, Lennart Poettering wrote:
On Mi, 27.02.19 10:40, Mantas Mikulėnas (graw...@gmail.com) wrote:
On Tue, Feb 26, 2019 at 7:29 PM Hans de Goede wrote:
Hi
Hi,
On 28-02-19 10:27, Colin Guthrie wrote:
Hans de Goede wrote on 27/02/2019 19:12:
On 27-02-19 17:04, Lennart Poettering wrote:
Another option is to do this in your soruces btw:
```c
(void) kill(1, SIGRTMIN+21);
```
Sending SIGRTMIN+21 to PID 1 will disable the status output
explicitly
Hi All,
When using full-disk encryption the console keymap is used in the
initrd to enter the disk-crypt password.
There are a couple of issues with this:
1) keymap changes do not become effective until a new kernel
(which generated a new initrd which includes the updated vconsole.conf)
gets in
Hi,
On 30-07-19 10:49, Hans de Goede wrote:
Hi All,
When using full-disk encryption the console keymap is used in the
initrd to enter the disk-crypt password.
There are a couple of issues with this:
1) keymap changes do not become effective until a new kernel
(which generated a new initrd
Hi Lennart,
On 31-07-19 14:07, Lennart Poettering wrote:
On Di, 30.07.19 10:49, Hans de Goede (hdego...@redhat.com) wrote:
I believe that the best way to fix is this is probably to specify the
keymap on the kernel commandline using vconsole.keymap= on the kernel
commandline.
As you found
Hi All,
I already filed a github issue for $subject:
https://github.com/systemd/systemd/issues/13437
But I'm not sure how close github issues are watched hence this email. It would
be nice if we can get this fixed for F31 beta, or if some more time is needed,
at least get this regression fixed
Hi,
On 02-09-19 07:17, Mantas Mikulėnas wrote:
On Mon, Sep 2, 2019 at 7:34 AM Chris Murphy mailto:li...@colorremedies.com>> wrote:
systemd-243~rc2-2.fc31.x86_64
kernel-5.3.0-0.rc6.git1.1.fc32.x86_64
This might be a regression, at least I don't remember this happening
before. I
Hi Daniel,
On 05-09-19 11:05, Daniel Drake wrote:
Hi,
so sometimes we even apply the
wrong quirks. Two recent examples:
https://bugzilla.redhat.com/show_bug.cgi?id=1717712 (more on this case below)
I see the latest development of having the hwdb specify whether the
accelerometer is in
Hi,
On 05-09-19 12:49, Bastien Nocera wrote:
On Thu, 2019-09-05 at 18:38 +0800, Daniel Drake wrote:
On Thu, Sep 5, 2019 at 6:07 PM Bastien Nocera
wrote:
I've read through this, and I'm happy blacklisting the hp_accel
driver
in code. For the other devices, I'd rather leave it as-is.
That wou
Hi,
On 05-09-19 13:28, Bastien Nocera wrote:
On Thu, 2019-09-05 at 13:13 +0200, Hans de Goede wrote:
Hi,
On 05-09-19 12:49, Bastien Nocera wrote:
On Thu, 2019-09-05 at 18:38 +0800, Daniel Drake wrote:
On Thu, Sep 5, 2019 at 6:07 PM Bastien Nocera
wrote:
I've read through this, an
Hi,
On 05-09-19 14:11, Hans de Goede wrote:
Hi,
On 05-09-19 13:28, Bastien Nocera wrote:
On Thu, 2019-09-05 at 13:13 +0200, Hans de Goede wrote:
Hi,
On 05-09-19 12:49, Bastien Nocera wrote:
On Thu, 2019-09-05 at 18:38 +0800, Daniel Drake wrote:
On Thu, Sep 5, 2019 at 6:07 PM Bastien
Hi all,
Currently, at least in Fedora, but I do not believe that this problem is
unique to Fedora, there are 2 problems with keymap handling in the initrd.
1: If the keymap in vconsole.conf is changed then this does not apply to the
initrd without rebuilding it. This means that any changes are o
Hi,
On 26-09-2019 11:10, Michael Chapman wrote:
On Thu, 26 Sep 2019, Hans de Goede wrote:
[...]
I believe that the best alternative is to have localed append / update
a rd.vconsole.keymap=foo argument to the kernel commandline, to override
the vconsole.conf KEYMAP setting, but only in the
Hi,
On 26-09-2019 11:53, Michael Chapman wrote:
On Thu, 26 Sep 2019, Hans de Goede wrote:
Hi,
On 26-09-2019 11:10, Michael Chapman wrote:
On Thu, 26 Sep 2019, Hans de Goede wrote:
[...]
I believe that the best alternative is to have localed append / update
a rd.vconsole.keymap=foo argument
ee if this will also
work for them. If they are happy with this then I plan to start implementing
this when I'm done with the plymouth keyboard layout indicator stuff.
Regards,
Hans
On Thu, Sep 26, 2019 at 12:43 PM Hans de Goede mailto:hdego...@redhat.com>> wrote:
Hi,
On
Hi,
On 9/27/19 1:49 PM, Lennart Poettering wrote:
On Mi, 25.09.19 16:50, Hans de Goede (hdego...@redhat.com) wrote:
Hi all,
Currently, at least in Fedora, but I do not believe that this problem is
unique to Fedora, there are 2 problems with keymap handling in the
initrd.
Hmm, why do you
Hi,
On 9/27/19 1:59 PM, Lennart Poettering wrote:
On Fr, 27.09.19 10:20, Hans de Goede (hdego...@redhat.com) wrote:
"So my plan for regular Fedora for this is as follows:
1. Have a /boot/initramfs-config.img which for now will just contain
/etc/vconsole.conf (chances are this wil
Hi,
On 29-09-2019 12:08, Lennart Poettering wrote:
On Fr, 27.09.19 16:00, Hans de Goede (hdego...@redhat.com) wrote:
Anyway, even if you insist that the Fedora desktop should care about
non-EFI, which I can accept, isn't the lesson to learn to add some
concept like EFI vars to those
Hi,
On 30-09-2019 13:23, Hans de Goede wrote:
Hi,
On 29-09-2019 12:08, Lennart Poettering wrote:
On Fr, 27.09.19 16:00, Hans de Goede (hdego...@redhat.com) wrote:
Anyway, even if you insist that the Fedora desktop should care about
non-EFI, which I can accept, isn't the lesson to
Hi All,
For Fedora 33 I would like to get rid of some ugly hacks we have
wrt the grub-hidden-menu feature Fedora has been shipping for a
while now.
One part of this will be setting SYSTEMD_REBOOT_TO_BOOT_LOADER_ENTRY
in logind's environment, and add /run/systemd/reboot-to-boot-loader-menu
suppor
Hi,
On 6/30/20 11:36 AM, Lennart Poettering wrote:
On Mo, 29.06.20 11:02, Hans de Goede (hdego...@redhat.com) wrote:
Hi All,
For Fedora 33 I would like to get rid of some ugly hacks we have
wrt the grub-hidden-menu feature Fedora has been shipping for a
while now.
One part of this will be
Hi All,
$subject is somewhat misleading, what I actually want is to make:
systemctl reboot --boot-loader-menu=60
Work as a regular user (who is physically present at the console).
So I looked at:
/usr/share/polkit-1/actions/org.freedesktop.login1.policy, which has:
R
Hi again,
On 7/13/20 4:11 PM, Hans de Goede wrote:
Hi All,
$subject is somewhat misleading, what I actually want is to make:
systemctl reboot --boot-loader-menu=60
Work as a regular user (who is physically present at the console).
So I looked at:
/usr/share/polkit-1/actions
Hi,
On 7/14/20 10:03 AM, Lennart Poettering wrote:
On Di, 30.06.20 12:17, Hans de Goede (hdego...@redhat.com) wrote:
1. The user has logged in successfully and the session lasts
at least 2 minutes (could be a bit shorter, we want to catch the
case where the session immediately exits / crashes
Hi,
On 3/16/21 5:26 PM, Alan Stern wrote:
> On Tue, Mar 16, 2021 at 06:26:30AM +0100, Matthias Schwarzott wrote:
>> I implemented solution 3b. This is the pullrequest for udev (systemd
>> repository):
>>
>> https://github.com/systemd/systemd/pull/19002
>>
>> Now Lennart asks if udev is the be
Hi,
On 3/16/21 6:04 PM, Alan Stern wrote:
> On Tue, Mar 16, 2021 at 05:43:34PM +0100, Hans de Goede wrote:
>> Hi,
>>
>> On 3/16/21 5:26 PM, Alan Stern wrote:
>>> On Tue, Mar 16, 2021 at 06:26:30AM +0100, Matthias Schwarzott wrote:
>>>> I implemented sol
Hi,
On 3/17/21 6:56 PM, Matthias Schwarzott wrote:
> Am 17.03.21 um 16:17 schrieb Alan Stern:
>> On Wed, Mar 17, 2021 at 01:21:50PM +0100, Hans de Goede wrote:
>>> Hi,
>>>
>>> On 3/16/21 6:04 PM, Alan Stern wrote:
>>>> I think it would be mildly bet
imal overhead.
>
> Reported-and-tested-by: Matthias Schwarzott
> Signed-off-by: Alan Stern
> CC:
Thanks, patch looks good to me:
Reviewed-by: Hans de Goede
Regards,
Hans
>
> ---
>
>
> [as1953]
>
>
> drivers/usb/storage/transport.c|7
ixing this on the systemd/hwdb side.
Regards,
Hans
Forwarded Message
Subject: [PATCH regression fix] firmware/dmi: Move product_sku info to the end
of the modalias
Date: Tue, 31 Aug 2021 15:05:08 +0200
From: Hans de Goede
To: Jean Delvare
CC: Hans de Goede , linu
emd/issues/20550
Link: https://github.com/systemd/systemd/pull/20562
Fixes: e26f023e01ef ("firmware/dmi: Include product_sku info to modalias")
Cc: sta...@vger.kernel.org
Cc: Kai-Chuan Hsieh
Cc: Erwan Velu
Signed-off-by: Hans de Goede
---
drivers/firmware/dmi-id.c | 6 +-
1 file ch
Hi,
On 8/31/21 3:08 PM, Hans de Goede wrote:
> Hi,
>
> I BCc-ed systemd-devel on this, to avoid reply-to-all from kernel folks
> getting bounces because of them not being subscribed, but it seems the
> list does not like being in the BCc, so hence this forward.
>
> Note
Hi All,
So as you may have heard, I'm working on hiding the grub-menu
by default on single OS Fedora Workstation. Part of the plan
here is to detect if a previous boot was successful and
cleanly shutdown the machine and show the menu (not hide the
menu) if the previous boot has failed to set eit
Hi,
On 11-06-18 13:31, Lennart Poettering wrote:
On Mo, 11.06.18 12:48, Hans de Goede (hdego...@redhat.com) wrote:
Hi All,
So as you may have heard, I'm working on hiding the grub-menu
by default on single OS Fedora Workstation. Part of the plan
here is to detect if a previous boo
Hi,
On 11-06-18 16:37, Lennart Poettering wrote:
On Mo, 11.06.18 15:37, Hans de Goede (hdego...@redhat.com) wrote:
Uurks. Quite frankly, it appears strange to me to delay this for this
long. I mean we reworked most code that delayed worked to shutdown
like this these days to happen as early
Hi,
On 11-06-18 17:48, Jérémy Rosen wrote:
We solve a problem which is kinda similar in the embedded world when we do A/B
update
I'll describe how we do it so you see if this can help
* Have a single "last boot went wrong" flag
When grub starts
* if the flag is set, show the boot menu (or a t
Hi,
On 12-06-18 10:24, Lennart Poettering wrote:
On Mo, 11.06.18 17:40, Hans de Goede (hdego...@redhat.com) wrote:
It am very sure it's not worth trying to maintain a shutdown_sucess
variable that is determined that early. That's a pointless excercise,
OB> > you won't
Hi,
The mention of "systemctl reboot --firmware" in the other thread
made me realize that it would be good to also have a
"systemctl reboot --bootmenu".
First a question about "systemctl reboot --firmware" is this
available to a normal user (through policykit and the user
being on a physical att
Hi,
On 13-06-18 05:40, Alexander E. Patrakov wrote:
Hans de Goede :
Hi All,
So as you may have heard, I'm working on hiding the grub-menu
by default on single OS Fedora Workstation. Part of the plan
here is to detect if a previous boot was successful and
cleanly shutdown the machin
Hi,
On 12-06-18 19:11, Lennart Poettering wrote:
On Di, 12.06.18 11:33, Hans de Goede (hdego...@redhat.com) wrote:
AFAIK the service actually doing the updates is supposed to call
systemctl reboot --force when it is done, so any targets after
system-update.target won't get started ?
Hi,
On 13-06-18 17:05, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jun 13, 2018 at 04:55:27PM +0200, Hans de Goede wrote:
Hi,
On 12-06-18 19:11, Lennart Poettering wrote:
On Di, 12.06.18 11:33, Hans de Goede (hdego...@redhat.com) wrote:
AFAIK the service actually doing the updates is
Hi,
On 13-06-18 17:05, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jun 13, 2018 at 04:55:27PM +0200, Hans de Goede wrote:
Hi,
On 12-06-18 19:11, Lennart Poettering wrote:
On Di, 12.06.18 11:33, Hans de Goede (hdego...@redhat.com) wrote:
AFAIK the service actually doing the updates is
This model needs the trackpoint sensitivity to be boosted to not be too slow
to be usable, see: https://bugzilla.redhat.com/show_bug.cgi?id=1200717
---
hwdb/70-pointingstick.hwdb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/hwdb/70-pointingstick.hwdb b/hwdb/70-pointingstick.hwdb
index 72c
Like many other recent thinkpads the factory default pointingstick
sensitivity on these devices is quite low, making the pointingstick
very slow in moving the cursor.
This extends the existing hwdb rules for tweaking the sensitivity to
also apply to the T550 / W550s models.
BugLink: https://bugzi
Like many other recent thinkpads the factory default pointingstick
sensitivity on these devices is quite low, making the pointingstick
very slow in moving the cursor.
This extends the existing hwdb rules for tweaking the sensitivity to
also apply to the X1 carbon 3rd gen model.
BugLink: https://b
Hi,
On 14-09-15 14:28, Daniel Mack wrote:
On 09/14/2015 02:16 PM, Hans de Goede wrote:
Like many other recent thinkpads the factory default pointingstick
sensitivity on these devices is quite low, making the pointingstick
very slow in moving the cursor.
This extends the existing hwdb rules
Dear udev developers,
We (me and some kernel devs mostly) would like to add support to
the kernel for userspace telling the kernel that it is done with
the *initial* loading of modules, with the purpose of cleaning up
(disabling) unused harware resources like e.g. regulators and
clocks.
Currentl
Hi,
On 17-01-15 14:56, Greg KH wrote:
On Sat, Jan 17, 2015 at 09:44:00AM +0100, Hans de Goede wrote:
Dear udev developers,
We (me and some kernel devs mostly) would like to add support to
the kernel for userspace telling the kernel that it is done with
the *initial* loading of modules, with
Hi,
On 16-03-15 12:31, David Herrmann wrote:
Hi Hans & Martin
I've pushed some patches that change the hwdb 60-keyboard matching
logic. This was needed to support bluetooth devices, and then I just
went ahead and cleaned up the other rules. This email is meant as a
heads-up to you guys, as you
Hi,
On some of the ARM boards I work on in my spare time I've
done "systemctl enable getty@ttyGS0.service" to get a getty
on the usb gadget serial port which I've configured on the
devices otg controller.
This serial port device node /dev/ttyGS0 shows up as soon
as the gadget serial port driver
Hi,
On 16-03-15 18:12, David Herrmann wrote:
Hi Hans
On Mon, Mar 16, 2015 at 5:15 PM, Hans de Goede wrote:
Hi,
On some of the ARM boards I work on in my spare time I've
done "systemctl enable getty@ttyGS0.service" to get a getty
on the usb gadget serial port which I'
Hi,
On 16-03-15 20:41, David Herrmann wrote:
Hi
On Mon, Mar 16, 2015 at 7:32 PM, Hans de Goede wrote:
Hi,
On 16-03-15 18:12, David Herrmann wrote:
Hi Hans
On Mon, Mar 16, 2015 at 5:15 PM, Hans de Goede
wrote:
Hi,
On some of the ARM boards I work on in my spare time I've
, also add support for the
recently added INPUT_PROP_ACCELEROMETER property bit.
Signed-off-by: Hans de Goede
---
src/udev/udev-builtin-input_id.c | 21 +++--
1 file changed, 19 insertions(+), 2 deletions(-)
diff --git a/src/udev/udev-builtin-input_id.c b/src/udev/udev-builtin
Hi All,
Testing has shown that the default experience of trackpoints on different
model laptops differs quite a lot, from almost unusably fast, to just plain
unusably slow on some models.
It seems that before libinput people where using the huge amount of
configurability Xorg gives them to work a
only sends delta events in the 1-2 range, tweak the
sensitivity to make it send a wider range of deltas and apply a const accel
factor to make it have a more reasonable speed by default.
Signed-off-by: Hans de Goede
---
hwdb/70-trackpoint.hwdb | 14 ++
1 file changed, 14 insertions
are a better match to this.
Signed-off-by: Hans de Goede
---
hwdb/70-trackpoint.hwdb | 59 +++
rules/70-mouse.rules | 1 +
rules/70-trackpoint.rules | 16 +
3 files changed, 76 insertions(+)
create mode 100644 hwdb/70
movement
speeds, rather then the expected fluid scale.
Changing the sensitivity to a higher level then the bootup default fixes this,
the rule additions in this commit allows specifying a new sensitivity default
through hwdb giving a better ootb experience.
Signed-off-by: Hans de Goede
---
hwdb/70
The trackpoint of the Dell Latitude E6400 is somewhat slow by default,
where as the trackpoint of the Dell Latitude D620 is much too fast by default,
set TRACKPOINT_CONST_ACCEL for both of them to adjust for this.
Signed-off-by: Hans de Goede
---
hwdb/70-trackpoint.hwdb | 12
1
Hi,
On 02-04-15 12:21, Lennart Poettering wrote:
On Thu, 02.04.15 11:48, Hans de Goede (hdego...@redhat.com) wrote:
The kernel has been setting the INPUT_PROP_POINTING_STICK property bit
on trackpoints for a while now, and this is useful information to have
in various places, so make input_id
Hi,
On 02-04-15 12:23, Lennart Poettering wrote:
On Thu, 02.04.15 11:48, Hans de Goede (hdego...@redhat.com) wrote:
+# Same as below but also sets the TPPS/2 IBM TrackPoint driver sensitivity
+KERNELS=="input*", ATTR{device/name}=="TPPS/2 IBM TrackPoint", \
+ I
Hi,
On 02-04-15 12:27, Lennart Poettering wrote:
On Thu, 02.04.15 12:21, Lennart Poettering (lenn...@poettering.net) wrote:
On Thu, 02.04.15 11:48, Hans de Goede (hdego...@redhat.com) wrote:
The kernel has been setting the INPUT_PROP_POINTING_STICK property bit
on trackpoints for a while
Hi,
On 02-04-15 12:27, Lennart Poettering wrote:
On Thu, 02.04.15 12:21, Lennart Poettering (lenn...@poettering.net) wrote:
On Thu, 02.04.15 11:48, Hans de Goede (hdego...@redhat.com) wrote:
The kernel has been setting the INPUT_PROP_POINTING_STICK property bit
on trackpoints for a while
Hi All,
Note this patch depends on Peter Hutterer's recent patch titled:
"udev: input_id: tag pointing sticks as ID_INPUT_POINTINGSTICK"
Regards,
Hans
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailm
existing detection
and will ensure that no other tags get set on the device.
Signed-off-by: Hans de Goede
---
src/shared/missing.h | 4
src/udev/udev-builtin-input_id.c | 5 +
2 files changed, 9 insertions(+)
diff --git a/src/shared/missing.h b/src/shared/missing.h
index
Hi,
On 03-04-15 13:13, Lennart Poettering wrote:
On Fri, 03.04.15 12:07, Hans de Goede (hdego...@redhat.com) wrote:
input_id already (tries to) tag accelerometers as such, but this only works
for absolute accelerometers. Recent kernels mark accelerometers through an
input prop. Trust that
Hi All,
Here is v2 of my pointstick set.
Changes since v1:
-Drop the patch to set ID_INPUT_TRACKPOINT, Peter already send almost the
same patch to set ID_INPUT_POINTINGSTICK
-s/trackpoint/pointingstick/ unlike trackpoint pointingstick is a vendor
neutral name, and pointingstick is also what the
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 specifying a
per model POINTINGSTICK_CONST_ACCEL value which can be used by
The IBM / Lenovo trackpoints are special, they allow specifying a sensitivity
setting through a ps/2 command, which changes the range of the deltas send when
using the trackpoint. One some models with normal usage one only deltas
of 1 or 2 are send, resulting in there only being 2 mouse cursor move
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
default, set POINTINGSTICK_CONST_ACCEL for both of them to adjust for this.
---
hwdb/70-pointingstick.hwdb | 12
1 file changed, 12 insert
Lenovo has changed the sensitity of the trackpoint on the x240 / T440s / T540
generation of Thinkpads, making them somewhat unsensitive by default, add a
hwdb entry to tweak the sensitivity setting.
The ThinkPad X200s is way way too slow by default and unless you push the
trackpoint quite hard onl
Hi,
On 03-04-15 15:51, David Herrmann wrote:
Hi
On Fri, Apr 3, 2015 at 12:07 PM, Hans de Goede wrote:
input_id already (tries to) tag accelerometers as such, but this only works
for absolute accelerometers. Recent kernels mark accelerometers through an
input prop. Trust that prop and always
2015 or thereabouts, Hans de Goede wrote:
Hi,
On 03-04-15 15:51, David Herrmann wrote:
Hi
On Fri, Apr 3, 2015 at 12:07 PM, Hans de Goede wrote:
input_id already (tries to) tag accelerometers as such, but this only works
for absolute accelerometers. Recent kernels mark accelerometers through an
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 of Thinkpads, making them somewhat unsensitive by default, add a
I
Hi,
Thanks for the review, v3 with all the commit message corrections
taken care of coming up.
On 07-04-15 07:06, Peter Hutterer wrote:
On Fri, Apr 03, 2015 at 04:11:58PM +0200, Hans de Goede wrote:
diff --git a/hwdb/70-pointingstick.hwdb b/hwdb/70-pointingstick.hwdb
index a893da6
IBM / Lenovo trackpoints allow specifying a sensitivity setting through a
ps/2 command, which changes the range of the deltas sent when using the
trackpoint. On some models with normal usage only deltas of 1 or 2 are send,
resulting in there only being 2 mouse cursor movement speeds, rather than
th
Lenovo has changed the sensitivity of the trackpoint on the x240 / T440s / T540
generation of Thinkpads, making them somewhat insensitive by default, add a
hwdb entry to tweak the sensitivity setting.
The ThinkPad X200s is way way too slow by default and unless you push the
trackpoint quite hard o
The pointingstick of the Dell Latitude E6400 is somewhat slow by default,
whereas the pointingstick of the Dell Latitude D620 is much too fast by
default, set POINTINGSTICK_CONST_ACCEL for both of them to adjust for this.
---
hwdb/70-pointingstick.hwdb | 12
1 file changed, 12 inserti
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 specifying a
per model POINTINGSTICK_CONST_ACCEL value which can be used by
Hi All,
Here is v3 of my pointingstick set.
Changes since v2:
-Fix numerous spelling / gramatical errors in commit messages
-Add a reference to the kernel sources for the ibm trackpoint sensitivity
setting
Changes since v1:
-Drop the patch to set ID_INPUT_TRACKPOINT, Peter already send almost t
Hi,
On 07-04-15 12:23, David Herrmann wrote:
Hi
On Tue, Apr 7, 2015 at 12:09 PM, Hans de Goede wrote:
IBM / Lenovo trackpoints allow specifying a sensitivity setting through a
ps/2 command, which changes the range of the deltas sent when using the
trackpoint. On some models with normal usage
Hi,
On 07-04-15 13:46, David Herrmann wrote:
Hi
On Tue, Apr 7, 2015 at 1:40 PM, Hans de Goede wrote:
The series looks reasonable, but I wonder why we cannot merge it into
60-keyboard.rule (60-evdev.rule now) like Peter's series does? In that
case, please make this a builtin of input_id
: Sjoerd Timmer
Reported-by: Sjoerd Timmer
Signed-off-by: Hans de Goede
---
src/udev/udev-builtin-input_id.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/src/udev/udev-builtin-input_id.c b/src/udev/udev-builtin-input_id.c
index ecfc447..f07f86e 100644
--- a/src/udev/udev-builtin
: Sjoerd Timmer
Reported-by: Sjoerd Timmer
Signed-off-by: Hans de Goede
---
Changes in v2:
-Use test_pointers() / test_key return value()
---
src/udev/udev-builtin-input_id.c | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/src/udev/udev-builtin-input_id.c b/src
Make test_pointer / test_keys return a boolean indicating whether or not
they've set any properties on the device.
While touching allmost all test_bit() using lines anyways also remove
the extra space between the function name and the '(' (coding style issue).
Signed-off-by
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 device.
While touching allmost all test_bit() using lines an
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 evdev builtin (which is called
keyboard for historical reasons)
Changes since v2:
-Fix numerous spelling / gramatical errors in commit messages
-Add a refe
IBM / Lenovo trackpoints allow specifying a sensitivity setting through a
ps/2 command, which changes the range of the deltas sent when using the
trackpoint.
On some models with normal usage only deltas of 1 or 2 are send, resulting in
there only being 2 mouse cursor movement speeds, rather than t
The pointingstick of the Dell Latitude E6400 is somewhat slow by default,
whereas the pointingstick of the Dell Latitude D620 is much too fast by
default, set POINTINGSTICK_CONST_ACCEL for both of them to adjust for this.
---
hwdb/70-pointingstick.hwdb | 12
1 file changed, 12 inserti
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 hwdb file which allows specifying a per model
POINTINGSTICK_CONST_ACCEL value which can be used by the userspace in
Lenovo has changed the sensitivity of the trackpoint on the x240 / T440s / T540
generation of Thinkpads, making them somewhat insensitive by default, add a
hwdb entry to tweak the sensitivity setting.
The ThinkPad X200s is way way too slow by default and unless you push the
trackpoint quite hard o
Like the T440s these need the sensitity to be set significantly higher
then the default of 128 for the trackpoint to be usable. Like with the
T440s 200 seems to be a good value to get a reasonable but not too high
sensitivity.
Signed-off-by: Hans de Goede
---
hwdb/70-pointingstick.hwdb | 10
reserved codes, making
the other 5 keys work.
Cc: Hans de Goede
Signed-off-by: Hans de Goede
---
hwdb/60-keyboard.hwdb | 7 +++
1 file changed, 7 insertions(+)
diff --git a/hwdb/60-keyboard.hwdb b/hwdb/60-keyboard.hwdb
index 59f467b..06caba9 100644
--- a/hwdb/60-keyboard.hwdb
+++ b/hwdb/60
, making the Inspiron 1520 work
like most modern laptops which emit brightness up / down events through
acpi-video only.
BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1141525
Cc: Pavel Malyshev
Reported-by: Pavel Malyshev
Signed-off-by: Hans de Goede
---
hwdb/60-keyboard.hwdb | 5 +
1
Hi,
For some reason after I've built the Xorg xserver from git, and then login
through gdm (on an otherwise unmodified F-20 install), the acls on
/dev/snd/pcm* (and likely others too) no longer get setup to give the user
I've just logged in with access to them.
Reverting to Xorg from the F-20 pa
Hi,
On 01/20/2014 10:54 AM, Colin Guthrie wrote:
'Twas brillig, and Hans de Goede at 20/01/14 08:42 did gyre and gimble:
Hi,
For some reason after I've built the Xorg xserver from git, and then login
through gdm (on an otherwise unmodified F-20 install), the acls on
/dev/snd/pcm* (
Hi,
On 01/27/2014 03:19 PM, Lennart Poettering wrote:
> On Sun, 26.01.14 00:21, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
>>
>> +static int writev_safe(int fd, const struct iovec *w, int j, bool
>> async_signal_safe) {
>> +if (!async_signal_safe)
>> +retu
Hi,
Currently when people want to use usbredirection to a virtual machine from
spice-client, they must launch the spice-client as root so that it can
access device nodes under /dev/bus/usb.
Since the purpose is for usbredirection to just work plug and play for
virtual machines, this needs to cha
1 - 100 of 104 matches
Mail list logo
