From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Vasut Date: Thu, 17 May 2018 16:02:58 +0200 Subject: [U-Boot] [PATCH] soc: zynqmp: Update required API version to 1.0 In-Reply-To: <85f364b5-eb14-a6c0-ead4-d944918053f5@xilinx.com> References: <2c30872dee20fd3cefe885317b3987d473d7d2e0.1526305142.git.michal.simek@xilinx.com> <85f364b5-eb14-a6c0-ead4-d944918053f5@xilinx.com> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 05/17/2018 03:59 PM, Michal Simek wrote: > On 14.5.2018 22:55, Marek Vasut wrote: >> On 05/14/2018 03:39 PM, Michal Simek wrote: >>> From: Rajan Vaja >>> >>> 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. > > PMUFW contains EEMI api which has also changed and the biggest reason > for bumping up PMUFW version were changes in EEMI api. And these > versions are also aligned. So uh, the meta-xilinx 2018.1 release which contains pmufw 2017.3 uses the new API 1.0 , while meta-xilinx 2018.1 release which contains pmufw 2017.3 as well does not use the API 1.0 ? I think the versioning is a complete CF then ... -- Best regards, Marek Vasut