Acked-by: Jason Ekstrand
On Thu, Jun 28, 2018 at 6:26 AM, Johan Klokkhammer Helsing <
johan.hels...@qt.io> wrote:
> Although it would probably default to the license at the root of the
> repository anyway, it's best to be explicit about it, and also be
> consistent with
Sorry to drag up ancient threads, but what's the status of this? I see
rumors that it's in Weston. Is it stable? Is it implemented anywhere
else? It'd be great, for the sake of Vulkan, if we could get this stable
and everywhere.
--Jason
On Mon, Dec 17, 2018 at 11:25 AM Tomek Bury wrote:
> T
On Fri, Feb 28, 2020 at 11:00 AM Rob Clark wrote:
>
> On Fri, Feb 28, 2020 at 3:43 AM Michel Dänzer wrote:
> >
> > On 2020-02-28 10:28 a.m., Erik Faye-Lund wrote:
> > >
> > > We could also do stuff like reducing the amount of tests we run on each
> > > commit, and punt some testing to a per-weeke
On Sat, Feb 29, 2020 at 3:47 PM Timur Kristóf wrote:
>
> On Sat, 2020-02-29 at 14:46 -0500, Nicolas Dufresne wrote:
> > >
> > > 1. I think we should completely disable running the CI on MRs which
> > > are
> > > marked WIP. Speaking from personal experience, I usually make a lot
> > > of
> > > cha
I don't think we need to worry so much about the cost of CI that we need to
micro-optimize to to get the minimal number of CI runs. We especially
shouldn't if it begins to impact coffee quality, people's ability to merge
patches in a timely manner, or visibility into what went wrong when CI
fai
hort order.
Again, sorry I was so terse. I was just trying to slow the panic.
> Le dimanche 01 mars 2020 à 14:18 -0600, Jason Ekstrand a écrit :
> > I've seen a number of suggestions which will do one or both of those things
> > including:
> >
> > - Batching m
on to start moving others and maybe we can actually build the
momentum to get most everything converted.
For reference, you can find the kernel RFC patches and mesa MR here:
https://lists.freedesktop.org/archives/dri-devel/2020-March/258833.html
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4037
At this point, I welcome your thoughts, comments, objections, and
maybe even help/review. :-)
--Jason Ekstrand
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
On Wed, Mar 11, 2020 at 12:31 PM Jason Ekstrand wrote:
>
> All,
>
> Sorry for casting such a broad net with this one. I'm sure most people
> who reply will get at least one mailing list rejection. However, this
> is an issue that affects a LOT of components and that'
very much want to solve the problem "properly" but unless
we're very sure we can get it solved properly everywhere quickly, a
solution which lets us improve our driver kernel APIs independently of
misc. Wayland compositors seems advantageous.
On Wed, Mar 11, 2020 at 6:02 PM Adam Jack
explain it.)
--Jason
On March 13, 2020 21:03:21 Marek Olšák wrote:
There is no synchronization between processes (e.g. 3D app and compositor)
within X on AMD hw. It works because of some hacks in Mesa.
Marek
On Wed, Mar 11, 2020 at 1:31 PM Jason Ekstrand wrote:
All,
Sorry for casting such a
On Mon, Mar 16, 2020 at 5:20 AM Laurent Pinchart
wrote:
>
> On Wed, Mar 11, 2020 at 04:18:55PM -0400, Nicolas Dufresne wrote:
> > (I know I'm going to be spammed by so many mailing list ...)
> >
> > Le mercredi 11 mars 2020 à 14:21 -0500, Jason Ekstrand a écrit :
>
On Mon, Mar 16, 2020 at 10:33 AM 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:
>
> "OpenGL and OpenGL ES m
On Mon, Mar 16, 2020 at 4:15 PM Laurent Pinchart
wrote:
>
> Hi Jason,
>
> On Mon, Mar 16, 2020 at 10:06:07AM -0500, Jason Ekstrand wrote:
> > On Mon, Mar 16, 2020 at 5:20 AM Laurent Pinchart wrote:
> > > On Wed, Mar 11, 2020 at 04:18:55PM -0400, Nicolas Dufresne wrote:
On Mon, Mar 16, 2020 at 6:39 PM Roman Gilg wrote:
>
> On Wed, Mar 11, 2020 at 8:21 PM Jason Ekstrand wrote:
> >
> > On Wed, Mar 11, 2020 at 12:31 PM Jason Ekstrand
> > wrote:
> > >
> > > All,
> > >
> > > Sorry for casting such a b
On Tue, Mar 17, 2020 at 3:01 AM Simon Ser wrote:
>
> On Monday, March 16, 2020 5:04 PM, Jason Ekstrand
> wrote:
>
> > Hopefully, that will provide some motivation for other compositors
> > (kwin, gnome-shell, etc.) because they now have a real user of it in
> >
On Tue, Mar 17, 2020 at 10:33 AM Nicolas Dufresne wrote:
>
> Le lundi 16 mars 2020 à 23:15 +0200, Laurent Pinchart a écrit :
> > Hi Jason,
> >
> > On Mon, Mar 16, 2020 at 10:06:07AM -0500, Jason Ekstrand wrote:
> > > On Mon, Mar 16, 2020 at 5:20 AM Laurent Pinch
On Tue, Mar 17, 2020 at 12:13 PM Jacob Lifshay wrote:
>
> One related issue with explicit sync using sync_file is that combined
> CPUs/GPUs (the CPU cores *are* the GPU cores) that do all the
> rendering in userspace (like llvmpipe but for Vulkan and with extra
> instructions for GPU tasks) but ne
On Tue, Mar 17, 2020 at 7:16 PM Jacob Lifshay wrote:
>
> On Tue, Mar 17, 2020 at 11:14 AM Lucas Stach wrote:
> >
> > Am Dienstag, den 17.03.2020, 10:59 -0700 schrieb Jacob Lifshay:
> > > I think I found a userspace-accessible way to create sync_files and
> > > dma_fences that would fulfill the re
On Wed, Mar 18, 2020 at 12:20 AM Jacob Lifshay wrote:
>
> On Tue, Mar 17, 2020 at 7:08 PM Jason Ekstrand wrote:
> >
> > On Tue, Mar 17, 2020 at 7:16 PM Jacob Lifshay
> > wrote:
> > >
> > > On Tue, Mar 17, 2020 at 11:14 AM Lucas Stach wrote:
> >
First off, I think you all did a fantastic job. I felt that things
ran very smoothly and, as far as the talks themselves go, I think it
went almost as smoothly as an in-person XDC. I'm really quite
impressed. I do have a couple pieces of more nuanced feedback:
1. I think we were maybe a bit to
Adding mesa-dev and wayland-devel for broader circulation.
On Wed, Mar 17, 2021 at 5:19 PM Jason Ekstrand wrote:
>
> Modern userspace APIs like Vulkan are built on an explicit
> synchronization model. This doesn't always play nicely with the
> implicit synchronization used
On Tue, Mar 23, 2021 at 2:06 PM Simon Ser wrote:
>
> From a user-space point-of-view, this looks super useful! The uAPI sounds
> good to me.
>
> Acked-by: Simon Ser
>
> Would be nice to have some short docs as well. Here's an example of a
> patch adding some docs for an ioctl [1], if you aren't f
y for now.
Mesa MR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4037
IGT tests: https://patchwork.freedesktop.org/series/90490/
v10 (Jason Ekstrand, Daniel Vetter):
- Add reviews/acks
- Add a patch to rename _rcu to _unlocked
- Split things better so import is clearly RFC status
Cc:
y for now.
Mesa MR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4037
IGT tests: https://patchwork.freedesktop.org/series/90490/
v10 (Jason Ekstrand, Daniel Vetter):
- Add reviews/acks
- Add a patch to rename _rcu to _unlocked
- Split things better so import is clearly RFC status
v1
On Thu, Jun 10, 2021 at 3:11 PM Chia-I Wu wrote:
>
> On Tue, May 25, 2021 at 2:18 PM Jason Ekstrand wrote:
> > Modern userspace APIs like Vulkan are built on an explicit
> > synchronization model. This doesn't always play nicely with the
> > implicit synchroni
y for now.
Mesa MR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4037
IGT tests: https://patchwork.freedesktop.org/series/90490/
v10 (Jason Ekstrand, Daniel Vetter):
- Add reviews/acks
- Add a patch to rename _rcu to _unlocked
- Split things better so import is clearly RFC status
v1
had uAPI for a while to ignore fences. Those changes
are years in the past. If we have a real problem here (not sure on
that yet), then we'll have to figure out how to fix it without nuking
uAPI.
--Jason
> Regards,
> Christian.
>
> Am 10.06.21 um 23:09 schrieb Jason Ekstrand:
&g
ext, engine. That amdgpu
> doesn't wait for fences from the same process can be seen as just a
> special case of this.
That doesn't totally solve the issue, though. RADV suffers in the WSI
arena today from too much cross-process implicit sharing. I do think
you want some sort of "ign
y for now.
Mesa MR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4037
IGT tests: https://patchwork.freedesktop.org/series/90490/
v10 (Jason Ekstrand, Daniel Vetter):
- Add reviews/acks
- Add a patch to rename _rcu to _unlocked
- Split things better so import is clearly RFC status
v11 (Dani
y for now.
Mesa MR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4037
IGT tests: https://patchwork.freedesktop.org/series/90490/
v10 (Jason Ekstrand, Daniel Vetter):
- Add reviews/acks
- Add a patch to rename _rcu to _unlocked
- Split things better so import is clearly RFC status
v11 (Dani
On Tue, Feb 9, 2016 at 8:55 AM, Derek Foreman
wrote:
> I saw a presentation once where someone said that even the simplest
> implementation of wayland network transparency that just pushed the
> existing protocol over tcp/ip would still be better than X.
>
> Let's test that theory.
> Hint - appli
buffer_damage allows damage to be registered on a surface
>>> in buffer co-ordinates, avoiding this problem.
>>>
>>> Credit where it's due, these ideas are not entirely my own:
>>> Over a year ago the idea of changing damage co-ordinates to buffer
>>> co-ord
see also the second e-mail link below. I proposed to make
wl_display version 0 so that libraries can detect whether the client
was built against old or new libwayland.
--Jason
> 2015-11-12 22:01 GMT+02:00 Derek Foreman :
>> From: Jason Ekstrand
>>
>> This provides a standardize
On Nov 13, 2015 10:43 AM, "Derek Foreman" wrote:
>
> On 13/11/15 02:03 AM, Pekka Paalanen wrote:
> > On Thu, 12 Nov 2015 13:48:10 -0600
> > Derek Foreman wrote:
> >
> >> On 12/11/15 01:27 PM, Jason Ekstrand wrote:
> >>> Thanks for pic
On Wed, Nov 25, 2015 at 10:15 AM, Derek Foreman wrote:
> On 13/11/15 12:21 PM, Jason Ekstrand wrote:
>> On Fri, Nov 13, 2015 at 3:18 AM, Giulio Camuffo
>> wrote:
>>> So do i understand correctly that if the app creating the
>>> wl_compositor was built against a
On Nov 25, 2015 12:03 PM, "Derek Foreman" wrote:
>
> On 13/11/15 12:21 PM, Jason Ekstrand wrote:
> > On Fri, Nov 13, 2015 at 3:18 AM, Giulio Camuffo
wrote:
> >> So do i understand correctly that if the app creating the
> >> wl_compositor was built aga
ind specific versions of anyway.
>
> Signed-off-by: Derek Foreman
Reviewed-by: Jason Ekstrand
> ---
>
> This follows on Jason's proxy version patch that I rebased
> and reposted a little while ago.
>
> src/wayland-client.c | 33 +++-
; in buffer co-ordinates, avoiding this problem.
>
> Credit where it's due, these ideas are not entirely my own:
> Over a year ago the idea of changing damage co-ordinates to buffer
> co-ordinates was suggested (by Jason Ekstrand), and it was at least
> partially reje
> > in buffer co-ordinates, avoiding this problem.
> > >
> > > Credit where it's due, these ideas are not entirely my own:
> > > Over a year ago the idea of changing damage co-ordinates to buffer
> > > co-ordinates was suggested (by Jason Ekstrand)
On Dec 7, 2015 7:20 AM, "Pekka Paalanen" wrote:
>
> On Wed, 25 Nov 2015 10:25:42 -0800
> Jason Ekstrand wrote:
>
> > On Wed, Nov 25, 2015 at 10:15 AM, Derek Foreman
wrote:
> > > On 13/11/15 12:21 PM, Jason Ekstrand wrote:
> > >> On Fri, Nov
LAND_DISPLAY and WAYLAND_SOCKET. The former is the
catch-all "connect to this socket; it lives in XDG_RUNTIME_DIR." The other
is a mechanism for passing the client a specific file descriptor that it is
expected to use for it's connection. This is usually used for launching
trusted clien
how can
I handle delete_surrounding_text properly?)
>
> 3. Maybe, I’m totally misunderstood about the payload size.
If you're misunderstanding something, it's probably the input_methods
protocol. Unfortunately, my knowledge starts to break down here. I don't
know to
Signed-off-by: Jason Ekstrand
---
src/wayland-client.c | 10 +-
src/wayland-server.c | 10 +-
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/src/wayland-client.c b/src/wayland-client.c
index 363d5dd..799ebab 100644
--- a/src/wayland-client.c
+++ b/src/wayland
In order to keep from overloading the debug handler, we first squash the
entire message into a string and call wl_debug once.
Signed-off-by: Jason Ekstrand
---
src/connection.c | 54 ---
src/wayland-client.c | 6 ++
src/wayland-client.h
Signed-off-by: Jason Ekstrand
---
src/wayland-util.c | 41 +
src/wayland-util.h | 1 +
2 files changed, 42 insertions(+)
diff --git a/src/wayland-util.c b/src/wayland-util.c
index 4fe9c81..c9d6d0e 100644
--- a/src/wayland-util.c
+++ b/src/wayland-util.c
This series adds a wl_debug function and associated handler that can be set
by the uesr. The first patch is merely a rename to prepare for the third.
The second adds a useful helper function used by the third.
Jason Ekstrand (3):
Rename wl_debug to debug_server/client
Add a wl_array_printf
Signed-off-by: Jason Ekstrand
---
This version of the patch adds a wl_array_vprintf function if we want it.
Both versions accomplish exactly the same thing as far as the series is
concerned. However, wl_array_vprintf might be nice in the future. Feel
free to use whichever one you prefer.
src
Pekka,
Thanks for looking at them!
On Thu, Dec 19, 2013 at 2:17 AM, Pekka Paalanen wrote:
> On Wed, 18 Dec 2013 20:56:17 -0600
> Jason Ekstrand wrote:
>
> > This series adds a wl_debug function and associated handler that can
> > be set by the uesr. The first patch
Ander,
I don't neciserally disagree we with this change, but shouldn't the GL
renderer clean up after itself better?
--Jason
On Dec 20, 2013 1:07 PM, "Ander Conselvan de Oliveira"
wrote:
> From: Ander Conselvan de Oliveira
>
> Currently we destroy the renderer before the outputs are destroyed, b
Looks like a good idea to me.
--Jason
On Dec 20, 2013 1:07 PM, "Ander Conselvan de Oliveira"
wrote:
> From: Ander Conselvan de Oliveira
>
> Set the internal pointer for the client to NULL. This fixes a
> segmentation fault at shutdown, where the shell would hang up before
> and cause libwayland
sed to be that wl_touch and wl_keyboard had no
requests (this has since changed) and, at the time, I think we handed in a
null implementation. (This has changed in version 3 of wl_seat and they
now have "release" requests and handlers.)
I'm sorry that I didn't look at this
backend because it frequently sends only a frame request in order to cause
a refresh.
Signed-off-by: Jason Ekstrand
---
src/compositor.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/src/compositor.c b/src/compositor.c
index bb1dfa9..8c69f3c 100644
--- a/src
Signed-off-by: Jason Ekstrand
---
src/gl-renderer.c | 110 --
1 file changed, 81 insertions(+), 29 deletions(-)
diff --git a/src/gl-renderer.c b/src/gl-renderer.c
index 0e5afbe..c8dfa4b 100644
--- a/src/gl-renderer.c
+++ b/src/gl-renderer.c
Signed-off-by: Jason Ekstrand
---
src/gl-renderer.c | 99 ++-
1 file changed, 98 insertions(+), 1 deletion(-)
diff --git a/src/gl-renderer.c b/src/gl-renderer.c
index c8dfa4b..5654006 100644
--- a/src/gl-renderer.c
+++ b/src/gl-renderer.c
Signed-off-by: Jason Ekstrand
---
The second version properly sets the EGL_SWAP_BEHAVIOR surface attribute to
EGL_BUFFER_PRESERVED.
src/gl-renderer.c | 104 +-
1 file changed, 103 insertions(+), 1 deletion(-)
diff --git a/src/gl-renderer.c b
Never mind, the first one was correct. I misunderstood buffer age.
--Jason
On Jan 16, 2014 10:52 PM, "Jason Ekstrand" wrote:
> Signed-off-by: Jason Ekstrand
> ---
>
> The second version properly sets the EGL_SWAP_BEHAVIOR surface attribute to
> EGL_BUFFER_PRESERVED.
>
Yeah, this is probably better.
--Jason Ekstrand
Reviewed-By: Jason Ekstrand
On Jan 21, 2014 9:02 AM, "Neil Roberts" wrote:
> It looks like the rest of the code assumes that shsurf->children_link
> is always a consistent list. For example, shell_surface_set_parent
> reset
ing advantage of some new cool
> technology.
>
> Btw. if you think that using UST for presentation timing and feedback
> is nonsense, and MSC is the only right way, let me know and I can start
> another email thread about that detail after preparing my material.
>
>
it easy to have
program logic errors that don't result in a crash, just things being subtly
wrong and impossible to track down.
All said, I think I'd be in favor of making double-remove safe. However,
it's not a silver bullet.
--Jason Ekstrand
On Jan 28, 2014 11:22 AM, "Jonathan How
know which client is which because (I assume) you should be launching
them privately and manually creating the wl_client objects.
Thanks,
--Jason Ekstrand
On Jan 30, 2014 5:35 AM, "Pekka Paalanen" wrote:
> On Thu, 30 Jan 2014 10:32:03 +0100
> Iago Toral wrote:
>
> >
Signed-off-by: Jason Ekstrand
---
Version 3 properly #ifdefs around things so it will still build on systems
that do not provide the extension in eglext.h
src/gl-renderer.c | 107 ++
1 file changed, 107 insertions(+)
diff --git a/src/gl
Signed-off-by: Jason Ekstrand
---
No change from previous version. Just resending to keep things together.
src/gl-renderer.c | 110 --
1 file changed, 81 insertions(+), 29 deletions(-)
diff --git a/src/gl-renderer.c b/src/gl-renderer.c
index
---
Makefile.am | 1 +
1 file changed, 1 insertion(+)
diff --git a/Makefile.am b/Makefile.am
index 21b2b17..5e8556b 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -485,6 +485,7 @@ weston_nested_CFLAGS = $(CLIENT_CFLAGS)
weston_nested_client_SOURCES = clients/nested-client.c
weston_nested_clien
rlying
graphics drivers pass sync fences or do other things to keep from doing a
full glFinish and stalling the GPU. Therefore, in most cases, you shouldn't
need to be calling wl_surface.commit manually. Perhaps I'm just
misunderstanding something?
I hope that helps,
--Jason Ekstrand
On Fr
On Fri, Feb 7, 2014 at 12:57 PM, Prabhu S wrote:
> Please find my comments inline.
>
>
>
>
> On Fri, Feb 7, 2014 at 8:18 AM, Jason Ekstrand wrote:
>
>> Hi Prabhu,
>> Could you be a little more specific as to what you are doing. It sounds
>> like you a
On Wed, Feb 5, 2014 at 11:04 PM, Kristian Høgsberg wrote:
> On Wed, Dec 18, 2013 at 08:56:20PM -0600, Jason Ekstrand wrote:
> > In order to keep from overloading the debug handler, we first squash the
> > entire message into a string and call wl_debug once.
> >
> > Si
ugins than the
ones provided with weston.
--Jason Ekstrand
On Sat, Feb 8, 2014 at 2:01 AM, Nobuhiko Tanibata <
nobuhiko_tanib...@xddp.denso.co.jp> wrote:
> Add key:shell to CORE SECTION and move a example of desktop-shell from
> key:modules to key:shell.
> Add cms-colord.so to ke
the drivers don't
> support the query, the compositor might need to wait for the next
> vblank before it can reply. Or the compositor might reply with so old
> data that it is not useful anymore. Any delays would void the benefit
> of achieving early sync.
>
> A more fundame
tor's target timestamp would be
> better defined.
>
> Opinions?
>
I agree. The current frame (or frame for the currently pending flip)
should be treated as if it has a timestamp of its expected next
presentation time. I'm still not completely understanding the algorithm
for pre
OK, that makes more sense. Thank you for stating it in terms of intervals.
I still need to think about it a bit more.
On Feb 8, 2014 4:14 PM, "Axel Davy" wrote:
> On 08/02/2014, Axel Davy wrote :
>
> Hi,
>
>
> On 08/02/2014, Jason Ekstrand wrote :
>
>
>
On Feb 9, 2014 7:18 AM, "nobuhiko_tanibata" <
nobuhiko_tanib...@xddp.denso.co.jp> wrote:
>
> Hi Jason,
>
> 2014-02-09 01:54 に Jason Ekstrand さんは書きました:
>
>> Nobuhiko,
>> These look pretty good assuming they properly compile (I can't compile
>
On Mon, Feb 10, 2014 at 3:53 AM, Pekka Paalanen wrote:
> On Sat, 8 Feb 2014 15:23:29 -0600
> Jason Ekstrand wrote:
>
> > Pekka,
> > First off, I think you've done a great job over-all. I think it will
> both
> > cover most cases and work well I've got
On Mon, Feb 10, 2014 at 5:51 AM, Pekka Paalanen wrote:
> On Sat, 8 Feb 2014 15:39:57 -0600
> Jason Ekstrand wrote:
>
> > On Wed, Feb 5, 2014 at 1:32 AM, Pekka Paalanen
> wrote:
> >
> > > On Thu, 30 Jan 2014 17:35:17 +0200
> > > Pekka Paalanen wrote:
&
to the modesetting portion of the protocol.
Feedback there is appreciated as well.
Thanks,
--Jason Ekstrand
Jason Ekstrand (11):
Add a fullscreen shell protocol
Generate/build the fullscreen shell protocol files
Add a signal for when a seat updates its capabilities
Add a
or so,
I will attempt to implement all this in weston and see how well it works.
However, I would also like to know how well this will work for other
compositors such as KWin or Hawaii.
Thanks for your feedback,
--Jason Ekstrand
= Protocol follows: =
Displays a single
Hi Pekka! Thanks for the review. Comments follow.
On Fri, Feb 14, 2014 at 1:14 AM, Pekka Paalanen wrote:
> Hi Jason
>
> On Thu, 13 Feb 2014 22:37:53 -0600
> Jason Ekstrand wrote:
>
> > The following is yet another take on the fullscreen shell protocol.
> > Pre
surface state without either a full
repaint or a new EGL extension. The obvious answer is "just re-send the
old wl_buffer". However, EGL clients don't have acess to it and can't
re-send. They can only repaing and have EGL send a new buffer. Therefore,
if we want to allow for u
Yeah, I've wanted to do that for a while.
Reviewed-By: Jason Ekstrand
On Feb 17, 2014 6:04 PM, "Jasper St. Pierre" wrote:
> In some cases, like Xwayland, stdout and stderr are redirected to
> /dev/null, losing us valuable information, while wl_log can be
> overridden, a
I just added an implementation of RFCv4 which can be found here:
https://github.com/jekstrand/weston/tree/fullscreen-shell-RFCv4
Thanks,
--Jason Ekstrand
On Sat, Feb 15, 2014 at 1:12 AM, Pekka Paalanen wrote:
> On Fri, 14 Feb 2014 11:11:33 -0600
> Jason Ekstrand wrote:
>
>
x27;s
desktop-shell panel spawns things right now.
> 4) store both settings in WAYLAND_SOCKET. D-Bus does that:
> DBUS_SESSION_BUS_ADDRESS can contain multiple addresses, to be attempted in
> order.
>
That's an interesting idea. Not sure what benefit it would have for
Wayland right now though.
Hope that helps,
--Jason Ekstrand
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
nd miss the flip,
but that's really no worse than waiting before sending the frame callback.
Point is, it should be a compositor decision and I think you made that
clear enough.
Looks good to me.
--Jason Ekstrand
Reviewed-by: Jason Ekstrand
On Fri, Feb 21, 2014 at 7:46 AM, Pekka Paalanen
gt; I don't think having to do an attach with the old buffer is a good idea,
and I favor Pekka's proposition.
I wasn't arguing against it. :-)
>
> Axel Davy
>
> On 22/02/2014, Jason Ekstrand wrote :
>>
>> Pekka,
>> Sorry this e-mail took so long to send. N
On Feb 23, 2014 1:45 AM, "Pekka Paalanen" wrote:
>
> Hi,
>
> thanks for all the comments, it's encouraging to see a concensus
> emerging. One reply below...
>
> On Sat, 22 Feb 2014 07:50:01 -0600
> Jason Ekstrand wrote:
>
> > On Feb 22,
On Feb 23, 2014 1:50 AM, "Pekka Paalanen" wrote:
>
> On Fri, 21 Feb 2014 21:38:15 -0600
> Jason Ekstrand wrote:
>
> > Pekka,
> > Sorry this e-mail took so long to send. Not much time lately. The
first
> > time or two I read this suggested re-wording I d
Jonas, thanks for reviewing.
On Feb 24, 2014 4:03 PM, "Jonas Ådahl" wrote:
>
> On Thu, Feb 13, 2014 at 10:37:53PM -0600, Jason Ekstrand wrote:
> > The following is yet another take on the fullscreen shell protocol.
> > Previous versions more-or-less followed th
When buffer_transform and buffer_scale were first introduced, added, we
specified surface damage to be in surface coordinates. However, this does
not and will never work properly with EGL. Because the buffer transform
and scale are handled directly by the client and not passed through EGL,
the EG
And I forgot reply-all again. This is why I shouldn't respond from my
phone.
On Tue, Feb 25, 2014 at 8:07 AM, Pekka Paalanen wrote:
> On Tue, 25 Feb 2014 07:44:24 -0600
> Jason Ekstrand wrote:
>
> > I'll do a full reply later, just a quick one now.
> >
P session. Seats from RDP are
added as aditional seats.
I hope you all like it! Feedback is appreciated.
Thanks,
--Jason Ekstrand
Jason Ekstrand (15):
Add a fullscreen shell protocol
Generate/build the fullscreen shell protocol files
Add a signal for when a seat updates its capab
Signed-off-by: Jason Ekstrand
---
Makefile.am | 1 +
1 file changed, 1 insertion(+)
diff --git a/Makefile.am b/Makefile.am
index dc50da3..0e749b0 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -928,6 +928,7 @@ EXTRA_DIST += \
protocol/text-cursor
Signed-off-by: Jason Ekstrand
---
clients/window.c | 22 ++
clients/window.h | 6 ++
2 files changed, 28 insertions(+)
diff --git a/clients/window.c b/clients/window.c
index b4b9588..6e132d5 100644
--- a/clients/window.c
+++ b/clients/window.c
@@ -349,6 +349,8 @@ struct
Signed-off-by: Jason Ekstrand
---
Makefile.am| 20 ++
configure.ac | 8 +
src/fullscreen-shell.c | 822 +
3 files changed, 850 insertions(+)
create mode 100644 src/fullscreen-shell.c
diff --git a/Makefile.am b/Makefile.am
Signed-off-by: Jason Ekstrand
---
src/compositor.h | 1 +
src/input.c | 2 ++
2 files changed, 3 insertions(+)
diff --git a/src/compositor.h b/src/compositor.h
index 63e4e2c..7edf7b3 100644
--- a/src/compositor.h
+++ b/src/compositor.h
@@ -494,6 +494,7 @@ struct weston_seat
Signed-off-by: Jason Ekstrand
---
Makefile.am | 3 +
clients/fullscreen.c | 165 +++
2 files changed, 156 insertions(+), 12 deletions(-)
diff --git a/Makefile.am b/Makefile.am
index d94f0d0..c1ab74b 100644
--- a/Makefile.am
+++ b
Signed-off-by: Jason Ekstrand
---
src/gl-renderer.c | 4
1 file changed, 4 insertions(+)
diff --git a/src/gl-renderer.c b/src/gl-renderer.c
index d03bce6..444aa97 100644
--- a/src/gl-renderer.c
+++ b/src/gl-renderer.c
@@ -962,6 +962,10 @@ gl_renderer_read_pixels(struct weston_output
Signed-off-by: Jason Ekstrand
---
protocol/fullscreen-shell.xml | 158 ++
1 file changed, 158 insertions(+)
create mode 100644 protocol/fullscreen-shell.xml
diff --git a/protocol/fullscreen-shell.xml b/protocol/fullscreen-shell.xml
new file mode 100644
Signed-off-by: Jason Ekstrand
---
src/compositor-wayland.c | 61 +---
1 file changed, 37 insertions(+), 24 deletions(-)
diff --git a/src/compositor-wayland.c b/src/compositor-wayland.c
index fc9c9b5..ff02649 100644
--- a/src/compositor-wayland.c
+++ b
Signed-off-by: Jason Ekstrand
---
clients/window.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/clients/window.c b/clients/window.c
index 91c1ea0..b4b9588 100644
--- a/clients/window.c
+++ b/clients/window.c
@@ -4423,7 +4423,7 @@ window_create_internal(struct display
This forces weston to create one output for every parent output. This is
enabled by default if it detects a wl_fullscreen_shell. The --sprawl
option is primarily to enable this on wl_shell.
Signed-off-by: Jason Ekstrand
---
src/compositor-wayland.c | 10 +++---
src/compositor.c
es is outside the scope of this patch so it is hard-coded for
now.
Signed-off-by: Jason Ekstrand
---
Makefile.am| 22 ++
configure.ac | 13 +
src/screen-share.c | 1082
3 files changed, 1117 insertions(+)
create mode 100644 src/s
Signed-off-by: Jason Ekstrand
---
Makefile.am | 3 +
src/compositor-wayland.c | 470 ---
2 files changed, 451 insertions(+), 22 deletions(-)
diff --git a/Makefile.am b/Makefile.am
index c1ab74b..838a051 100644
--- a/Makefile.am
+++ b
1 - 100 of 743 matches
Mail list logo
