From: Andy Voltz <andy.voltz@timesys.com>
To: Post Lauren-RAA013 <RAA013@freescale.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm]: Wayland/Weston issue with gpu-viv-bin-mx6q 3.5.7-1.0.0-alpha.2
Date: Thu, 24 Oct 2013 14:07:47 -0400 [thread overview]
Message-ID: <20131024180747.GD25185@timesys.com> (raw)
In-Reply-To: <2BC32295742BF14CA5950C3659567EB6797221@039-SN1MPN1-002.039d.mgd.msft.net>
Hi Lauren,
On Thu, Oct 24, 2013 at 01:47:42PM -0400, Post Lauren-RAA013 wrote:
> Wayland Weston is fully support in 3.10.9-1.0.0 so it is better to use that version over 3.5.7. There were some additional components that needed updates for Weston to work outside of the graphics package that are in the 3.10.9-1.0.0 alpha release. These changes are in master-next now.
>
Is it ill-advised to use the gpu-viv-bin-mx6q binaries with the 3.0.35-4.1.0 release? It passed a smoke test with wayland, but I haven't dug in further with X, dfb, fb.
Perhaps we'll only pull in the -wl.so libraries for 4.1.0 for now until 3.10 is non-alpha.
Also, when I tried the vivante samples in a 3.10 master-next build, they seemed to take over the framebuffer. The weston 'simple-egl' client runs in a window without an issue. Can you recommend any other tests from viv_samples, or is this pretty much expected functionality? Just trying to make sure things are working properly in our environment.
Thanks for the clarification.
Regards
--
Andy Voltz
Timesys Corporation
next prev parent reply other threads:[~2013-10-24 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 16:06 [meta-fsl-arm]: Wayland/Weston issue with gpu-viv-bin-mx6q 3.5.7-1.0.0-alpha.2 Andy Voltz
2013-10-24 17:47 ` Erik Botö
2013-10-24 17:47 ` Post Lauren-RAA013
2013-10-24 18:07 ` Andy Voltz [this message]
2013-10-24 20:32 ` Post Lauren-RAA013
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131024180747.GD25185@timesys.com \
--to=andy.voltz@timesys.com \
--cc=RAA013@freescale.com \
--cc=meta-freescale@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.