[meta-intel] Xrandr support on CrownBay with EMGD

[Kamble, Nitin A]

Hi Chad,
  To avoid the v1.3 beta version, I have moved the libxrander recipe back to v1.2.3 now. The new commit is in the same branch.

Thanks,
Nitin


From: meta-intel-bounces at yoctoproject.org [mailto:meta-intel-bounces at yoctoproject.org] On Behalf Of Kamble, Nitin A
Sent: Thursday, January 09, 2014 3:31 PM
To: Burton, Ross
Cc: meta-intel at yoctoproject.org; Chad Bishop
Subject: Re: [meta-intel] Xrandr support on CrownBay with EMGD



From: Burton, Ross [mailto:ross.burton at intel.com]
Sent: Thursday, January 09, 2014 1:00 PM
To: Kamble, Nitin A
Cc: Chad Bishop; meta-intel at yoctoproject.org<mailto:meta-intel at yoctoproject.org>
Subject: Re: [meta-intel] Xrandr support on CrownBay with EMGD

On 9 January 2014 19:56, Kamble, Nitin A <nitin.a.kamble at intel.com<mailto:nitin.a.kamble at intel.com>> wrote:
I have resurrected coupel of xrandr recipes in the meta-intel test branch here:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-contrib/log/?h=nitin/misc

I have not got a chance to validate these commits. In addition, I am not sure whether both xrander and libxrander need to be changed.
If you get a chance, can you try these commits? Mark these specific versions as a dependency on the EMGD, and rebuild and test the BSP. If it solves the issue we can push some commits to fix this issue in the meta-intel.

Version 1.2.99.4 indicates that it's actually a 1.3 beta, so if you really need 1.2.x then I suggest you downgrade some more.  That said I'm very curious as to why xrandr 1.2 will work, considering that the xrandr protocol is versioned and the clients will use whatever version is supported by the server (unless the backward compatibility code has broken, in which case fixing that is preferable).

Ross


  Thanks for pointing out the beta version Ross. It is not clear yet whether changing the xrandr version solves the issue. One would expect the newer version to support the older API. If that is broken I would also prefer to fix it, assuming it can be done easily.

Nitin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-intel/attachments/20140109/61157898/attachment-0001.html>