[meta-freescale] RFC regarding glimagesink

Rogerio Nunes ronunes at gmail.com
Mon Jul 29 12:29:13 PDT 2013


My apologies, Eric.

I misread your email the first time.

I'm trying a clean build now with master-next, but I'm having dependency issues.
As soon as I fix this I'll look into glimagesink.

On Mon, Jul 29, 2013 at 11:08 AM, Eric Nelson
<eric.nelson at boundarydevices.com> wrote:
> Thanks Rogerio,
>
>
> On 07/29/2013 07:35 AM, Rogerio Nunes wrote:
>>
>> Hi Eric,
>>
>> I've been usually working without X, so don't know much about glimagesink.
>> I have some comments about bitbuck branches bellow.
>>
>
> Note that my testing was also without X.
>
>> On Sun, Jul 28, 2013 at 7:44 PM, Eric Nelson
>> <eric.nelson at boundarydevices.com> wrote:
>>>
>>> Hi all,
>>>
>>> <snip>
>
>>>
>>>
>>> By the way, the attached patch is against branch fsl-0.10
>>> in the Bitbucket tree, which appears to match up with the
>>> Yocto build, but I notice that Jeremy has a patch applied
>>> in the Yocto-0.10.
>>>
>>> Is 'fsl-0.10' the right baseline to use for future work?
>>
>>
>> fsl-0.10 - branch with  "as is" code from fsl BSPs.
>>
>> yocto-0.10 - branch with patch(es) from the poky layer
>>
>> 0.10 - branch to merge fsl-0.10, yocto-0.10, upstream-0.10 and to
>> refactor the code to port to master (still ongoing)
>>
>
> That's good to know.
>
> Regards,
>
>
> Eric
>



More information about the meta-freescale mailing list