From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id DAFEA41D66; Fri, 24 Feb 2023 19:24:11 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7FD1640A87; Fri, 24 Feb 2023 19:24:11 +0100 (CET) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by mails.dpdk.org (Postfix) with ESMTP id AC2DE40697 for ; Fri, 24 Feb 2023 19:24:09 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1677263049; x=1708799049; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=v3WReYP/xqmaSUaX5lYrdrcU5tL2nk28/aJa1/5qFBc=; b=bNOUICwr20a+TcqZlpoGXo9vOf5OkzthiMqOS8iqF5rUkYvHrHj2l0Ex pW4eq1ygynjRNbtxqnLFgBrA2cq+V90eVmiR0LVkndAAwoclaQvqOabOw ZBG6J88m2itGM/BY9hbWX5uju32KQWmvduCXuGqytLzWRALaqNtBsF1xL 2RF9eVUFl8AyQcXD8g4KM5weTp7uthVFFbj1jOp3TT+Ha7l/KW77tML66 en0lROwd5su/3vndeq7rJFqKVsSSZ8W/tef9aJsz9UuGAcGSpcMXKFF3t RVxaHaQv1OHjS64dxvDv8oJA2JV0oANsPOQsl/DvP5vFEFy6F9tpZ0lha A==; X-IronPort-AV: E=McAfee;i="6500,9779,10631"; a="332233330" X-IronPort-AV: E=Sophos;i="5.97,325,1669104000"; d="scan'208";a="332233330" Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Feb 2023 10:24:08 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10631"; a="741736301" X-IronPort-AV: E=Sophos;i="5.97,325,1669104000"; d="scan'208";a="741736301" Received: from spr-npg-bds1-eec2.sn.intel.com (HELO spr-npg-bds1-eec2..) ([10.233.181.123]) by fmsmga004.fm.intel.com with ESMTP; 24 Feb 2023 10:24:08 -0800 From: Nicolas Chautru To: dev@dpdk.org, maxime.coquelin@redhat.com Cc: hernan.vargas@intel.com, Nicolas Chautru Subject: [PATCH v1 1/1] doc: update to Intel vRAN Boost PMD Date: Fri, 24 Feb 2023 18:20:19 +0000 Message-Id: <20230224182019.83342-2-nicolas.chautru@intel.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20230224182019.83342-1-nicolas.chautru@intel.com> References: <20230224182019.83342-1-nicolas.chautru@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Cosmetic change to refer explictly to the full name of the PMD Intel vRAN Boost v1. VRB1 acronym is only used as a prefix within the code. Signed-off-by: Nicolas Chautru --- doc/guides/bbdevs/vrb1.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/guides/bbdevs/vrb1.rst b/doc/guides/bbdevs/vrb1.rst index f5a9dff804..9c48d30964 100644 --- a/doc/guides/bbdevs/vrb1.rst +++ b/doc/guides/bbdevs/vrb1.rst @@ -104,7 +104,7 @@ Initialization -------------- When the device first powers up, its PCI Physical Functions (PF) -can be listed through these commands for VRB1: +can be listed through these commands for Intel vRAN Boost v1: .. code-block:: console @@ -123,7 +123,7 @@ Install the DPDK igb_uio driver, bind it with the PF PCI device ID and use ``lspci`` to confirm the PF device is under use by ``igb_uio`` DPDK UIO driver. The igb_uio driver may be bound to the PF PCI device using one of two methods -for VRB1: +for Intel vRAN Boost v1: #. PCI functions (physical or virtual, depending on the use case) can be bound to the UIO driver by repeating this command for every function. @@ -252,7 +252,7 @@ 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 VRB1 PMD, the command below can be used +Specifically for the bbdev Intel vRAN Boost v1 PMD, the command below can be used (note that ACC200 was used previously to refer to VRB1): .. code-block:: console -- 2.34.1