[meta-fsl-arm-extra] errors while building boundary kernel 3.14.28

[meta-fsl-arm-extra] errors while building boundary kernel 3.14.28

[Carlos Rafael Giani]

Hello,

I tried to build an image for a nitrogen6x, using the newest master 
version of Poky, meta-openembedded, and meta-fsl-arm & 
meta-fsl-arm-extra. However, the kernel doesn't compile. I get lots of 
errors like:

| arch/arm/mm/cache-l2x0.o: In function `nop_flush_kern_cache_louis':
| cache-l2x0.c:(.text+0xa38): multiple definition of 
`nop_flush_kern_cache_louis'
| arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1438): first defined here
| arch/arm/mm/cache-l2x0.o: In function `nop_flush_user_cache_all':
| cache-l2x0.c:(.text+0xa48): multiple definition of 
`nop_flush_user_cache_all'
| arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1448): first defined here
| arch/arm/mm/cache-l2x0.o: In function `nop_flush_user_cache_range':
| cache-l2x0.c:(.text+0xa58): multiple definition of 
`nop_flush_user_cache_range'
| arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1458): first defined here

At least one other person apparently had the same problem, since I found 
this log paste: http://pastebin.com/rwu5a6ru

Any ideas what's the cause?

Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28

[Otavio Salvador]

On Mon, Oct 19, 2015 at 5:26 PM, Carlos Rafael Giani
<dv@pseudoterminal.org> wrote:
> I tried to build an image for a nitrogen6x, using the newest master version
> of Poky, meta-openembedded, and meta-fsl-arm & meta-fsl-arm-extra. However,
> the kernel doesn't compile. I get lots of errors like:
>
> | arch/arm/mm/cache-l2x0.o: In function `nop_flush_kern_cache_louis':
> | cache-l2x0.c:(.text+0xa38): multiple definition of
> `nop_flush_kern_cache_louis'
> | arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1438): first defined here
> | arch/arm/mm/cache-l2x0.o: In function `nop_flush_user_cache_all':
> | cache-l2x0.c:(.text+0xa48): multiple definition of
> `nop_flush_user_cache_all'
> | arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1448): first defined here
> | arch/arm/mm/cache-l2x0.o: In function `nop_flush_user_cache_range':
> | cache-l2x0.c:(.text+0xa58): multiple definition of
> `nop_flush_user_cache_range'
> | arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1458): first defined here
>
> At least one other person apparently had the same problem, since I found
> this log paste: http://pastebin.com/rwu5a6ru
>
> Any ideas what's the cause?

Yes; it needs:

https://github.com/Freescale/linux-fslc/commit/22f692548037e39809c32759b5600ee066ef59e9.patch

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28

[Carlos Rafael Giani]

Hm, this doesn't fix it :(

Am 2015-10-19 um 21:46 schrieb Otavio Salvador:
> On Mon, Oct 19, 2015 at 5:26 PM, Carlos Rafael Giani
> <dv@pseudoterminal.org> wrote:
>> I tried to build an image for a nitrogen6x, using the newest master version
>> of Poky, meta-openembedded, and meta-fsl-arm & meta-fsl-arm-extra. However,
>> the kernel doesn't compile. I get lots of errors like:
>>
>> | arch/arm/mm/cache-l2x0.o: In function `nop_flush_kern_cache_louis':
>> | cache-l2x0.c:(.text+0xa38): multiple definition of
>> `nop_flush_kern_cache_louis'
>> | arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1438): first defined here
>> | arch/arm/mm/cache-l2x0.o: In function `nop_flush_user_cache_all':
>> | cache-l2x0.c:(.text+0xa48): multiple definition of
>> `nop_flush_user_cache_all'
>> | arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1448): first defined here
>> | arch/arm/mm/cache-l2x0.o: In function `nop_flush_user_cache_range':
>> | cache-l2x0.c:(.text+0xa58): multiple definition of
>> `nop_flush_user_cache_range'
>> | arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1458): first defined here
>>
>> At least one other person apparently had the same problem, since I found
>> this log paste: http://pastebin.com/rwu5a6ru
>>
>> Any ideas what's the cause?
> Yes; it needs:
>
> https://github.com/Freescale/linux-fslc/commit/22f692548037e39809c32759b5600ee066ef59e9.patch
>

Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28

[Gary Thomas]

On 2015-10-19 14:07, Carlos Rafael Giani wrote:
> Hm, this doesn't fix it :(

What rev of meta-fsl-arm-extra are you using?
Ian posted some updates to this recipe recently - perhaps you could try them?

>
> Am 2015-10-19 um 21:46 schrieb Otavio Salvador:
>> On Mon, Oct 19, 2015 at 5:26 PM, Carlos Rafael Giani
>> <dv@pseudoterminal.org> wrote:
>>> I tried to build an image for a nitrogen6x, using the newest master version
>>> of Poky, meta-openembedded, and meta-fsl-arm & meta-fsl-arm-extra. However,
>>> the kernel doesn't compile. I get lots of errors like:
>>>
>>> | arch/arm/mm/cache-l2x0.o: In function `nop_flush_kern_cache_louis':
>>> | cache-l2x0.c:(.text+0xa38): multiple definition of
>>> `nop_flush_kern_cache_louis'
>>> | arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1438): first defined here
>>> | arch/arm/mm/cache-l2x0.o: In function `nop_flush_user_cache_all':
>>> | cache-l2x0.c:(.text+0xa48): multiple definition of
>>> `nop_flush_user_cache_all'
>>> | arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1448): first defined here
>>> | arch/arm/mm/cache-l2x0.o: In function `nop_flush_user_cache_range':
>>> | cache-l2x0.c:(.text+0xa58): multiple definition of
>>> `nop_flush_user_cache_range'
>>> | arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1458): first defined here
>>>
>>> At least one other person apparently had the same problem, since I found
>>> this log paste: http://pastebin.com/rwu5a6ru
>>>
>>> Any ideas what's the cause?
>> Yes; it needs:
>>
>> https://github.com/Freescale/linux-fslc/commit/22f692548037e39809c32759b5600ee066ef59e9.patch
>>
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28

