umb: Introduce the USB umb(4) network driver

This includes the port of a driver originally from OpenBSD, later
ported to NetBSD by the author:

* The umb(4) kernel driver
* The umbctl(8) companion t

umb: Introduce the USB umb(4) network driver

This includes the port of a driver originally from OpenBSD, later
ported to NetBSD by the author:

* The umb(4) kernel driver
* The umbctl(8) companion tool

This driver supports USB network devices implementing the
Mobile Broadband Interface Model (MBIM), often found in modern
(internal) USB models for 4G/LTE mobile broadband access.

It is currently limited to IPv4.

umbctl has to be used to display or set MBIM cellular modem
interface parameters (4G/LTE).

Differential Revision: https://reviews.freebsd.org/D48167
Approved by: adrian, zlei
Sponsored by: FreeBSD Foundation
PR: kern/263783
Submitted by: Pierre Pronchery <khorben@defora.org>

show more ...

twe.4: Remove manpage for previously-removed driver

Reviewed by: ziaee, imp
Fixes: 062a7b918fac twe: Remove driver
Differential Revision: https://reviews.freebsd.org/D48403

Remove SOC FPGA drivers

The drivers have been disconnected from the build since the removal of
the SOCFPGA kernel configs.

Reviewed by: manu, imp, andrew
Sponsored by: AFRL, DARPA
Differential Revi

Remove SOC FPGA drivers

The drivers have been disconnected from the build since the removal of
the SOCFPGA kernel configs.

Reviewed by: manu, imp, andrew
Sponsored by: AFRL, DARPA
Differential Revision: https://reviews.freebsd.org/D47885

show more ...

Install pvscsi man page

This was lost during the initial introduction of the pvscsi driver [1].
Later the driver was enabled on arm64 [2], so also install the man page
on arm64.

1. 052e12a5084f Add

Install pvscsi man page

This was lost during the initial introduction of the pvscsi driver [1].
Later the driver was enabled on arm64 [2], so also install the man page
on arm64.

1. 052e12a5084f Add the pvscsi driver to the tree
2. 375d797b8191 Enable pvscsi and vmx in arm64 GENERIC

Reviewed by: emaste, Alexander Ziaee <concussious.bugzilla_runbox.com> (manpages)
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D47712

show more ...

Install vmx man page also on arm64

Fixes: 375d797b8191 Enable pvscsi and vmx in arm64 GENERIC
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D47711

p9fs.5: rename to p9fs.4

This is a filesystem (driver), not a file format, so it should be in
section 4.

Pull Request: https://github.com/freebsd/freebsd-src/pull/1520

ixgbe.4: rename to ix.4

PR: 213026
MFC after: 3 days
Reported by: Sergey Akhmatov <sergey@akhmatov.ru>
Co-authored-by: Alexander Ziaee <concussious@runbox.com>

rtw89: add man page and hook driver up to the build

After two years, add the initial man page and hook Realteks rtw89
driver up to the build for more people to test given successful
reports.
devd.co

rtw89: add man page and hook driver up to the build

After two years, add the initial man page and hook Realteks rtw89
driver up to the build for more people to test given successful
reports.
devd.conf is already providing support based on the rtw<n+> regex.
The driver uses the LinuxKPI compat layer.

Firmware is provided by ports: net/wifi-firmware-rtw89-kmod or
one of the flavours. People are advised to used fwget(8) to
automatically install the correct firmware for their chipset.

Please note that for the moment the driver requires a tunable to
be set in loader.conf: compat.linuxkpi.skb.mem_limit=1

Many thanks to everyone who in the last two years helped testing,
debugged, submitted patches to get the driver to this stage where
initial functionality seems working.

Sponsored by: The FreeBSD Foundation
MFC after: 3 days

show more ...

hn: fix build on !x86

hv_netvm aren't installed on !x64. Do the canonical thing with the
links.

Fixes: 83e93d53f674
Sponsored by: Netflix

hv_netvsc.4: mlink to hn(4)/if_hn(4) + tag spdx

dmesg for this device says:
> hn0: <Hyper-V Network Interface> on vmbus0

Add links so that `man hn` and `man if_hn` work.

MFC after: 3 days
Reviewed

hv_netvsc.4: mlink to hn(4)/if_hn(4) + tag spdx

dmesg for this device says:
> hn0: <Hyper-V Network Interface> on vmbus0

Add links so that `man hn` and `man if_hn` work.

MFC after: 3 days
Reviewed by: imp
Pull Request: https://github.com/freebsd/freebsd-src/pull/1377

show more ...

man4: Add a comment about Hardware Notes

The Hardware Notes for each release are generated automatically from a
template file and the HARDWARE sections of driver man pages. When man
pages for new d

man4: Add a comment about Hardware Notes

The Hardware Notes for each release are generated automatically from a
template file and the HARDWARE sections of driver man pages. When man
pages for new drivers are added here, they should usually be added to
the release notes template file.

Suggested by: bz
Sponsored by: Amazon

show more ...

Add dummymbuf module for testing purposes

Reviewed by: kp
Differential Revision: https://reviews.freebsd.org/D45928

Add examples to veriexec(8)

Add missing flags to veriexec(8) as well as some examples to
help explain usage.

Also add veriexec.4

Sponsored by: Juniper Networks, Inc.

Reviewed by: imp
Differential

Add examples to veriexec(8)

Add missing flags to veriexec(8) as well as some examples to
help explain usage.

Also add veriexec.4

Sponsored by: Juniper Networks, Inc.

Reviewed by: imp
Differential Revision: https://reviews.freebsd.org/D46207

show more ...

sound: Implement dummy driver

