Hey guys,
I have been noticing that Wayland apps like simple-egl only get about 40 FPS in
Headless mode. I followed the logic and it seems to me that this is inevitable
in the current code (unless of course I am miscalculating 😉).
Here’s the flow of events:
1. headless_output_repaint is calle
Hi Arunkumar,
Have you measured:
1) The time to load all of the dependencies and get to "int main" of the
compositor?
2) The time from "int main" to the first rendered frame? Is this what you mean
by 500 ms? This looks abnormally large to me.
First one may be improved by programs like preload.
Hey guys,
Any ideas on this one?
-Satyeshwar
From: wayland-devel On Behalf Of
Singh, Satyeshwar
Sent: Thursday, July 9, 2020 4:52 PM
To: wayland-devel@lists.freedesktop.org
Subject: How to get access to the FB in headless mode
Hi,
I am working on a project that requires Weston to be used in
Hi,
I am working on a project that requires Weston to be used in headless backend
mode. I need to stream the FB contents over to another system. I noticed that
the virtual output concept is only present for the drm backend and it basically
gets the FB that it needs to remote from drm (drmPrimeHa
shwar
-Original Message-
From: Pekka Paalanen [mailto:ppaala...@gmail.com]
Sent: Wednesday, February 6, 2019 12:16 AM
To: Singh, Satyeshwar
Cc: wayland-devel@lists.freedesktop.org
Subject: Re: Limiting Xwayland to only one screen
On Tue, 5 Feb 2019 19:51:41 +0000
"Singh, Satyeshwar" wr
Hi,
I have a 2 screen configuration running Weston. When I run XWayland on top, it
initially shows a black screen on both the screens. I am wondering if there is
a way to limit XWayland to only using one screen? Is there a config file or
command line option that allows me to do so?
-Satyeshwar
Hey guys,
As you know, Weston doesn't wait for client buffers to finish rendering. That
is typically left as an exercise for the kernel mode graphics driver. I am
wondering if anyone knows why this policy decision was made? More importantly,
is there any harm (or any side effect) that I am not t
Yes, not sure what was the issue around TTYs.
-Original Message-
From: wayland-devel [mailto:wayland-devel-boun...@lists.freedesktop.org] On
Behalf Of Pekka Paalanen
Sent: Thursday, September 27, 2018 12:41 AM
To: Singh, Satyeshwar
Cc: Jan Engelhardt ; deepan muthusamy
; wayland-devel
Saw a response from Deepan where he said "I changed type from notify to simple.
Now problem has been solved. Thank you".
-Original Message-
From: wayland-devel [mailto:wayland-devel-boun...@lists.freedesktop.org] On
Behalf Of Jan Engelhardt
Sent: Wednesday, September 26, 2018 12:16 AM
T
Hi Deepan,
Do you have any Weston logs when it restarts? Maybe you want to add --log
option to redirect all output to some log file and share that with us?
-Satyeshwar
From: wayland-devel [mailto:wayland-devel-boun...@lists.freedesktop.org] On
Behalf Of deepan muthusamy
Sent: Friday, September 2
Looks like some drm issue. Just wondering if you can use KMS APIs directly
without seeing this issue? So for example, will kmscube draw something on the
screen (https://github.com/robclark/kmscube)? BTW, noticed that you are using
/dev/dri/card1 in your logs. What's at card0? Note that this kmsc
This happened to me in a VMWare image. Do you think that would make a
difference?
-Original Message-
From: Kristian Høgsberg [mailto:hoegsb...@gmail.com]
Sent: Thursday, June 06, 2013 10:17 PM
To: Singh, Satyeshwar
Cc: wayland-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/1] evdev
The problem was that if we ever switched to another tty while running
Weston, then we would essentially not handle any remaining events and Weston
would enter an infinite loop where it's trying to process an event but it
can't because the processing function evdev_device_data exits before it can
re
:ppaala...@gmail.com]
Sent: Thursday, April 18, 2013 11:47 PM
To: Singh, Satyeshwar
Cc: Jason Ekstrand; wayland-devel@lists.freedesktop.org; Andrew Voron
Subject: Re: Seats support
On Thu, 18 Apr 2013 19:36:55 -0500
Jason Ekstrand wrote:
> Singh,
> On Thu, Apr 18, 2013 at 12:35 PM, Singh
Hi Jason,
> As of right now, weston doesn't have a way (as far as I know) to split
> your devices into multiple seats. Then again, I don't really see why
> you would want to unless you plan to have two people working on the
> same computer simultaneously (I guess that's a possibility).
In a car,
The issue was that touch::down event from the compositor to client apps
would send the previous motion events coordinates and this obviously made
the client do the wrong thing. This happened because we were not waiting for
a SYN event to come from evdev before sending down, motion or up events.
Th
16 matches
Mail list logo
