All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gaëtan Carlier" <gcembed@gmail.com>
To: Sivasubramanian Patchaiperumal
	<sivasubramanian.patchaiperumal@linaro.org>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>
Subject: Re: i.MX6, Mesa, GLES2, Vivante GC320 + GC880
Date: Fri, 10 May 2019 07:52:58 +0200	[thread overview]
Message-ID: <eb672d53-7995-92a0-2983-db551dfffa30@gmail.com> (raw)
In-Reply-To: <CAHcVMqw6C-p15OE1L6Snn1F3VMapjyZsy6ubn3qqnamkORLw-g@mail.gmail.com>

Hi ,
Thank you but it didn't help.
I remove everything and start from scratch and everything is now building (except u-boot.imx which don't want to install).

1) Are libdrm, kernel-module-imlx-gpu-viv, ... patches/bbappends still needed as EtnaViv's Github[1] says that everything have been upstreamed to drm, mesa and kernel ?
It seems that a great job has been done to avoid the need of extra packages to have 2D/3D acceleration working in mainline trees, so I am now totally lost of what it is really needed or not.

2) I really want a minimum of extra freescale packages because I was so disappointed with i.MX27. So, is the package imx-gpu-viv still needed ?

I am going to test the image and try to enable Qt. I will wait to have a fully working image because trying to switch to kernel 5.0

Best regards,
Gaëtan.

[1] https://github.com/etnaviv/etna_viv

On 5/10/19 6:20 AM, Sivasubramanian Patchaiperumal wrote:
> Hi Gaëtan,
> Kindly check which component (mostly
> https://github.com/Freescale/meta-freescale/blob/master/recipes-graphics/imx-gpu-viv/imx-gpu-viv-6.inc
> should)
> is providing "virtual/egl" package for iMX6 like
> 
> PROVIDES = "virtual/egl"
> 
> and confirm whether it's building first by say
> 
> bitbake imx-gpu-viv (if imx-gpu-viv provides virtual/egl)
> 
> On Thu, 9 May 2019 at 17:09, Gaëtan Carlier <gcembed@gmail.com> wrote:
> 
>> Hi,
>>
>> I have a board with a i.MX6 DL which has a Vivante GC320 (2D) and GC880
>> (3D) GPUs.
>> I successfully build an image on Debian 8 using rocko branches of the
>> following meta: meta-poky, meta-yocto-bsp, meta-freescale, meta-etnaviv
>> The Kernel used is imx_4.9.88_2.0.0_ga with CONFIG_DRM_VIVANTE enabled
>>
>> The following packages were built :
>>     - eglinfo-x11 armv7ahf_neon_imx 1.0.0
>>     - libdrm-armada0 armv7ahf_neon 0.1+git0+6b461c163b
>>     - libdrm-etnaviv1 armv7ahf_neon 2.4.83
>>     - libegl-mesa armv7ahf_neon_imx 17.1.7
>>     - libgl-mesa armv7ahf_neon_imx 17.1.7
>>     - libglapi0 armv7ahf_neon_imx 17.1.7
>>     - libgles1-mesa armv7ahf_neon_imx 17.1.7
>>     - libgles2-mesa armv7ahf_neon_imx 17.1.7
>>     - mesa armv7ahf_neon_imx 17.1.7
>>     - mesa-demos armv7ahf_neon_imx 8.3.0
>>     - xf86-video-armada armv7ahf_neon 0.1+git0+a4306d9717_f64d77abbb
>>     - xserver-xorg armv7ahf_neon_imx 1.19.3
>>
>> Now that I am using Debian 10, I had to switch to Warrior branch but when
>> I try to build the image, I have several errors due to mesa-demos or any
>> other OpenGL demos packages because nothing provides virtual/libegl. I try
>> several configuration enabling X11, disabling X11 and only use gles2, ...
>> but each time there is an different error "Nothing provides virtal/xxx".
>> Sometimes it talks me about imx-gpu-viv package.
>> On Warrior branch, Mesa is now 19.x and meta-etnaviv is just used to have
>> the xorg.conf file as everything else is now upstreamed in mesa, libdrm and
>> kernel
>>
>>
>> conf/local.conf is the clean/original generated when I called "source
>> oe-init-build-env".
>> conf/bblayers.conf only has the following meta enabled : meta, meta-poky,
>> meta-yocto-bsp and meta-freescale.
>>
>> The command I used is :
>> MACHINE=imx6qdl bitbake core-image-x11
>>
>> Here is the resulting error:
>> ERROR: Nothing PROVIDES 'virtual/egl' (but
>> /home/gc/Documents/projects/dev_git/imx28/poky/meta/recipes-gnome/gtk+/gtk+
>> 3_3.24.5.bb,
>> /home/gc/Documents/projects/dev_git/imx28/poky/meta/recipes-graphics/libepoxy/
>> libepoxy_1.5.3.bb DEPENDS on or otherwise requires it). Close matches:
>>   virtual/kernel
>>   virtual/perf
>>   virtual/mesa
>> NOTE: Runtime target 'matchbox-terminal' is unbuildable, removing...
>> Missing or unbuildable dependency chain was: ['matchbox-terminal',
>> 'gtk+3', 'virtual/egl']
>> NOTE: Runtime target 'packagegroup-core-x11-base' is unbuildable,
>> removing...
>> Missing or unbuildable dependency chain was:
>> ['packagegroup-core-x11-base', 'matchbox-terminal', 'gtk+3', 'virtual/egl']
>> ERROR: Required build target 'core-image-x11' has no buildable providers.
>> Missing or unbuildable dependency chain was: ['core-image-x11',
>> 'packagegroup-core-x11-base', 'matchbox-terminal', 'gtk+3', 'virtual/egl']
>>
>>
>> The goal is also to use the kernel 5.x
>>
>> Thank you for your help.
>>
>> Best regards,
>> Gaëtan.
>> --
>> _______________________________________________
>> meta-freescale mailing list
>> meta-freescale@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-freescale
>>
> 
> 



  reply	other threads:[~2019-05-10  5:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 11:39 i.MX6, Mesa, GLES2, Vivante GC320 + GC880 Gaëtan Carlier
2019-05-10  4:20 ` Sivasubramanian Patchaiperumal
2019-05-10  5:52   ` Gaëtan Carlier [this message]
2019-05-10  8:21     ` Gaëtan Carlier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=eb672d53-7995-92a0-2983-db551dfffa30@gmail.com \
    --to=gcembed@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=sivasubramanian.patchaiperumal@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.