EtnaViv and i.MX6Q

EtnaViv and i.MX6Q

[Keskinarkaus, Teemu]

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

Hi,

We have custom i.MX6Q based HW and I've been trying to get graphics working with Etnaviv driver so I could get Weston 2.0 up and running.

I'm using Yocto 2.3 and have MACHINEOVERRIDES in local.conf so kernel linux-fslc-4.9 is built with Etnaviv driver in it.

I've used NXP Beta-branch to test their linux 4.9.11 - kernel so I've been able to update/test device tree with 4.9-series kernel and there the kernel outputs picture just fine. (Of course Weston 2.0 doesn't work with it, but that was expected. Linux outputs the logos at startup so that way I knew display was configured ok).

If I then build Etnaviv - version the system starts okay and it seems Etnaviv driver is also loaded without any errors. Problem is that no picture is displayed on screen. It stays completely white ie. screen has no output at all.

I tried to look up, but I wasn't sure/couldn't find that is there something else needed or should Yocto 2.3 Etnaviv - driver be working and I just have some wrong configuration (where?) or does Etnaviv driver need some patches still that are not part of the Yocto 2.3?

With Etnaviv - driver also /dev/fb0 is missing.

I did find meta-etnaviv - layer, but it hasn't been updated in a year and didn't seem to have anything Wayland related so I'm not sure if it's needed or not.

-Teemu Keskinarkaus

________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

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

Re: EtnaViv and i.MX6Q

[Otavio Salvador]

Hello Teemu,

On Tue, Nov 21, 2017 at 4:16 AM, Keskinarkaus, Teemu
<teemu.keskinarkaus@crosscontrol.com> wrote:
> We have custom i.MX6Q based HW and I’ve been trying to get graphics working
> with Etnaviv driver so I could get Weston 2.0 up and running.

It won't. Etnaviv requires Weston 3.0.

> I’m using Yocto 2.3 and have MACHINEOVERRIDES in local.conf so kernel
> linux-fslc-4.9 is built with Etnaviv driver in it.

Please focus on 2.4 as it has newer versions of mesa and libdrm.

> I’ve used NXP Beta-branch to test their linux 4.9.11 – kernel so I’ve been
> able to update/test device tree with 4.9-series kernel and there the kernel
> outputs picture just fine. (Of course Weston 2.0 doesn’t work with it, but
> that was expected. Linux outputs the logos at startup so that way I knew
> display was configured ok).
>
> If I then build Etnaviv – version the system starts okay and it seems
> Etnaviv driver is also loaded without any errors. Problem is that no picture
> is displayed on screen. It stays completely white ie. screen has no output
> at all.

You must have the display set in the device tree.

-- 
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: [EXT] Re: EtnaViv and i.MX6Q

[Keskinarkaus, Teemu]

-----Original Message-----
From: Otavio Salvador [mailto:otavio.salvador@ossystems.com.br]
Sent: 21. marraskuuta 2017 13:07
To: Keskinarkaus, Teemu
Cc: meta-freescale@yoctoproject.org
Subject: [EXT] Re: [meta-freescale] EtnaViv and i.MX6Q

Hello Teemu,

On Tue, Nov 21, 2017 at 4:16 AM, Keskinarkaus, Teemu <teemu.keskinarkaus@crosscontrol.com> wrote:
> We have custom i.MX6Q based HW and I’ve been trying to get graphics
> working with Etnaviv driver so I could get Weston 2.0 up and running.

It won't. Etnaviv requires Weston 3.0.

[Teemu]  This wasn't documented anywhere and Yocto 2.3 builds Weston 2.0 and Etnaviv. That's how I got impression that that combo should be working.

> I’m using Yocto 2.3 and have MACHINEOVERRIDES in local.conf so kernel
> linux-fslc-4.9 is built with Etnaviv driver in it.

Please focus on 2.4 as it has newer versions of mesa and libdrm.
[Teemu] I will have to take a look of that.

> I’ve used NXP Beta-branch to test their linux 4.9.11 – kernel so I’ve
> been able to update/test device tree with 4.9-series kernel and there
> the kernel outputs picture just fine. (Of course Weston 2.0 doesn’t

You must have the display set in the device tree.

[Teemu]  As said there, the device tree was tested with NXP kernel version 4.9.11 and display worked fine. When loaded the Etnaviv image with 4.9 - kernel I had no display output. I'm not sure if kernel built-in logos should be shown with Etnaviv driver or does it need something from the user space as well? Also the /dev/fb0 wasn't there although I would assume the device tree is configured ok or do Etnaviv need some changes there? I assume that it shouldn't need.

-Teemu Keskinarkaus


________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

Re: [EXT] Re: EtnaViv and i.MX6Q

[Otavio Salvador]

On Tue, Nov 21, 2017 at 10:16 AM, Keskinarkaus, Teemu
<teemu.keskinarkaus@crosscontrol.com> wrote:
>> I’ve used NXP Beta-branch to test their linux 4.9.11 – kernel so I’ve
>> been able to update/test device tree with 4.9-series kernel and there
>> the kernel outputs picture just fine. (Of course Weston 2.0 doesn’t
>
> You must have the display set in the device tree.
>
> [Teemu]  As said there, the device tree was tested with NXP kernel version 4.9.11 and display worked fine. When loaded the Etnaviv image with 4.9 - kernel I had no display output. I'm not sure if kernel built-in logos should be shown with Etnaviv driver or does it need something from the user space as well? Also the /dev/fb0 wasn't there although I would assume the device tree is configured ok or do Etnaviv need some changes there? I assume that it shouldn't need.

I am using it with a custom board but now at 4.14. I suggest you using
4.14 as it has a number of fixes for etnaviv.

-- 
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: [EXT] Re: EtnaViv and i.MX6Q

[Keskinarkaus, Teemu]

-----Original Message-----
From: Otavio Salvador [mailto:otavio.salvador@ossystems.com.br]

> [Teemu]  As said there, the device tree was tested with NXP kernel version 4.9.11 and display worked fine. When loaded the Etnaviv image with 4.9 - kernel I had no display output. I'm not sure if kernel built-in logos should be shown with Etnaviv driver or does it need something from the user space as well? Also the /dev/fb0 wasn't there although I would assume the device tree is configured ok or do Etnaviv need some changes there? I assume that it shouldn't need.

I am using it with a custom board but now at 4.14. I suggest you using
4.14 as it has a number of fixes for etnaviv.

[Teemu] I'll take a look at the 4.14. There has been some discussion if the Yocto 2.4 is 'stable' enough, but I guess it's stable enough for testing. :)

-Teemu Keskinarkaus


________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.