From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: Christian Betz <christian.betz@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Chromium acceleration
Date: Wed, 02 Apr 2014 14:28:21 +0200 [thread overview]
Message-ID: <533C0265.7090603@pseudoterminal.org> (raw)
In-Reply-To: <CAC9ffDFbv2iUDU72W+O1UnjD6Ff6ikbb7u7R-QrY3BX2QuWBoQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
On 2014-04-02 14:02, Christian Betz wrote:
>
> The VPU part could be because of missing firmware. Check if
> the vpu files are present in /lib/firmware.
>
> As for MP4, this is a known problem. You are building Chromium,
> not Chrome. MP4 support is part of the restricted feature set,
> which is included in Chrome but not Chromium. Try a WebM file for
> example.
>
>
> this apparently can be worked around with gyp options:
>
> "proprietary_codecs=1 ffmpeg_branding=Chrome branding=Chrome to allow
> Chrome to play h.264 content, which is the only codec VAVDA knows
> about today."
>
> this is described on a wiki page setting up hw video decode on
> **intel** processors:
>
> https://code.google.com/p/chromium/wiki/LinuxHWVideoDecode
>
> note: i haven't actually tried this! (but i would like to)
We tried that back then. The Chrome branding enabled a million other
things , which caused all sorts of difficulties. Also note that enabling
the Chrome branding might have legal repercussions.
[-- Attachment #2: Type: text/html, Size: 2597 bytes --]
next prev parent reply other threads:[~2014-04-02 12:28 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
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 [this message]
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=533C0265.7090603@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=christian.betz@gmail.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.