1 .. SPDX-License-Identifier: BSD-3-Clause
2 Copyright 2019 Mellanox Technologies, Ltd
4 Mellanox BlueField Board Support Package
5 ========================================
7 This document has information about steps to setup Mellanox BlueField platform
8 and common offload HW drivers of **Mellanox BlueField** family SoC.
11 Supported BlueField family SoCs
12 -------------------------------
14 - `BlueField <https://docs.mellanox.com/category/bluefieldsnic>`_
17 Supported BlueField Platforms
18 -----------------------------
20 - `BlueField-1 <https://docs.mellanox.com/display/bluefieldsniceth/Introduction>`_
21 - `BlueField-2 <https://docs.mellanox.com/display/BlueField2DPUENUG/Introduction>`_
24 Common Offload HW Drivers
25 -------------------------
29 See :doc:`../nics/mlx5` for Mellanox mlx5 NIC driver information.
31 2. **Cryptodev Driver**
33 This is based on the crypto extension support of armv8. See
34 :doc:`../cryptodevs/armv8` for armv8 crypto driver information.
38 BlueField has a variant having no armv8 crypto extension support.
41 Steps To Setup Platform
42 -----------------------
44 Toolchains, OS and drivers can be downloaded and installed individually
45 from the web, but it is recommended to follow instructions at:
47 - `Mellanox BlueField-1 Software Website <https://docs.mellanox.com/display/BlueFieldSWv31011424/SmartNIC+Bring-Up+and+Driver+Installation>`_
48 - `Mellanox BlueField-2 Software Website <https://docs.mellanox.com/display/NVIDIABlueField2DPUQSG#NVIDIABlueField2DPUSoftwareQuickStartGuide-Post-installationProcedurePost-installationProcedure>`_
54 DPDK can be compiled either natively on BlueField platforms or cross-compiled on
55 an x86 based platform.
60 Refer to :doc:`../nics/mlx5` for prerequisites. Either Mellanox OFED/EN or
61 rdma-core library with corresponding kernel drivers is required.
63 .. code-block:: console
71 Refer to :doc:`../linux_gsg/cross_build_dpdk_for_arm64` to install the cross
72 toolchain for ARM64. Base on that, additional header files and libraries are
80 Such header files and libraries can be cross-compiled and installed on to the
81 cross toolchain directory like depicted in
82 :ref:`arm_cross_build_getting_the_prerequisite_library`, but those can also be
83 simply copied from the filesystem of a working BlueField platform. The following
84 script can be run on a BlueField platform in order to create a supplementary
85 tarball for the cross toolchain.
87 .. code-block:: console
89 mkdir -p aarch64-linux-gnu/libc
91 cd aarch64-linux-gnu/libc
95 cp -a /lib64/libibverbs* lib64/
96 cp -a /lib64/libmlx5* lib64/
97 cp -a /lib64/libnl-3* lib64/
98 cp -a /lib64/libnl-route-3* lib64/
101 mkdir -p usr/include/infiniband
102 cp -a /usr/include/infiniband/ib_user_ioctl_verbs.h usr/include/infiniband/
103 cp -a /usr/include/infiniband/mlx5*.h usr/include/infiniband/
104 cp -a /usr/include/infiniband/tm_types.h usr/include/infiniband/
105 cp -a /usr/include/infiniband/verbs*.h usr/include/infiniband/
107 # Create supplementary tarball
109 tar cf aarch64-linux-gnu-mlx.tar aarch64-linux-gnu/
111 Then, untar the tarball at the cross toolchain directory on the x86 host.
113 .. code-block:: console
115 cd $(dirname $(which aarch64-linux-gnu-gcc))/..
116 tar xf aarch64-linux-gnu-mlx.tar
118 .. code-block:: console
120 meson build --cross-file config/arm/arm64_bluefield_linux_gcc