From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 4A98DE00708; Wed, 21 Oct 2015 11:11:38 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE, SPF_HELO_PASS autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.0 SPF_HELO_PASS SPF: HELO matches SPF record * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message Received: from ptmx.org (ptmx.org [178.63.28.110]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 9D259E006D5 for ; Wed, 21 Oct 2015 11:11:36 -0700 (PDT) Received: from [192.168.178.14] (chello062178118086.5.14.vie.surfer.at [62.178.118.86]) by ptmx.org (Postfix) with ESMTPSA id C172923241; Wed, 21 Oct 2015 20:11:34 +0200 (CEST) To: Sundararaj Prabhu , Otavio Salvador References: <562543CC.5040705@pseudoterminal.org> <56254D6E.4070409@pseudoterminal.org> <56273EE6.90307@pseudoterminal.org> <5627D27A.5060704@pseudoterminal.org> From: Carlos Rafael Giani Message-ID: <5627D556.4010505@pseudoterminal.org> Date: Wed, 21 Oct 2015 20:11:34 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Cc: "meta-freescale@yoctoproject.org" Subject: Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28 X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Oct 2015 18:11:38 -0000 Content-Type: multipart/alternative; boundary="------------030806040106000705050200" --------------030806040106000705050200 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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 mobile > > > > > On Wed, Oct 21, 2015 at 10:59 AM -0700, "Carlos Rafael Giani" > > wrote: > > > > Am 2015-10-21 um 14:31 schrieb Otavio Salvador: > > On Wed, Oct 21, 2015 at 5:29 AM, Carlos Rafael Giani > > 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 --------------030806040106000705050200 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit 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 mobile




On Wed, Oct 21, 2015 at 10:59 AM -0700, "Carlos Rafael Giani" <dv@pseudoterminal.org> wrote:



Am 2015-10-21 um 14:31 schrieb Otavio Salvador:
> On Wed, Oct 21, 2015 at 5:29 AM, Carlos Rafael Giani
> <dv@pseudoterminal.org> 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

--------------030806040106000705050200--