[Carlos Rafael Giani]

I am at revision 3757ea15f5bae89e09cd76137bb2fbb6821099b5 , which is the 
most recent one in master.

Am 2015-10-19 um 22:12 schrieb Gary Thomas:
> On 2015-10-19 14:07, Carlos Rafael Giani wrote:
>> Hm, this doesn't fix it :(
>
> What rev of meta-fsl-arm-extra are you using?
> Ian posted some updates to this recipe recently - perhaps you could 
> try them?
>
>>
>> Am 2015-10-19 um 21:46 schrieb Otavio Salvador:
>>> On Mon, Oct 19, 2015 at 5:26 PM, Carlos Rafael Giani
>>> <dv@pseudoterminal.org> wrote:
>>>> I tried to build an image for a nitrogen6x, using the newest master 
>>>> version
>>>> of Poky, meta-openembedded, and meta-fsl-arm & meta-fsl-arm-extra. 
>>>> However,
>>>> the kernel doesn't compile. I get lots of errors like:
>>>>
>>>> | arch/arm/mm/cache-l2x0.o: In function `nop_flush_kern_cache_louis':
>>>> | cache-l2x0.c:(.text+0xa38): multiple definition of
>>>> `nop_flush_kern_cache_louis'
>>>> | arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1438): first 
>>>> defined here
>>>> | arch/arm/mm/cache-l2x0.o: In function `nop_flush_user_cache_all':
>>>> | cache-l2x0.c:(.text+0xa48): multiple definition of
>>>> `nop_flush_user_cache_all'
>>>> | arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1448): first 
>>>> defined here
>>>> | arch/arm/mm/cache-l2x0.o: In function `nop_flush_user_cache_range':
>>>> | cache-l2x0.c:(.text+0xa58): multiple definition of
>>>> `nop_flush_user_cache_range'
>>>> | arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1458): first 
>>>> defined here
>>>>
>>>> At least one other person apparently had the same problem, since I 
>>>> found
>>>> this log paste: http://pastebin.com/rwu5a6ru
>>>>
>>>> Any ideas what's the cause?
>>> Yes; it needs:
>>>
>>> https://github.com/Freescale/linux-fslc/commit/22f692548037e39809c32759b5600ee066ef59e9.patch 
>>>
>>>
>>
>

Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28

[Otavio Salvador]

On Mon, Oct 19, 2015 at 6:07 PM, Carlos Rafael Giani
<dv@pseudoterminal.org> wrote:
> Hm, this doesn't fix it :(

There are two problems; the patch I sent the link is to fix the kernel
module build. However the Boundary's kernel are also lacking the
patches to fix the build for GCC 5.2.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28

[Carlos Rafael Giani]

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.

Am 2015-10-20 um 13:21 schrieb Otavio Salvador:
> On Mon, Oct 19, 2015 at 6:07 PM, Carlos Rafael Giani
> <dv@pseudoterminal.org> wrote:
>> Hm, this doesn't fix it :(
> There are two problems; the patch I sent the link is to fix the kernel
> module build. However the Boundary's kernel are also lacking the
> patches to fix the build for GCC 5.2.
>

Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28

[Carlos Rafael Giani]

Forgot to say: these commits are from linux-fslc.

Am 2015-10-21 um 09:29 schrieb Carlos Rafael Giani:
> 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.
>
> Am 2015-10-20 um 13:21 schrieb Otavio Salvador:
>> On Mon, Oct 19, 2015 at 6:07 PM, Carlos Rafael Giani
>> <dv@pseudoterminal.org> wrote:
>>> Hm, this doesn't fix it :(
>> There are two problems; the patch I sent the link is to fix the kernel
>> module build. However the Boundary's kernel are also lacking the
>> patches to fix the build for GCC 5.2.
>>
>

Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28

[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?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28

[Carlos Rafael Giani]

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

Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28

[Otavio Salvador]

On Wed, Oct 21, 2015 at 3:59 PM, 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

lsmod? Xorg log?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28

[Sundararaj Prabhu]

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]

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" <dv@pseudoterminal.org<mailto: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

[-- Attachment #2: Type: text/html, Size: 1888 bytes --]

Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28

[Carlos Rafael Giani]

[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]

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" 
> <dv@pseudoterminal.org <mailto: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


[-- Attachment #2: Type: text/html, Size: 3350 bytes --]

Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28

[Otavio Salvador]

On Wed, Oct 21, 2015 at 4:11 PM, Carlos Rafael Giani
<dv@pseudoterminal.org> wrote:
> 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.

This was the first patch I pointed you to apply.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28

[Carlos Rafael Giani]

Am 2015-10-21 um 20:21 schrieb Otavio Salvador:
> On Wed, Oct 21, 2015 at 4:11 PM, Carlos Rafael Giani
> <dv@pseudoterminal.org> wrote:
>> 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.
> This was the first patch I pointed you to apply.
>

The strange thing is that this *is* applied already. I am checking if 
perhaps for some reason MULTI_CACHE is defined.