[meta-xilinx] Mali Kernel Module for ZCU102

Manjukumar Harthikote Matha MANJUKUM at xilinx.com
Mon Jul 16 01:20:12 PDT 2018


Hi Emily,

You can use something like this
https://github.com/Xilinx/meta-xilinx/blob/rel-v2018.2/meta-xilinx-bsp/conf/machine/include/machine-xilinx-default.inc#L32-L36

The above can be used from master/sumo branch.

This hasn't been added yet to master, note that not all variants of FPGA support MALI 400 GPU.
I will send a patch this week to update the defaults using the override mechanism.

Thanks,
Manju

> -----Original Message-----
> From: meta-xilinx-bounces at yoctoproject.org [mailto:meta-xilinx-
> bounces at yoctoproject.org] On Behalf Of Jean-Francois Dagenais
> Sent: Sunday, July 15, 2018 5:06 PM
> To: Emily Smith <easmith5 at uchicago.edu>
> Cc: Luca Ceresoli <luca at lucaceresoli.net>; meta-xilinx at lists.yoctoproject.org
> Subject: Re: [meta-xilinx] Mali Kernel Module for ZCU102
> 
> Hi Emily,
> 
> The lines you are quoting are from includes (.inc) so you should be getting them
> on the zcu102 machine conf. What version of meta-xilinx are you using?
> 
> In recent versions, the mali stuff is triggered by the SOC_VARIANT variable being
> at least "eg". This triggers a series of smart yocto "overrides" and all the mali stuff
> follows. As usual, "grep" is your friend in figuring most of this stuff out. There is no
> nice walkthrough, one has to hack a little bit to get things going the way you want
> to. ;) It gets much easier as you "suffer" along the way. (I'm talking about yocto in
> general here ;)
> 
> Cheers!
> 
> 
> 
> 	On Jul 13, 2018, at 6:29 PM, Emily Smith <easmith5 at uchicago.edu
> <mailto:easmith5 at uchicago.edu> > wrote:
> 
> 	Hi Luca / All -
> 
> 	Like I mentioned previously, my machine conf didn't have the lines you
> indicated
> 
> 	    PREFERRED_PROVIDER_virtual/libgles2 = "libmali-xlnx"
> 	    PREFERRED_PROVIDER_virtual/egl      = "libmali-xlnx"
> 
> 
> 
> 	Is there a reason why they aren't in the default machine conf for ZCU102
> since it does have the Mali 400 GPU?
> 
> 
> 	When I do add them, I end up with this error:
> 
> 
> 
> 	ERROR: Nothing PROVIDES 'virtual/libgl' (but
> /local/d6/easmith5/BuildOS/openembedded-core/meta/recipes-
> graphics/mesa/libglu_9.0.0.bb, /local/d6/easmith5/BuildOS/openembedded-
> core/meta/recipes-graphics/glew/glew_2.0.0.bb DEPENDS on or otherwise
> requires it)
> 	mesa-gl PROVIDES virtual/libgl but was skipped:
> PREFERRED_PROVIDER_virtual/libgl set to mesa, not mesa-gl
> 	mesa PROVIDES virtual/libgl but was skipped:
> PREFERRED_PROVIDER_virtual/libgles2 set to libmali-xlnx, not mesa
> 	mesa PROVIDES virtual/libgl but was skipped:
> PREFERRED_PROVIDER_virtual/libgles2 set to libmali-xlnx, not mesa
> 	mesa-gl PROVIDES virtual/libgl but was skipped:
> PREFERRED_PROVIDER_virtual/libgl set to mesa, not mesa-gl
> 
> 
> 
> 
> 
> 
> 	I haven't had any luck trying to set the preferred provider for virtual/libgl
> to get rid of this error.
> 
> 
> 	In the recipe I'm currently working on I did also set RDEPENDS for libmali-
> xlnx, but I'm not sure that worked properly. It seems to have built fine, but I still
> don't seem to have the mali kernel module afterwards.
> 	Do you have any further suggestions?
> 
> 
> 	Thanks very much for your time!
> 	Emily
> ________________________________
> 
> 
> 	From: Luca Ceresoli <luca at lucaceresoli.net
> <mailto:luca at lucaceresoli.net> >
> 	Sent: Friday, July 13, 2018 3:22:52 AM
> 	To: Emily Smith; meta-xilinx at lists.yoctoproject.org <mailto:meta-
> xilinx at lists.yoctoproject.org>
> 	Subject: Re: [meta-xilinx] Mali Kernel Module for ZCU102
> 
> 
> 	Hi Emily,
> 
> 	On 12/07/2018 17:12, Emily Smith wrote:
> 	> Hi Everyone -
> 	>
> 	>
> 	> I'm using poky and bitbake to build an OS for the Xilinx ZCU102 board,
> 	> and I'm having trouble with the Mali Kernel Module here:
> 	>
> 	> https://github.com/Xilinx/meta-xilinx/tree/master/meta-xilinx-
> bsp/recipes-graphics/mali
> 	>
> 	>
> 	> I thought it should be built with the  /meta-xilinx/meta-xilinx-bsp
> 	> layer added in bitbake, but  I'm not seeing a .ko file anywhere that's
> 	> produced, or on the board once I boot it.  Nothing was showing up
> 	> with lsmod either. Do I need to enable anything, or set any variables
> 	> for this to be built in the first place?
> 	>
> 	>
> 	> Any information you can give me would be very helpful.
> 
> 	kernel-module-mali is pulled in by libmali-xlnx:
> 
> 	  $ git grep -B1 kernel-module-mali
> 	  .../libmali-xlnx.bb-RDEPENDS_${PN} = " \
> 	  .../libmali-xlnx.bb:       kernel-module-mali \
> 
> 	Is libmali-xlnx built?
> 
> 	A few things to check, in top-bottom order:
> 	 1. your machine conf should have something like
> 	    PREFERRED_PROVIDER_virtual/libgles2 = "libmali-xlnx"
> 	    PREFERRED_PROVIDER_virtual/egl      = "libmali-xlnx"
> 	 2. libmali-xlnx should then be built
> 	 3. libmali-xlnx RDEPENDS on kernel-module-mali, so it should
> 	    be built as well
> 
> 	Bye,
> 	--
> 	Luca
> 
> 	--
> 	_______________________________________________
> 	meta-xilinx mailing list
> 	meta-xilinx at yoctoproject.org <mailto:meta-xilinx at yoctoproject.org>
> 	https://lists.yoctoproject.org/listinfo/meta-xilinx
> 



More information about the meta-xilinx mailing list