Re: [PATCH] compositor-drm: launch without input devices

Hi Andrea, On 12.10.2017 17:49, Andrea Giammarchi wrote: > I thought this was resolved via `require-input=false` in weston.ini, > which works already for the Pi too. > > Is this patch enabling that directive automatically? Thank you for the prompt feedback. I didn't know the require-input

Re: [PATCH wayland] cursor: add forward declaration for struct wl_buffer

Hi Emil, > On Oct 12, 2017, at 5:39 AM, Emil Velikov wrote: > > From: Emil Velikov > > This makes the header self-contained, since the struct is considered > opaque from waylad-cursor POV. > > As we're here move the wl_shm fwd.

Re: [PATCH] compositor-drm: launch without input devices

I thought this was resolved via `require-input=false` in weston.ini, which works already for the Pi too. Is this patch enabling that directive automatically? On Thu, Oct 12, 2017 at 10:30 AM, Leon Anavi wrote: > During demonstrations of Automotive Grade Linux (AGL),

[PATCH] compositor-drm: launch without input devices

During demonstrations of Automotive Grade Linux (AGL), GENIVI Development Platform (GDP), Tizen and other platforms relying on Weston it is very convenient to launch it even if there are no input devices such as a keyboard or a mouse. This fix is particularly useful for Raspberry Pi which is a

[PATCH wayland] cursor: add forward declaration for struct wl_buffer

From: Emil Velikov This makes the header self-contained, since the struct is considered opaque from waylad-cursor POV. As we're here move the wl_shm fwd. declaration alongside the others. Making it easier to read and track. Signed-off-by: Emil Velikov

Re: [PATCH weston v12 00/40] Atomic modesetting

Hi Emre, On 12 October 2017 at 10:20, Ucan, Emre (ADITG/ESB) wrote: > I tested your branch " wip/2017-09/atomic-v12" on Intel Apollo Lake with: > - Linux Kernel v4.9 > - Libdrm 2.4.83 > - Mesa 13.0.6 Thanks for testing! > In the end, I could not test the atomic

[PATCH weston v4 6/9] xwm: dump_property() to use FILE internally

From: Pekka Paalanen Write the output of dump_property() out in one log call. When multiple processes (weston and Xwayland) are writing to the same file, this will keep the property dump uninterrupted by Xwayland debug prints. This is also preparation for more development in the

[PATCH weston v4 5/9] compositor: offer logs via weston-debug

From: Pekka Paalanen This registers a new weston-debug scope "log" through which one can get live log output interspersed with possible other debugging prints. Signed-off-by: Pekka Paalanen pass the log_scope to weston_debug_scope_timestamp API to append the scope name to the

[PATCH weston v4 8/9] xwm: convert WM_DEBUG into a weston-debug scope

From: Pekka Paalanen Instead of a compile time choice, offer the XWM debugging messages through the weston-debug protocol and tool on demand. Users will not need to recompile weston to get XWM debugging, and it won't flood the weston log. The debug scope needs to be initialized in

[PATCH weston v4 9/9] compositor: protocol logger

From: Pekka Paalanen This is better than running Weston with WAYLAND_DEBUG=server: - It is enabled on demand, no unnecessary flooding and no need to restart the compositor if debug was enabled. - It prints client pointers so that messages with different clients can be seen

[PATCH weston v4 7/9] xwm: move FILE to the callers of dump_property()

From: Pekka Paalanen This is preparation for using the weston-debug infrastructure for WM_DEBUG. dump_property() may be called from different debugging contexts and often needs to be prefixed with more information. An alternative to this patch would be to pass in the

[PATCH weston v4 1/9] protocol: add weston-debug.xml

From: Pekka Paalanen This is a new debugging extension for non-production environments. The aim is to replace all build-time choosable debug prints in the compositor with runtime subscribable debug streams. Signed-off-by: Pekka Paalanen Added new libweston-$MAJOR-protocols.pc

[PATCH weston v4 2/9] libweston: add weston_debug API and implementation

From: Pekka Paalanen weston_debug is both a libweston API for relaying debugging messages, and the compositor-debug wayland protocol implementation for accessing those debug messages from a Wayland client. weston_debug_compositor_{create,destroy}() are private API, hence not

[PATCH weston v4 3/9] compositor: add option to enable weston_debug

From: Pekka Paalanen Let users enable the compositor debug protocol on the compositor command line. This allows weston-debug tool to work. Signed-off-by: Pekka Paalanen Signed-off-by: Maniraj Devadoss --- compositor/main.c | 7 +++

[PATCH weston v4 4/9] clients: add weston-debug

From: Pekka Paalanen A tool for accessing the zcompositor_debug_v1 interface features. Installed along weston-info, because it should be potentially useful for people running libweston-based compositors. Signed-off-by: Pekka Paalanen Added a man page for weston-debug client

[PATCH weston v4 0/9] weston-debug API and tool

This series of patches are from weston debug protocol RFC posted by Pekka Paalanen along with the modifications done by Maniraj Devadoss . https://lists.freedesktop.org/archives/wayland-devel/2017-June/034227.html v3: 1. protocol is renamed to weston-debug.xml 2. libweston-3-protocols-pc is

RE: [PATCH weston v12 00/40] Atomic modesetting

Hi Daniel, I tested your branch " wip/2017-09/atomic-v12" on Intel Apollo Lake with: - Linux Kernel v4.9 - Libdrm 2.4.83 - Mesa 13.0.6 In the end, I could not test the atomic modesetting with this setup. I got this warning "DRM: does not support atomic modesetting". When I checked the source

Re: Ideas on portable APIs to cheaply copy a GBM bo?

Hi Pekka, On 12 October 2017 at 07:56, Pekka Paalanen wrote: > On Wed, 11 Oct 2017 09:01:30 -0500 > Matt Hoosier wrote: >> I'll have a look there. One thing that for simplicity I left out of >> the original description above is that this custom

Re: [PATCH wayland] scanner: Add --strict flag

On Thu, Oct 12, 2017 at 10:09:43AM +0300, Pekka Paalanen wrote: > On Wed, 11 Oct 2017 17:31:33 +0800 > Jonas Ådahl wrote: > > > Add a --strict flag for making wayland-scanner fail if the DTD > > verification fails. This is useful for testing, so that a test case can > > fail a

Re: [PATCH wayland] scanner: Add --strict flag

On Wed, 11 Oct 2017 17:31:33 +0800 Jonas Ådahl wrote: > Add a --strict flag for making wayland-scanner fail if the DTD > verification fails. This is useful for testing, so that a test case can > fail a scan when the protocol doesn't comply with the DTD. > > Signed-off-by:

Re: Ideas on portable APIs to cheaply copy a GBM bo?

On Wed, 11 Oct 2017 09:01:30 -0500 Matt Hoosier wrote: > On Tue, Oct 10, 2017 at 11:53 AM, Daniel Stone wrote: > > >> Another option is to enforce a synchronous handshake between the > >> Weston foreground loop and the compressor/transmit