Ah, found it. Something else is missing from the kernel.
galcore: Unknown symbol v7_dma_flush_range (err 0)
galcore: Unknown symbol v7_dma_map_area (err 0)
galcore: Unknown symbol v7_dma_flush_range (err 0)
I recall that these symbols have to be exposed explcitely, because they
aren't exposed by default.
Am 2015-10-21 um 20:02 schrieb Sundararaj Prabhu:
Does galcore shows in lsmod?
Also try modprobe galcore
Sent from Outlook <http://aka.ms/Ox5hz3> mobile
On Wed, Oct 21, 2015 at 10:59 AM -0700, "Carlos Rafael Giani"
<[email protected] <mailto:[email protected]>> wrote:
Am 2015-10-21 um 14:31 schrieb Otavio Salvador:
> On Wed, Oct 21, 2015 at 5:29 AM, Carlos Rafael Giani
> <[email protected]> wrote:
>> I applied the commits aeea3592a13bf12861943e44fc48f1f270941f8d
>> 76ae03828756bac2c1fa2c7eff7485e5f815dbdb
>> 3183696961eda6bef4e848d3ed0b4931de180b2c on the kernel, and it
builds now.
>>
>> However, GPU support is broken. It looks as if the boundary kernel is
>> incompatible with the newer Vivante firmware. Both G2D and OpenGL
ES are
>> broken.
> Are broken how? Does the module is being loaded?
>
Not sure. I see this in dmesg:
[drm] Initialized drm 1.1.0 20060810
[drm] Initialized vivante 1.0.0 20120216 on minor 0
opkg shows these package versions:
imx-gpu-viv - 1:5.0.11.p7.1-hfp-r0
kernel-module-imx-gpu-viv - 5.0.11.p7.1+fslc+git0+eeeb23c0fb-r0
--
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale
