src/sys/modules/Makefile, branch release/13.2.0

irdma: fix LINT-NOIP/NOINET/NOINET6 builds

2023-02-21T22:40:49Z

This module depends on the presence of both INET and INET6 options in order to compile. Reviewed by: erj Fixes: cdcd52d41e24 ("irdma: Add RDMA driver for Intel(R) Ethernet...") Approved by: re (cperciva) Differential Revision: https://reviews.freebsd.org/D35343 (cherry picked from commit acdfbc6cbe0a8a976d446216be84994c8ee8d5c1) (cherry picked from commit 7333d34e5ec96db747648ab7b245d814d3140738)

irdma: Add RDMA driver for Intel(R) Ethernet Controller E810

2023-02-08T00:23:44Z

This is an initial commit for RDMA FreeBSD driver for Intel(R) Ethernet Controller E810, called irdma. Supporting both RoCEv2 and iWARP protocols in per-PF manner, RoCEv2 being the default. Testing has been done using krping tool, perftest, ucmatose, rping, ud_pingpong, rc_pingpong and others. Signed-off-by: Eric Joyner Reviewed by: #manpages (pauamma_gundo.com) [documentation] Relnotes: yes Sponsored by: Intel Corporation Differential Revision: https://reviews.freebsd.org/D34690 (cherry picked from commit cdcd52d41e246ba1c0fcfad0769bd691487355ef) (cherry picked from commit e602a30bb9fc7ee041a0e629d0fd2db7933ffa32) (cherry picked from commit a6e275af46644af1de365a1edf19742bfa28bb69)

netlink: add netlink support

2023-01-23T19:18:08Z

Netlinks is a communication protocol currently used in Linux kernel to modify, read and subscribe for nearly all networking state. Interfaces, addresses, routes, firewall, fibs, vnets, etc are controlled via netlink. It is async, TLV-based protocol, providing 1-1 and 1-many communications. The current implementation supports the subset of NETLINK_ROUTE family. To be more specific, the following is supported: * Dumps: - routes - nexthops / nexthop groups - interfaces - interface addresses - neighbors (arp/ndp) * Notifications: - interface arrival/departure - interface address arrival/departure - route addition/deletion * Modifications: - adding/deleting routes - adding/deleting nexthops/nexthops groups - adding/deleting neghbors - adding/deleting interfaces (basic support only) * Rtsock interaction - route events are bridged both ways The implementation also supports the NETLINK_GENERIC family framework. Implementation notes: Netlink is implemented via loadable/unloadable kernel module, not touching many kernel parts. Each netlink socket uses dedicated taskqueue to support async operations that can sleep, such as interface creation. All message processing is performed within these taskqueues. Compatibility: Most of the Netlink data models specified above maps to FreeBSD concepts nicely. Unmodified ip(8) binary correctly works with interfaces, addresses, routes, nexthops and nexthop groups. Some software such as net/bird require header-only modifications to compile and work with FreeBSD netlink. Reviewed by: imp Differential Revision: https://reviews.freebsd.org/D36002 MFC after: 2 months (cherry picked from commit 7e5bf68495cc0a8c9793a338a8a02009a7f6dbb6)

Add initial DPAA2 support

2023-01-22T14:06:23Z

DPAA2 is a hardware-level networking architecture found in some NXP SoCs which contain hardware blocks including Management Complex (MC, a command interface to manipulate DPAA2 objects), Wire Rate I/O processor (WRIOP, packets distribution, queuing, drop decisions), Queues and Buffers Manager (QBMan, Rx/Tx queues control, Rx buffer pools) and the others. The Management Complex runs NXP-supplied firmware which provides DPAA2 objects as an abstraction layer over those blocks to simplify an access to the underlying hardware. Each DPAA2 object has its own driver (to perform an initialization at least) and will be visible as a separate device in the device tree. Two new drivers (dpaa2_mc and dpaa2_rc) act like firmware buses in order to form a hierarchy of the DPAA2 devices: acpiX (or simplebusX) dpaa2_mcX dpaa2_rcX dpaa2_mcp0 ... dpaa2_mcpN dpaa2_bpX dpaa2_macX dpaa2_io0 ... dpaa2_ioM dpaa2_niX dpaa2_mc is suppossed to be a root of the hierarchy, comes in ACPI and FDT flavours and implements helper interfaces to allocate and assign bus resources, MSI and "managed" DPAA2 devices (NXP treats some of the objects as resources for the other DPAA2 objects to let them function properly). Almost all of the DPAA2 objects are assigned to the resource containers (dpaa2_rc) to implement isolation. The initial implementation focuses on the DPAA2 network interface to be operational. It is the most complex object in terms of dependencies which uses I/O objects to transmit/receive packets. Approved by: bz (mentor) Tested by: manu, bz Differential Revision: https://reviews.freebsd.org/D36638 (cherry picked from commit ba7319e9091b4f6ef15a9c4be3d3d076f3047f72) (cherry picked from commit 7fb975c8fb970b35fc34561ed30a0fe220346cb6) (cherry picked from commit 2782ed8f6cd3d7f59219a783bc7fa7bbfb1fe26f) (cherry picked from commit d6eabdac2ef444b62aba186c793fbd5d4226b157) (cherry picked from commit 16295b0a5a577aa70f47d3b3314277e631caee63) (cherry picked from commit ff270fce1631cdfbf8d3d76b9a9f5342b78972c9)

bnxt: Only filter out i386

2023-01-19T01:02:26Z

Only i386 is missing bus_read_8. The other 32-bit platforms can be fixed with a cast to a printf. Suggested by: kevans Sponsored by: Netflix (cherry picked from commit eb40e3e757a7eb80c2b5c38ce05fc4b411b369f9)

Import the WireGuard driver from zx2c4.com.

2022-11-11T21:44:11Z

This commit brings back the driver from FreeBSD commit f187d6dfbf633665ba6740fe22742aec60ce02a2 plus subsequent fixes from upstream. Relative to upstream this commit includes a few other small fixes such as additional INET and INET6 #ifdef's, #include cleanups, and updates for recent API changes in main. Reviewed by: pauamma, gbe, kevans, emaste Obtained from: git@git.zx2c4.com:wireguard-freebsd @ 3cc22b2 Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D36909 (cherry picked from commit 744bfb213144c63cbaf38d91a1c4f7aebb9b9fbc)

modules: Only build MAC modules if options MAC is set

2022-06-23T22:22:18Z

They are not loadable otherwise. Reviewed by: emaste MFC after: 1 week Sponsored by: Juniper Networks, Inc. Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D35369 (cherry picked from commit 648a47b85476ed0f8e3c61800b134bd3bb6001ee)

rtw88: add man pages and hook up to build

2022-06-03T15:51:16Z

Add man pages for rtw88 and rtw88fw. Install a copy of the firmware license file and hook up the driver and firmware modules to the build. Sponsored by: The FreeBSD Foundation Relnotes: yes (cherry picked from commit 20eeed6844e2ab82b909e02c720101297e78d916)

cgem: Support building as a loadable kernel module

2022-04-11T14:04:08Z

For development, building a driver as kernel module is both convenient and a time saver (no need for reboot on some change, testing it requires just kldunload and kldload, a matter of seconds). For some special cases, it may be even desirable to postpone initializing the network interface after some action is done (loading a FPGA bitstream may be required for Zynq/ZynqMP based hardware as an example). Building is limited to ARM, ARM64 and RISC-V architectures (for Zynq, ZynqMP, PolarFire Soc based boards, and HiFive based boards are known to use CGEM at the moment). Reviewed by: mhorne MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D34687 (cherry picked from commit 242cd60a0a670ff7cc446436bedd129fbdce062c)

powerpc: enable ice in GENERIC64LE

2022-03-08T00:09:12Z

Approved by: erj Differential Revision: https://reviews.freebsd.org/D33974 (cherry picked from commit a0f3abb098799ec05b6dd8a40363b1093cf81d49)