From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 02EF31B4E1 for ; Fri, 12 Oct 2018 12:16:35 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 81DAA21FF1; Fri, 12 Oct 2018 06:16:34 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 12 Oct 2018 06:16:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=i6dDtkFN41Z+Ao1K4E3DDVnvzvU1vzfu2u7fYOTD59A=; b=bDN9mf/87ZQj VWNgh4JHQmXej1lsCltd9IEaV3vwWPHjCS8j1vJS5j67Nq1WRDBQGSVPdvG2JQVK +8+2+tloxrmLFzdaPVVrtNpYKlxMu9xvxMAfnkutgwMKGeSmKQNNCyNquX0Hm9/x btU5khWACkaZ7pHNyPDqc5RGWpyGKNg= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=i6dDtkFN41Z+Ao1K4E3DDVnvzvU1vzfu2u7fYOTD5 9A=; b=yL+LOEsA8IEH+Xa8gC95QWdDLuJzu6uh5wTTzWFnVK7JabOp69THI0Rnz Pgoivw464ff5h5MbBLmIRxVpBDnEdEAVFOhq7hPeev8mRvAejEeA5NkL4LdB2aW8 mkvWePz6+JKpEsKjfF6VnB24v1GWw5pXrRH2UJiHABVkOV3JRCvXu06oFdxfU9rx xW3UNzJ3j+viVkYQFnfY80N/5WWLInYssp+OLM01kne+LMrN/04BhQLXeefL8VYn Lt7zAU3jeAvjABd02OeHuYcYT0y3liP/FD/Is8kNm6xXMOPCBqlRSlWaiKv6yCED tBkO6XhxEWxePpqx3HoaI1lS0XwmA== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (90.87.136.77.rev.sfr.net [77.136.87.90]) by mail.messagingengine.com (Postfix) with ESMTPA id 1A601102E9; Fri, 12 Oct 2018 06:16:31 -0400 (EDT) From: Thomas Monjalon To: Shreyansh Jain Cc: dev@dpdk.org, ferruh.yigit@intel.com Date: Fri, 12 Oct 2018 12:16:28 +0200 Message-ID: <9015218.8t0llQzSWg@xps> In-Reply-To: <9025a1a3-b6a9-c9ea-1ca5-3b711cef8587@nxp.com> References: <20180917103631.32304-1-shreyansh.jain@nxp.com> <20180926180440.31726-1-shreyansh.jain@nxp.com> <9025a1a3-b6a9-c9ea-1ca5-3b711cef8587@nxp.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 00/15] Upgrade DPAA2 FW and other feature/bug fixes X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2018 10:16:37 -0000 12/10/2018 11:32, Shreyansh Jain: > On Wednesday 26 September 2018 11:34 PM, Shreyansh Jain wrote: > > About the series: > > > > This series of patches upgrades the DPAA2 driver firmware to > > v10.10.10 (MC Firmware). > > As the bus/fslmc is modified, it is a dependent object for other > > drivers like net/crypto/qdma. Also, the changes are mostly tightly > > linked - thus, the patches include upgrade as well as sequential > > changes to driver. > > Once done, it would imply that DPAA2 driver won't work with any MC > > FW lower than 10.10.10. > > > > Support for this new firmware is available in publically available > > LSDK (Layerscape SDK) release [1]. > > > > Besides the FW change, there are other subtle changes as well: > > - Support reading the MAC address from NIC device, rather than > > using a default MAC > > - Adding support for QBMan 5.0 FW APIs > > - Some patches for NXP's LX2 platform specific features > > - And some bug fixes. > > > > Dependency: > > > > * These patches are based on net-next/master 58c3b609699a8c > > * Series [1] is logically related to this, but has no git/patch > > related dependency. It is series for upgrade of DPAA. > > > > [1] https://lsdk.github.io/index.html > > [2] http://patches.dpdk.org/project/dpdk/list/?series=1090&state=* > > > > Version History: > > v1->v2: > > - Bumped up the version of the libraries (pmd/bus/crypto/event) as the > > first set of patches (MC firmware update) breaks the internal ABI > > - Added support for ordered processing APIs. These APIs are expected > > to be used in subseqent feature updates on DPAA2 ethernet driver. > > - Some internal bug fixes. > > (Patches increased from 11~15) > > > > Hi Thomas, > > Would you be taking this series for RC1? Yes > (Ideally being driver code, this should have been with Ferruh but > patchwork is showing your name). Ferruh is taking patches for drivers/net/ and related. This series is touching a lot more.