[yocto] Graphics Acceleration on crownbay - 1.2M3 + meta-intel tip

[Autif Khan]

>> >> >> >> Minor correction to the subject - I am using 1.2M3, not 1.2M2
>> >> >> >>
>> >> >> >> On Wed, Mar 21, 2012 at 4:14 PM, Autif Khan <autif.mlist at gmail.com> wrote:
>> >> >> >> > I am trying to get hardware accelerated graphics (video in particular)
>> >> >> >> > to work on my crownbay based hardware. I have EMGD 1.10 driver
>> >> >> >> > integrated and working. The evidence for this is that when I use
>> >> >> >> > glxgears (form mesa-demos) I get 115 fps instead of 4-5 fps.
>> >> >> >> >
>> >> >> >> > This is good, however, when I go over to the web2 browser (enabled by
>> >> >> >> > defining WEB = "web-webkit" for recipe task-core-apps-x11-pimlico) - I
>> >> >> >> > do not get graphics acceleration for javascript graphics. I also do
>> >> >> >> > not get graphics acceleration when I watch an MP4 movie. I get 2-3 fps
>> >> >> >> > instead of the standard 25 or 29 fps.
>> >> >> >> >
>> >> >> >> > This was not the case when Yocto used EMGD 1.8 driver - video worked
>> >> >> >> > fine - I am not sure about accelerated javascript based graphics in
>> >> >> >> > browser as I was not as far ahead in the project.
>> >> >> >> >
>> >> >> >> > Is this a known issue?
>> >> >> >> >
>> >> >> >
>> >> >> > When I tested video using gst-launch, I saw the same thing, which was
>> >> >> > due to a missing libva-tpi.  The latest commit in meta-intel added that
>> >> >> > and fixed the problem for me.
>> >> >> >
>> >> >> > commit 162f3d1d3c538d7582a5e81205a9cdab74125b2b
>> >> >> > Author: Tom Zanussi <tom.zanussi at intel.com>
>> >> >> > Date:   Mon Mar 12 19:57:29 2012 -0500
>> >> >> >
>> >> >> >    ia32-base: add libva display dependencies to emgd xserver
>> >> >> >
>> >> >>
>> >> >> I did a build today with tip - I have confirmed that I have this in the source.
>> >> >>
>> >> >> What files should have been added to the root filesystem image as a
>> >> >> reult of adding libva-tpi, libva-glx and libva-egl?
>> >> >>
>> >> >
>> >> > You should see those shared libraries in /usr/lib
>> >>
>> >> I think that I do:
>> >>
>> >> root at crownbay:/usr/lib# ls -l *libva*
>> >> lrwxrwxrwx    1 root     root            19 Mar 21 17:38
>> >> libva-egl.so.1 -> libva-egl.so.1.0.12
>> >> -rwxr-xr-x    1 root     root          3040 Mar 21 17:07 libva-egl.so.1.0.12
>> >> lrwxrwxrwx    1 root     root            19 Mar 21 17:38
>> >> libva-glx.so.1 -> libva-glx.so.1.0.12
>> >> -rwxr-xr-x    1 root     root         14868 Mar 21 17:07 libva-glx.so.1.0.12
>> >> lrwxrwxrwx    1 root     root            19 Mar 21 17:38
>> >> libva-tpi.so.1 -> libva-tpi.so.1.0.12
>> >> -rwxr-xr-x    1 root     root          3856 Mar 21 17:07 libva-tpi.so.1.0.12
>> >> lrwxrwxrwx    1 root     root            19 Mar 21 17:38
>> >> libva-x11.so.1 -> libva-x11.so.1.0.12
>> >> -rwxr-xr-x    1 root     root         28476 Mar 21 17:07 libva-x11.so.1.0.12
>> >> lrwxrwxrwx    1 root     root            15 Mar 21 17:38 libva.so.1 ->
>> >> libva.so.1.0.12
>> >> -rwxr-xr-x    1 root     root         68816 Mar 21 17:07 libva.so.1.0.12
>> >>
>> >> The older image did not have egl, glx and tpi
>> >>
>> >> However, when I execute gst-launch -v playbin2 uri=file:///media/hdd/BBB.ogv
>> >>
>> >> I get a lot of "There may be a timestamping problem, or this computer
>> >> is too slow." warnings.
>> >>
>> >> Attached are the logs created by the above command.
>> >>
>> >> Is there something else that needs to be done?
>> >
>> > Hmm, looks like the acceleration isn't kicking in.  Is that a supported
>> > format for emgd accelaration? - I've been testing with 1080p .h264
>> > videos, http://www.bigbuckbunny.org/index.php/download/, maybe if you
>> > could try that so we know we're on the same page.
>> >
>>
>> I was hoping that Ogg Video is supported.
>>
>> I tried the H.264 (BBB stands for bigbuck bunny, I got these movies
>> from an earlier email from you). But I am getting another error -
>> ERROR: pipeline doesn't want to preroll.
>>
>> Do I need some other codec or some library? Are there licensing
>> implications of using H.264?
>
> It should work as-is - the image I tested wasn't against 1.2M3, but
> that's what I'll now build and try again myself.
>
> So just for more information, all this used to work using emgd 1.8, but
> the same thing with 1.10 no longer does?


Yes, all this worked for 1.8, it does not seem to work for 1.0 anymore.


> Could you also send the debug output for that and also the output of
> 'gst-inspect'?

I have attached the log files (zipped)

The directory called "works" have logs from machine that runs EMGD
1.8. There are 4 logs file. BBB is Big Buck Bunny. Simpsons is a
trailer. 3 of these work, BBB.ogv does not work - the framerate is
very bad. Simpsons.ogv runs just fine. The difference is that BBB.ogv
was downloaded from the site you sent and Simpsons.ogv was transcoded
by me using tools on Ubuntu. gstinspect log is also included.

The directory called "does_not_work" has all the same logs. ogv for
both run with a framerate of 0.5 or less. H.264 and MP4 do not work at
all - they error out with "Failed to init mixvideo" and "pipeline
doesn't want to preroll."

The directory called "works_master" is the super latest master tip
build and it seems like the behavior it is identical to EMGD 1.8 -
everything works except BBB.ogv, however, Simpsons.ogv works just
fine.

At this point of time - the issue is resolved.

However, if a video guru can figure out why BBB.ogv does not work
where as Simpsons.ogv works from the logs, I will be more than happy.

Tom, Thanks for all the help :-)

I took me a while to build the latest master tip and the old build
with 1.8 drivers - but it seems to have paid off. Thanks again!

> The licensing implications are mentioned in the EMGD documentation, but
> I've also discussed them with Jeffrey Moore, so you might want to talk
> to him about the details for your project.

Apologies for this - JM set me straight.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logs.tgz
Type: application/x-gzip
Size: 52199 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20120322/21cf3866/attachment.bin>