On Tue, 16 Oct 2018 at 08:17, Peter Hutterer wrote:
> On Mon, Oct 15, 2018 at 10:49:24AM -0400, Harry Wentland wrote:
> > + \item Support free and open source projects through the
> > freedesktop.org
> > + infrastructure. For projects outside the scope of item (\ref{1})
> > support
> > +
Hi,
On Fri, 26 Oct 2018 at 11:57, Daniel Vetter wrote:
> On Fri, Oct 26, 2018 at 10:13:51AM +1000, Peter Hutterer wrote:
> > On Wed, Oct 17, 2018 at 02:37:25PM +0200, Daniel Vetter wrote:
> > > On Wed, Oct 17, 2018 at 2:05 PM Daniel Stone wrote:
> > > > Yeah, I thi
require any future
> clients to use MAP_PRIVATE if they use a seat version above 6.
>
> If a compositor can't use sealing or a similar facility, it should
> still protect itself with copied keymaps, but clients must always
> assume s
Hi Simon,
Thanks a lot for taking this on! :)
On Thu, 1 Nov 2018 at 16:45, Simon Ser wrote:
> This commit introduces a new wp_linux_dmabuf_device_hints object. This object
> advertizes a preferred device via a file descriptor and a set of preferred
> formats/modifiers.
s/advertizes/advertises/g
Hi Alexandros,
On Tue, 8 Aug 2017 at 15:25, Alexandros Frantzis
wrote:
> This protocol specifies a set of interfaces used to control the alpha
> compositing and blending of surface contents.
>
> It's based on the Chromium Wayland protocol of the same name ([1]),
> with a few changes made to the b
Hi,
On Thu, 8 Nov 2018 at 13:01, Pekka Paalanen wrote:
> On Wed, 07 Nov 2018 20:22:38 + Simon Ser wrote:
> > I missed this before, but: is there a reason why the "linux" prefix has been
> > dropped here? Maybe it should be renamed to
> > zwp_linux_surface_synchronization_v1? What about zwp_b
id, Daniel, since your name is in the maintainers, can I have your
> R-b, please?
The protocol is:
Reviewed-by: Daniel Stone
The Weston implementation looks pretty good so far, though there's no
full implementation of release yet.
Cheers,
Daniel
___
Hi Scott,
[As a general note, I'm on holiday in Australia this month and not
back at work until mid-Jan, so am not reading email very attentively;
if there's something I should be looking at, please either directly CC
me on this address rather than my work email, or poke me on IRC.]
On Fri, 21 Dec
Hi Pekka,
On Sat, 12 Jan 2019 at 12:55, Pekka Paalanen wrote:
> since meson is there and autotools on its final count-down, let's update
> the main Weston build guide to use Meson.
Looks good, thanks for doing this. Series is:
Reviewed-by: Daniel Stone
> Things that would need
Hi Emre,
On Sat, 19 Jan 2019 at 20:39, Ucan, Emre (ADITG/ESB)
wrote:
> I would like to push XDG shell support for ivi-shell:
> https://gitlab.freedesktop.org/wayland/weston/merge_requests/86
>
> It would be great if you and other maintainers can ack and/or review this
> merge request till begin
Hi Harish,
On Wed, 23 Jan 2019 at 09:35, Pekka Paalanen wrote:
> On Wed, 23 Jan 2019 11:32:34 +0530 Harish Krupo
> wrote:
> > Proposal 1:
> > * Each of the shaders (gamma/degamma/main/tone mapping) would be
> > independent strings.
> > * When the view needs to be rendered, renderer will gener
se be _very_ careful
that you are replying to the original sender (in Reply-To) and not the
list itself.
Cheers,
Daniel
-- Forwarded message -----
From: Daniel Stone
Date: Mon, 11 Feb 2019 at 23:38
Subject: PSA: Mailman changes, From addresses no longer accurate
To: ,
Hi all,
We hav
Hi Scott,
On Mon, 18 Feb 2019 at 03:27, Scott Anderson
wrote:
> In the Weston implementation, it's simply a case of the compositor
> getting the fence from the client, using eglWaitSyncKHR (or equivilent)
> on it, and passing back a release fence from OUT_FENCE_FD.
Yep, that's pretty much the MV
ecause people apparently do use wl_output's
> refresh rate for synchronization purposes in Firefox [1]. I think it
> would be a good thing to make sure people are aware they should be using
> frame callbacks instead.
Thanks a lot for bumping this. Patch i
Hi,
On Fri, 25 Jan 2019 at 16:05, Derek Foreman
wrote:
> On 1/18/19 4:20 PM, Derek Foreman wrote:
> > Does anyone have objections to an early February freeze and a March
> > release? Anyone with large series near completion?
> >
> > Also, I'd like to float the idea of removing the fbdev backend
On Mon, 18 Feb 2019 at 10:13, Scott Anderson
wrote:
> On 18/02/19 11:02 pm, Daniel Stone wrote:
> > Doing this gets _really_ tricky as you start considering things like
> > synchronised subsurfaces (which always seems to be the case), since
> > you have to make sure
Hi all,
I'd like to open up a discussion on enlarging wayland-protocols to a
wider audience, with a better definition of what it contains.
Currently, wayland-protocols is a relatively small set of protocols
which were either grandfathered in from Weston, or a semi-opinionated
set of protocols that
Hi,
On Tue, 19 Feb 2019 at 18:36, Drew DeVault wrote:
> On 2019-02-19 4:50 PM, Daniel Stone wrote:
> > - other clients: Chromium (client), Firefox, Mesa (EGL/Vulkan)
>
> This might start getting out of hand, I think. Here's an incomplete list
> of clients
Hi James,
On Fri, 22 Feb 2019 at 13:55, James Feeney wrote:
> On 2/21/19 12:10 PM, Simon Ser wrote:
> > Sorry, these comments feel a bit off-topic here. I'd appreciate if we
> > could stay focused. Thanks!
>
> And, what topic would that be, then, given that the subject of the thread is
> "waylan
A common request is to split single large patch into multiple patches. This
> can
> +happen, for example, if when adding a new feature you notice a bug in
> Weston's
And again.
But the rest looks good to me and I'm thrilled to see it, so:
Reviewed-by: Daniel Stone
Ch
to go, then all we need to do is the appropriate small tweaks
when we finalise things. I don't expect to have time to do this any
time soon; I can certainly help others through it if you have issues
or questions, but volunteers would be very much welcome.
On Fri, 22 Feb 2019 at 02:39, Drew DeVaul
On Fri, 5 Apr 2019 at 14:52, Derek Foreman
wrote:
> I no longer have as much time to dedicate to this as I used to, so I
> think it would be best if someone else could take over managing the
> releases for Weston and Wayland.
Thanks for everything Derek! Really appreciate what you've done over
th
Hi,
On Mon, 8 Apr 2019 at 11:02, Pekka Paalanen wrote:
> On Fri, 05 Apr 2019 18:01:45 + Simon Ser wrote:
> > Regarding the need for a new release manager for Wayland, I'd like to
> > step in and volunteer for this role. I'm willing to take the time
> > necessary to (1) learn the current rele
Hi Drew,
Thanks for writing this up! I think the broad concept is fine, but a
few things jump out at me:
On Fri, 5 Apr 2019 at 19:43, Drew DeVault wrote:
> I've written up a governance document for us to bikeshed, which is
> included at the end of this email. Some comments upfront.
>
> Logistical
Hi,
On Wed, 13 Mar 2019 at 01:03, Drew DeVault wrote:
> On 2019-03-08 11:28 AM, Daniel Stone wrote:
> > Under what he's describing, xdg_shell isn't miscategorised, because it
> > _is_ the thing that everyone agrees on and uses. If we reserve xdg_*
> > for uncont
Hi,
On Wed, 1 May 2019 at 09:53, Pekka Paalanen wrote:
> On Wed, 24 Apr 2019 10:07:47 -0700 Chia-I Wu wrote:
> > Can you commit this patch for me, if all looks good?
>
> I was almost already pushing this, but Daniel said he wants to have
> a good look first.
Indeed, I hadn't followed the discus
t 'done', and ideally have it come in
the same version bump, but with that and one small nitpick resolved
this is:
Acked-by: Daniel Stone
- xdg_output_manager.get_xdg_output). This event is only sent once per
+ xdg_output_manager.get_xdg_output) and whenever the description
+
Hi,
On Mon, 24 Jun 2019 at 09:00, Jonas Ådahl wrote:
> On Fri, Jun 21, 2019 at 05:35:35PM -0700, Jasper St. Pierre wrote:
> > To be clear, the patch does break backwards compatibility with compositor
> > behavior -- it only weakens a guarantee by saying that transparent
> > fullscreen content is
Hi Drew,
Sorry for the long delay - has taken a while to catch up after
holidays. Thanks for pushing this forward though.
On Mon, 6 May 2019 at 01:41, Drew DeVault wrote:
> I chose not to change the wording of the xdg namespace definition,
> despite Daniel's objection. I couldn't come up with a w
Hi Barry,
On Sun, 21 Jul 2019 at 00:33, Barry Song <21cn...@gmail.com> wrote:
> if i want to send the framebuffers using DRM backend as the video src
> in gstreamer to networks through rtsp, does weston have an existing
> solution.
>
> i mean something similar with the below for /dev/fb0 backend:
On Thu, 25 Jul 2019 at 04:34, HalleyZhao wrote:
> in Mesa, I could find some implement for vulkan, but not for EGL.
>
> maybe, desktop developer care more on mesa than mobile developers, and most
> desktop driver does implicitly sync instead of depending on
> explicit-synchronization-unstable-v1
On Thu, 25 Jul 2019 at 10:17, HalleyZhao wrote:
> looking for an example to use in EGL
Weston itself provides an example of using dma-fences with EGL - both
extracting them from EGL to refer to previous rendering, and asking
EGL to wait on them.
If you're looking for an example of how you would
On Fri, 9 Aug 2019 at 10:47, HalleyZhao wrote:
> some buffer attributes may influence how weston use it, for example: tiling
> mode, Swizzling, compression.
> weston may depend on these attribute to decide to assign the buffer to a hw
> plane or composite it as texture.
Yes. The open-source dri
Hi Sichem,
On Mon, 26 Aug 2019 at 02:38, Sichem Zhou wrote:
> I found that currently there is no way to change `xkb_keymap` after Weston is
> running.
>
> By different backends, xkb_info in wayland works differently, for example,
> the wayland and x11 backend, weston_keyboard is initialized wit
y: Pekka Paalanen
>
> Do you need me to land this?
>
> Since wayland-protocols is still using email workflow, please give all
> your Reviewed-by and Acked-by tags explicitly.
With the same rationale - this will only hurt people generating rich
bindings, who are the exact peopl
Hi Sichem,
On Sat, 31 Aug 2019 at 03:01, Sichem Zhou wrote:
> I hope to make a follow up to this thread. I made a change and submitted to
> MR but it seemed to gain little interest so I am trying my luck here.
>
> My problem is that I need to change `xkb_keymap` in the Weston run time,
> though
On Thu, 10 Oct 2019 at 01:21, Simon Ser wrote:
> This is v4 of the proposal.
>
> Changes from v3 to v4: relax implementation requirements for inclusion
> in "xdg" and "wp" (Jonas, Drew).
>
> Diff: https://
utter: Jonas Ådahl @jadahl
* KWin: Roman Gilg @romangg
* Qt: Johan Helsing @johanhelsing
* Weston: Daniel Stone @daniels, Pekka Paalanen @pq
* wlroots (& its users): Drew DeVault @ddevault, Simon Ser @emersion
If we find interest from other projects, we can use their membership
applic
Hi,
On Thu, 14 Nov 2019 at 22:44, Scott Anderson wrote:
> On 15/11/19 4:04 am, Drew DeVault wrote:
> > I think that there would be value in being able to suggest that a
> > particluar buffer be scanned out for performance reasons. But, as a
> > suggestion, and not a demand, and definitely not for
Hi,
On Tue, 19 Nov 2019 at 11:48, Guillermo Rodriguez
wrote:
> El mar., 19 nov. 2019 a las 11:47, Pekka Paalanen ()
> escribió:
> > If the OSD is just a piece of a bigger application and only needs to be
> > on top of that application's windows, you could probably use xdg
> > extensions or a sub
Hi Drew,
On Thu, 27 Feb 2020 at 22:43, Drew DeVault wrote:
> I rigged up SourceHut CI for use with gitlab.fd.o several months ago, as
> part of investigation to see if wlroots and sway could be moved there.
> It's still set up - anyone with a sr.ht account can go to dispatch.sr.ht
> and create a
Hi Matt,
On Thu, 27 Feb 2020 at 23:45, Matt Turner wrote:
> We're paying 75K USD for the bandwidth to transfer data from the
> GitLab cloud instance. i.e., for viewing the https site, for
> cloning/updating git repos, and for downloading CI artifacts/images to
> the testing machines (AFAIU).
I b
On Fri, 28 Feb 2020 at 03:38, Dave Airlie wrote:
> b) we probably need to take a large step back here.
>
> Look at this from a sponsor POV, why would I give X.org/fd.o
> sponsorship money that they are just giving straight to google to pay
> for hosting credits? Google are profiting in some minor
On Fri, 28 Feb 2020 at 08:48, Dave Airlie wrote:
> On Fri, 28 Feb 2020 at 18:18, Daniel Stone wrote:
> > The last I looked, Google GCP / Amazon AWS / Azure were all pretty
> > comparable in terms of what you get and what you pay for them.
> > Obviously providers like Packet
On Fri, 28 Feb 2020 at 10:06, Erik Faye-Lund
wrote:
> On Fri, 2020-02-28 at 11:40 +0200, Lionel Landwerlin wrote:
> > Yeah, changes on vulkan drivers or backend compilers should be
> > fairly
> > sandboxed.
> >
> > We also have tools that only work for intel stuff, that should never
> > trigger an
Hi Jan,
On Fri, 28 Feb 2020 at 10:09, Jan Engelhardt wrote:
> On Friday 2020-02-28 08:59, Daniel Stone wrote:
> >I believe that in January, we had $2082 of network cost (almost
> >entirely egress; ingress is basically free) and $1750 of
> >cloud-storage cost (almost all
Hi Tomek,
On Mon, 16 Mar 2020 at 12:55, Tomek Bury wrote:
> I've been wrestling with the sync problems in Wayland some time ago, but only
> with regards to 3D drivers.
>
> The guarantee given by the GL/GLES spec is limited to a single graphics
> context. If the same buffer is accessed by 2 cont
Hi,
On Mon, 16 Mar 2020 at 15:33, Tomek Bury wrote:
> > GL and GLES are not relevant. What is relevant is EGL, which defines
> > interfaces to make things work on the native platform.
> Yes and no. This is what EGL spec says about sharing a texture between
> contexts:
Contexts are different tho
Hi Oliver,
On Wed, 25 Mar 2020 at 10:31, Wohlmuth, Oliver
wrote:
> I just started to work with Wayland/Weston, so please forgive me if I ask
> silly questions.
>
> I’m running Weston (8.0.0) on a custom ARM SoC using the DRM backend. As the
> OpenGL
> driver is not (yet) adapted for Wayland, I'
Hi,
On Mon, 27 Apr 2020 at 10:02, Pekka Paalanen wrote:
> On Mon, 27 Apr 2020 15:07:20 +0800 zou lan wrote:
> > I read some documents about chrome OS run Android Apks such as
> > https://qiangbo-workspace.oss-cn-shanghai.aliyuncs.com/2019-09-10-chromeos-with-android-app/Arcpp_Graphics.pdf
> > A
Hi,
On Thu, 18 Jun 2020 at 07:25, Brad Robinson
wrote:
> I'm putting together a set of C# bindings for Wayland and it's coming along
> nicely but I've hit an issue with wl_registry_bind where its implementation
> doesn't seem to match the xml.
>
> The wayland.xml file declares it as: (essential
Hi,
On Thu, 25 Jun 2020 at 10:01, Brad Robinson
wrote:
> As a toolkit developer coming from Windows/OSX this is fairly shocking. I'm
> aware of the decoration protocol, but given it's not supported (and by the
> sound of it never will be) on some of the major distros makes it almost
> worthle
Hi,
On Wed, 1 Jul 2020 at 20:13, Simon Ser wrote:
> On Wednesday, July 1, 2020 8:49 PM, Jan Engelhardt wrote:
> > Usecases.. checking for releases, both new and, sometimes historic research,
> > old ones.
> >
> > A fileindex has a "tabular" appearance where each "row" contains filename
> > and
Hi,
On Thu, 9 Jul 2020 at 15:38, Pekka Paalanen wrote:
> On Thu, 9 Jul 2020 10:32:56 +0200
> Olivier Fourdan wrote:
> > In the meantime, Peter has already submitted patches to wayland-info
> > (thanks Peter!) so the tip of wayland-info is different from
> > weston-info (basically, we have diverg
Hi Arunkumar,
On Mon, 27 Jul 2020 at 06:59, arunkrish20 wrote:
> We are working with the i.MX8 platform. We are working with weston and DRM
> backend. Below are the version details.
>
> NXP BSP Version: 4.14.98_2.0.0_ga
> SC Firmware Version : 1.3.1
> wayland version 1.16 am
> weston- ivi - 5.0.
Hi,
On Sat, 1 Aug 2020 at 06:28, Vadivelu Babu, Surendar (S.)
wrote:
> As Arun stated , we tried to boot the Weston application from initramfs ,
> however there is “pam” library dependency which is required for Weston . When
> we include all the “pam” libraries the initramfs size increases from
Hi Leo,
On Mon, 9 Nov 2020 at 16:17, enpeng xu wrote:
> I have a question about the functions of wl_display_dispatch/wl_display_poll.
> In the function wl_display_poll, it ignores EINTR and keeps polling until it
> gets an event from remote.
> I am not sure if this is the expected, but a typical
Hi Nimi,
On Mon, 21 Dec 2020 at 18:50, Nimi Wariboko Jr. wrote:
> The crux of the issue is that when we create our OpenGL context we create it
> with a display connection that we initiate. Further down the line when we
> need to create a wl_egl_window, we are given a wl_surface that was created
Hi all,
Going with a lot of other Git-based projects (and following the leads of
e.g. GitHub and GitLab), freedesktop.org is planning to change the default
branch name for its new projects to 'main' rather than 'master'.
Mesa is already migrating, and they have helpfully prepared a small Python
sc
On Thu, 8 Apr 2021 at 14:02, Jan Engelhardt wrote:
> On Thursday 2021-04-08 13:20, Daniel Stone wrote:
> >I propose that we do this for all the wayland/* repositories, either this
> weekend or next; I'm happy
> >to make the changes (rename 'master' to 'ma
Hi,
On Mon, 19 Apr 2021 at 13:06, Simon Ser wrote:
> I'm working on a Wayland extension [1] that, among other things, allows
> compositors to advertise the preferred device to be used by Wayland
> clients.
>
> In general, compositors will send a render node. However, in the case
> of split rende
Hi all,
On Thu, 8 Apr 2021 at 12:20, Daniel Stone wrote:
> I propose that we do this for all the wayland/* repositories, either this
> weekend or next; I'm happy to make the changes (rename 'master' to 'main'
> and retarget all open MRs). Does anyone have any
Hi,
On Wed, 26 May 2021 at 10:30, Pekka Paalanen wrote:
> On Tue, 25 May 2021 22:10:38 -0500 Igor Korot wrote:
> > > Positioning - Don't position and Wayland discourages it by not having
> > > such an
> > > API. Sizing - do whatever you like.
> >
> > It just discourages it, so it is not complet
Hi RyunHyeon,
On Tue, 8 Jun 2021 at 11:55, 김륜현 (RH Kim) wrote:
> Hello, I want to output weston to specific display. So I searched about
> Weston option.
>
>
> I found "--connector" option.
>
> This option configures specific display for output
>
>
> However, I checked the mailing list that said
Sorry for the mobile reply, but V4L2 is absolutely not write-only; there has
never been an intersection of V4L2 supporting dmabuf and not supporting reads.
I see your point about the heritage of dma_resv but it’s a red herring. It
doesn’t matter who’s right, or who was first, or where the code w
Hi Alyssa,
On Tue, 27 Jul 2021 at 20:30, Alyssa Ross wrote:
> Hi! I'm Alyssa and I'm working on Spectrum[1], which is a project
> aiming to create a compartmentalized desktop Linux system, with high
> levels of isolation between applications.
I've seen, it's neat!
> One big issue for us is pro
On Thu, 5 Aug 2021 at 21:15, David Deyo wrote:
> I was able to re-create the files of your patch and added them into my
> build tree.
>
>
>
> Not having an accelerometer, I’ve had to make a few changes.
>
> When you said, ‘It had issues’, I am also seeing some issues.
>
>
>
> I can rotate my scre
Hi David,
On Thu, 5 Aug 2021 at 22:17, David Deyo wrote:
> > Sounds like you're missing wl_display_flush() in your client code, so the
> > requests don't make it to the socket buffer until they're forced to because
> > it's filled up.
>
> That did it. You guys are awesome. I don’t suppose the
Hi Guillermo,
On Fri, 6 Aug 2021 at 10:44, Guillermo Rodriguez Garcia
wrote:
> El vie, 6 ago 2021 a las 10:14, Daniel Stone ()
> escribió:
>> kiosk-shell is something we have in newer versions of Weston which
>> sounds like it would work well for your usecases - it's de
Hi Chris,
On Fri, 5 Nov 2021 at 12:01, chris.lapla...@agilent.com
wrote:
> Can anyone please explain how eglGetConfigs actually works? i.e. what
> information is it consulting in order to determine the configs to return?
> Unfortunately we are using a processor (Xilinx Zynq UltraScale) with a G
Hi Rusty,
On Fri, 10 Dec 2021 at 20:38, Rusty Howell wrote:
> We are working on an embedded linux device built using Yocto (dunfell). We
> have weston running and we are seeing our QT5 application running as well.
> One problem we are having is that our application is crashing weston if the
Hi Egy,
On Mon, 16 May 2022 at 15:09, Egy Ketto wrote:
> I'm digging the source code of wayland and weston. I'm stuck at getting the
> code generated by wayland-scanner. I was following the build instructions for
> wayland:
>
> $ git clone https://gitlab.freedesktop.org/wayland/wayland.git
> $
On Mon, 13 Jun 2022 at 05:17, Peter Hutterer wrote:
> On Sun, Jun 12, 2022 at 05:57:05PM -0700, Jeremy Sequoia wrote:
> > I was going to spend a little bit of time putting out an update to XQuartz
> > to address a few bugs that I've been meaning to squash, but I'm having a bit
> > of an issue pull
Hi,
On Mon, 13 Jun 2022 at 08:39, Daniel Stone wrote:
> Yes, that's what's happening. Our (multi-host-replicated etc) Ceph
> storage setup has entered a degraded mode due to the loss of a couple
> of disks - no data has been lost but the cluster is currently unhappy.
>
Hi,
On Tue, 14 Jun 2022 at 15:40, Zack Rusin wrote:
> On Tue, 2022-06-14 at 10:36 +0300, Pekka Paalanen wrote:
> > The reason I am saying that you need to fix other issues with
> > virtualized drivers at the same time is because those other issues are
> > the sole and only reason why the driver w
Hi Jim,
On Fri, 29 Jul 2022 at 08:30, Jim Shargo wrote:
> TL;DR: I'm working on extending VKMS and wanted feedback from other
> compositor/wayland devs.
Awesome! :) Glad to see it, and yeah, I second everything Pekka said.
Having hotplug in particular would be really great.
> // Questions
>
>
Hi all,
On Fri, 5 Aug 2022 at 10:42, Jean-Michaël Celerier
wrote:
> [lots of musing about win32 snipped]
>
> It would make me pretty sad to tell these people (both end-users and devs)
> that Windows is a better operating system for their use case than desktop
> Linux.
OK, this discussion is cl
On Fri, 5 Aug 2022 at 14:11, samuel ammonius wrote:
> Please don't close this discussion on account of something someone
> else said. Wouldn't it be better for users, compositors, and apps if there
> was a way to manage window positions, but the compositor could choose
> not to let them? The best
On Fri, 5 Aug 2022 at 17:21, Igor Korot wrote:
> On Thu, Aug 4, 2022 at 9:20 PM Thiago Macieira wrote:
> > No, they are about position too. 100,100 on a 1920x1080 resolution is about
> > 5%
> > to the right of the left edge and 10% from the top. 100,100 on 3840x2160 is
> > 2.5% from the left and
Igor,
On Mon, 8 Aug 2022 at 15:54, Igor Korot wrote:
> Or even better - when one of you will need to quickly create a
> "proof-of-concept" application that will jump all over the places on every
> startup...
We've written applications for years. We know how to make it work.
We've explained to
Hi Samuel,
On Mon, 8 Aug 2022 at 17:04, samuel ammonius wrote:
> On Mon, Aug 8, 2022 at 12:06 PM Simon Ser wrote:
>> If you are not interested in explaining the use-cases, and are just
>> interested in blindly adding new features: sorry, but this isn't how we
>> want to approach things.
>
> Sorr
vices present, will hit this.
Signed-off-by: Daniel Stone
Reported-by: Thierry Reding
Reported-by: Daniel Vetter
---
libweston/compositor-drm.c | 92 --
1 file changed, 57 insertions(+), 35 deletions(-)
v2: Unbreak logind, which only allows a device
vices present, will hit this.
Signed-off-by: Daniel Stone
Reported-by: Thierry Reding
Reported-by: Daniel Vetter
---
libweston/compositor-drm.c | 92 --
1 file changed, 57 insertions(+), 35 deletions(-)
diff --git a/libweston/compositor-drm.c b/libw
Hi,
On 13 January 2017 at 11:42, Pekka Paalanen wrote:
> Weston's desktop-shell uses an event from the helper client to signal
> when it is ready, and fades in only after that (if the fade-in
> animation is enabled). I understand you want to keep the boot splash
> image instead, but keep that eve
Hi,
On 15 January 2017 at 18:07, Quentin Glidic
wrote:
> On 15/01/2017 18:54, Emmanuel Gil Peyrot wrote:
>> This makes the background image look much nicer, at the expense of
>> slightly more memory bandwidth used.
>>
>> Signed-off-by: Emmanuel Gil Peyrot
>
> I see no reason not to:
> Reviewed-b
Hi Quentin,
On 15 January 2017 at 13:05, Quentin Glidic
wrote:
> On 29/11/2016 18:00, Daniel Stone wrote:
>> We had two non-pkg-config check paths in the configure script, to
>> support XCB functionality used before XCB had had an accompanying
>> release: xcb_poll_for_queu
ever trigger. With that fixed (i.e. the dep being on glib-2.0
instead):
Reviewed-by: Daniel Stone
Cheers,
Daniel
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
The manpage claims that none is valid, so let's make it so.
Signed-off-by: Daniel Stone
---
clients/desktop-shell.c | 25 -
1 file changed, 12 insertions(+), 13 deletions(-)
diff --git a/clients/desktop-shell.c b/clients/desktop-shell.c
index bd0032a..b133d86 1
The desktop-shell output destroy code assumes that we always set up a
panel listener. Initialise its list explicitly, so if we don't have a
panel, then we can still unconditionally destroy the listener on output
destroy.
Signed-off-by: Daniel Stone
---
desktop-shell/shell.c | 1 +
1
ing merged, this is:
Reviewed-by: Daniel Stone
Cheers,
Daniel
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Hi,
On 17 December 2016 at 12:40, Quentin Glidic
wrote:
> Currently, layers’ order depends on the module loading order and it does
> not survive runtime modifications (like shell locking/unlocking).
> With this patch, modules can safely add their own layer at the expected
> position in the stack,
ick up, rather than
blithely configuring our own.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 27 ++-
1 file changed, 22 insertions(+), 5 deletions(-)
diff --git a/libweston/compositor-drm.c b/libweston/compositor-drm.c
index ecc872e..030f82f 100644
Hi,
On 16 January 2017 at 15:12, Quentin Glidic
wrote:
> Hey, didn’t it work already? A tiny warning is no big. ;-)
Nope, it warned and then left the panel on the left.
> Anyway:
> Reviewed-by: Quentin Glidic
Thanks! Pushed both, and your manpage fix:
To ssh://git.freedesktop.org/git/wayland/
Hi,
On 21 November 2016 at 11:07, Jan Engelhardt wrote:
> On Monday 2016-11-21 12:00, Daniel Stone wrote:
>>COMPOSITOR_LIBS is full of -Lfoo -lsyslib. To the best of my
>>knowledge, these belong in LDADD
>
> Negative. _LDADD is ignored for library type outputs, and _LI
e_init -> wet_shell_init, but just typing
that out makes me realise it may be more effort than it's worth.
Either way, with 2/5 properly split (or convince me why it's necessary
to combine them), let's get this merged early:
Reviewed-by: Daniel Stone
Cheers,
ane, and the vblank events for the planes, to arrive before
disarming the timer. Without doing that, we could get a false
negative: if the pageflip completion arrives but not the vblank event,
we'll disarm the event, but not actually resume repaint.
With that fixed:
Reviewed-by
, &refresh);
> + if (n != 2 && n !=3) {
This should be 'n != 3' (space on both sides). Generally I'd just fix
this up when applying since it's so trivial, but I'd like this to be
changed to 'WxH@R' rather than 'Wx
Hi Dima,
On 30 November 2016 at 20:10, Dima Ryazanov wrote:
> This can happen if you right-click in weston-terminal a few times very
> quickly.
> The pointer_handle_enter callback already checks for NULL, so let's do that in
> keyboard_handle_enter, too.
Good catch, thanks! Pushed with review:
Hi,
On 10 December 2016 at 00:21, Daniel Stone wrote:
> On 9 December 2016 at 21:58, Armin Krezović wrote:
>> +#ifdef ENABLE_EGL /* Defined but not used */
>> +#ifdef ENABLE_EGL /* Force pixman when EGL support is disabled */
>> b->use_pixman = new_confi
hardware plane, skipping GPU composition.
In light of all this, just remove the test.
Signed-off-by: Daniel Stone
---
Makefile.am | 7 --
protocol/weston-test.xml | 7 --
tests/buffer-count-test.c | 172 --
tests
501 - 600 of 2140 matches
Mail list logo
