Re: wayland/weston on displaylink?

yan.w...@linux.intel.com wrote (ao): > > Would it be possible to run weston on a displaylink device? > > By my understanding, display link device should have multiply methods to > display. One is capture screen image by software and transferring by USB, > another is construct one virtual display d

Re: wayland/weston on displaylink?

> Hello All, > > Would it be possible to run weston on a displaylink device? By my understanding, display link device should have multiply methods to display. One is capture screen image by software and transferring by USB, another is construct one virtual display driver to capture as the second d

Re: Wayland client library thread safety

On Mon, Apr 30, 2012 at 3:58 PM, Kristian Høgsberg wrote: > On Fri, Apr 27, 2012 at 11:09:55PM +0200, Arnaud Vrac wrote: >> On Fri, Apr 20, 2012 at 10:06 PM, Kristian Hoegsberg >> wrote: >> > On Thu, Apr 19, 2012 at 03:38:39PM +0200, Arnaud Vrac wrote: >> >> Hello everyone, >> >> >> >> I am hitti

Re: Wayland client library thread safety

On Fri, Apr 27, 2012 at 11:09:55PM +0200, Arnaud Vrac wrote: > On Fri, Apr 20, 2012 at 10:06 PM, Kristian Hoegsberg > wrote: > > On Thu, Apr 19, 2012 at 03:38:39PM +0200, Arnaud Vrac wrote: > >> Hello everyone, > >> > >> I am hitting a bug when using Qt5 and wayland on an embedded platform, > >> f

Re: Weston on Android - First light

On Sat, 28 Apr 2012 10:00:18 +0800 Alex Wu wrote: > 于 2012/4/27 20:56, Pekka Paalanen 写道: > > Hi all, > > > > I am happy to announce the first step towards a Wayland stack on > > Android: simple-shm runs with Weston on a Galaxy Nexus! > > > > The whole story, a picture, and a video: > > http://pp

wayland/weston on displaylink?

Hello All, Would it be possible to run weston on a displaylink device? I compiled a 3.4-rc5 kernel with: x301:/usr/src/linux-3.4-rc5# grep DRM.*=y .config CONFIG_DRM=y CONFIG_DRM_USB=y CONFIG_DRM_KMS_HELPER=y CONFIG_DRM_UDL=y And get a text console on a Samsung Syncmaster 2243qw, connected to a

Re: [PATCH 1/2] compositor-drm: call EGL cleanup functions on exit

On Mon, Apr 30, 2012 at 01:31:28PM +0300, Ander Conselvan de Oliveira wrote: That looks good, applied. Kristian > --- > src/compositor-drm.c |6 ++ > 1 files changed, 6 insertions(+), 0 deletions(-) > > diff --git a/src/compositor-drm.c b/src/compositor-drm.c > index dcd5e99..e7433f7 1

Re: [PATCH 2/2] compositor-drm: don't create and destroy kms fbs on every frame

On Mon, Apr 30, 2012 at 01:31:29PM +0300, Ander Conselvan de Oliveira wrote: > Use the new gbm_get/set_user_data() to reuse the kms fbs if the gbm > surface's bo's are reused. This doesn't look right. drm_output_render() always allocates and sets user data, which overwrite previously set user dat

[PATCH 2/2] compositor-drm: don't create and destroy kms fbs on every frame

Use the new gbm_get/set_user_data() to reuse the kms fbs if the gbm surface's bo's are reused. --- src/compositor-drm.c | 94 +++-- 1 files changed, 75 insertions(+), 19 deletions(-) diff --git a/src/compositor-drm.c b/src/compositor-drm.c index e7433

[PATCH 0/2] Reuse kms fbs

Instead of creating and destroying a kms fb object on every frame, use gbm_bo_get/set_user_data() to store the fb object in a gbm_surface bo and reuse it when needed. This depends on the gbm patches I just sent to the mesa-dev mailing list. I needed the first patch to be able to test the changes

[PATCH 1/2] compositor-drm: call EGL cleanup functions on exit

--- src/compositor-drm.c |6 ++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/src/compositor-drm.c b/src/compositor-drm.c index dcd5e99..e7433f7 100644 --- a/src/compositor-drm.c +++ b/src/compositor-drm.c @@ -1578,6 +1578,12 @@ drm_destroy(struct weston_compositor *ec)