From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.cybertec.at (ns.km31432.keymachine.de [87.118.86.135]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id E9221E00BE0 for ; Fri, 4 Apr 2014 02:28:52 -0700 (PDT) Received: from localhost.localdomain (unknown [87.242.12.103]) by mail.cybertec.at (Postfix) with ESMTPSA id 1CCE23900FB2; Fri, 4 Apr 2014 09:28:31 +0000 (UTC) Message-ID: <533E7B3F.4030602@pr.hu> Date: Fri, 04 Apr 2014 11:28:31 +0200 From: Boszormenyi Zoltan User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Carlos Rafael Giani , 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> <533C0265.7090603@pseudoterminal.org> In-Reply-To: <533C0265.7090603@pseudoterminal.org> 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: Fri, 04 Apr 2014 09:28:53 -0000 Content-Type: multipart/alternative; boundary="------------040709060003090806050703" --------------040709060003090806050703 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit 2014-04-02 14:28 keltezéssel, Carlos Rafael Giani írta: > 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. A comment on that page says to use these flags (Chrome branding is not needed, only chromeos=1): export GYP_DEFINES="chromeos=1 proprietary_codecs=1 ffmpeg_branding=Chrome" do_configure succeeds but do_compile fails with "brlapi.h" missing. A google search gave me this: https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/StpTzFnf8ok Supposedly, running "build/install-build-deps.sh" fixes it but it turned out it only fixes things for building Chromium for the host and the script wants an Ubuntu host OS. Is there a ready to use recipe for brlapi/brltty somewhere or should I make one? Thanks in advance, Zoltán Böszörményi --------------040709060003090806050703 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
2014-04-02 14:28 keltezéssel, Carlos Rafael Giani írta:
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.

A comment on that page says to use these flags (Chrome branding is not needed, only chromeos=1):

export GYP_DEFINES="chromeos=1 proprietary_codecs=1 ffmpeg_branding=Chrome"

do_configure succeeds but do_compile fails with "brlapi.h" missing. A google search
gave me this: https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/StpTzFnf8ok
Supposedly, running "build/install-build-deps.sh" fixes it but it turned out it only fixes
things for building Chromium for the host and the script wants an Ubuntu host OS.

Is there a ready to use recipe for brlapi/brltty somewhere or should I make one?

Thanks in advance,
Zoltán Böszörményi

--------------040709060003090806050703--