Sponsored by: The FreeBSD Foundation
MFC after: 2 days
Reviewed by: dev_submerge.ch
Differential Revision: https://reviews.freebsd.org/D45967

Remove residual blank line at start of Makefile

This is a residual of the $FreeBSD$ removal.

MFC After: 3 days (though I'll just run the command on the branches)
Sponsored by: Netflix

mac_do: add a new MAC/do policy and mdo(1) utility

This policy enables a user to become another user without having to be
root (hence no setuid binary). it is configured via rules using sysctl
secur

mac_do: add a new MAC/do policy and mdo(1) utility

This policy enables a user to become another user without having to be
root (hence no setuid binary). it is configured via rules using sysctl
security.mac.do.rules

For example:
security.mac.do.rules=uid=1001:80,gid=0:any

The above rule means the user identifier by the uid 1001 is able to
become user 80
Any user of the group 0 are allowed to become any user on the system.

The mdo(1) utility expects the MAC/do policy to be installed and its
rules defined.

Reviewed by: des
Differential Revision: https://reviews.freebsd.org/D45145

show more ...

Add man page for the ice network driver.

PR: 262892
MFC after: 3 days
Reviewed by: concussious.bugzilla@runbox.com, erj
Differential Revision: https://reviews.freebsd.org/D45270

Trim a spurious trailing backslash

Reported by: dim
Fixes: 1687d77197c0 man filesystems: move driver pages to section four

man filesystems: move driver pages to section four

Filesystem manual pages describe drivers, not formats;
except for fs, which describes the structures of ffs/ufs,
not how to use it in the system.

man filesystems: move driver pages to section four

Filesystem manual pages describe drivers, not formats;
except for fs, which describes the structures of ffs/ufs,
not how to use it in the system.

Reported by: emaste
Reviewed by: des, imp, meena (previous version)
Pull Request: https://github.com/freebsd/freebsd-src/pull/1077

show more ...

Add man page for nfslockd.

PR: 130238
MFC after: 3 days
Differential Revision: https://reviews.freebsd.org/D45139

snd_hdsp(4): RME HDSP 9632 and HDSP 9652 sound card driver.

Add a sound(4) bridge device driver for the RME HDSP 9632 and HDSP 9652
sound cards. These cards require a nowadays rare PCI 32bit (not PC

snd_hdsp(4): RME HDSP 9632 and HDSP 9652 sound card driver.

Add a sound(4) bridge device driver for the RME HDSP 9632 and HDSP 9652
sound cards. These cards require a nowadays rare PCI 32bit (not PCIe)
slot, but still see use due to their value and wealth of features.
The HDSP 9632 is mostly comparable to the newer HDSPe AIO, while the
HDSP 9652 is similar to the HDSPe RayDAT. These HDSPe PCIe cards are
supported by the snd_hdspe(4) driver which was taken as a starting point
for development of snd_hdsp(4).

Implementation is kept separately due to substantial differences in
hardware configuration and to allow easy removal in case PCI 32bit
support would be phased out in the future.

The snd_hdsp(4) kernel module is not enabled by default, and can be
loaded at runtime with kldload(8) or during boot via loader.conf(5).
Basic operation was tested with both cards, not including all optional
cable connectors and expansion boards. Features should be roughly on par
with the snd_hdspe(4) supported cards.

Reviewed by: christos, br
Differential Revision: https://reviews.freebsd.org/D45112

show more ...

Remove gbde.4 man page

sg: Add sg(4) man page

Add minimal sg(4) manual page. This implements a subset of the Linux
IOCTL interface for either native FreeBSD programs, or for Linux
binaries in the linuxulator.

Noticed by:

sg: Add sg(4) man page

Add minimal sg(4) manual page. This implements a subset of the Linux
IOCTL interface for either native FreeBSD programs, or for Linux
binaries in the linuxulator.

Noticed by: Lexi Winter
Sponsored by: Netflix

show more ...

nvmft: The in-kernel NVMe over Fabrics controller

This is the server (target in SCSI terms) for NVMe over Fabrics.
Userland is responsible for accepting a new queue pair and receiving
the initial Co

nvmft: The in-kernel NVMe over Fabrics controller

This is the server (target in SCSI terms) for NVMe over Fabrics.
Userland is responsible for accepting a new queue pair and receiving
the initial Connect command before handing the queue pair off via an
ioctl to this CTL frontend.

This frontend exposes CTL LUNs as NVMe namespaces to remote hosts.
Users can ask LUNS to CTL that can be shared via either iSCSI or
NVMeoF.

Reviewed by: imp
Sponsored by: Chelsio Communications
Differential Revision: https://reviews.freebsd.org/D44726

show more ...

nvmf: The in-kernel NVMe over Fabrics host

This is the client (initiator in SCSI terms) for NVMe over Fabrics.
Userland is responsible for creating a set of queue pairs and then
handing them off via

nvmf: The in-kernel NVMe over Fabrics host

This is the client (initiator in SCSI terms) for NVMe over Fabrics.
Userland is responsible for creating a set of queue pairs and then
handing them off via an ioctl to this driver, e.g. via the 'connect'
command from nvmecontrol(8). An nvmeX new-bus device is created
at the top-level to represent the remote controller similar to PCI
nvmeX devices for PCI-express controllers.

As with nvme(4), namespace devices named /dev/nvmeXnsY are created and
pass through commands can be submitted to either the namespace devices
or the controller device. For example, 'nvmecontrol identify nvmeX'
works for a remote Fabrics controller the same as for a PCI-express
controller.

nvmf exports remote namespaces via nda(4) devices using the new NVMF
CAM transport. nvmf does not support nvd(4), only nda(4).

Sponsored by: Chelsio Communications
Differential Revision: https://reviews.freebsd.org/D44714

show more ...