From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 44DA3F94 for ; Sat, 9 Mar 2019 02:25:02 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id DDE1B221D6; Fri, 8 Mar 2019 20:25:01 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 08 Mar 2019 20:25:01 -0500 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=1BO/1Du2ndW97WuyI87c/3uaRMSF2PTXSjmQOoTX2qU=; b=DLjBhslOTnxl BJswTSTHFuEb80ux3+lHI3VT+pphRlnEbIg2d30U/4OdN2uJIR5dBie6C9+0ZqSS OJNrAOJOIHnKiRe75HvxiLDudCXbicyE4VhxB+OPhLJUySJXQRyms0iMWFd0Zt6J gXol0LmiH3zRbaBfVwX2ukNXKbGkNVA= 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=fm2; bh=1BO/1Du2ndW97WuyI87c/3uaRMSF2PTXSjmQOoTX2 qU=; b=riANLLnc9WcZtCR5gTsiodgwTmLortp/4PiuWhetNNR66ou61Lcz5XFRF 9c66V9GS9Xa4jREBgE8ZQTkYgsfmVH1bnvTxLiRze2n7UJOfgzvW5LtP9bpnlz3Z 8rkC3YpNEztlvUGL8MVZ9f2jiOGPTNKoIx1Jk4UIma/SH+8q9I+OKlRRCJaV+45C vkU2i2WrnnjY0n/DDZsRCc6E84r6/+abQ4Z9pzIRgUY+fZ1cG5AoWJirr0CVxVzb nc+IZvLsGGFAhhQz2mga49AcsWDSMdGksYLdgyEqS5Yrc+1DZg3LpKQve+pKLrqT Nj74lbWIL7lE2Q7054+5LgEQ5e2wA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrgedugdeffecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 3CB58E4580; Fri, 8 Mar 2019 20:25:00 -0500 (EST) From: Thomas Monjalon To: "Smith, Eleanor" Cc: dev@dpdk.org, ferruh.yigit@intel.com, pablo.de.lara.guarch@intel.com, akhil.goyal@nxp.com, nicolas.scheidecker@intel.com Date: Sat, 09 Mar 2019 02:24:58 +0100 Message-ID: <5172789.3VQKzHaggZ@xps> In-Reply-To: <1551461010-881-2-git-send-email-eleanor.smith@intel.com> References: <1551461010-881-1-git-send-email-eleanor.smith@intel.com> <1551461010-881-2-git-send-email-eleanor.smith@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v1 1/4] baseband/fpga_lte_fec: addition of driver for 4G turbo FEC with PAC N300 FPGA card 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: Sat, 09 Mar 2019 01:25:02 -0000 Hi, 01/03/2019 18:23, Smith, Eleanor: > Addition of a FPGA driver for acceleration of 4G turbo encoding and > decoding. > > Signed-off-by: Smith, Eleanor I'm really not comfortable adding a new Intel bbdev driver, while the turbo sw driver cannot be freely compiled. I know some work is in progress in Intel to fix this compilation issue, and I am interested in checking it before proceeding with a new driver. > +Section 3 of the DPDK manual provides instuctions on installing and compiling DPDK. The > +default set of bbdev compile flags may be found in config/common_base, where for example > +the flag to build the FPGA LTE FEC device, ``CONFIG_RTE_LIBRTE_PMD_FPGA_LTE_FEC``, is already > +set. It is assumed DPDK has been compiled for an icc 64-bit target using: > + > +.. code-block:: console > + > + make install T=x86_64-native-linuxapp-icc Is it possible to build this driver with gcc? We cannot accept any maintenance operation if icc is required.