[meta-freescale] [meta-fsl-arm-extra PATCH 2/2] linux-boundary: Add support to Vivante 4.6.9p12 GPU code

[Post Lauren-RAA013]

Just to clear up some confusion

For gpu-viv-bin-mx6 packages
- 3.0.35-4.1.0 is also p12 with some fixes on top of 3.5.7-1.0.0 alpha (but only swfp)

We are planning to update in a few weeks in master branch a new 3.5.7 gpu-viv-bin-mx6q that has same fixes from 3.0.35-4.1.0 release.

The question about using an alpha package on a production system in this case is not an issue since 3.0.35-4.1.0 is using updated p12 gpu-viv-bin-mx6q version that 3.5.7 used.

Hope this clears this up.  The 3.0.35-4.1.0 has a fix for the performance issue with window mode as shown in es2gears-x11 (not glxgears).  It does not fix the glmark2 crash with the new version on master (dylan version does not have crash) - there is a workaround posted on bugzilla.  There might be more fixes but I'll document them when the package is ready to go public.  

Lauren Post

-----Original Message-----
From: meta-freescale-bounces at yoctoproject.org [mailto:meta-freescale-bounces at yoctoproject.org] On Behalf Of Daiane Angolini
Sent: Monday, August 12, 2013 12:20 PM
To: Eric Nelson
Cc: meta-freescale Mailing List; Otavio Salvador
Subject: Re: [meta-freescale] [meta-fsl-arm-extra PATCH 2/2] linux-boundary: Add support to Vivante 4.6.9p12 GPU code

On 08/12/2013 02:07 PM, Eric Nelson wrote:
> On 08/12/2013 09:45 AM, Daiane Angolini wrote:
>> On 08/12/2013 01:34 PM, Otavio Salvador wrote:
>>> On Mon, Aug 12, 2013 at 12:48 PM, Eric Nelson 
>>> <eric.nelson at boundarydevices.com> wrote:
>>>> On 08/12/2013 08:18 AM, Otavio Salvador wrote:
>>>>>
>>>>> On Mon, Aug 12, 2013 at 11:05 AM, Eric Nelson 
>>>>> <eric.nelson at boundarydevices.com> wrote:
>>>>>>
>>>>>> On 08/12/2013 05:50 AM, Otavio Salvador wrote:
>>>>>>>
>>>>>>> On Sat, Aug 10, 2013 at 7:12 PM, Eric Nelson 
>>>>>>> <eric.nelson at boundarydevices.com> wrote:
>>>>>>>>
>>>>>>>> Right now, gpu-viv-bin-mx6q-3.5.7-1.0.0-hfp.bin only supports 
>>>>>>>> hard float. Will the EABI (4.0.0) binaries continue to be 
>>>>>>>> supported or will there be a corresponding package of EABI binaries?
>>>>>>>
>>>>>>>
>>>>>>> There's also a gpu-viv-bin-mx6q-3.5.7-1.0.0-sfp.bin and it is 
>>>>>>> taken in case you're building for Soft Float-Point. It should 
>>>>>>> 'Just Work'.
>>>>>>>
>>>>>>
>>>>>> If that's the case, we can just push the patches onto our main 
>>>>>> branch and not deal with the old/new GPU package question.
>>>>>
>>>>> Not really as it will make impossible for your customers to use 
>>>>> the kernel with LTIB at 4.0.0 BSP (well, I'd love they stop using 
>>>>> it but...).
>>>>>
>>>>
>>>> It's not just LTIB that's a question mark. The same comment goes 
>>>> for Debian, Buildroot, Timesys, Ubuntu, Arch or home-brew 
>>>> userspaces.
>>>>
>>>> If it's Freescale's recommendation that this GPU package is the 
>>>> **right** one for production use, our primary kernel branch should 
>>>> probably reflect that.
>>>
>>> I think the recommendation is to stay in their 'official' and 'test'
>>> set of packages so I think it is better to have p12 support as 
>>> patches so it is clear it is something we are doing 'by ourselves'.
>
> Okay. I didn't mean to open a can of worms here. I was just trying to 
> simplify things.
>
>>
>> 3.5.7-1.0.0 - is an alpha release. It does not have the same "stability"
>> comparing with a GA release. It is not shared with *all* customers.
>>
>
> My bad. I figured since patches were being released into the wild, 
> this is officially "shared".

If you try to look for the release under the normal freescale.com/imx you will not see it.

Please, don't ask me what's the difference.

>
>>>
>>>> There's no reason someone using another userspace builder can't 
>>>> patch their process to update things.
>>>
>>> Well yes but it makes their life harder and a branch which won't 
>>> work with 'official' package set. So I think patches are the way to 
>>> go for now.
>>>
>>>> That said, I haven't quite heard this as Freescale's recommendation.
>>>> Daiane, I don't suppose you want to stick your neck out...?
>>>
>>> Poor Daiane ;-)
>
> I'm not trying to get you in trouble, Daiane. Just trying to grok the 
> current status.

I know that ;)

>
>>
>> When I'm talking to meta-freescale I'm "Freescale". When I'm talking 
>> to guys inside Freescale, I'm "community".
>>
>
> But but but, we're all the "community", right?
>
> We're all trying to get the best stuff into end-users' hands so they 
> can build great applications with a minimum of hassle!
>
>> Here, I can only say public and official stuff. If you need 
>> Freescale's help, please enter a SR or a question on imx-community.
>>
>> =(
>>
>
> Sounds scary! Like there may be lawyers trolling there ;)

lawyers, ninjas, gnomes, who knows?

>
> Regards,
>
>
> Eric
>


--
Daiane

_______________________________________________
meta-freescale mailing list
meta-freescale at yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale