DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Smith, Eleanor" <eleanor.smith@intel.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com,
	pablo.de.lara.guarch@intel.com, akhil.goyal@nxp.com,
	nicolas.scheidecker@intel.com
Subject: Re: [dpdk-dev] [PATCH v1 1/4] baseband/fpga_lte_fec: addition of driver for 4G turbo FEC with PAC N300 FPGA card
Date: Sat, 09 Mar 2019 02:24:58 +0100	[thread overview]
Message-ID: <5172789.3VQKzHaggZ@xps> (raw)
In-Reply-To: <1551461010-881-2-git-send-email-eleanor.smith@intel.com>

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 <eleanor.smith@intel.com>

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.

  reply	other threads:[~2019-03-09  1:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-01 17:23 [dpdk-dev] [PATCH v1 0/4] baseband/fpga_lte_fec: BBDEV FPGA driver for 4G turbo FEC Smith, Eleanor
2019-03-01 17:23 ` [dpdk-dev] [PATCH v1 1/4] baseband/fpga_lte_fec: addition of driver for 4G turbo FEC with PAC N300 FPGA card Smith, Eleanor
2019-03-09  1:24   ` Thomas Monjalon [this message]
2019-03-26 11:25     ` Akhil Goyal
2019-03-26 11:25       ` Akhil Goyal
2019-03-01 17:23 ` [dpdk-dev] [PATCH v1 2/4] usertools: update to usertool to allow binding of baseband device Smith, Eleanor
2019-03-01 17:23 ` [dpdk-dev] [PATCH v1 3/4] test-bbdev: update bbdev test-app for FPGA driver testing Smith, Eleanor
2019-03-01 17:23 ` [dpdk-dev] [PATCH v1 4/4] librte_bbdev: update device info structure to use rte_device Smith, Eleanor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5172789.3VQKzHaggZ@xps \
    --to=thomas@monjalon.net \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=eleanor.smith@intel.com \
    --cc=ferruh.yigit@intel.com \
    --cc=nicolas.scheidecker@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).