All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: meta-freescale@yoctoproject.org
Subject: Re: imx6: webkit html5 video with hardware acceleration
Date: Tue, 23 Sep 2014 21:15:46 +0200	[thread overview]
Message-ID: <5421C6E2.9040202@pseudoterminal.org> (raw)
In-Reply-To: <20140923190600.GB24931@netboy>

[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]

On 2014-09-23 21:06, Richard Cochran wrote:
> On Tue, Sep 23, 2014 at 11:55:55AM -0700, Bin Lin wrote:
>> We tried to get the HTML5 playback working with Qt5.2.1 webkit on
>> daisy branch.  It hangs when it is trying to play.  We tried it on
>> both the youtubeview example of Qt5 webkitqml and the browser
>> example of webkitwidgets, eglfs setup.  The results are the same.
> Right, both Qt4 and Qt5 webkits also don't work.
>
>> What are the steps you followed to make the HTML5 at least to play
>> under webkit?
> That is the point. It doesn't play videos.
>
> The 'daisy' branch has midori, and I was able to build midori without
> any issues, and this builds webkit.
>
> IIRC, you can see that webkit-gtk will start gstreamer, but there is
> no picture at all.
>
> Sorry,
> Richard

Oh that is probably because it is using GStreamer 0.10. The 0.10 
Freescale plugins for the VPU are known to not work with WebKit. See 
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4155 and 
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4156. Check if it was 
built with its GStreamer 0.10 or 1.0 backend. With 1.0 , you can use 
gstreamer-imx for decoding.

[-- Attachment #2: Type: text/html, Size: 2033 bytes --]

  reply	other threads:[~2014-09-23 19:15 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23 18:13 imx6: webkit html5 video with hardware acceleration Richard Cochran
2014-09-23 18:33 ` Gerard Bucas
2014-09-23 18:55   ` Bin Lin
2014-09-23 19:02     ` Carlos Rafael Giani
2014-09-23 19:14       ` Richard Cochran
2014-09-23 19:20         ` Carlos Rafael Giani
2014-09-23 19:30           ` Richard Cochran
2014-09-23 19:32             ` Carlos Rafael Giani
2014-09-23 19:52               ` Richard Cochran
2014-09-23 19:56                 ` Carlos Rafael Giani
2014-09-23 19:57                 ` Otavio Salvador
2014-09-23 20:12                   ` Richard Cochran
2014-09-23 20:27                     ` Otavio Salvador
2014-09-23 20:42                       ` Richard Cochran
2014-09-23 20:46                         ` Carlos Rafael Giani
2014-09-24  4:50                           ` Richard Cochran
2014-09-24 16:42                             ` Eric Nelson
2014-09-24 17:05                               ` Richard Cochran
2014-09-24  8:58                       ` Richard Cochran
2014-09-24 11:21                         ` Otavio Salvador
2014-09-24 12:07                           ` Richard Cochran
2014-09-24 15:28                             ` Daiane Angolini
2014-09-24 15:32                         ` Bin Lin
2014-09-23 19:26       ` Bin Lin
2014-09-23 19:29         ` Carlos Rafael Giani
2014-09-23 19:06     ` Richard Cochran
2014-09-23 19:15       ` Carlos Rafael Giani [this message]
2014-09-23 19:23         ` Richard Cochran
2014-09-23 19:29           ` Carlos Rafael Giani
2014-09-23 19:39             ` Richard Cochran
2014-09-23 19:44               ` Bin Lin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5421C6E2.9040202@pseudoterminal.org \
    --to=dv@pseudoterminal.org \
    --cc=meta-freescale@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.