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
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
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
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
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:
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
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
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
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:
> >
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 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 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 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 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 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 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 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 :
>
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
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
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'
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
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
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
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
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
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
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
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
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
> > 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)
; 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
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 +++-
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
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 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
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
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
It also occurred to me that it would be nice to install Wayland
headers
> > > into a wayland/ sub-directory, but that's another story.
> > >
> > > And I suppose we don't want to actually push people away from the old
> > > headers if they work fine, ri
and-egl.h, what if the core version of it did not
> include anything? It doesn't need to, it just needs forward
> declarations of wl_surface and... that's it.
>
> I would like to see this patch split into three:
> 1. the header stuff not including wayland-egl.h changes
> 2.
On Thu, Apr 2, 2015 at 12:35 AM, Dave Airlie wrote:
> So nvidia have indicated they would like to use an EGLstreams based
> solution to enable wayland on their binary driver stack at some point.
As per their recent XDC talk, they sounded like they had given up on
eglstreams for implementing the W
On Sat, Mar 28, 2015 at 6:57 AM, x414e54 wrote:
> I am attempting to pass a GL_TEXTURE_2D directly to a Wayland compositor
by
> first converting it so an EGLImageKHR and then to a wl_buffer.
>
> eglCreateImageKHR appears to work fine but when calling
> glCreateWaylandBufferFromImageWL I get EGL_BA
On Mar 24, 2015 6:14 PM, "Jonas Ådahl" wrote:
>
> On Wed, Mar 25, 2015 at 10:27:10AM +1000, Peter Hutterer wrote:
> > The axis_source event determines how an axis event was generated. This
enables
> > clients to judge when to use kinetic scrolling.
> >
> > The axis_stop event notifies a client abo
On Tue, Mar 24, 2015 at 5:27 PM, Peter Hutterer
wrote:
> The axis_source event determines how an axis event was generated. This enables
> clients to judge when to use kinetic scrolling.
>
> The axis_stop event notifies a client about the termination of a scroll
> sequence, likewise needed to calcu
On Sun, Mar 22, 2015 at 8:57 PM, Jonas Ådahl wrote:
> On Mon, Mar 23, 2015 at 01:21:38PM +1000, Peter Hutterer wrote:
>> On Mon, Mar 23, 2015 at 10:23:18AM +0800, Jonas Ådahl wrote:
>> > On Mon, Mar 09, 2015 at 01:28:04PM +1000, Peter Hutterer wrote:
>> > > The axis source determines how an event
LGTM
On Mar 20, 2015 6:59 AM, "Pekka Paalanen" wrote:
> From: Pekka Paalanen
>
> Tablet shell is long gone. Might as well list what we have now.
>
> Signed-off-by: Pekka Paalanen
> ---
> man/weston.man | 27 +--
> 1 file changed, 17 insertions(+), 10 deletions(-)
>
> di
On Mar 17, 2015 5:34 AM, "Pekka Paalanen" wrote:
>
> On Tue, 17 Mar 2015 13:02:34 +0100
> Thilo Cestonaro wrote:
>
> > Hey!
> >
> > > Just curious, why didn't you get the fbdev backend to work? Was it the
> > > color format thing?
> > >
> > No, I got the color format to work, but I need to rotate
On Tue, Mar 10, 2015 at 12:00 PM, Bill Spitzak wrote:
> On 03/09/2015 10:32 PM, Jasper St. Pierre wrote:
>>
>> Mouse input is reported in a 24.8 fixed-point format. Subpixel mouse
>> locations are entirely possible.
>
>
> Yes events are doing this which is ok.
>
> There is a problem that clients m
iewed-by: Jason Ekstrand
On Tue, Mar 10, 2015 at 7:48 AM, Derek Foreman
wrote:
> On 10/03/15 08:01 AM, Pekka Paalanen wrote:
> > From: Pekka Paalanen
> >
> > Hi,
> >
> > as requested by Derek, here is a revised series from
> >
> http://lists.freedeskt
On Tue, Mar 10, 2015 at 12:51 PM, Bill Spitzak wrote:
> This all looks really good to me.
>
> It is possible to avoid "GL coordinates" even in GL. Set the projection
> matrix to an ortho matrix:
>
> glMatrixMode(GL_PROJECTION);
> glLoadIdentity()
> glOrtho(0, width, height, 0, -1, 1);
> g
On Tue, Mar 10, 2015 at 6:01 AM, Pekka Paalanen wrote:
> From: Pekka Paalanen
>
> Move code into a new helper function. No changes.
>
> Signed-off-by: Pekka Paalanen
> Reviewed-By: Derek Foreman
> ---
> src/pixman-renderer.c | 31 ++-
> 1 file changed, 18 insertion
Manuel,
Thanks for keeping this going. I don't have a whole lot of comments at the
moment as it's a pretty small protocol change. I would like to hear some
commentary from Jasper and some of the other desktop devs though.
The one comment I will make about the protocol is that you may want to
cha
On Feb 27, 2015 5:11 AM, "Pekka Paalanen" wrote:
>
> On Fri, 27 Feb 2015 13:38:49 +0200
> Pekka Paalanen wrote:
>
> > On Fri, 13 Feb 2015 14:02:02 +0800
> > Jonas Ådahl wrote:
> >
> > > From: "Jasper St. Pierre"
> > >
> > > ---
> > > clients/simple-damage.c | 2 +-
> > > clients/simple-egl.c
Just spent a little time crawling through things to remind myself of how it
all works. Your comment seems correct. Not sure if it's really sufficient
documentation for view.clip though.
Reviewed-by: Jason Ekstrand
On Tue, Feb 17, 2015 at 4:19 AM, Pekka Paalanen wrote:
> From: Pekka
er, this gets tricky if the parent
compositor says an output is transformed by 90 and the child wants it
transformed by 180. Do you add the transformations? Just let the client
override? Lots of interesting questions there.
--Jason Ekstrand
On Thu, Jan 8, 2015 at 1:37 PM, Imran Zaman wrote:
Previously, we blindly created a mode for the output based on surface size
and completely ignoring the output transform. This caused modesets to fail
on outputs that were transformed by 90 or 270 degrees. We should be
swapping the width and the height in this case.
---
fullscreen-shell/fullscree
Hi Martin!
First off, thanks for looking at it and giving your thoughs. I'm going to
reply to a few things below from a sort-of "general wayland perspective"
I'll leave the hashing out of details to the people who actually work on
real compositors. Hopefully, the rest of the list shows similar re
Bryce,
Thanks for your thoughts. I've got a few of my own, but I decided to reply
to your e-mail as it seemed the best branch-point for the actual discussion
without replying to everything.
On Mon, Dec 8, 2014 at 3:26 PM, Bryce Harrington
wrote:
> On Mon, Dec 08, 2014 at 02:01:32PM +0200, Pekka
On Tue, Dec 2, 2014 at 5:49 AM, Jonas Ådahl wrote:
> Hi again,
>
> At XDC2014 some of us sat down and talked through how pointer locking
> and related protocols should look like, and this series is more or less
> work-in-progress result of that discussion.
>
> The series contains two parts (and o
A couple of doc comments below, but the protocol otherwise looks pretty
good. Again, I've only glanced at the implementation.
On Tue, Dec 2, 2014 at 5:49 AM, Jonas Ådahl wrote:
> This patch introduces a new protocol for locking and confining a
> pointer. It consists of a new global object with
Haven't looked at the weston implementation but the protocol bits look
pretty good to me. Sounds like what we discussed.
--Jason
On Tue, Dec 2, 2014 at 5:49 AM, Jonas Ådahl wrote:
> A wl_relative_pointer object is an extension to the wl_pointer interface
> only used for emitting relative pointe
I agree with Pekka's comments, I also have a couple of my own below. (Most
of them are pretty trivial). With Pekka's and my comments addressed, this
series looks good to me.
--Jason
On Sat, Nov 22, 2014 at 12:28 PM, Jasper St. Pierre
wrote:
> This rewrites basically all of the text inside xdg-
I don't see anything wrong with this patch, but I'm forced to ask the
question: What's the point? I mean, it's a little bouncing ball, why does
it need to be configurable?
On Sat, Nov 29, 2014 at 5:36 AM, Seedo Eldho Paul
wrote:
> Also change "simple-shm exiting" to "simple-damage exiting"
>
>
On Thu, Oct 16, 2014 at 11:16 PM, Pekka Paalanen
wrote:
> On Thu, 16 Oct 2014 10:40:20 +0300
> Pekka Paalanen wrote:
>
> > On Thu, 16 Oct 2014 09:46:39 +0300
> > Pekka Paalanen wrote:
> >
> > > On Wed, 15 Oct 2014 22:44:25 +0400
> > > Dmitry Cherkassov wrote:
> > >
> > > > Hi list!
> > > >
> >
On Oct 19, 2014 12:03 AM, "Pekka Paalanen" wrote:
>
> On Sat, 18 Oct 2014 11:19:55 -0700
> Jason Ekstrand wrote:
>
> > On Thu, Oct 16, 2014 at 11:16 PM, Pekka Paalanen
> > wrote:
> >
> > > On Thu, 16 Oct 2014 10:40:20 +0300
> > > Pekka P
plicit? For instance, the compositor can easily grab the
socket and chmod it. It has the privileges and knows what socket it is.
--Jason Ekstrand
>
> Signed-off-by: Imran Zaman
> ---
> src/wayland-server.c | 27 +++
> 1 file changed, 27 insertions(+)
>
&g
I don't see how this belongs in libwayland. Sure, we use strtol twice, but
I don't think that warrants adding 100 lines of wrapper functions and test
cases.
--Jason Ekstrand
On Wed, Oct 15, 2014 at 6:16 AM, Rémi Denis-Courmont
wrote:
> Le 2014-10-15 16:14, Imran Zaman a éc
Looks good to me. Pushed.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
..
>
>
>
>Is there a way that I can mentioning in weston.ini file so that the
> displays are clone of each other..
>
As far as I know, this is not yet implemented in Weston. There was someone
working on it at one point, but I haven't heard anything about it in a
while.
--J
On Oct 6, 2014 12:45 AM, "Pekka Paalanen" wrote:
>
> Re-adding CCs and some more...
>
> On Mon, 06 Oct 2014 09:17:41 +0300
> Rémi Denis-Courmont wrote:
>
> > Hello,
> >
> > Le 2014-10-06 03:29, Jason Ekstrand a écrit :
> > > Remi,
>
s later.
>
> In the wl_buffer case, we could not extend wl_buffer itself even with
> associate interface (like wl_viewport is for wl_surface, or the role
> mechanism), because EGL does not normally expose wl_buffer to client
> code.
>
> > On Sun, Oct 5, 2014 at 5:30 PM, Jason
On Sun, Oct 5, 2014 at 2:23 PM, Karsten Otto wrote:
> Am 29.09.2014 um 06:31 schrieb Jason Ekstrand :
>
> >
> > On Sep 28, 2014 11:49 AM, "Karsten Otto" wrote:
> > >
> > > From: Philip Withnall
> > >
> > > This happens if the so
Ping
On Fri, Apr 11, 2014 at 1:36 AM, Jason Ekstrand
wrote:
> On Fri, Apr 11, 2014 at 2:03 AM, Pekka Paalanen
> wrote:
>
>> On Thu, 10 Apr 2014 09:42:55 -0500
>> Jason Ekstrand wrote:
>>
>> > On Thu, Apr 10, 2014 at 6:37 AM, Pekka Paalanen
>> wrote:
ement this
a while ago but it never got merged. You can find it here:
http://lists.freedesktop.org/archives/wayland-devel/2014-April/014004.html
--Jason Ekstrand
On Sun, Oct 5, 2014 at 2:02 AM, Rémi Denis-Courmont wrote:
> In some scenarii, a component will obtain a reference to a proxy
On Fri, Oct 3, 2014 at 8:21 AM, Derek Foreman
wrote:
> On 02/10/14 07:09 PM, Jason Ekstrand wrote:
> >
> >
> > On Thu, Oct 2, 2014 at 3:21 PM, Derek Foreman > <mailto:der...@osg.samsung.com>> wrote:
> >
> > On 02/10/14 02:37 PM, Jason Ekstrand wr
On Thu, Oct 2, 2014 at 3:21 PM, Derek Foreman
wrote:
> On 02/10/14 02:37 PM, Jason Ekstrand wrote:
> >
> > On Oct 2, 2014 12:37 AM, "Pekka Paalanen" > <mailto:ppaala...@gmail.com>> wrote:
> >>
> >> On Wed, 1 Oct 2014 18:09:32 -0700
&g
On Oct 2, 2014 12:37 AM, "Pekka Paalanen" wrote:
>
> On Wed, 1 Oct 2014 18:09:32 -0700
> Jason Ekstrand wrote:
>
> > Allow me to chip in here. Sorry that I haven't had a chance to really
look
> > over things carefully. I have been reading this thread, j
Allow me to chip in here. Sorry that I haven't had a chance to really look
over things carefully. I have been reading this thread, just haven't had a
chance to respond.
On Wed, Oct 1, 2014 at 12:41 AM, Pekka Paalanen wrote:
> On Tue, 30 Sep 2014 14:35:24 -0500
> Derek Foreman wrote:
>
> > Tha
While that looks correct, I'm sure it breaks something. As the person who
wrote that code, that choice was very intentional. Even though the
protocol type is uint32_t, new_id arguments are always passed into
libwayland as either a wl_proxy or wl_resource and that's what this code is
designed to h
On Sep 28, 2014 11:49 AM, "Karsten Otto" wrote:
>
> From: Philip Withnall
>
> This happens if the socket has been gracefully closed.
>
> [KAO: It prevents a potential infinite loop when using a different
> event handling mechanism than epoll, if said mechanism cannot
> distinguish EOF from regula
On Sep 28, 2014 6:54 PM, "Bill Spitzak" wrote:
>
> On 09/28/2014 11:49 AM, Karsten Otto wrote:
>
>> + msg.msg_control = NULL;
>> + msg.msg_controllen = 0;
>> msg.msg_flags = 0;
>>
>> + /* Only set msg_control when sending ancillary data */
On Fri, Sep 26, 2014 at 7:38 AM, Jasper St. Pierre
wrote:
>
>
> On Fri, Sep 26, 2014 at 4:07 AM, Carlos Garnacho
> wrote:
>
>> Hey,
>>
>> On Thu, Sep 25, 2014 at 7:30 PM, Matthias Clasen <
>> matthias.cla...@gmail.com> wrote:
>>
>>> On Thu, Sep 25, 2014 at 10:32 AM, Jasper St. Pierre
>>> wrote:
On Sep 25, 2014 3:04 PM, "Jasper St. Pierre" wrote:
>
>
>
> On Thu, Sep 25, 2014 at 3:58 PM, Bill Spitzak wrote:
>>
>> On 09/25/2014 01:57 PM, Jasper St. Pierre wrote:
>>
>>>
https://github.com/magcius/weston/commit/c1e5a846f4f57400bca1262111f9793e451c5b49
>>
>>
>> That patch has nothing to do wi
oposal can do that Jonas' one can't do ?
> => The only thing I can find is the case where a seat doesn't have a
> wl_pointer but have relative events. For all the rest, Jonas' proposal
> seems to work.
> => My proposition seems simpler to me. Less dependencies b
Bill, That's an interesting idea, but there are a few problems (which may
be solvable). I do kind of like the way it completely sidesteps the
acceleration issue.
On Tue, Sep 23, 2014 at 12:43 PM, Bill Spitzak wrote:
> In any case this all sounds excessively complicated. I think this will
> work
Hi Matthieu,
Could you please provide more explanation on what use-cases you are
considering and why the current proposal fails to accomplish them? All I
was able to get from your post was the example of a TV remote. It's all
well and good to completely disagree with the proposed approach, but
wi
On Tue, Sep 23, 2014 at 8:17 AM, Nils Chr. Brause
wrote:
> On Tue, Sep 23, 2014 at 8:35 AM, Pekka Paalanen
> wrote:
> > On Tue, 23 Sep 2014 13:59:39 +0800
> > Boyan Ding wrote:
> >
> >> On Mon, 2014-09-22 at 11:27 -0700, Jason Ekstrand wrote:
> >>
>
On Mon, Sep 22, 2014 at 12:52 PM, Jonas Ådahl wrote:
> On Mon, Sep 22, 2014 at 11:31:27AM -0700, Jason Ekstrand wrote:
> > On Sun, Sep 21, 2014 at 11:43 PM, Pekka Paalanen
> > wrote:
> >
> > > On Sat, 20 Sep 2014 11:43:22 -0700
> > > Jason Ekstrand wrote
On Mon, Sep 22, 2014 at 12:48 PM, Jasper St. Pierre
wrote:
>
>
> On Mon, Sep 22, 2014 at 12:27 PM, Jason Ekstrand
> wrote:
>
>>
>>
>> On Mon, Sep 22, 2014 at 9:30 AM, Nils Chr. Brause <
>> nilschrbra...@gmail.com> wrote:
>>
>>>
On Sun, Sep 21, 2014 at 11:43 PM, Pekka Paalanen
wrote:
> On Sat, 20 Sep 2014 11:43:22 -0700
> Jason Ekstrand wrote:
>
> > On Sat, Sep 20, 2014 at 1:29 AM, Pekka Paalanen
> wrote:
> >
> > > On Fri, 19 Sep 2014 20:20:53 +0200
> > > Jonas Ådahl wrote:
&
On Mon, Sep 22, 2014 at 9:30 AM, Nils Chr. Brause
wrote:
> On Mon, Sep 22, 2014 at 11:21 AM, Pekka Paalanen
> wrote:
> >
> > On Wed, 3 Sep 2014 19:44:04 +0200
> > "Nils Chr. Brause" wrote:
> >
> > > This replaces "[PATCH wayland] Add "enum" attribute to "arg" elements".
> > > Previous concers h
> > > > On Fri, 19 Sep 2014 08:33:13 +0200
> > > > Jonas Ådahl wrote:
> > > >
> > > > > On Thu, Sep 18, 2014 at 10:43:47AM -0700, Jason Ekstrand wrote:
> > > > > > On Thu, Sep 18, 2014 at 2:26 AM, Pekka Paalanen <
> ppaala...@g
On Sat, Sep 20, 2014 at 12:58 AM, Pekka Paalanen
wrote:
> On Fri, 19 Sep 2014 12:46:20 -0700
> Jason Ekstrand wrote:
>
> > On Fri, Sep 19, 2014 at 11:20 AM, Jonas Ådahl wrote:
> >
> > > On Fri, Sep 19, 2014 at 11:00:21AM -0600, Jasper St. Pierre wrote:
> >
> >
> > > > On Thu, Sep 18, 2014 at 10:43:47AM -0700, Jason Ekstrand wrote:
> > > > > On Thu, Sep 18, 2014 at 2:26 AM, Pekka Paalanen <
> ppaala...@gmail.com>
> > > wrote:
> > > > >
> > > > > > On Wed, 17 Sep 201
On Thu, Sep 18, 2014 at 2:26 AM, Pekka Paalanen wrote:
> On Wed, 17 Sep 2014 22:35:40 +0200
> Jonas Ådahl wrote:
>
> > On Wed, Sep 17, 2014 at 11:16:06PM +0300, Giulio Camuffo wrote:
> > > 2014-09-17 23:11 GMT+03:00 Jonas Ådahl :
> > > > On Wed, Sep 17, 2014 at 10:56:13PM +0300, Giulio Camuffo w
I took a look at it too and it looks good to me
--Jason
On Thu, Sep 11, 2014 at 1:46 AM, Pekka Paalanen wrote:
> On Wed, 10 Sep 2014 12:47:14 +0200
> Marek Chalupa wrote:
>
> > Calling wl_display_read_events() after an error should be equivalent
> > to wl_display_cancel_read(), so that display
On Mon, Sep 1, 2014 at 8:33 AM, Derek Foreman
wrote:
> On 01/09/14 04:52 AM, Jason Ekstrand wrote:
> > On Mon, Sep 1, 2014 at 2:37 AM, Pekka Paalanen
> wrote:
> >
> >> On Fri, 29 Aug 2014 23:35:37 -0700
> >> Jason Ekstrand wrote:
> >>
> >&
On Mon, Sep 1, 2014 at 2:37 AM, Pekka Paalanen wrote:
> On Fri, 29 Aug 2014 23:35:37 -0700
> Jason Ekstrand wrote:
>
> > On Aug 29, 2014 6:25 PM, "Derek Foreman" wrote:
> > >
> > > On 29/08/14 06:42 PM, Jason Ekstrand wrote:
> > > > Derek,
1 - 100 of 743 matches
Mail list logo
