The EGL backend is broken? I didn't notice. I ran chromium with EGL and GLESv2 based rendering successfully with it.

I vote for option 1. Option 2 means there wouldn't be an FSL supported kernel in master until January, which is a rather strange situation. I understand FSL wants to maximize the feedback they get, but isn't it important to have a FSL supported kernel available? Yes, it is there in daisy, but master is a reviewed branch, so customers can actually use it. Instead, I'd keep 3.10.17 , but encourage customers and hobbyists to try out the beta, since they would benefit from this as well.

On 08/18/2014 05:54 PM, Alfonso Tamés wrote:
Option 2! 3.10.17 seems to have the EGL backend broken so let's embrace the 
future in master branch.

Thanks,

Alfonso

On 18/08/2014, at 10:32, Lauren Post <[email protected]> wrote:

Our 3.10.31-1.1.0 Beta release is now in field trial to be completed by next 
week.  My team will be up-streaming this release next week into master-next 
branch.

This release has the following new features
    -  Kernel upgrade to 3.10.31
    -  Supports new i.MX6 SoloX SabreSD machine
    -  U-Boot-imx upgrade to 2014.04 version
    -  New GPU Vivante version v5
        o   Supports OpenGLES 3.0 APIs with backward compatibility with earlier 
version APIs.
        o   DirectFB 1.7.1
        o   Wayland 1.5
        o   Xorg 1.15
        o   Qt5 fixes for X11, Wayland and Framebuffer backends on i.MX parts 
containing 3D GPU.
        o   i.MX 6 SoloLite fixes for DirectFB, Wayland and frame buffer 
backends.
        o   fsl-gpu-sdk version 1.2 supporting all backends.
    -   Multimedia Features
        o   Freescale Gstreamer 1.0 support
        o   Gstreamer 0.1 Fixes
        o   Upgraded VPU firmware and wrapper software
        o   G2D integration

We have a question to community.  Our 3.10.31-1.1.0 GA release is not 
public/released until January.   We have two options for upstream of 3.10.31 
into meta-fsl-arm and would like feedback from community.

- Option 1 - Upstream 3.10.31 beta into master-next branch and branch master 
with 3.10.17 once Yocto Project 1.7 name is announced in late Sept or early 
October
    o   This means that 3.10.31-1.1.0_beta will be in master-next branch during 
September.
    o   Also means Freescale will get less feedback from community to fix for 
our 3.10.31-1.1.0 GA release.
    o   3.10.31-1.1.0 GA will be part of Yocto Project 1.8 release only in 
April 2015.
- Option 2 - Upstream 3.10.31-1.1.0 Beta into master branch and remove 3.10.17 
from master branch.
    o   This means Yocto Project 1.7 release will not be production code for 
i.MX6 until our 3.10.31-1.1.0 GA release planned in January.
    o   Allows earlier production release of 3.10.31-1.1.0 GA with SoloX and 
Graphics as part of Yocto Project 1.7 in January.
    o   Beta is not supported (by freescale/for production/by SR).  However 
bugs can be sent to imx-community and if time before GA code freeze Freescale 
can try to fix in our GA release.

Please provide your feedback.  Freescale prefers Option 2 because we can get 
more feedback about bugs to fix in our 3.10.31-1.1.0 GA release but we will 
abide by community wishes if they prefer Option 1.

Thanks,
Lauren Post
Yocto Project i.MX Team Lead

--
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale

--
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale

Reply via email to