From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
Carlos Rafael Giani <dv@pseudoterminal.org>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Chromium acceleration
Date: Thu, 20 Mar 2014 07:29:54 -0700 [thread overview]
Message-ID: <532AFB62.7030601@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKodBaM+80i2CRKf=cxBK--AQ-n4-FN_3MxpWP1gQYiDzw@mail.gmail.com>
Thanks Otavio,
On 03/20/2014 05:22 AM, Otavio Salvador wrote:
> On Thu, Mar 20, 2014 at 5:30 AM, Carlos Rafael Giani
> <dv@pseudoterminal.org> wrote:
>> Hi Eric and Christian,
>>
>> <snip>
>>
>> As for the decoder itself: I implemented it in the Chromium media framework,
>> in media/ . I simply took the vpx decoder code, copied it, and modified it
>> to use the VPU. I had VP8, MPEG2, MPEG4, and h264 decoding working. It wasnt
>> much code, but unfortunately, the interfaces tend to change between
>> versions, so the code would have to be updated for the newest Chromium
>> version. It is not much code, I will try to clean it up a bit and post it.
>> In addition, I will ask the colleagues for the other patches for
>> accelerating the 2D and WebGL rendering.
>
> \m/ bear on mind I pushed Chromium 35 in meta-browser ;-)
>
I sent an RFC patch yesterday regarding inclusion of meta-qt5 into
fsl-community-bsp-platform.
Is there any interest or conflict in the same for meta-browser?
A simplistic test shows that it's really straightforward to
add both Chromium and Firefox into fsl-image-gui by pulling
in meta-browser.
Regards,
Eric
next prev parent reply other threads:[~2014-03-20 14:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 20:49 Chromium acceleration Eric Nelson
2014-03-19 21:00 ` Carlos Rafael Giani
2014-03-19 22:40 ` Eric Nelson
2014-03-20 1:29 ` Christian Betz
2014-03-20 2:50 ` Eric Nelson
2014-03-20 8:30 ` Carlos Rafael Giani
2014-03-20 12:22 ` Otavio Salvador
2014-03-20 14:07 ` Christian Betz
2014-03-20 15:02 ` Otavio Salvador
2014-03-20 14:29 ` Eric Nelson [this message]
2014-03-20 14:58 ` Otavio Salvador
2014-03-21 11:49 ` Diego
2014-03-21 14:17 ` Eric Nelson
2014-03-20 13:46 ` Christian Betz
2014-03-20 23:19 ` Carlos Rafael Giani
2014-03-21 12:21 ` Dmitriy B.
2014-04-01 19:22 ` Eric Nelson
2014-04-02 10:21 ` Carlos Rafael Giani
2014-04-02 10:28 ` Gary Thomas
2014-04-02 10:33 ` Carlos Rafael Giani
[not found] ` <533BE4A3.7040301@pr.hu>
2014-04-02 10:23 ` Carlos Rafael Giani
2014-04-02 11:12 ` Boszormenyi Zoltan
2014-04-02 12:02 ` Christian Betz
2014-04-02 12:28 ` Carlos Rafael Giani
2014-04-04 9:28 ` Boszormenyi Zoltan
2014-04-02 10:29 ` Boszormenyi Zoltan
2014-04-02 14:16 ` Eric Nelson
2014-03-20 12:47 ` Lauren Post
2014-03-20 14:25 ` Eric Nelson
2014-03-20 14:27 ` Lauren Post
-- strict thread matches above, loose matches on Subject: below --
2014-03-25 9:32 zboszor
2014-03-25 9:35 ` Eric Bénard
2014-03-25 9:46 ` Marco Trillo
2014-03-25 12:58 ` Boszormenyi Zoltan
2014-11-27 10:14 Becue Paul
2014-12-01 14:34 ` Daiane Angolini
2014-12-01 15:07 ` Otavio Salvador
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=532AFB62.7030601@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=dv@pseudoterminal.org \
--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.