From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ptmx.org (ptmx.org [178.63.28.110]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id BA42BE00BD3 for ; Wed, 2 Apr 2014 05:28:23 -0700 (PDT) Received: from [10.1.14.248] (unknown [91.114.0.140]) by ptmx.org (Postfix) with ESMTPSA id BD73B22757; Wed, 2 Apr 2014 14:28:21 +0200 (CEST) Message-ID: <533C0265.7090603@pseudoterminal.org> Date: Wed, 02 Apr 2014 14:28:21 +0200 From: Carlos Rafael Giani User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Christian Betz References: <532A02E5.7060607@boundarydevices.com> <532A057E.2010805@pseudoterminal.org> <532A1CC6.1020609@boundarydevices.com> <532A5782.4050809@boundarydevices.com> <532AA723.1010901@pseudoterminal.org> <532B7776.5090700@pseudoterminal.org> <533B11E6.5040103@boundarydevices.com> <533BE4A3.7040301@pr.hu> <533BE511.8020608@pseudoterminal.org> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" Subject: Re: Chromium acceleration X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2014 12:28:24 -0000 Content-Type: multipart/alternative; boundary="------------020302090303030409070008" --------------020302090303030409070008 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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. --------------020302090303030409070008 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
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.
--------------020302090303030409070008--