Some machine (like on dpdk.org) may fail to build the prog guide PDF because of
the complex table inserted in the bbdev chapter.
Fixes: 3f3f608142cf ("doc: update bbdev guide for 5GNR operations")
Signed-off-by: Nicolas Chautru <nicolas.chau...@intel.com>
---
doc/guides/prog_guide/bbdev.rst | 32 ++++++++++++++++----------------
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/doc/guides/prog_guide/bbdev.rst b/doc/guides/prog_guide/bbdev.rst
index ef05dcb..6c0bb3c 100644
--- a/doc/guides/prog_guide/bbdev.rst
+++ b/doc/guides/prog_guide/bbdev.rst
@@ -800,21 +800,21 @@ The LDPC encode parameters are set out in the table below.
|op_flags |bitmask of all active operation capabilities
|
+----------------+--------------------------------------------------------------------+
|**cb_params** |code block specific parameters (code block mode only)
|
-+----------------+------------+-------------------------------------------------------+
-| |e |E, length of the rate matched output sequence
in bits |
-+----------------+------------+-------------------------------------------------------+
++----------------+--------------------------------------------------------------------+
+|e |E, length of the rate matched output sequence in bits
|
++----------------+--------------------------------------------------------------------+
|**tb_params** | transport block specific parameters (transport block mode
only) |
-+----------------+------------+-------------------------------------------------------+
-| |c |number of CBs in the TB or partial TB
|
-+----------------+------------+-------------------------------------------------------+
-| |r |index of the first CB in the inbound mbuf data
|
-+----------------+------------+-------------------------------------------------------+
-+ +c_ab +number of CBs that use Ea before switching to
Eb |
-+----------------+------------+-------------------------------------------------------+
-| |ea |Ea, length of the RM output sequence in bits, r
< cab |
-+----------------+------------+-------------------------------------------------------+
-| |eb |Eb, length of the RM output sequence in bits, r
>= cab |
-+----------------+------------+-------------------------------------------------------+
++----------------+--------------------------------------------------------------------+
+|c |number of CBs in the TB or partial TB
|
++----------------+--------------------------------------------------------------------+
+|r |index of the first CB in the inbound mbuf data
|
++----------------+--------------------------------------------------------------------+
++c_ab +number of CBs that use Ea before switching to Eb
|
++----------------+--------------------------------------------------------------------+
+|ea |Ea, length of the RM output sequence in bits, r < cab
|
++----------------+--------------------------------------------------------------------+
+|eb |Eb, length of the RM output sequence in bits, r >= cab
|
++----------------+--------------------------------------------------------------------+
The mbuf input ``input`` is mandatory for all BBDEV PMDs and is the
incoming code block or transport block data.
@@ -865,7 +865,7 @@ calculated by BBDEV before signalling to the driver.
The number of CBs in the group should not be confused with ``c``, the
total number of CBs in the full TB (``C`` as per 3GPP TS 38.212 section 5.2.2)
-Figure 13.1 above showing the Turbo encoding of CBs using BBDEV
+Figure :numref:`figure_turbo_tb_encode` above showing the Turbo encoding of
CBs using BBDEV
interface in TB-mode is also valid for LDPC encode.
BBDEV LDPC Decode Operation
@@ -1077,7 +1077,7 @@ total number of CBs in the full TB (``C`` as per 3GPP TS
38.212 section 5.2.2)
The ``length`` is total size of the CBs inclusive of any CRC24A and CRC24B in
case they were appended by the application.
-Figure 13.2 above showing the Turbo decoding of CBs using BBDEV
+Figure :numref:`figure_turbo_tb_decode` above showing the Turbo decoding of
CBs using BBDEV
interface in TB-mode is also valid for LDPC decode.
--
1.8.3.1
