On Thu, Feb 06, 2014 at 11:28:49PM +0100, Eugen Friedrich wrote:
> Hi together,
> i would like to put some input from the embedded/ automotive perspective.
>
> you can think about huge amount of different configurations for different
> device types.
> A lot of configuration in the initial post dea
When calculating view's damage region in view_accumulate_damage(), the
coordinates of view's damage are incoherent with other regions, which are
treated together, such as view transform's boundingbox and opaque regions. This
commit simply removes the translation to plane coordinates to solve this
i
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 :
>
>
>
>> For each surface with queued cont
Hallo Jonas,
Thanks for fast replay, basically we have already proprietary
implementation in place to fulfil requirements from different customers.
Now we are looking forward to find a good open source component to
contribute our knowledge, experience and maybe code.
Since we using wayland, li
On 08/02/2014, Axel Davy wrote :
Hi,
On 08/02/2014, Jason Ekstrand wrote :
For each surface with queued content updates and matching main
output, the compositor picks the update with the highest
timestamp no later than a half frame period after the predicted
Hi,
On 08/02/2014, Jason Ekstrand wrote :
For each surface with queued content updates and matching main
output, the compositor picks the update with the highest
timestamp no later than a half frame period after the predicted
presentation time. The inte
On Wed, Feb 5, 2014 at 1:32 AM, Pekka Paalanen wrote:
> On Thu, 30 Jan 2014 17:35:17 +0200
> Pekka Paalanen wrote:
>
> > Hi,
> >
> > it's time for a take two on the Wayland presentation extension.
> >
> >
> > 1. Introduction
> >
> > The v1 proposal is here:
> >
> http://lists.freed
More comments!
On Fri, Jan 31, 2014 at 7:29 AM, Pekka Paalanen wrote:
> On Thu, 30 Jan 2014 17:35:17 +0200
> Pekka Paalanen wrote:
>
> > The v1 proposal is here:
> >
> http://lists.freedesktop.org/archives/wayland-devel/2013-October/011496.html
> >
> > In v2 the basic idea is the same: you can
eglCreateContext fails with every EGLConfig that
nvidia blob 334.16 provides causing NULL pointer
dereference in gl_renderer_destroy when destroying
fragment and fan bindings.
This should fix #74699.
Signed-off-by: Mariusz Ceier
---
src/gl-renderer.c | 6 --
1 file changed, 4 insertions(+),
Nobuhiko,
These look pretty good assuming they properly compile (I can't compile the
man format in my head). One comment, is that we should probably remove
tablet-shell from the list of shells while we're at it. It might also be
worth noting that this can be used to load other shell plugins than
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.
> >
> > Signed-off-by: Jason Ekstrand
>
Well, there's not really anything that allows process A to arbitrarily
modify process B's memory. The only thing that's close is memory-mapped
files, and that's already what we use to share image data between the
client and the compositor.
There's also memfd, which is "more secure" than a memory-m
On Sat, 8 Feb 2014 08:19:06 +
"Wang, Quanxian" wrote:
> Hi, All
>
> I want to allocate some space in client, and let compositor set
> some data in this space and then return back to client.
>
> It seems like user data mechanism.
>
> Any way to implement that?
Not really, it's nothing like
With this patch, a user can keep a reference to a libinput_seat
instance, which will cause the seat to never be unlinked from the
libinput context nor destroyed.
Previously, a when the last device of a seat was removed, the seat was
unlinked and if a new device was discovered with a previously emp
On Fri, 7 Feb 2014 22:27:00 -0800
Kristian Høgsberg wrote:
> On the client side we log fatal errors before we exit. If a
> client doesn't set a log handler, it's hard to figure out what
> goes wrong. ---
> src/wayland-util.c | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> di
On Fri, 07 Feb 2014 09:54:36 -0800
Bill Spitzak wrote:
> Okay, removing everything with "gallium" in it's name from the
> install worked. But "make install" in mesa puts it all back!
> Would "clean" fix this?
>
> What I am really interested in is the proper configure line for
> mesa. I am curren
Hi, All
I want to allocate some space in client, and let compositor set some data in
this space and then return back to client.
It seems like user data mechanism.
Any way to implement that?
Thanks
Regards
Quanxian Wang
___
wayland-devel mailing li
Add key:shell to CORE SECTION and move a example of desktop-shell from
key:modules to key:shell.
Add cms-colord.so to key:modules of CORE SECTION.
Signed-off-by: Nobuhiko Tanibata
---
man/weston.ini.man | 17 ++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/man/w
18 matches
Mail list logo
