Hi all,
This is the official release for Weston 14.0.0.
Apart from the version bump, no changes have been added since RC3.
Changelog since RC3:
Marius Vlad (1):
build: bump to version 14.0.0 for the official release
git tag: 14.0.0
https://gitlab.freedesktop.org/wayland/weston
Hi all,
This is the RC3 release for Weston 14.0.0.
Changelog since RC2:
Derek Foreman (1):
libweston: Fix crash with mirror-of
Marius Vlad (1):
build: bump to version 13.0.95 for the RC3 release
git tag: 13.0.95
https://gitlab.freedesktop.org/wayland/weston/-/releases/13.0.95
Hi all,
This is the RC2 release for Weston 14.0.0.
Changelog since RC1:
Marius Vlad (2):
libweston/color-management: Add fallback for static_assert
build: bump to version 13.0.94 for the RC2 release
git tag: 13.0.94
https://gitlab.freedesktop.org/wayland/weston/-/releases/13.0.94
Hi all,
This is the RC2 release for Weston 14.0.0.
Changelog since RC1:
Marius Vlad (2):
libweston/color-management: Add fallback for static_assert
build: bump to version 13.0.94 for the RC2 release
git tag: 13.0.94
https://gitlab.freedesktop.org/wayland/weston/-/releases/13.0.94
Hi all,
This is the RC1 release for Weston 14.0.0.
Changelog since beta release:
Marius Vlad (3):
libweston/drm-virtual: Add prepare_repaint to perform a repaint
libweston/drm-virtual: Point output base backend the DRM backend
build: bump to version 13.0.93 for the RC1
Hi all,
This is the beta release for Weston 14.0.0.
Changelog since the alpha release:
Derek Foreman (1):
drm: Remove unnecessary parameter from drm_output_state_alloc()
Marius Vlad (1):
build: bump to version 13.0.92 for the beta release
git tag: 13.0.92
https
Hi all,
This is the alpha release for Weston 14.0.0. A few things made it
through, like initial HW underlay support, configuration for output mirroring,
PipeWire dmabuf improvements, and many more which I probably forgot.
Do check out the changelog for particularities.
As usual, a number of bug
ke to propose
> the following release schedule for Weston 14.
>
> - Alpha: August 7th (in 2 weeks)
> - Beta: August 14
> - RC1: August 21
> - First potential final release: August 28 (in 5 weeks)
>
> If there's something you'd like to see landing before that
Le 13/01/2023 à 13:13, Matti Ristimäki a écrit :
Hi,
Any tips, where/how to debug RDP related problem with Wayland/Weston.
Not kind of sure if this is Weston problem or Qt problem…
Goal:
Trying to create a RDP connection to a Qt GUI-application.
[Service]
# Requires systemd-notify.so
Hi all,
We haven't had a new release in a while so I'd like to propose
the following release schedule for Weston 14.
- Alpha: August 7th (in 2 weeks)
- Beta: August 14
- RC1: August 21
- First potential final release: August 28 (in 5 weeks)
If there's something you'd like t
Hi Marius,
We are using pure upstream Weston 10.0.2.
Will open a gitlab issue.
Thanks,
Namit
-Original Message-
From: Marius Vlad
Sent: Friday, July 5, 2024 3:37 PM
To: Namit Solanki (QUIC)
Cc: Pritama Biswas (QUIC) ;
wayland-devel@lists.freedesktop.org
Subject: Re: Blank screen
Hi Pritama, Namit,
On Fri, Jul 05, 2024 at 07:14:35AM +, Namit Solanki (QUIC) wrote:
> Hi Weston team,
>
> Can you please let us know if you faced this issue on Weston 10?
No. I've tried this with 10.0.2 and 10.0.5 (our latest bug-fix release Weston
10).
>
> Or else
Hi Weston team,
Can you please let us know if you faced this issue on Weston 10?
Or else can you please give some pointers to debug this issue?
Thanks,
Namit
From: Pritama Biswas (QUIC)
Sent: Wednesday, July 3, 2024 6:29 PM
To: wayland-devel@lists.freedesktop.org
Cc: Namit Solanki (QUIC
Hi Team,
We are observing the following issue on Weston 10.0.2:
When we launch Weston with drm-backend and pixman renderer, we are seeing blank
screen. Upon doing hotplug, display is coming up.
In layer dumps, we can see that a fully opaque layer is getting created during
issue case as shown
Hi Team,
We are observing the following issue on Weston 10.0.2:
When we launch Weston with drm-backend and pixman renderer, we are seeing blank
screen. Upon doing hotplug, display is coming up.
In layer dumps, we can see that a fully opaque layer is getting created during
issue case as shown
>>
>>
>> -Original Message-
>> From: Hoosier, Matt
>> Sent: Monday, June 17, 2024 8:28 AM
>> To: Pekka Paalanen
>> Cc: 'Marius Vlad' ;
>> 'wayland-devel@lists.freedesktop.org' ;
>> 'Daniel Stone'
&
desktop.org>; 'Daniel Stone'
> Subject: Re: Full-motion zero-copy screen capture in Weston
>
> On Fri, 14 Jun 2024 18:36:57 +
> "Hoosier, Matt" wrote:
>
> >
> > Hmm. As I read through the history of the original support for
> > wr
On Fri, 14 Jun 2024 18:36:57 +
"Hoosier, Matt" wrote:
>
> Hmm. As I read through the history of the original support for
> writeback screenshots
> (https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/458)
> and get some initial results just trying to
.freedesktop.org>; 'Daniel Stone'
> Subject: Re: Full-motion zero-copy screen capture in Weston
>
> On Wed, 12 Jun 2024 21:35:48 +
> "Hoosier, Matt" wrote:
>
> > > -Original Message-
> > > From: Hoosier, Matt
> > &g
-devel@lists.freedesktop.org; Daniel
> > Stone
> > Subject: RE: Full-motion zero-copy screen capture in Weston
> >
> > > -Original Message-
> > > From: Pekka Paalanen
> > > Sent: Wednesday, June 12, 2024 4:03 AM
> > > To: Hoosi
-devel@lists.freedesktop.org; Daniel
> > Stone
> > Subject: RE: Full-motion zero-copy screen capture in Weston
> >
> > > -Original Message-
> > > From: Pekka Paalanen
> > > Sent: Wednesday, June 12, 2024 4:03 AM
> > >
> -Original Message-
> From: Hoosier, Matt
> Sent: Wednesday, June 12, 2024 8:37 AM
> To: Pekka Paalanen
> Cc: s...@cmpwn.com; cont...@emersion.fr; Marius Vlad
> ; wayland-devel@lists.freedesktop.org; Daniel
> Stone
> Subject: RE: Full-motion zero-copy
> -Original Message-
> From: Pekka Paalanen
> Sent: Wednesday, June 12, 2024 4:03 AM
> To: Hoosier, Matt
> Cc: s...@cmpwn.com; cont...@emersion.fr; Marius Vlad
> ; wayland-devel@lists.freedesktop.org; Daniel
> Stone
> Subject: Re: Full-motion zero-copy screen c
n option to guarantee that the source of the
> screen capture involves the writeback connector (similar to what
> you've done with weston_output_capture), I don't really think it
> would be a good idea to make Weston explicitly aware of any of this
> funny hypervisor business g
Hi Matt,
On Fri, 7 Jun 2024 at 16:30, Hoosier, Matt wrote:
> Okay, makes sense that you don’t want to have to repeat the dependencies’
> builds for every CI test. I’m not arguing that you should – it was just more
> a thought experiment to see whether riding Meson subprojects is a reasonable
>
ector (similar to what you've done with
weston_output_capture), I don't really think it would be a good idea to make
Weston explicitly aware of any of this funny hypervisor business going on.
The title on this email conversation was probably poorly chosen, in retrospect.
I'm not so
On Fri, 7 Jun 2024 14:16:32 +
"Hoosier, Matt" wrote:
> > What do you mean you can capture all virtual machines with KMS
> > writeback?
> >
> > What's the architecture there? How do virtual machines access KMS
> > hardware? Why would Weston be a
7, 2024 10:17 AM
To: Hoosier, Matt
Cc: Pekka Paalanen ; Marius Vlad
; wayland-devel@lists.freedesktop.org
Subject: Re: Ways to test Weston during development (Re: Full-motion zero-copy
screen capture in Weston)
Hi Matt, On Fri, 7 Jun 2024 at 15: 30, Hoosier, Matt wrote: > Would Meso
Hi Matt,
On Fri, 7 Jun 2024 at 15:30, Hoosier, Matt wrote:
> Would Meson’s dependency wrapping capabilities be a viable solution here? I
> think that most of Weston’s dependencies that have aggressive version
> requirements are themselves also Meson projects.
>
> The Weston C
Would Meson’s dependency wrapping capabilities be a viable solution here? I
think that most of Weston’s dependencies that have aggressive version
requirements are themselves also Meson projects.
The Weston CI configuration builds a bunch of its dependencies (Mesa, libdrm,
libwayland
> What do you mean you can capture all virtual machines with KMS
writeback?
>
> What's the architecture there? How do virtual machines access KMS
hardware? Why would Weston be able to capture their outputs at all?
The world of virtualization on commercially supported embedded SOCs
in branch. Had to delete the tag and re-create it. Should now point
> correctly. All links are the same, with the same files.
>
> Thanks for heads-up Dylan!
>
> On Tue, Apr 23, 2024 at 06:55:45PM +0300, Marius Vlad wrote:
> > Hi all,
> >
> > Weston 13.0
point release
build: bump to version 13.0.3 for the point release
Pekka Paalanen (1):
CI: work around LeakSanitizer crashes with use_tls=0
git tag: 13.0.3
https://gitlab.freedesktop.org/wayland/weston/-/releases/13.0.3/downloads/weston-13.0.3.tar.xz
S
Thanks, everybody.
After some trial and error, I find that if I install seatd in the host and the
seatd dev package in the Toolbox container and I then symlink the host seatd
socket into /tmp on the container, Weston seems to start up okay on my physical
KMS connectors:
user@host:~$ toolbox
> >
> > But the DRM backend *really* doesn't want to start nowadays unless
> > you're running on a system with seatd and/or logind available.
> > Toolbox [1] is the de facto way to develop on bleeding edge copies of
> > components these days. But it logind and seat
nless
> you're running on a system with seatd and/or logind available.
> Toolbox [1] is the de facto way to develop on bleeding edge copies of
> components these days. But it logind and seatd aren't exposed into it.
>
> How do Weston people interactively develop
t
> logind and seatd aren't exposed into it.
>
> How do Weston people interactively develop on the Weston DRM backend nowadays?
With either seatd or logind. I suspect people use containers to build
but run it on the device.
>
> [1] https://docs.fedoraproject.org/en-US/fedora-
is the de
facto way to develop on bleeding edge copies of components these days. But it
logind and seatd aren't exposed into it.
How do Weston people interactively develop on the Weston DRM backend nowadays?
[1] https://docs.fedoraproject.org/en-US/fedora-silverblue/toolbox/
> ---
On Mon, 3 Jun 2024 17:57:18 +
"Hoosier, Matt" wrote:
> > What do you mean you can capture all virtual machines with KMS
> > writeback?
> >
> > What's the architecture there? How do virtual machines access KMS
> > hardware? Why would W
> What do you mean you can capture all virtual machines with KMS
> writeback?
>
> What's the architecture there? How do virtual machines access KMS
> hardware? Why would Weston be able to capture their outputs at all?
I hope to have more to say about this shortly.
> T
x27;s the architecture there? How do virtual machines access KMS
hardware? Why would Weston be able to capture their outputs at all?
> Frankly, weston_output_capture_v1's model that clients allocate the
> buffers would make it very difficult to support efficient screen
> capture for mo
Hi Matt,
fös., 31. maí 2024 kl. 15:34 skrifaði Hoosier, Matt :
>
> Thanks, understood. I would expect that I need to take some care in
> allocating a buffer that my DRM driver accepts for writeback, in this usage.
>
>
>
> Do I interpret right that the wlroots screencopy extension wants the client
starting point.
-Matt
From: Simon Ser
Date: Friday, May 31, 2024 at 10:16 AM
To: Andri Yngvason
Cc: "Hoosier, Matt" , Pekka Paalanen
, "s...@cmpwn.com" , Marius Vlad
, "wayland-devel@lists.freedesktop.org"
Subject: Re: Full-motion zero-copy screen capture in Weston
On Friday, May 31st, 2024 at 16:45, Simon Ser wrote:
> > See:
> > https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/124
> >
> > > My goal is to implement this screen capture with a guarantee that the
> > > copy comes from a KMS writeback connector. I know this sounds li
On Friday, May 31st, 2024 at 16:39, Andri Yngvason wrote:
> Hi Matt,
>
> fös., 31. maí 2024 kl. 13:26 skrifaði Hoosier, Matt matt.hoos...@garmin.com:
>
> > Hi,
> >
> > Yeah. I agree that although I can prototype something quick and dirty here
> > as a change to weston_output_capture_v1, it's
Hi Matt,
fös., 31. maí 2024 kl. 13:26 skrifaði Hoosier, Matt :
>
> Hi,
>
> Yeah. I agree that although I can prototype something quick and dirty here as
> a change to weston_output_capture_v1, it's probably not a good fit there.
>
> Drew or Simon, does either of
> https://github.com/swaywm/wlroo
screen capture for more
> than one simultaneous client. You can only target one writeback framebuffer
> per page flip. Having the compositor manage the buffers' lifetimes and just
> publishing out handles (in the style of those two wlr extensions) to those
> probably fits bett
Vlad; wayland-devel@lists.freedesktop.org
Subject: Re: Full-motion zero-copy screen capture in Weston
On Thu, 30 May 2024 13:40:15 +
"Hoosier, Matt" wrote:
> Okay, interesting thoughts on all of that.
>
> I'm not sure how far I'm going to get toward a complete overhaul of
>
On Thu, 30 May 2024 13:40:15 +
"Hoosier, Matt" wrote:
> Okay, interesting thoughts on all of that.
>
> I'm not sure how far I'm going to get toward a complete overhaul of
> the capture mechanism. Maybe it would be useful to know a couple
> things about the current one (weston_output_capture_
tt
> > mailto:matt.hoos...@garmin.com>>
> > Cc: wayland-devel@lists.freedesktop.org
> > <mailto:wayland-devel@lists.freedesktop.org>
> > Subject: Re: Full-motion zero-copy screen capture in Weston
> >
> > On Tue, 28 May 2024 20:04:45 +0300
>
to help with this. This is more of a
wish than a requirement.
Thanks,
pq
>
> > -Original Message-
> > From: Pekka Paalanen
> > Sent: Wednesday, May 29, 2024 2:43 AM
> > To: Marius Vlad ; Hoosier, Matt
> >
> > Cc: wayland-devel@lists.freedeskto
ero-copy screen capture in Weston
>
> On Tue, 28 May 2024 20:04:45 +0300
> Marius Vlad wrote:
>
> > On Tue, May 28, 2024 at 03:53:23PM +, Hoosier, Matt wrote:
> > > Hi Marius,
> > Hi,
> > >
> > > Okay, I guess that answers the bit about nee
> > But I'm still a little unclear about a couple things, if I were to try to
> > build on this PW backend as a starting point:
> >
> > First, it looks to me like when you use the PW backend to Weston, that
> > becomes your display. That is, rendering directly
Hi again,
The MR I'd like to link is actually at
https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1476
On Tue, May 28, 2024 at 08:04:52PM +0300, Marius Vlad wrote:
> On Tue, May 28, 2024 at 03:53:23PM +, Hoosier, Matt wrote:
> > Hi Marius,
> Hi,
> >
uild on this PW backend as a starting point:
>
> First, it looks to me like when you use the PW backend to Weston, that
> becomes your display. That is, rendering directly targets it. I was
> hoping for a way to get it to broadcast the very same framebuffer(s)
> that are getting sca
nd to Weston, that becomes
your display. That is, rendering directly targets it. I was hoping for a way to
get it to broadcast the very same framebuffer(s) that are getting scanned out
for the current frame by the DRM backend.
Second, I'm don't see the path to getting this
echanism is active
>
> The desktop environments' compositors implement the XDG screencast portal. If
> I read things correctly, that one deposits the stream of dmabuf frame fds
> into the Pipewire stream indicated by the user invoking the D-Bus Screencast
> API.
>
> Tha
tream of dmabuf frame fds into
the Pipewire stream indicated by the user invoking the D-Bus Screencast API.
That doesn't really seem like a starter for doing this in Weston. There was
conversation back in 2019 about trying to add zero-copy dmabuf support in
Weston's own Pipewire inte
ut I
> have not seen follow up on the topic since then. Is there any change
> in the status?
Yes, we landed that in Weston 13, but configuring was left out
for the next version. That work is currently WIP at
https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/147
status?
thanks,
Dawn
From: Daniel Stone
Sent: Friday, June 23, 2023 10:04 AM
To: Dawn HOWE
Cc: wayland-devel@lists.freedesktop.org
Subject: Re: Weston mirror/clone to 2 different displays
Hi Dawn,
On Thu, 22 Jun 2023 at 18:09, Dawn HOWE
mailto:dawn.h
On Wed, 24 Apr 2024 14:06:17 +0530 Akshaya Maran
said:
> Hi,
>
> I am using the Weston 11 version. fbdev backend i s dropped in weston 11 .
> Is there any alternative to the fb-dev backend since there is no drm device
> in my custom board.
add kms/drm driver for your di
Hi,
I am using the Weston 11 version. fbdev backend i s dropped in weston 11 .
Is there any alternative to the fb-dev backend since there is no drm device
in my custom board.
Thanks,
Akshaya.M
Hi all,
>
> Weston 13.0.1, a bug fix release for 13.0.0 has been released.
>
> Full changelog below:
>
> Arnaud Vrac (3):
> desktop-shell: clamp view alpha correctly
> desktop-shell: set proper curtain size when no output is created yet
> clients/de
Hi all,
Weston 13.0.1, a bug fix release for 13.0.0 has been released.
Full changelog below:
Arnaud Vrac (3):
desktop-shell: clamp view alpha correctly
desktop-shell: set proper curtain size when no output is created yet
clients/desktop-shell: fix crash on init when panel is
Hi all,
Weston 12.0.4, a bug fix release for 12.0.0 has been released.
Full changelog below:
Arnaud Vrac (2):
desktop-shell: clamp view alpha correctly
clients/desktop-shell: fix crash on init when panel is disabled
Marius Vlad (1):
build: bump to version 12.0.4 for the point
Hi all,
I've been postponing these for a while now, and given that Weston 14 is
still in development with some in-flight changes, think it would good to
have at least an intermediary, bug-fix release, for Weston 13,
respectively Weston 12.
Next week, 23 of April, 2024, I'd like to cut
On Sat, Mar 30, 2024 at 09:16:57AM +0530, Akshaya Maran wrote:
> Hi Marius,
Hi,
>
> pvr kernel module was not loaded properly . After loading the module , I
> end up with below issue ,
>
> *weston.service - Weston, a Wayland compositor, as a system service*
> *Loaded: loaded
On 29/03/2024 01:20, Yosuke Nakayama wrote:
Dear Wayland-devel Community,
I am currently exploring the capabilities of Weston, the reference
compositor for Wayland, specifically in the context of an application
use case that I am working on. My goal is to achieve a functionality
where the
te:
>
> > On Fri, Mar 29, 2024 at 10:20:50AM +0900, Yosuke Nakayama wrote:
> > > Dear Wayland-devel Community,
> > Hi,
> > >
> > > I am currently exploring the capabilities of Weston, the reference
> > > compositor for Wayland, specifically in
On Fri, Mar 29, 2024 at 12:28:36AM +0530, Akshaya Maran wrote:
> Hi,
Hi,
>
> I am facing an issue while trying to start the weston service .
> Below is the error message :
>
> *weston.service - Weston, a Wayland compositor, as a system service*
>
> * Loaded: loa
On Fri, Mar 29, 2024 at 10:20:50AM +0900, Yosuke Nakayama wrote:
> Dear Wayland-devel Community,
Hi,
>
> I am currently exploring the capabilities of Weston, the reference
> compositor for Wayland, specifically in the context of an application use
> case that I am working on
Dear Wayland-devel Community,
I am currently exploring the capabilities of Weston, the reference
compositor for Wayland, specifically in the context of an application use
case that I am working on. My goal is to achieve a functionality where the
graphical output of a single application can be
Hi,
I am facing an issue while trying to start the weston service .
Below is the error message :
*weston.service - Weston, a Wayland compositor, as a system service*
* Loaded: loaded (/lib/systemd/system/weston.service; disabled; preset:
enabled)*
* Active: failed (Result: exit-code
bit more to try and gain some
understanding of what is going on and how this should all work.
So I have created a pure GStreamer/Wayland/Weston application to test
out how this should work. This is at:
https://portal.beam.ltd.uk/public//test022-wayland-video-example.tar.gz
This tries to implement
On 08/03/2024 15:23, Pekka Paalanen wrote:
On Fri, 8 Mar 2024 14:50:30 +
Terry Barnaby wrote:
On 05/03/2024 12:26, Pekka Paalanen wrote:
On Mon, 4 Mar 2024 17:59:25 +
Terry Barnaby wrote:
...
I would have thought it better/more useful to have a Wayland API call
like "stopCommit
On Fri, 8 Mar 2024 14:50:30 +
Terry Barnaby wrote:
> On 05/03/2024 12:26, Pekka Paalanen wrote:
> > On Mon, 4 Mar 2024 17:59:25 +
> > Terry Barnaby wrote:
> >
...
> >> I would have thought it better/more useful to have a Wayland API call
> >> like "stopCommiting" so that an applicati
and gain some
understanding of what is going on and how this should all work.
So I have created a pure GStreamer/Wayland/Weston application
to test
out how this should work. This is at:
https://portal.beam.ltd.uk/public//test022-wayland-video-example.tar.gz
This tries to implement a C++ Widget
>> While I am trying to investigate my issue in the QtWayland arena via
> >>>>>> the
> >>>>>> Qt Jira Bug system, I thought I would try taking Qt out of the equation
> >>>>>> to simplify the application a bit more to try a
created a pure GStreamer/Wayland/Weston application to test
out how this should work. This is at:
https://portal.beam.ltd.uk/public//test022-wayland-video-example.tar.gz
This tries to implement a C++ Widget style application using native
Wayland. It is rough and could easily be doing things wrong wrt
plication a bit more to try and gain some
> >>>> understanding of what is going on and how this should all work.
> >>>>
> >>>> So I have created a pure GStreamer/Wayland/Weston application to test
> >>>> out how this should work. T
, I thought I would try taking Qt out of the equation
to simplify the application a bit more to try and gain some
understanding of what is going on and how this should all work.
So I have created a pure GStreamer/Wayland/Weston application to test
out how this should work. This is at:
https
Jira Bug system, I thought I would try taking Qt out of the equation
> >> to simplify the application a bit more to try and gain some
> >> understanding of what is going on and how this should all work.
> >>
> >> So I have created a pure GStreamer/Wayland/Westo
gain some
understanding of what is going on and how this should all work.
So I have created a pure GStreamer/Wayland/Weston application to test
out how this should work. This is at:
https://portal.beam.ltd.uk/public//test022-wayland-video-example.tar.gz
This tries to implement a C++ Widget style
g of what is going on and how this should all work.
>
> So I have created a pure GStreamer/Wayland/Weston application to test
> out how this should work. This is at:
> https://portal.beam.ltd.uk/public//test022-wayland-video-example.tar.gz
>
> This tries to implement a C++
GStreamer/Wayland/Weston application to test
out how this should work. This is at:
https://portal.beam.ltd.uk/public//test022-wayland-video-example.tar.gz
This tries to implement a C++ Widget style application using native
Wayland. It is rough and could easily be doing things wrong wrt Wayland
of doing
this with XWindows.
As stated the reason this is not working with Qt6/Wayland/Weston is
probably a Qt6 bug/issue/feature. However a way to understand what is
happening is to look at the shared Wayland level and maybe there is a
way with Wayland protocol commands of overcoming
ed, only set once per wl_surface
life time. Sub-surface is a role.
>
> I need to find some way to actually display video, simply and
> efficiently on an embedded platform, in a Qt application in the year 2024 :)
>
> I have tried lots of work arounds but none have worked due to eith
ked due to either Qt
issues, Wayland restrictions, Gstreamer restrictions, Weston
issues/restrictions, NXP hardware engine issues/restrictions etc. Any
ideas gratefully received!
The higher level surfaces are created/managed by QtWayland, but maybe I
can override somehow.
That does not feel
,
> >>
> >> I have investigated a bit further. I have built my own Weston server to
> >> run under X11 on Fedora37 so I can add printf's and debug more easily
> >> than using a cross compiled iMX8mp target system etc. I added a new
> >> dsmc-s
Hi Pekka,
Thanks for the response. Notes below:
Terry
On 26/02/2024 13:28, Pekka Paalanen wrote:
On Sun, 25 Feb 2024 08:04:30 +
Terry Barnaby wrote:
Hi,
I have investigated a bit further. I have built my own Weston server to
run under X11 on Fedora37 so I can add printf's and
On Sun, 25 Feb 2024 08:04:30 +
Terry Barnaby wrote:
> Hi,
>
> I have investigated a bit further. I have built my own Weston server to
> run under X11 on Fedora37 so I can add printf's and debug more easily
> than using a cross compiled iMX8mp target system etc. I added
Hi,
I have investigated a bit further. I have built my own Weston server to
run under X11 on Fedora37 so I can add printf's and debug more easily
than using a cross compiled iMX8mp target system etc. I added a new
dsmc-shell to Weston which is identical to kiosk-shell (apart from
names)
I stated:
I have tried using "weston-debug scene-graph" and I am coming to the
conclusion that qtwayland 6.5.0 is not really using native Wayland
surfaces when Qt::WA_NativeWindow is used. From what I can see (and I
could easily be wrong) the Wayland protocol shows wl_surfaces being
c
Hi,
On Fri, Feb 23, 2024 at 06:14:11AM +, Terry Barnaby wrote:
> I have tried using "weston-debug scene-graph" and I am coming to the
> conclusion that qtwayland 6.5.0 is not really using native Wayland surfaces
> when Qt::WA_NativeWindow is used. From what I can see (an
On Fri, Feb 23, 2024 at 6:15 AM Terry Barnaby wrote:
>I don't know how to determine the Wayland surface ID from a
> wl_surface pointer unfortunately to really check this.
wl_proxy_get_id(static_cast(myWlSurface));
> >> Possibly when QWidget is below in hierarcy to be a child of of a parent,
> >
I have tried using "weston-debug scene-graph" and I am coming to the
conclusion that qtwayland 6.5.0 is not really using native Wayland
surfaces when Qt::WA_NativeWindow is used. From what I can see (and I
could easily be wrong) the Wayland protocol shows wl_surfaces being
creat
system that has Qt6, GStreamer,
Wayland and Weston.
We are having a problem displaying the video stream from GStreamer on a
QWidget. In the past we had this working with Qt5 and older GStreamer,
Wayland and Weston.
A simple test program also shows the issue on Fedora37 with QT6 and
KDE/Plasma
Hi,
On Thu, Feb 22, 2024 at 03:21:01PM +, Terry Barnaby wrote:
> Hi,
>
> We are developing a video processing system that runs on an NXP imx8
> processor using a Yocto embedded Linux system that has Qt6, GStreamer,
> Wayland and Weston.
>
> We are having a problem displa
Hi,
We are developing a video processing system that runs on an NXP imx8
processor using a Yocto embedded Linux system that has Qt6, GStreamer,
Wayland and Weston.
We are having a problem displaying the video stream from GStreamer on a
QWidget. In the past we had this working with Qt5 and
Hi,
Work towards adding this functionality is discussed at
https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1258
On Tue, Jan 23, 2024 at 01:13:20PM +, Namit Solanki (QUIC) wrote:
> Hi Weston team,
>
> For the use cases where the GPU composed output (output of
>
1 - 100 of 1001 matches
Mail list logo
