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.
--
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale
