On 11.12.2015 18:17, Martin Peres wrote:
> On 11/12/15 04:34, Michel Dänzer wrote:
>> From: Adam Jackson
>>
>> By the time we get to ComputeLocalClient, we've already done
>> NextAvailableClient → ReserveClientIds → DetermineClientCmd (assuming
>> we're built with #define
> From: Keith Packard
> Date: Thu, 10 Dec 2015 07:18:23 -0800
>
> Mark Kettenis writes:
>
> > Ugh. Exporting global variables as part of the ABI is generally not
> > such a good idea. Perhaps it is better to use functions to acquire
> > and release
On Fri, Dec 11, 2015 at 10:42 AM, Peter Hutterer
wrote:
> On Fri, Dec 11, 2015 at 09:58:34AM +0100, Benjamin Tissoires wrote:
>> Hi Peter,
>>
>> On Fri, Dec 11, 2015 at 12:58 AM, Peter Hutterer
>> wrote:
>> > InputClass sections use various
On 11 December 2015 at 10:20, Martin Peres wrote:
> On 11/12/15 11:30, Michel Dänzer wrote:
>>
>> On 11.12.2015 18:17, Martin Peres wrote:
>>>
>>> On 11/12/15 04:34, Michel Dänzer wrote:
From: Adam Jackson
By the time we get to
On 11/12/15 11:30, Michel Dänzer wrote:
On 11.12.2015 18:17, Martin Peres wrote:
On 11/12/15 04:34, Michel Dänzer wrote:
From: Adam Jackson
By the time we get to ComputeLocalClient, we've already done
NextAvailableClient → ReserveClientIds → DetermineClientCmd (assuming
2015-12-11 10:20 GMT+01:00 Uli Schlachter :
> Am 10.12.2015 um 21:25 schrieb Andreas Boll:
>> Set TZ=UTC before calling asciidoc to make the embedded dates invariant
>> to timezones in order to make the package build reproducibly.
>>
>> Fixes bug:
>>
On Fri, Dec 11, 2015 at 09:58:34AM +0100, Benjamin Tissoires wrote:
> Hi Peter,
>
> On Fri, Dec 11, 2015 at 12:58 AM, Peter Hutterer
> wrote:
> > InputClass sections use various MatchFoo directives to decide which device
> > to
> > apply to. This usually works fine for
From: Daniel Martin
We get multiple udev events for actions like docking a laptop into its
station or plugging a monitor to the station. By consuming as much
events as we can, we reduce the number of output re-evalutions.
I.e. having a Lenovo X250 in a ThinkPad Ultra
Set TZ=UTC before calling asciidoc to make the embedded dates invariant
to timezones in order to make the package build reproducibly.
Fixes bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795981
v2: Set TZ=UTC after $(AM_V_GEN) (fixes non-verbose build)
Suggested-by: Eduard Sanou
KDrive evdev driver deliberately name grabbed devices as "Evdev mouse"
or "Evdev keyboard". This patch will make it skip this step if
grabbed devices are already named (i.e. from udev).
Signed-off-by: Laércio de Sousa
---
hw/kdrive/linux/evdev.c | 6
From: Mikhail Krivtsov
When one hits {Num,Caps,Scroll}Lock key on a Xephyr's keyboard,
keyboard itself works as expected but LEDs are not updated
and always stay in off.
Currently logical LEDs are propagated to physical keyboard LEDs
for "CoreKeyboard" only. All
Multi-seat-capable display managers commonly pass command-line options
like "-novtswitch", "-sharevts", or "-layout seat" to Xorg server, but
Xephyr
currently refuses to start if these options are passed to it,
which may break Xephyr-based single-GPU multiseat setups.
Signed-off-by: Laércio
PLEASE NOTE: Xephyr is NOT my preferred approach for single-GPU
multi-seat configuration (mainly due to its current evdev-based
limited support for handling input devices --- no touchpads,
no touchscreens, no joysticks), but it's the easiest one to implement
in the moment. The best approach by far
This patch simplifies NewInputDeviceRequest() implementation
in kinput.c, making use of improved KdParseKbdOptions()/KdParsePointerOptions()
and merging several "if (ki)"/"if (pi)" clauses.
Signed-off-by: Laércio de Sousa
---
hw/kdrive/src/kinput.c | 76
If kdrive input driver "evdev" is available, no other driver was explicitly
set for a given input device, and its kernel device node is /dev/input/event*,
this patch will make kdrive set "evdev" driver automatically for such device.
Signed-off-by: Laércio de Sousa
This patch introduces a new flag ATTR_KEY for hotplugged input devices,
so we can better distinguish between real keyboards (i.e. devices with
udev property ID_INPUT_KEYBOARD="1") and other key input devices like
lid switches, power buttons, etc.
All supported hotplug backends (udev, hal, and
When used for single-GPU multi-seat purposes, there's no need to
enable ephyr virtual input devices, since Xephyr is supposed to
handle its own hardware devices.
Signed-off-by: Laércio de Sousa
---
hw/kdrive/ephyr/ephyrinit.c | 35
This patch introduces convenient command-line options -xkbrules,
-xkbmodel, -xkblayout, -xkbvariant, and -xkboptions, to set default
values for these properties.
These options can be handful in cases where corresponding values can't
be taken from devices' udev properties, and compile-time default
This patch introduces input hot-plugging support for kdrive-based
applications in multi-seat context. This feature is enabled
by passing -seat option with desired seat name. All keyboard/mouse
devices assigned to that seat will be automatically grabbed
by kdrive.
It supports udev and hal backends
On 11/12/2015 10:31, Emil Velikov wrote:
On 11 December 2015 at 10:20, Martin Peres wrote:
On 11/12/15 11:30, Michel Dänzer wrote:
On 11.12.2015 18:17, Martin Peres wrote:
On 11/12/15 04:34, Michel Dänzer wrote:
From: Adam Jackson
[...]
+#ifndef
Signed-off-by: Thomas Klausner
---
src/radeon_drm_queue.c | 8
src/radeon_kms.c | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/src/radeon_drm_queue.c b/src/radeon_drm_queue.c
index 5e54ef8..84d0509 100644
--- a/src/radeon_drm_queue.c
+++
Mark Kettenis writes:
> However, is there a reason why you didn't use the
> PTHREAD_MUTEX_RECURSIVE mtex type that is standardized by POSIX?
Sorry, my documentation only mentions a non-portable version of
recursive mutexes. I didn't even know that recursive mutexes had
Keith Packard writes:
> Mark Kettenis writes:
>
>> However, is there a reason why you didn't use the
>> PTHREAD_MUTEX_RECURSIVE mtex type that is standardized by POSIX?
>
> Sorry, my documentation only mentions a non-portable version of
> recursive
On Thu, Dec 10, 2015 at 11:42:36 -0800, Keith Packard wrote:
> Mark Kettenis writes:
>
> > Ugh. Exporting global variables as part of the ABI is generally not
> > such a good idea. Perhaps it is better to use functions to acquire
> > and release the input mutex
On 11/12/15 04:34, Michel Dänzer wrote:
From: Adam Jackson
By the time we get to ComputeLocalClient, we've already done
NextAvailableClient → ReserveClientIds → DetermineClientCmd (assuming
we're built with #define CLIENTIDS), so we can look up the name of the
client process
Am 10.12.2015 um 21:25 schrieb Andreas Boll:
> Set TZ=UTC before calling asciidoc to make the embedded dates invariant
> to timezones in order to make the package build reproducibly.
>
> Fixes bug:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795981
>
> Suggested-by: Eduard Sanou
Hi Peter,
On Fri, Dec 11, 2015 at 12:58 AM, Peter Hutterer
wrote:
> InputClass sections use various MatchFoo directives to decide which device to
> apply to. This usually works fine for specific snippets but has drawbacks for
> snippets that apply more generally to a
27 matches
Mail list logo