From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm-extra PATCH 2/2] linux-boundary: Add support to Vivante 4.6.9p12 GPU code
Date: Mon, 12 Aug 2013 07:05:06 -0700 [thread overview]
Message-ID: <5208EB92.3010108@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKo5y7-cr_AUKJv_GGX=aY7T3QSWRw_e_j7mEGzOMeCfyg@mail.gmail.com>
Thanks Otavio,
On 08/12/2013 05:50 AM, Otavio Salvador wrote:
> On Sat, Aug 10, 2013 at 7:12 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> On 08/10/2013 12:25 PM, Otavio Salvador wrote:
>>> On Sat, Aug 10, 2013 at 3:10 PM, Eric Nelson
>> Oops. I grabbed this from the first patch file in the series.
>> I renamed the branch in case it's helpful:
>> boundary-imx_3.0.35_4.0.0-plus-vivante-4.6.9p11.1
>
> Fine. Thanks.
>
>>>> Does anybody know if there are ABI changes in the corresponding
>>>> userspace bits?
>>>
>>>
>>> It has.
>>>
>>
>> If so, then we'll want them segregated into separate branches or the
>> patch files conditionally applied, right?
>>
>> 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.
> So far, all worked fine for me. Can you give it a try?
>
Absolutely. I'll give this a spin.
next prev parent reply other threads:[~2013-08-12 14:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 18:59 [meta-fsl-arm-extra PATCH 1/2] linux-wandboard: Add support to Vivante 4.6.9p12 GPU code Otavio Salvador
2013-07-23 18:59 ` [meta-fsl-arm-extra PATCH 2/2] linux-boundary: " Otavio Salvador
2013-08-10 18:10 ` Eric Nelson
2013-08-10 19:25 ` Otavio Salvador
2013-08-10 22:12 ` Eric Nelson
2013-08-12 12:50 ` Otavio Salvador
2013-08-12 14:05 ` Eric Nelson [this message]
2013-08-12 15:18 ` Otavio Salvador
2013-08-12 15:48 ` Eric Nelson
2013-08-12 16:34 ` Otavio Salvador
2013-08-12 16:45 ` Daiane Angolini
2013-08-12 17:07 ` Eric Nelson
2013-08-12 17:19 ` Daiane Angolini
2013-08-14 18:09 ` Post Lauren-RAA013
2013-08-12 13:02 ` Daiane Angolini
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=5208EB92.3010108@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.