[U-Boot] [PATCH] soc: zynqmp: Update required API version to 1.0

[Manjukumar Harthikote Matha]

> -----Original Message-----
> From: Marek Vasut [mailto:marex at denx.de]
> Sent: Monday, May 21, 2018 9:47 AM
> To: Manjukumar Harthikote Matha <MANJUKUM at xilinx.com>; Rajan Vaja
> <RAJANV at xilinx.com>
> Cc: monstr at monstr.eu; Albert Aribaud <albert.u.boot at aribaud.net>; Jolly Shah
> <JOLLYS at xilinx.com>; Michal Simek <michal.simek at xilinx.com>; u-
> boot at lists.denx.de
> Subject: Re: [PATCH] soc: zynqmp: Update required API version to 1.0
> 
> On 05/21/2018 06:27 PM, Manjukumar Harthikote Matha wrote:
> 
> [...]
> 
> >> Ah, I see, so there are three versions of pmu-firmware in a single
> >> release, but the one which is actually needed for the system to boot
> >> correctly is not in the meta-xilinx repo as one would expect, but in
> >> some other repo. That ... doesn't make any sense, but so be it.
> >>
> >
> > If you are planning to use rel-v2018.x Xilinx tools release branches,
> > stick with all the layers provided by Xilinx. The same is documented
> > in wiki as well
> >
> >
> http://www.wiki.xilinx.com/How%20to%20build%20images%20through%20yoct
> o
> >
> > If you want to use Yocto open-source release stick with branches likes rocko,
> morty etc. These branches will not have dependencies on Xilinx tools.
> 
> I think you missed my point, there are three different PMUFW recipes in those
> metalayers. The only one that matters is not in the BSP layer, which makes no
> sense to me, but so be it.

AFAIK, there are two. One in meta-xilinx-bsp and other in meta-xilinx-tools. You can use PREFERRED_PROVIDER to switch between the two in your distro.

I still don’t think you get the difference between Xilinx tools releases from Github and upstream Yocto project repository.
See http://git.yoctoproject.org/cgit.cgi/meta-xilinx/

Also note that none of the Xilinx tool release branches are present at http://git.yoctoproject.org/cgit.cgi/meta-xilinx/

The thing that matters to you is pmu-firmware recipe in meta-xilinx-bsp. The recipe is present and based on 2017.3 in master and Rocko. Stick with Rocko branch till the next release,Sumo branch is cut, which will get 2018.1 version.

> 
> btw I presume you do mean OpenEmbedded.
> 


http://git.yoctoproject.org/cgit.cgi/meta-xilinx/


> >> So it's this pmu-firmware_git recipe which provides different ABI in
> >> different versions of meta-xilinx-bsp, yet this is not in any way
> >> indicated by the package version, right ?
> >
> > Didn’t get what you mean here? Package version is set according to the
> > release under use
> > https://github.com/Xilinx/meta-xilinx-tools/blob/master/classes/xsctap
> > p.bbclass#L9
> 
> Ah, I see, so unlike any other regular recipe which encodes the version in the
> recipe file name, Xilinx stuff has custom class which is inherited into version-less
> recipe and sets the version. This is horrid.
> 

Not true, any recipe which includes version can be in an include file or in a class or in a conf file. 
There is no strict guidelines on where this version should be set (recipe, include, conf or class).
Just because you are familiar with one way of doing things, does not mean everything else is horrid.
 
> > This should indicate, release version with a part of commit id of git being used.
> 
> Right ...
> 
> >> Also, do I understand it correctly that Xilinx doesn't support arm64
> >> with multilib?
> >>
> >
> > Yes Xilinx does not support multilib way of building PMUFW
> 
> What are you talking about ? PMUFW is microblaze, which doesn't do multilib in
> the first place.
> 

Exactly, when you are building for zynqmp (zcu102 board), it is aarch64. Yocto build system needs to understand mixed architectures when building in the same project, hence the use of multilib to be build PMUFW. 

> >. The official support is in meta-xilinx-tools layer with a dependency
> >on xsct tool
> 
> Which btw is violating OE assumption that no host tools are pulled into the build,
> so this whole thing is broken.
> 

It is part of Xilinx tool release, if you don’t need it, don’t use it. 

Thanks,
Manju