From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id DA9ABA0521; Tue, 3 Nov 2020 16:06:43 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 49BD3CB93; Tue, 3 Nov 2020 16:06:42 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by dpdk.org (Postfix) with ESMTP id 9532FCB7A for ; Tue, 3 Nov 2020 16:06:39 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1604415998; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=x++3IzLnKjNFlyDX1s/6Cl8wnXtGjxf4Nvx08kQ7DjI=; b=SMaPUy3M+tkEUv1QJGR7GSx9Pwl43f4H9ZOxGJtxytlE7mY23ydnQ6Jn1IgUi9npQNhaeu 7q6+AN6Gs5x3UuCLPYgPmT/87Y2AOmo3+APsnbguGxsuSKWP3/IUFWgf0uFr+KaLTjPLbn yHrJkaGvI/Ti8mU1cP8V+fjNHpFXdqE= Received: from mail-ot1-f69.google.com (mail-ot1-f69.google.com [209.85.210.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-590-k4oaTm6eNCO0ek-I0C2C5A-1; Tue, 03 Nov 2020 10:06:36 -0500 X-MC-Unique: k4oaTm6eNCO0ek-I0C2C5A-1 Received: by mail-ot1-f69.google.com with SMTP id e6so7959825otk.13 for ; Tue, 03 Nov 2020 07:06:36 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=x++3IzLnKjNFlyDX1s/6Cl8wnXtGjxf4Nvx08kQ7DjI=; b=gqXhH7DQbREuT4Tz+DxnK1kFkBA9RqN2TqWKcGmQvRnuWJaSOy+qdRLKEZrYvNx0al 5EblTdCqAGoz+UQTqk1ZKKYRHVL10mhLbeWYwRgCLbt/fb091/a2S3JAG+gZMhujEv+F snei68RU76XJDNNcJqePinemuxvcNdKSRuRkidwtsyV4rw34FijCCzre8ioPjys8n7Ps ohU3pcJTVq5aj2x3nraNCI0cerr/CrF8KPfc6v1fiFzVWj+1brajNV7GKyTB63VeGV9u A9imsTlFrSJB57ySS76wBLfKcX9S8UtJcj/iv0p0pZdOPfuv5dMSAMrOBBUsB8FWw9xU kS6g== X-Gm-Message-State: AOAM5322eW34Cgkiy7sODWaB2/VLJxMgCkR2VRBjvfHRxsXmjA2dESHx EB/tHYlkuw3/MtbvDTUBzCOGN7PbRHy2I62r7/Cmwtl9s9yXw38vLV8Yc+kSfNbrGknurcX84sQ 2Tkw= X-Received: by 2002:a9d:4716:: with SMTP id a22mr3275534otf.82.1604415995395; Tue, 03 Nov 2020 07:06:35 -0800 (PST) X-Google-Smtp-Source: ABdhPJzh9ifcma5C1JNPyzLbYfjh07a8UkCWEbkIj7k7g68ByrQMcE7vGPZJ1NAzUDyQYL4u62YgFg== X-Received: by 2002:a9d:4716:: with SMTP id a22mr3275520otf.82.1604415995149; Tue, 03 Nov 2020 07:06:35 -0800 (PST) Received: from trix.remote.csb (075-142-250-213.res.spectrum.com. [75.142.250.213]) by smtp.gmail.com with ESMTPSA id f2sm4210951oig.15.2020.11.03.07.06.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 03 Nov 2020 07:06:34 -0800 (PST) To: Nicolas Chautru , dev@dpdk.org, akhil.goyal@nxp.com, thomas@monjalon.net Cc: john.mcnamara@intel.com, david.marchand@redhat.com, bruce.richardson@intel.com, tianjiao.liu@intel.com References: <1604350399-21015-1-git-send-email-nicolas.chautru@intel.com> <1604350399-21015-2-git-send-email-nicolas.chautru@intel.com> From: Tom Rix Message-ID: <28d8e618-96b7-14be-0e72-d44822800327@redhat.com> Date: Tue, 3 Nov 2020 07:06:32 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <1604350399-21015-2-git-send-email-nicolas.chautru@intel.com> Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=trix@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Subject: Re: [dpdk-dev] [PATCH v2] doc: add reference to companion configuration tool 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 11/2/20 12:53 PM, Nicolas Chautru wrote: > Adding reference to pf_bb_config in github to do > device configuration of the fpga_5gnr, fpga_lte and > acc100 devices and pmds. > > Signed-off-by: Nicolas Chautru > --- > doc/guides/bbdevs/acc100.rst | 19 +++++++++++++++++++ > doc/guides/bbdevs/fpga_5gnr_fec.rst | 19 +++++++++++++++++++ > doc/guides/bbdevs/fpga_lte_fec.rst | 19 +++++++++++++++++++ > 3 files changed, 57 insertions(+) > > diff --git a/doc/guides/bbdevs/acc100.rst b/doc/guides/bbdevs/acc100.rst > index 7a23c16..b772854 100644 > --- a/doc/guides/bbdevs/acc100.rst > +++ b/doc/guides/bbdevs/acc100.rst > @@ -223,3 +223,22 @@ In addition to the simple LDPC decoder and LDPC encoder tests, bbdev also provid > a range of additional tests under the test_vectors folder, which may be useful. The results > of these tests will depend on the ACC100 5G/4G FEC capabilities which may cause some > testcases to be skipped, but no failure should be reported. > + > + > +Alternate Baseband Device configuration tool > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + > +On top of the embedded configuration feature supported in test-bbdev using "- -init-device" > +option mentioned above, there is also a tool available to perform that device configuration > +using a companion application. > +The ``pf_bb_config`` application notably enables then to run bbdev-test from the VF > +and not only limited to the PF as captured above. > + > +See for more details: https://github.com/intel/pf-bb-config > + > +Specifically for the BBDEV ACC100 PMD, the command below can be used: > + > +.. code-block:: console > + > + ./pf_bb_config ACC100 -c acc100/acc100_config_vf_5g.cfg > + ./test-bbdev.py -e="-c 0xff0 -w${VF_PCI_ADDR}" -c validation -n 64 -b 32 -l 1 -v ./ldpc_dec_default.data > diff --git a/doc/guides/bbdevs/fpga_5gnr_fec.rst b/doc/guides/bbdevs/fpga_5gnr_fec.rst > index 61c19c3..78c1ce7 100644 > --- a/doc/guides/bbdevs/fpga_5gnr_fec.rst > +++ b/doc/guides/bbdevs/fpga_5gnr_fec.rst > @@ -286,3 +286,22 @@ Test Vectors > In addition to the simple LDPC decoder and LDPC encoder tests, bbdev also provides > a range of additional tests under the test_vectors folder, which may be useful. The results > of these tests will depend on the FPGA 5GNR FEC capabilities. > + > + > +Alternate Baseband Device configuration tool > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + > +On top of the embedded configuration feature supported in test-bbdev using "- -init-device" > +option, there is also a tool available to perform that device configuration using a companion > +application. > +The ``pf_bb_config`` application notably enables then to run bbdev-test from the VF > +and not only limited to the PF as captured above. > + > +See for more details: https://github.com/intel/pf-bb-config > + > +Specifically for the BBDEV FPGA 5GNR FEC PMD, the command below can be used: > + > +.. code-block:: console > + > + ./pf_bb_config FPGA_5GNR -c fpga_5gnr/fpga_5gnr_config_vf.cfg > + ./test-bbdev.py -e="-c 0xff0 -w${VF_PCI_ADDR}" -c validation -n 64 -b 32 -l 1 -v ./ldpc_dec_default.data > diff --git a/doc/guides/bbdevs/fpga_lte_fec.rst b/doc/guides/bbdevs/fpga_lte_fec.rst > index 9d64e15..a1b3e33 100644 > --- a/doc/guides/bbdevs/fpga_lte_fec.rst > +++ b/doc/guides/bbdevs/fpga_lte_fec.rst > @@ -305,3 +305,22 @@ of these tests will depend on the FPGA LTE FEC capabilities: > - ``turbo_enc_c2_k5952_r0_e17868_crc24b.data`` > - ``turbo_enc_c3_k4800_r2_e14412_crc24b.data`` > - ``turbo_enc_c4_k4800_r2_e14412_crc24b.data`` > + > + > +Alternate Baseband Device configuration tool > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + > +On top of the embedded configuration feature supported in test-bbdev using "- -init-device" > +option, there is also a tool available to perform that device configuration using a companion > +application. > +The ``pf_bb_config`` application notably enables then to run bbdev-test from the VF > +and not only limited to the PF as captured above. > + > +See for more details: https://github.com/intel/pf-bb-config > + > +Specifically for the BBDEV FPGA LTE FEC PMD, the command below can be used: > + > +.. code-block:: console > + > + ./pf_bb_config FPGA_lte -c fpga_lte/fpga_lte_config_vf.cfg >From inspection, pf_bb_config does not care about the case of FPGA_lte However for documentation, it is best if these examples are consistent. So this should be ./pf_bb_config FPGA_LTE ... Tom > + ./test-bbdev.py -e="-c 0xff0 -w${VF_PCI_ADDR}" -c validation -n 64 -b 32 -l 1 -v ./turbo_dec_default.data