[Buildroot] [PATCH v2 1/2] libimxvpuapi: add new package

[Gary Bisson]

Hi Peter,

On Wed, Feb 17, 2016 at 1:30 PM, Peter Seiderer <ps.report at gmx.net> wrote:
> Hello Gary,
>
>> <snip>
>> > No, working with boundarydevices linux-imx6-f4c8395 and original boundary config
>> > and there is a '/dev/galcore' entry on the target...
>>
>> Yes but that is the problem. Please try again with
>> BR2_PACKAGE_KERNEL_MODULE_IMX_GPU_VIV.
>>
>> As you know, 3D graphics libraries match a specific kernel driver.
>> Since it was an issue for many people, Vivante started to provide a
>> kernel module so you can easily have the latest driver on an older
>> kernel.
>>
>> Since I've updated the graphics to the latest (5.0.11 p7.1), the
>> driver inside the 3.14.28 kernel is outdated so you need to use the
>> Vivante kernel module. I didn't for the selection of the kernel module
>> when the libraries are selected since some kernels (3.14.52) have the
>> correct driver built-in.
>>
>
> Got it now, the missing part was:
>
>  BR2_PACKAGE_KERNEL_MODULE_IMX_GPU_VIV=y
>
> Qt5 eglfs and gstreamer imxeglvivsink are working now...

Good to hear!

>> Sorry for the confusion but know that if you want to make sure the
>> driver matches the user-space blobs, always select the Vivante kernel
>> module as I'll make to always update both at the same time.
>>
>
> Maybe a little hint in board/boundarydevices/nitrogen6x/readme.txt would be useful?

Well it is not Nitrogen6x-specific, it applies to all i.MX6 platforms
so I'm not sure where would be the best place to give this info apart
from the help text. Thomas, any idea on this?

Yocto is forcing the use of the Vivante kernel module, maybe we should
do the same but I'm not fond of this approach.

> Many thanks for your support...

No problem. Thanks for your valuable feedback!

Regards,
Gary