Hi Pekka,
Thank you for reply!. We would like to understand the behavior of weston in
following use cases
Scenario 1: What is the Alpha value on weston composed output buffer
in following use case
Screen has only one surface and which has alpha '0'
[image: image.png]
Hi Rob,
If the vendor driver doesn't have the hwpipe sub-object and kms plane is
one-to-one mapped to hwpipe (sspp),
do you think if below approach is acceptable if we still want to
virtualize the kms plane to support 4K/8K scanout?
1. At kms atomic check before calling drm_atomic_helper_chec
calling wl_event_loop_dispatch() is not a working solution: keeps tripping
over a few different assertions causing crash, and doesn't seem to dispatch key
events.
I've seen:
- page_flip_handler: Assertion `output->page_flip_pending' failed.
- weston_output_finish_frame: Assertion `output->repai
The notify_*() functions are called immediately, and then the 10 second delay.
The event loop is definitely sleeping.
What's the best way to wake it up from within the backend? I tried:
wl_event_loop_dispatch(loop, 0); and this works - just not sure if it is the
right way to do it (ran into s
On Tue, 11 Feb 2020 15:59:35 +
Josh Simonot wrote:
> Thanks for the reply!
> I have a big update: it's not the screen refresh at all.
>
> Using the weston-eventdemo, I see that the pointer events aren't
> delivered to the app until 10 seconds after clicking. Maybe that
> sheds some light on
On Wed, 12 Feb 2020 13:51:35 +0530
"Devashish Tiwari" wrote:
> Hello,
>
> I am running weston-5.0.0 on my EVM. I want to integrate my face
> authentication application with it.
>
> I want weston to lock the screen after some time (duration should be
> configurable) and then when I would want to
Hello,
I am running weston-5.0.0 on my EVM. I want to integrate my face authentication
application with it.
I want weston to lock the screen after some time (duration should be
configurable) and then when I would want to unlock it should open my face
authentication application first.
I am abl
