From: Gary Thomas <gary@mlbassoc.com>
To: meta-freescale@yoctoproject.org
Subject: Re: [PATCH v2] chromium: Update bbappend to version 37.0.2062.94
Date: Thu, 04 Sep 2014 10:53:33 -0600 [thread overview]
Message-ID: <5408990D.5030302@mlbassoc.com> (raw)
In-Reply-To: <CAP9ODKoXDBRKiLCATBRkXPJU9nQRWi1ss_LkBFrhfY95_vjxig@mail.gmail.com>
On 2014-09-04 10:31, Otavio Salvador wrote:
> On Thu, Sep 4, 2014 at 9:02 AM, Carlos Rafael Giani
> <dv@pseudoterminal.org> wrote:
>> Also update chromium-imx revision to support newer v5 Vivante drivers;
>> these no longer use "GL_VIV_direct_texture" as the name for the Vivante
>> texture extension, but "GL_VIV_tex_direct" instead
>>
>> Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org>
>
> What Daiane means, and which is not clear in the commit log, is if v4
> Vivante drivers also works.
>
Which brings up a related question - how can I tell (and from
which recipe(s)) which version of the Vivante firmware is being
used/installed? I don't recall any mention of v4 vs v5 etc in any
of the recipes which makes it very confusing [at least to me]
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-09-04 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 9:47 [PATCH] chromium: Update bbappend to version 37.0.2062.94 Carlos Rafael Giani
2014-09-04 11:55 ` Daiane Angolini
2014-09-04 12:00 ` [meta-browser][PATCH v2] " Carlos Rafael Giani
2014-09-04 12:01 ` Carlos Rafael Giani
2014-09-04 12:02 ` [PATCH " Carlos Rafael Giani
2014-09-04 16:31 ` Otavio Salvador
2014-09-04 16:53 ` Gary Thomas [this message]
2014-09-04 17:02 ` Otavio Salvador
2014-09-04 17:49 ` [PATCH v3] " Carlos Rafael Giani
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=5408990D.5030302@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=meta-freescale@yoctoproject.org \
/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.