From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-f52.google.com (mail-pb0-f52.google.com [209.85.160.52]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 2D919E00B48 for ; Wed, 19 Mar 2014 15:40:11 -0700 (PDT) Received: by mail-pb0-f52.google.com with SMTP id rr13so10224pbb.11 for ; Wed, 19 Mar 2014 15:40:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=rphLinuW8lY5ayfd3DkbMeXtYefQ07gIqJugw4XsF78=; b=Al/mMAKA3amPnNSpPZOe6Mf+A7Xp+REbXwkCaVjUCdDKZJVNgIf1ZMiDmG+fgykQe3 w1WoAHigI9WpYiPEkIaxFNb5O8kUR/tYyjd8r3pJJFlMyk8RyVgmioVybqquEJ9tiBLd BH/NGz+WOLyBAAKs8/mFACsA9uXAs298EBH+yoPIOuDhOrbNp0aRdMSVHdMQ7Ip/QMI1 MR4kIiF8Os65ApXO25hM7uKeDeTMGeoOXNAUSZaoWSwXVZrjfMbW7SaJQKhPO31S2ggy U1FfMZaT8UF6bfvWlWta/Y/5ZB927OjBabrRrxeKaa2YLAf7ED/jPMowQIpMh6V+yH43 kK3w== X-Gm-Message-State: ALoCoQmfbqcy/DTQz37SqnrCpI1kMqOlz7bwSLm3AQAmnTmAOLSotZ90Bqgn4Eaxcbcysl6zlpzS X-Received: by 10.68.198.97 with SMTP id jb1mr41127229pbc.104.1395268811592; Wed, 19 Mar 2014 15:40:11 -0700 (PDT) Received: from [192.168.0.53] ([63.226.49.26]) by mx.google.com with ESMTPSA id pq3sm508967pbb.57.2014.03.19.15.40.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Mar 2014 15:40:10 -0700 (PDT) Message-ID: <532A1CC6.1020609@boundarydevices.com> Date: Wed, 19 Mar 2014 15:40:06 -0700 From: Eric Nelson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Carlos Rafael Giani , meta-freescale@yoctoproject.org References: <532A02E5.7060607@boundarydevices.com> <532A057E.2010805@pseudoterminal.org> In-Reply-To: <532A057E.2010805@pseudoterminal.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, 19 Mar 2014 22:40:13 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi Carlos, On 03/19/2014 02:00 PM, Carlos Rafael Giani wrote: > Hello, > > I wrote a patch for VPU acceleration in Chromium months ago for a > company project. I got the OK from the customer to cleanup and > eventually opensource the patches, but didn't have the time yet. You're the man! What can we do to help find you the time? > Together with other colleagues we also got HW-accelerated WebGL to work, > though some other areas weren't running so well (multitouch for > example). Also, Canvas remained unaccelerated. As the Chromium > developers explained, there are conceptual problems with the Canvas API > that make acceleration difficult. > Nice! I have to admit being a bit less interested in WebGL than in video acceleration, but I'm sure others really want this. > > What is also missing is a zerocopy method for displaying video frames. > Do we really want zero copy? It seems that at some level, having a single copy into a GPU accelerated rendering stack is more convenient. > In theory, the direct textures from the Vivante GPU could be used; > however, this requires passing the physical buffers through to a > modified renderer somehow. > > Chromium can use OpenGL ES for rendering everything, but does not > contain anything to introduce special video textures yet. > I'm not quite sure I'm grokking this. 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). Or, (he says instead of finding the code), is this handled by ffmpeg-mt? Using an IPU overlay (a.la. mfw_v4lsink) is nice, but makes doing overlays and such more difficult, and you probably know how web-developers can be ;). Regards, Eric