[meta-freescale] Chromium acceleration
eric.nelson at boundarydevices.com
Wed Mar 19 19:50:42 PDT 2014
On 03/19/2014 06:29 PM, Christian Betz wrote:
> The Vivante libraries can map the physical buffers produced by
> the VPU directly, so they could do format conversion on their
> way to the graphics stack if the Chromium bindings have access
> to that (the "single copy" I referred to above).
> in my experience "zero-copy" really means zero memcpy() (or similar
> system call, or really anything that involves the cpu to move around
> image data. /metadata /such as buffer pointers is generally allowed). in
> other words having the GPU do format conversion isn't considered a copy.
> here's a great article on this general technique implemented in
That's a nice article, and if Webkit (Blink) retains the same mapping,
video buffers from the VPU would end up hitting a RenderObject and
the only "copy" would be in rendering that to the Framebuffer.
Since we're on the fat end of the pipe here, that copy can be expensive
and might limit things to 1x1080P decode, but I'd be happy with that.
In the mfw_v4lsink case at least, this can be bypassed by having
the V4L2 buffer filled by the VPU and also displayed by the IPU
(such that copy), but aiming there would keep the video out of the
rest of the RenderLayer tree (I think).
This is what I was so awkwardly trying to suggest.
> moving beyond semantics... let me tell you what i know about this
> particular issue:
> there is source code in chromium to accomplish a similar goal.
> specifically there is a "generic" android driver, which works out of the
> box with i.mx6 because freescale implements the standard android video
> decode interface that allows VPU -> GPU texture uploading (don't quote
> me on this, i'm just reading the source code:
> sadly there is no such standard interface on GNU/Linux. outside of
> android (i.e. chromeos), there are drivers for particular chipsets, like
> samsung exynos. here is the source for that:
> the group should also be aware of the current situation regarding these
> modules /only/ working when certain flags to enable "chromeos" are used
> (explained here:
> https://code.google.com/p/chromium/wiki/LinuxHWVideoDecode). in other
> words: this stuff doesn't work on your x86 with the chrome you download
> from google.
Again, thanks for the info.
More information about the meta-freescale