Re: fsl framebuffer image ?

[David Hill <David.Hill@Oracle.com>]

I can confirm that wih DISTRO_FEATURES_remove = "x11 wayland" that bitbake qt4e-demo-image is not copying the libEGL.so and friends to the resulting image.

On 2/6/14, Feb 6, 5:48 PM, David Hill wrote:
> On 2/5/14, Feb 5, 12:37 AM, Filip Piechocki wrote:
>> Hi,
>>
>> I currently also needed an image with accelerated framebuffer (so I could run Qt5 eglfs on it) on wandboard-dual. I followed those instructions: http://wiki.wandboard.org/index.php/Building_Qt5_using_yocto_on_Wandboard , with some modifications. I suggest you to do:
>> - add DISTRO_FEATURES_remove = "x11 wayland"
>> - add IMAGE_INSTALL_append = " gpu-viv-bin-mx6q "
>>
>> Then I bitbaked core-image-minimal and it has libGAL, libEGL (and so on) in framebuffer version.
>
> I did a bitbake qt4e-demo-image and did not get the accelerated images as you probably saw earlier.
>
> Turns out that the needed libraries are in the build tree, but the script that picks which of the versions to install may not be correct.
>
> You want these:
> tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/gpu-viv-bin-mx6q/1_3.10.9-1.0.0-hfp-r0/gpu-viv-bin-mx6q-3.10.9-1.0.0-hfp/usr/lib/libEGL-fb.so
> tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/gpu-viv-bin-mx6q/1_3.10.9-1.0.0-hfp-r0/gpu-viv-bin-mx6q-3.10.9-1.0.0-hfp/usr/lib/libGAL-fb.so
> tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/gpu-viv-bin-mx6q/1_3.10.9-1.0.0-hfp-r0/gpu-viv-bin-mx6q-3.10.9-1.0.0-hfp/usr/lib/libVIVANTE-fb.so
>
> It was suggested that I do:
>
> # force the gpu-viv-bin-mx6q install script to fall through to framebuffer
> DISTRO_FEATURES_remove = "x11 wayland"
>
> bitbake qt4e-demo-image
>
> When I did the qt4e-demo-image without the remove, I did get a libEGL.so, but it was libEGL-x11.so based on the checksum. Copying the correct libEGL-fb.so and libGAL.fb allowed me to render to the fb just fine using my test app.
>
> If curious, the install script is sources/meta-fsl-arm/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc, which explained to me why the remove x11 might do something.
>
> But I have not done a second build with the x11 remove quite yet (partly because I misunderstood the suggestion). Perhaps I will know by tomorrow (I have a slow bld machine - 11 plus hours per build).
>
> Dave
>
>
>
>


-- 
David Hill <David.Hill@Oracle.com>
Java Embedded Development

"If you put tomfoolery into a computer, nothing comes out of it but tomfoolery. But this tomfoolery, having passed through a very expensive machine, is somehow ennobled and no-one dares criticize it."
-- Pierre Gallois