On Tue, 5 Sep 2017 22:04:38 +0800 lan lan said:
> Hi,
>
> weston doesn't seem to have any kind of "settings manager", regular
> desktop controls,
> or task-bar. Is there a lightweight desktop environments for Wayland?
Probably the lightest weight might be enlightenment
Hi,
XDC was a really great conference and loved the fact that it was
in just one room which kept all the hallway conversations in that room resulting
into more networking.
But I agree with Andres that for the videos, it would be great to split the
huge youtube video stream per presentation and
Any plan to support for drmModeAddFB2WithModifiers and query preferred
FB modifier?
On Tue, Sep 26, 2017 at 12:15 PM, Daniel Stone
wrote:
> We currently do the same thing in two places, and will soon have a
> third.
>
> Signed-off-by: Daniel Stone
From: Sergi Granell
The per-plane IN_FORMATS property adds information about format
modifiers; we can use these to both feed GBM with the set of modifiers
we want to use for rendering, and also as an early-out test when we're
trying to see if a FB will go on a particular
We currently do the same thing in two places, and will soon have a
third.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 93 --
1 file changed, 48 insertions(+), 45 deletions(-)
diff --git
Now we have a more comprehensive overview of the transform we're going
to apply, use this to explicitly disallow scaling and rotation.
XXX: This does not actually disallow rotation for square surfaces.
We would have to build up a full buffer->view->output transform
matrix, and then
Hi,
Here's a cleaned-up and fully-tested version of the atomic series. I'm
fairly happy with it now. There are a few things I'd want to change, but
figured I'd send it all out now rather than waiting another however
long:
* I'd rather track unused_{crtcs,connectors} by putting them all in
Nothing in this loop reorders views within the compositor's view_list.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libweston/compositor-drm.c b/libweston/compositor-drm.c
index
Much like we already have to_drm_output and to_drm_backend.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/libweston/compositor-drm.c b/libweston/compositor-drm.c
index
Split repaint into two stages, as implied by the grouped-repaint
interface: drm_output_repaint generates the repaint state only, and
drm_repaint_flush applies it.
This also moves DPMS into output state. Previously, the usual way to
DPMS off was that repaint would be called and apply its state,
Add support for using the atomic-modesetting API to apply output state.
Unlike previous series, this commit does not unflip sprites_are_broken,
until further work has been done with assign_planes to make it reliable.
Signed-off-by: Daniel Stone
Co-authored-by: Pekka
Move drm_assign_planes into two functions: one which proposes a plane
configuration, and another which applies that state to the Weston
internal structures. This will be used to try multiple configurations
and see which is supported.
Signed-off-by: Daniel Stone
---
Use the same codepath, which has the added advantage of being able to
import dmabufs.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 62 +-
1 file changed, 12 insertions(+), 50 deletions(-)
diff --git
Use the shiny new helper we have for working through scanout as well.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 66 --
1 file changed, 23 insertions(+), 43 deletions(-)
diff --git a/libweston/compositor-drm.c
Return a pointer to the plane state, rather than indirecting via a
weston_plane.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 73 ++
1 file changed, 42 insertions(+), 31 deletions(-)
diff --git
Use the new helper to populate the cursor state as well, with some
special-case handling to account for how we always upload a full-size
BO.
Signed-off-by: Daniel Stone
Reported-by: Derek Foreman
---
libweston/compositor-drm.c | 48
Add a test environment variable to allow disabling atomic modesetting.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/libweston/compositor-drm.c b/libweston/compositor-drm.c
index
Now that we can sensibly test proposed plane configurations with atomic,
sprites are not broken.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git
Add support for multiple modes: toggling whether or not the renderer
and/or planes are acceptable. This will be used to implement a smarter
plane-placement heuristic when we have support for testing output
states.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c
When we come to assign_planes, try very hard to ignore views which are
only visible on other outputs, rather than forcibly moving them to the
primary plane, which causes damage all round and unnecessary repaints.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c
Use the extended GBM allocator interface to support modifiers and
multi-planar BOs.
Depends on bwidawsk's 'modifiers' tree.
Signed-off-by: Daniel Stone
---
configure.ac | 3 +++
libweston/compositor-drm.c | 57 ++
Add support for the GBM_BO_IMPORT_FD_MODIFIER path, which allows us to
import multi-plane dmabufs, as well as format modifiers.
Signed-off-by: Daniel Stone
---
configure.ac | 3 -
libweston/compositor-drm.c | 181
If AddFB2 ever fails for any reason, we fall back to legacy AddFB, which
doesn't support the same swathe of formats, or multi-planar formats, or
modifiers.
This can happen with arbitrary client buffers, condemning us to the
fallback forever more. Remove this, at the cost of an unnecessary ioctl
In our new and improved helper to determine the src/dest values for a
buffer on a given plane, make sure we account for all buffer
transformations, including viewport clipping.
Rather than badly open-coding it ourselves, just use the helper which
does exactly this.
Signed-off-by: Daniel Stone
Rather than a hardcoded ARGB -> XRGB translation inside a
GBM-specific helper, just determine whether or not the view is opaque,
and use the generic helpers to implement the format translation.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 111
Use the new drmModeAddFB2WithModifiers interface to import buffers with
modifiers.
Signed-off-by: Daniel Stone
---
configure.ac | 3 +++
libweston/compositor-drm.c | 28 ++--
2 files changed, 29 insertions(+), 2 deletions(-)
diff
Since we now incrementally test atomic state as we build it, we can
loosen restrictions on what we can do with planes, and let the kernel
tell us whether or not it's OK.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 22 ++
1 file
The atomic API can allow us to test state before we apply it, to see if
it will be valid. Add support for this, which we will later use in
assign_planes to ensure our plane configuration is valid.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 180
Make it a bit more clear what the purpose of the variable is.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/libweston/compositor-drm.c b/libweston/compositor-drm.c
index
For atomic modesetting support, the mode is identified by a blob
property ID, rather than being passed inline. Add a blob_id member to
drm_mode to handle this, including refactoring mode destruction into a
helper function.
Signed-off-by: Daniel Stone
---
From: Pekka Paalanen
Set the atomic client cap, where it exists, and use this to discover the
plane/CRTC/connector properties we require for atomic modesetting.
Signed-off-by: Daniel Stone
Co-authored-by: Pekka Paalanen
Use a real drm_plane to back the scanout plane, displacing
output->fb_{last,cur,pending} to their plane-tracked equivalents.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 167 +++--
1 file changed, 101 insertions(+),
When trying to assign planes, keep track of the areas which are
already occluded, and ignore views which are completely occluded. This
allows us to build a state using planes only, when there are occluded
views which cannot go into a plane behind views which can.
Signed-off-by: Daniel Stone
Pull this into a helper function, so we can use it everywhere.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 157 +
1 file changed, 88 insertions(+), 69 deletions(-)
diff --git a/libweston/compositor-drm.c
When leaving Weston, don't attempt to restore the previous CRTC
settings. The framebuffer may well have disappeared, and in every
likelihood, whoever gets the KMS device afterwards will be repainting
anyway.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 26
Rather than a more piecemeal approach at backend creation, explicitly
track connectors and CRTCs we do not intend to use, so we can ensure
they are disabled where appropriate.
Signed-off-by: Daniel Stone
Reviewed-by: Pekka Paalanen
---
If we have an unused CRTC or connector, explicitly disable it during the
end of the repaint cycle, or when we get VT-switched back in.
Signed-off-by: Daniel Stone
Reviewed-by: Pekka Paalanen
---
libweston/compositor-drm.c | 60
Track dynamic plane state (CRTC, FB, position) in separate structures,
rather than as part of the plane. This will make it easier to handle
state management later, and much more closely tracks what the kernel
does with atomic modesets.
The fb_last pointer previously used in drm_plane now becomes
If we don't have any damage for the primary plane, then don't force a
repaint; simply reuse the old buffer we already have.
Signed-off-by: Daniel Stone
Reviewed-by: Pekka Paalanen
---
libweston/compositor-drm.c | 15 +--
1 file
Add a test environment variable to allow disabling universal planes.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/libweston/compositor-drm.c b/libweston/compositor-drm.c
index
Currently this doesn't actually really do anything, but will be used in
the future to track the state for both modeset and repaint requests.
Completion of the request gives us a single request-completion path for
both pageflip and vblank events.
This merges the timing paths for scanout and
Change the type of cursor_plane from a weston_plane (base tracking
structure) to a drm_plane (wrapper containing additional DRM-specific
details), and make it a dynamically-allocated pointer.
Using the standard drm_plane allows us to reuse code which already deals
with drm_planes, e.g. a common
Hi all,
First again big thanks to Stéphane and Jennifer for organizing a great XDC.
Like last year we'd like to hear feedback on how this year's XDC went,
both the good (and what you'd like to see more of) and the not so
good. Talk selection, organization, location, scheduling of talks,
anything
On 2017-09-26 09:23 AM, Pekka Paalanen wrote:
On Tue, 26 Sep 2017 14:26:36 +0100
Daniel Stone wrote:
On 26 September 2017 at 14:09, Matt Hoosier wrote:
This change replaces a queued emission of buffer-release events (which
is prone to
Changes look fine to me, in the end my patches would be pushed as is
and then this one pushed on top, right?
--
Marco Martin
On Tue, Sep 26, 2017 at 3:53 PM, Jonas Ådahl wrote:
> It stilled referred to the removed requests, so change those places to
> refer to the renamed
On Thu, 2017-09-14 at 09:21 +0900, Boram Park wrote:
> Before putting data into a buffer, we have to make sure that the data
> size is
> smaller than not only the buffer's full size but also the buffer's empty
> size.
>
> https://bugs.freedesktop.org/show_bug.cgi?id=102690
>
> Signed-off-by:
On Tue, 26 Sep 2017 14:26:36 +0100
Daniel Stone wrote:
> On 26 September 2017 at 14:09, Matt Hoosier wrote:
> > This change replaces a queued emission of buffer-release events (which
> > is prone to starvation) with a regular event emission. This
On Wed, 6 Sep 2017 08:17:22 -0400
nerdopolis wrote:
> ---
> libweston/compositor-fbdev.c | 35 +--
> 1 file changed, 33 insertions(+), 2 deletions(-)
>
> diff --git a/libweston/compositor-fbdev.c b/libweston/compositor-fbdev.c
>
It stilled referred to the removed requests, so change those places to
refer to the renamed ones.
While at it, also change documentation to refer directly to
xdg_toplevel, as that has now been introduced.
Signed-off-by: Jonas Ådahl
---
Hi,
On Tue, Sep 26, 2017 at 03:06:05PM
On Thu, 14 Sep 2017 23:08:51 -0400
nerdopolis wrote:
> On Wednesday, September 6, 2017 8:17:21 AM EDT nerdopolis wrote:
> > This attempts to wake up secondary framebuffer devices
> > (/dev/fb1 and up) as usually these devices start powered off, and
> > the
On Wed, 6 Sep 2017 08:17:20 -0400
nerdopolis wrote:
> ---
> libweston/launcher-logind.c | 22 --
> 1 file changed, 12 insertions(+), 10 deletions(-)
>
Hi,
I think this patch is good. Logind does everything around VT
management, right? So
On 26 September 2017 at 14:09, Matt Hoosier wrote:
> This change replaces a queued emission of buffer-release events (which
> is prone to starvation) with a regular event emission. This means that
> client programs no longer need to secretly install surface frame
>
Done:
https://lists.freedesktop.org/archives/wayland-devel/2017-September/035191.html
On Tue, Sep 26, 2017 at 2:28 AM, Pekka Paalanen wrote:
> On Mon, 25 Sep 2017 10:31:35 -0500
> Matt Hoosier wrote:
>
>> This change replaces a queued emission of
On Wed, 6 Sep 2017 08:17:19 -0400
nerdopolis wrote:
> ---
Hi,
the commit message is missing a rationale and Signed-off-by.
> compositor/main.c| 2 ++
> libweston/compositor-fbdev.c | 5 -
> libweston/compositor-fbdev.h | 1 +
> 3 files
On Wed, 6 Sep 2017 08:17:18 -0400
nerdopolis wrote:
> ---
Hi,
the commit message should contain at least briefly why we want this. I
have a feeling this is the right thing to do, but I can't quite put the
reason into words myself.
We would also prefer a
This change replaces a queued emission of buffer-release events (which
is prone to starvation) with a regular event emission. This means that
client programs no longer need to secretly install surface frame
listeners just to guarantee that they get correctly notified of buffer
lifecycle events.
ping?
On Mon, Sep 18, 2017 at 2:09 PM, Marco Martin wrote:
> as export is a reserved keyword in C++, in order for the
> output generated by wayland_scanner to compile correctly
> rename export to export_toplevel and import to import_toplevel
> this needs a new protocol version
On Tue, 19 Sep 2017 14:59:10 +0300
Alexandros Frantzis wrote:
> The sync file functionality is required by the upcoming GPU render
> timeline work, but it's only available in relatively new linux kernel
> versions (4.7 and above).
>
> This commit provides an
Le 22/09/2017 à 16:31, Pekka Paalanen a écrit :
> From: Pekka Paalanen
>
> Add 'name' argument to weston_output_init(). This is much more obvious
> than the assert inside weston_output_init() to ensure the caller has set
> a field in weston_output first.
>
> Now
On Mon, 25 Sep 2017 10:31:35 -0500
Matt Hoosier wrote:
> This change replaces a queued emission of buffer-release events (which
> is prone to starvation) with a regular event emission. This means that
> client programs no longer need to secretly install surface frame
>
On 22/09/2017, 17.32, "wayland-devel on behalf of Pekka Paalanen"
wrote:
>
> From: Pekka Paalanen
>
> Initialize the list in weston_output_init() instead of doing it
> separately in
On 22/09/2017, 17.33, "wayland-devel on behalf of Pekka Paalanen"
wrote:
>
> From: Pekka Paalanen
>
> If we pass the base->enabled test, then the renderer output is
> guaranteed to
On 22/09/2017, 17.33, "wayland-devel on behalf of Pekka Paalanen"
wrote:
>
> From: Pekka Paalanen
>
> Rename fbdev_frame_buffer_destroy() to fbdev_frame_buffer_unmap()
> because that
On 22/09/2017, 17.33, "wayland-devel on behalf of Pekka Paalanen"
wrote:
>
> From: Pekka Paalanen
>
> Change all backends to set the core backend pointer early.
>
> This is
On 22/09/2017, 17.33, "wayland-devel on behalf of Pekka Paalanen"
wrote:
>
> From: Pekka Paalanen
>
> Check and ensure that a compositor can only load one backend
> successfully. If
On 22/09/2017, 17.33, "wayland-devel on behalf of Pekka Paalanen"
wrote:
>
> From: Pekka Paalanen
>
> 'release' is a more appropriate name because the function does not free
> the
On 22/09/2017, 17.33, "wayland-devel on behalf of Pekka Paalanen"
wrote:
>
> From: Pekka Paalanen
>
> A client may have bound the same wl_output multiple times, for who knows
> what
67 matches
Mail list logo