From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Vasut Date: Mon, 21 May 2018 18:47:23 +0200 Subject: [U-Boot] [PATCH] soc: zynqmp: Update required API version to 1.0 In-Reply-To: References: <2c30872dee20fd3cefe885317b3987d473d7d2e0.1526305142.git.michal.simek@xilinx.com> Message-ID: <8475fe06-bec5-d82e-9562-1c45d2777dba@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable To: u-boot@lists.denx.de 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. >> >=20 > If you are planning to use rel-v2018.x Xilinx tools release branches, sti= ck with all the layers provided by Xilinx. The same is documented in wiki a= s well >=20 > http://www.wiki.xilinx.com/How%20to%20build%20images%20through%20yocto >=20 > If you want to use Yocto open-source release stick with branches likes ro= cko, 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. btw I presume you do mean OpenEmbedded. >> 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 ? >=20 > Didn=E2=80=99t get what you mean here? Package version is set according t= o the release under use > https://github.com/Xilinx/meta-xilinx-tools/blob/master/classes/xsctapp.b= bclass#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. > This should indicate, release version with a part of commit id of git bei= ng used. Right ... >> Also, do I understand it correctly that Xilinx doesn't support arm64 >> with multilib? >> >=20 > 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. >. 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. --=20 Best regards, Marek Vasut