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

[Manjukumar Harthikote Matha <MANJUKUM@xilinx.com>]

Hi Marek,

> -----Original Message-----
> From: Marek Vasut [mailto:marex at denx.de]
> Sent: Monday, May 21, 2018 2:45 AM
> To: Rajan Vaja <RAJANV@xilinx.com>
> Cc: monstr at monstr.eu; Albert Aribaud <albert.u.boot@aribaud.net>;
> Manjukumar Harthikote Matha <MANJUKUM@xilinx.com>; Jolly Shah
> <JOLLYS@xilinx.com>; Michal Simek <michal.simek@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:53 AM, Rajan Vaja wrote:
> > Hi Marek,
> >
> >> -----Original Message-----
> >> From: Marek Vasut [mailto:marex at denx.de]
> >> Sent: 15 May 2018 02:26 AM
> >> To: Michal Simek <michal.simek@xilinx.com>; u-boot at lists.denx.de
> >> Cc: Rajan Vaja <RAJANV@xilinx.com>; monstr at monstr.eu; Albert Aribaud
> >> <albert.u.boot@aribaud.net>
> >> Subject: Re: [PATCH] soc: zynqmp: Update required API version to 1.0
> >>
> >> On 05/14/2018 03:39 PM, Michal Simek wrote:
> >>> From: Rajan Vaja <rajan.vaja@xilinx.com>
> >>>
> >>> Existing EEMI version is to as 1.0 (available from xilinx v2018.1
> >>> version). Update required API version to match with EEMI API version.
> >>
> >> Not sure I understand this sentence.
> >>
> >>> New PMUFW version is required for operations with programmable logic.
> >>
> >> Seems the meta-xilinx 2018.1 comes with PMUFW 2017.3
> >> https://github.com/Xilinx/meta-xilinx/tree/rel-v2018.1/meta-xilinx-
> >> bsp/recipes-bsp/pmu-firmware
> >>
> >> Is this out of date ?
> > [Rajan] PMU firmware is built using meta-xilinx-tools layer and not meta-xilinx-
> bsp.
> > The recipe in meta-xilinx-bsp is to build OSL flow (using multilib) this is not
> recommended nor supported from Xilinx.
> 
> 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%20yocto

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.
 
> 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/xsctapp.bbclass#L9

This should indicate, release version with a part of commit id of git being used.

> 
> Also, do I understand it correctly that Xilinx doesn't support arm64
> with multilib?
> 

Yes Xilinx does not support multilib way of building PMUFW. The official support is in meta-xilinx-tools layer with a dependency on xsct tool

Thanks,
Manju