Hi,
I'm not sure if Yocto 2.3 has new enough version of Mesa and kernel for that.
Seems that it defaults to Weston 1.11 so I'd assume no. Also I got impression
that NXP versions of drivers support HW better (graphics work faster etc.
maybe?). That I don't have my own experience so just relying
We have heuristics for detecting whether a keyboard is internal or external,
but in some cases (e.g. Surface 3) these heuristics fail. Add a udev property
that we can apply to these cases so we have something that's reliable.
This will likely eventually become ID_INPUT_KEYBOARD_INTEGRATION as ship
From: Benjamin Tissoires
On unreliable LID switches, we might have the LID declared as closed
while it is actually not. We can not wait for the first switch event to setup
the keyboard listener: it will never occur.
https://bugs.freedesktop.org/show_bug.cgi?id=101099
Signed-off-by: Benjamin Tis
Signed-off-by: Peter Hutterer
---
src/evdev-lid.c | 4
1 file changed, 4 insertions(+)
diff --git a/src/evdev-lid.c b/src/evdev-lid.c
index 9e694ba1..9815b8fa 100644
--- a/src/evdev-lid.c
+++ b/src/evdev-lid.c
@@ -74,6 +74,10 @@ lid_switch_keyboard_event(uint64_t time,
* re
Only pair if the keyboard is either tagged as internal device.
This has another (unlikely) behaviour change: previously we would override the
paired keyboards with ones that look more accurate (e.g. a usb keyboard paired
before a serial would be unpaired and the serial keyboard takes its place).
N
From: Benjamin Tissoires
What we do not want is libinput to believe the LID is closed while
it's not. But the internal notifier state need to be in sync with the evdev
node, or it's going to be a pain setting the keyboard listener.
But since we don't know if the state is reliable, we track the i
Turns out the Surface3 lid switch handling didn't work as well as it should
(or at all?). The only patch that affects other devices now is 2/5, we tag
keyboards as internal/external which eventually will feed into the other
bits of libinput for DWT detection. That bit will come once this set is
me
On 5/23/17 1:21 PM, Jussi Kukkonen wrote:
Thanks for feedback,
Anything I didn't comment on I think I agree with -- the
wayland-scanner.m4 proposal I'll have to consider but I'd like to be
_really_ sure of what most wayland-scanner users want before going that way.
If we cannot find a way th
Thanks for feedback,
Anything I didn't comment on I think I agree with -- the wayland-scanner.m4
proposal I'll have to consider but I'd like to be _really_ sure of what
most wayland-scanner users want before going that way.
Jussi
On 23 May 2017 at 11:56, Quentin Glidic
wrote:
>
> On 5/23/17 10
On 9/9/16 4:31 AM, Bryce Harrington wrote:
Updated to include review feedback from Quentin on the v5. That
involves refinements to the destructor behavior, reorganizing patches a
bit, and noting that if the idle manager is destroyed by the client, the
individual inhibitor objects remain active.
On 3/13/17 11:40 AM, Sergei Trofimovich wrote:
Before the change build failed on Gentoo as:
libweston/weston_launch-weston-launch.o: In function `handle_open':
weston/libweston/weston-launch.c:363: undefined reference to `major'
weston/libweston/weston-launch.c:365: undefined reference
On 4/4/17 4:34 PM, Emmanuel Gil Peyrot wrote:
From: Emmanuel Gil Peyrot
This fetches the _NET_WM_ICON property of the X11 window, and use the
first image found as the frame icon.
This has been tested with various X11 programs, and improves usability
and user-friendliness a bit.
Changes since
On 4/17/17 1:11 PM, Oliver Smith wrote:
I ran Weston on a Nexus 4 mobile phone, with a native GNU/Linux userland,
and the latest Android kernel for that device from LineageOS [1].
calculate_refresh_rate() returned 1 (mHz), which gets rounded to 0 Hz later
and results in nothing being drawn to th
On 5/8/17 6:47 PM, Lyude wrote:
A little earlier today I ended up spending a lot of time trying to
figure out why weston wasn't managing to launch over SSH and telling me
that I did not have a --tty option specified, despite me passing the
option strings ["--tty", "3"]. Turns out weston just does
On 5/23/17 10:05 AM, Jussi Kukkonen wrote:
Modify wayland-scanner lookup: Use the path given by pkg-config
but offer an option to override the path with
"--with-wayland-scanner-path=PATH". The latter is useful for
cross-compile situations.
I would rather use --with-wayland-scanner.
AC_PATH_P
Modify wayland-scanner lookup: Use the path given by pkg-config
but offer an option to override the path with
"--with-wayland-scanner-path=PATH". The latter is useful for
cross-compile situations.
AC_PATH_PROG is no longer used.
Also add a AC_SUBST-call (it seems previously the pkg-config value w
Hi Teemu,
On 23 May 2017 at 05:33, Keskinarkaus, Teemu
wrote:
> I just ran into this although support was dropped almost a year ago.
>
> Since FBDEV no longer has EGL ‘hackery’ support, what is then the ‘proper’
> way to use EGL drivers? ie. What way they _should_ be used?
>
> I’m in no way expe
17 matches
Mail list logo
