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 221F3A04E7; Tue, 3 Nov 2020 20:07:46 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8290154AE; Tue, 3 Nov 2020 20:07:44 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by dpdk.org (Postfix) with ESMTP id AEB104C96 for ; Tue, 3 Nov 2020 20:07:41 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1604430460; 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=Ky+485arx4XW5v+VIynLfxhz6yjUjOdtadm2KEi4Dj0=; b=UVdb9Ov5z0otp2sHTg4FNFwpiSF5lgRid84DLV8WDZ5zXEMLVKxWOW1dDCnSQiMMsrh8b8 uoAUlZJkLQbBkK4GavFy4ZNIJ9TKpz9yf1MohVxlAGCWnwgvImUxJg9OFb2J76kLgaKo3x UOS3mBhwcwhRuzJuA00FyfesfL9ljxU= Received: from mail-oo1-f71.google.com (mail-oo1-f71.google.com [209.85.161.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-353-zL4F90xgNTC_WkU61_tobA-1; Tue, 03 Nov 2020 14:07:37 -0500 X-MC-Unique: zL4F90xgNTC_WkU61_tobA-1 Received: by mail-oo1-f71.google.com with SMTP id 4so7551833ooc.21 for ; Tue, 03 Nov 2020 11:07:37 -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=Ky+485arx4XW5v+VIynLfxhz6yjUjOdtadm2KEi4Dj0=; b=GvLnWxsG0l6AC8WfdaNcitIpKHzgJQ03DqNvVkyoivwkYfu6DxNmk1jz14JTxFSVlO dsxrJ7LLVSSLje6dEzdU05oergFoTSHewoBBlZizeZM9wo1zd+teKnyXxM25v/0pVEMh M5Nnfix8KCMduwfJMWQajjsTmXFmKMdr7t8Z3t7ha3xf9h+D4JC4KH4nP/Dwfk6y/puA F7GmWU3LXgyh7pzjVx2yfelfwPV6CCkvD6d+cOh8OQHRCLFQBU/ob0O5ebzJuTjPXvGq YRLN6ImTCC6cJ+5+Al8gURb60KQv3ro/or/CF4QouijazRTK9PbJitE3y1czSJf6qmMG y2pw== X-Gm-Message-State: AOAM53250I6DjsJgwNCEtvsAV5/s31XiruVtt0+SdM0bWpt+rmC0HlA0 AzEbQQCUElSsxEV/luFQVhQB36qBCSa8SB1ZhJP6LdFQ4nOH4cBU86kvmRnyTTmAv7BuBuYrczM sM24= X-Received: by 2002:aca:f188:: with SMTP id p130mr378575oih.106.1604430456960; Tue, 03 Nov 2020 11:07:36 -0800 (PST) X-Google-Smtp-Source: ABdhPJzpagxPFnC/k8FPO+F0lcnOGnzrWZJWiv9FE2JdEOV2ITUNvFMem+IMjUeG5b+nAAgjAVfdiw== X-Received: by 2002:aca:f188:: with SMTP id p130mr378558oih.106.1604430456781; Tue, 03 Nov 2020 11:07:36 -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 l19sm1395517otp.65.2020.11.03.11.07.35 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 03 Nov 2020 11:07:36 -0800 (PST) To: "Chautru, Nicolas" , "dev@dpdk.org" , "akhil.goyal@nxp.com" , "thomas@monjalon.net" Cc: "Mcnamara, John" , "david.marchand@redhat.com" , "Richardson, Bruce" , "Liu, Tianjiao" References: <1604350399-21015-1-git-send-email-nicolas.chautru@intel.com> <1604350399-21015-2-git-send-email-nicolas.chautru@intel.com> <28d8e618-96b7-14be-0e72-d44822800327@redhat.com> From: Tom Rix Message-ID: Date: Tue, 3 Nov 2020 11:07:34 -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: 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/3/20 7:58 AM, Chautru, Nicolas wrote: > >> -----Original Message----- >> From: Tom Rix >> Sent: Tuesday, November 3, 2020 7:07 AM >> To: Chautru, Nicolas ; dev@dpdk.org; >> akhil.goyal@nxp.com; thomas@monjalon.net >> Cc: Mcnamara, John ; >> david.marchand@redhat.com; Richardson, Bruce >> ; Liu, Tianjiao >> Subject: Re: [PATCH v2] doc: add reference to companion configuration tool >> >> >> 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 >>> + >>> + >>> + ./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 > What do you mean? comparing the call examples in the doc ./pf_bb_config ACC100 -c acc100/acc100_config_vf_5g.cfg ./pf_bb_config FPGA_5GNR -c fpga_5gnr/fpga_5gnr_config_vf.cfg ./pf_bb_config FPGA_lte -c fpga_lte/fpga_lte_config_vf.cfg For consistency, the last should use FPGA_LTE Tom > >> 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