aboutsummaryrefslogtreecommitdiff
path: root/share/man/man4
Commit message (Collapse)AuthorAgeFilesLines
* pci: Disable Electromechanical Interlock.Alexander Motin32 hours1-1/+3
| | | | | | | | | | | | | Add sysctl/tunable to control Electromechanical Interlock support. Disable it by default since Linux does not do it either and it seems the number of systems having it broken is higher than having working. This fixes NVMe backplane operation on ASUS RS500A-E11-RS12U server with AMD EPYC 7402 CPU, where attempts to control reported interlock for some reason end up in PCIe link loss, while interlock status does not change (it is not really there). MFC after: 2 weeks
* tcp: allow window scale and timestamps to be toggled individuallyRichard Scheffenegger2 days1-1/+12
| | | | | | | | | Simple change to allow for the individual toggling of RFC7323 window scaling and timestamp option. Reviewed By: rrs, tuexen, glebius, guest-ccui, #transport Sponsored by: NetApp, Inc. Differential Revision: https://reviews.freebsd.org/D36863
* Tcp progress timeoutRandall Stewart8 days1-0/+12
| | | | | | | | | | | Rack has had the ability to timeout connections that just sit idle automatically. This feature of course is off by default and requires the user set it on (though the socket option has been missing in tcp_usrreq.c). Lets get the progress timeout fully supported in the base stack as well as rack. Reviewed by: tuexen Sponsored by: Netflix Inc Differential Revision: https://reviews.freebsd.org/D36716
* snp(4): implement detachKonstantin Belousov10 days1-6/+0
| | | | | | | | | PR: 257964 Reported by: Bertrand Petit <bsdpr@phoe.frmug.org> Reviewed by: imp, markj Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D36690
* snp(4): properly report detached/revoked ttysKonstantin Belousov10 days1-6/+2
| | | | | | | | | PR: 257964 Reported by: Bertrand Petit <bsdpr@phoe.frmug.org> Reviewed by: imp, markj Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D36690
* iwlwifi.4: typo fixedMaxim Konovalov13 days1-1/+1
| | | | PR: 266554
* Fix dead references (wrong section) to sysctl(8).Jens Schweikhardt2022-09-161-1/+1
|
* bridge.4: describe new MTU behaviourKristof Provost2022-09-161-3/+6
| | | | | | | | | | | 1865ebfb12 changed if_bridge to have it change the MTU on newly added interfaces to match the if_bridge MTU, rather than rejecting them for having an incorrect MTU. Update the man page to reflect this, as pointed out by woodsb02. Reviewed by: woodsb02 Differential Revision: https://reviews.freebsd.org/D36481
* tcp: make CUBIC the default congestion control mechanism.Richard Scheffenegger2022-09-133-10/+10
| | | | | | | | | | | | | This changes the default TCP Congestion Control (CC) to CUBIC. For small, transactional exchanges (e.g. web objects <15kB), this will not have a material effect. However, for long duration data transfers, CUBIC allocates a slightly higher fraction of the available bandwidth, when competing against NewReno CC. Reviewed By: tuexen, mav, #transport, guest-ccui, emaste Relnotes: Yes Sponsored by: NetApp, Inc. Differential Revision: https://reviews.freebsd.org/D36537
* cxgbe(4): Add another setting to the knob that controls congestion.Navdeep Parhar2022-09-121-1/+2
| | | | | | | | hw.cxgbe.cong_drop=2 will generate backpressure *and* drop frames for queues that are congested. MFC after: 2 weeks Sponsored by: Chelsio Communications
* da.4: Don't document softtimeoutWarner Losh2022-09-101-7/+0
| | | | | | | | | | | | | | | | kern.cam.da.default_softtimeout currently does nothing. It sets a value in the CCB that SIMs could look at, only none do. Leave it undocumented until it actually does something. It was introduced to allow a 'soft recovery' to be started when things were taking too long in the SIM by not scheduling new I/O, or other measures the SIM knew would help when it seemed like things were getting 'backed up'. No SIM in the FreeBSD tree implements this and scsi_da doesn't use it other than to pass it down, so best remove it from the documentation until it does something. Sponsored by: Netflix Fixes: 53af9c235f5d Reviewed by: gbe Differential Review: https://reviews.freebsd.org/D36518
* da.4: Add some sysctl descriptionsFelix Johnson2022-09-101-9/+40
| | | | | | | | | | | | | | | | | | | Add descriptions for the following sysctl's: - kern.cam.da.default_softtimeout - kern.cam.da.disable_wp_protection - kern.cam.da.enable_biospeedup - kern.cam.da.enable_uma_ccbs - kern.cam.da.poll_period - kern.cam.da.send_ordered While here, fix some mandocs warnings. PR: 258727 Reported by: Felix Johnson <felix dot the dot red at gmail dot com> Reviewed by: debdrup, pauamma, gbe MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D32278
* ip_reass: add loader tunable to tune the reassembly hash sizeGleb Smirnoff2022-09-081-0/+2
|
* ip_reass: retire ipreass_slowtimo() in favor of per-slot calloutGleb Smirnoff2022-09-081-1/+3
| | | | | | | | | | | o Retire global always running ipreass_slowtimo(). o Instead use one callout entry per hash slot. The per-slot callout would be scheduled only if a slot has entries, and would be driven by TTL of the very last entry. o Make net.inet.ip.fragttl read/write and document it. o Retire IPFRAGTTL, which used to be meaningful only with PR_SLOWTIMO. Differential revision: https://reviews.freebsd.org/D36275
* ip6.4: Correct a typo in the manual pageGordon Bergling2022-09-041-1/+1
| | | | | | - s/the the/the/ MFC after: 3 days
* tcp: Functional implementation of Accurate ECNRichard Scheffenegger2022-08-311-0/+7
| | | | | | | | | | | | The AccECN handshake and TCP header flags are supported, no support yet for the AccECN option. This minimalistic implementation is sufficient to support DCTCP while dramatically cutting the number of ACKs, and provide ECN response from the receiver to the CC modules. Reviewed By: #transport, #manpages, rrs, pauamma Sponsored by: NetApp, Inc. Differential Revision: https://reviews.freebsd.org/D21011
* divert(4): maintain own cb database and stop using inpcb KPIGleb Smirnoff2022-08-301-3/+2
| | | | | | | | | | | | | | | | | | | | Here go cons of using inpcb for divert: - divert(4) uses only 16 bits (local port) out of struct inpcb, which is 424 bytes today. - The inpcb KPI isn't able to provide hashing for divert(4), thus it uses global inpcb list for lookups. - divert(4) uses INET-specific part of the KPI, making INET a requirement for IPDIVERT. Maintain our own very simple hash lookup database instead. It has mutex protection for write and epoch protection for lookups. Since now so->so_pcb no longer points to struct inpcb, don't initialize protosw methods to methods that belong to PF_INET. Also, drop support for setting options on a divert socket. My review of software in base and ports confirms that this has no use and unlikely worked before. Differential revision: https://reviews.freebsd.org/D36382
* divert: declare PF_DIVERT domain and stop abusing PF_INETGleb Smirnoff2022-08-301-15/+23
| | | | | | | | | | | | | | | | | | | | | | | | | The divert(4) is not a protocol of IPv4. It is a socket to intercept packets from ipfw(4) to userland and re-inject them back. It can divert and re-inject IPv4 and IPv6 packets today, but potentially it is not limited to these two protocols. The IPPROTO_DIVERT does not belong to known IP protocols, it doesn't even fit into u_char. I guess, the implementation of divert(4) was done the way it is done basically because it was easier to do it this way, back when protocols for sockets were intertwined with IP protocols and domains were statically compiled in. Moving divert(4) out of inetsw accomplished two important things: 1) IPDIVERT is getting much closer to be not dependent on INET. This will be finalized in following changes. 2) Now divert socket no longer aliases with raw IPv4 socket. Domain/proto selection code won't need a hack for SOCK_RAW and multiple entries in inetsw implementing different flavors of raw socket can merge into one without requirement of raw IPv4 being the last member of dom_protosw. Differential revision: https://reviews.freebsd.org/D36379
* Indicate which port gdb.1 and kgdb.1 come from.Jens Schweikhardt2022-08-174-14/+14
|
* Indicate that kgdb.1 is from ports/devel/gdb.Jens Schweikhardt2022-08-141-3/+3
|
* Indicate that X(7) cross refs are satisfied by ports/x11/xorg-docs.Jens Schweikhardt2022-08-146-7/+7
|
* Fix wrong capitalization in man page references.Jens Schweikhardt2022-08-133-4/+5
|
* rtw88: correct a typo in man pageAndres Ramirez2022-08-071-2/+2
| | | | | | s/mmeory/memory/ MFC after: 1 week
* tcp.4: Add missing sysctls, other fixesMike Karels2022-08-021-18/+80
| | | | | | | | | | | | | Add some of the missing sysctls to tcp.4, using references to other man pages where they exist. Added sysctls include recvbuf and sendbuf controls for automatic buffer sizing. Updated recvspace and sendspace. Add sysctl.8 to "see also" and intro to variable section. Rename "MIB Variables" section to "MIB (sysctl) Variables", as most people will associate with sysctl. Reviewed by: manpages(pauamma), tuexen Differential Revision: https://reviews.freebsd.org/D36004
* inet.4 icmp.4 udp.4: Add missing sysctls, other fixesMike Karels2022-08-023-13/+51
| | | | | | | | | | | Add missing sysctls to inet.4 and icmp.4, using references to ip.4 for variables and groups documented there. Add sysctl.8 to "see also" and intro to variable section. Rename "MIB Variables" section to "MIB (sysctl) Variables", as most people will associate with sysctl. Revise history: the ICMP implementation was in 4.2BSD. Reviewed by: manpages(pauamma) Differential Revision: https://reviews.freebsd.org/D36003
* ip6(4): document IP_ORIGDSTADDRAlan Somers2022-07-291-6/+12
| | | | | | | | | The option was originally added in r313524, but with incomplete documentation. MFC after: 1 week Reviewed by: karels, gbe (manpages) Differential Revision: https://reviews.freebsd.org/D35890
* qat: Import a new Intel (R) QAT driverJulian Grajkowski2022-07-271-0/+127
| | | | | | | | | | | | | | | | | | | | | | | | | | QAT in-tree driver ported from out-of-tree release available from 01.org. The driver exposes complete cryptography and data compression API in the kernel and integrates with Open Crypto Framework. Details of supported operations, devices and usage can be found in man and on 01.org. Patch co-authored by: Krzysztof Zdziarski <krzysztofx.zdziarski@intel.com> Patch co-authored by: Michal Jaraczewski <michalx.jaraczewski@intel.com> Patch co-authored by: Michal Gulbicki <michalx.gulbicki@intel.com> Patch co-authored by: Julian Grajkowski <julianx.grajkowski@intel.com> Patch co-authored by: Piotr Kasierski <piotrx.kasierski@intel.com> Patch co-authored by: Adam Czupryna <adamx.czupryna@intel.com> Patch co-authored by: Konrad Zelazny <konradx.zelazny@intel.com> Patch co-authored by: Katarzyna Rucinska <katarzynax.kargol@intel.com> Patch co-authored by: Lukasz Kolodzinski <lukaszx.kolodzinski@intel.com> Patch co-authored by: Zbigniew Jedlinski <zbigniewx.jedlinski@intel.com> Reviewed by: markj, jhb (OCF integration) Reviewed by: debdrup, pauamma (docs) Sponsored by: Intel Corporation Differential Revision: https://reviews.freebsd.org/D34632
* qat: Rename to qat_c2xxx and remove support for modern chipsetsMark Johnston2022-07-272-19/+11
| | | | | | | | | | A replacement QAT driver will be imported, but this replacement does not support Atom C2xxx hardware. So, the existing driver will be kept around to provide opencrypto offload support for those chipsets. Reviewed by: pauamma, emaste Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D35817
* vt.4: Provide a hint about Fn + K Scroll Lock combinationEd Maste2022-07-211-1/+3
| | | | | | | | | Many laptops do not have Scroll Lock and use a function key sequence to access it. MFC after: 1 week Sponsored by: The FreeBSD Foundation
* tcp.4: Sort sysctl variablesMike Karels2022-07-201-304/+321
| | | | | | | | | | | | | | In preparation for updates including missing variables, sort the sysctl variables in the MIB variables section alphabetically. Add a new "hostcache" entry for the hostcache node, containing the intro text that was previously in hostcache.enable. Also cleanups per review comments. Reviewed by: transport(tuexen), manpages(bcr) Differential Revision: https://reviews.freebsd.org/D35844 MFC after: 1 week (cherry picked from commit 5cf709ce72c0b6eb4b4d57db015a65f8a84166d5)
* icmp.4 inet.4 udp.4: sort sysctl variablesMike Karels2022-07-203-122/+122
| | | | | | | | | | | | | Sort the sysctl(3)/sysctl(8) variables in the MIB Variables section alphabetically. This is in preparation for adding missing variables (at least in inet.4 and icmp.4). A few other touchups suggested in review. Reviewed by: bcr Differential Revision: https://reviews.freebsd.org/D35843 MFC after: 1 week (cherry picked from commit 3b656d465127de066511b6ffd02fb9fef85c7a53)
* mac: add new mac_ddb(4) policyMitchell Horne2022-07-1812-2/+122
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Generally, access to the kernel debugger is considered to be unsafe from a security perspective since it presents an unrestricted interface to inspect or modify the system state, including sensitive data such as signing keys. However, having some access to debugger functionality on production systems may be useful in determining the cause of a panic or hang. Therefore, it is desirable to have an optional policy which allows limited use of ddb(4) while disabling the functionality which could reveal system secrets. This loadable MAC module allows for the use of some ddb(4) commands while preventing the execution of others. The commands have been broadly grouped into three categories: - Those which are 'safe' and will not emit sensitive data (e.g. trace). Generally, these commands are deterministic and don't accept arguments. - Those which are definitively unsafe (e.g. examine <addr>, search <addr> <value>) - Commands which may be safe to execute depending on the arguments provided (e.g. show thread <addr>). Safe commands have been flagged as such with the DB_CMD_MEMSAFE flag. Commands requiring extra validation can provide a function to do so. For example, 'show thread <addr>' can be used as long as addr can be checked against the system's list of process structures. The policy also prevents debugger backends other than ddb(4) from executing, for example gdb(4). Reviewed by: markj, pauamma_gundo.com (manpages) Sponsored by: Juniper Networks, Inc. Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D35371
* inet.4 tcp.4 udp.4: update date, fix typoMike Karels2022-07-143-4/+4
| | | | Update .Dd for man pages pushed yesterday; fix typo in inet.4.
* inet.4 tcp.4 udp.4: Replace *CTL_* OID macro names with sysctl namesMike Karels2022-07-143-50/+41
| | | | | | | | | | | | | | | | | Older sysctls with constant OID macros were identified with those in inet.4, tcp.4, and udp.4; newer sysctls with automatic numbering were identified by sysctl names. No one remembers the OID macros, or knows what they are; sysctls are always done by name now, usually via sysctl(8). Replace the OID macro names with sysctl names so that there is one uniform identifier type; sysctl names were previously in parens. Make the formatting a little more consistent in this area. In inet.4 and udp.4, move the "ip." or "udp." prefix from each entry into the top-level name at the start of the section, as they are all the same. Reviewed by: rpokala Differential Revision: https://reviews.freebsd.org/D35806
* IPv4: experimental changes to allow net 0/8, 240/4, part of 127/8Mike Karels2022-07-131-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Combined changes to allow experimentation with net 0/8 (network 0), 240/4 (Experimental/"Class E"), and part of the loopback net 127/8 (all but 127.0/16). All changes are disabled by default, and can be enabled by the following sysctls: net.inet.ip.allow_net0=1 net.inet.ip.allow_net240=1 net.inet.ip.loopback_prefixlen=16 When enabled, the corresponding addresses can be used as normal unicast IP addresses, both as endpoints and when forwarding. Add descriptions of the new sysctls to inet.4. Add <machine/param.h> to vnet.h, as CACHE_LINE_SIZE is undefined in various C files when in.h includes vnet.h. The proposals motivating this experimentation can be found in https://datatracker.ietf.org/doc/draft-schoen-intarea-unicast-0 https://datatracker.ietf.org/doc/draft-schoen-intarea-unicast-240 https://datatracker.ietf.org/doc/draft-schoen-intarea-unicast-127 Reviewed by: rgrimes, pauamma_gundo.com; previous versions melifaro, glebius Differential Revision: https://reviews.freebsd.org/D35741
* Revert "rtw88: split driver up into a core and pci part"Bjoern A. Zeeb2022-07-011-2/+2
| | | | | | | | | | | | | | | | | | After some discussion, for now, simply revert the change to split the driver up into if_rtw88_core.ko and if_rtw88_pci.ko as we do not have an if_rtw88.ko anymore. We do have code trying to auto-load modules, e.g. ifconfig, based on if_xxx.ko. We could, based on Makefile magic or further code, generate a if_rtw88.ko module with proper dependencies and keep this but for simplicity stay with the one slightly larger module for now. Should code appear to do this "properly" we can revisit this once USB support has landed. Slightly update the module Makefile to keep the separation of files between core and pci bits visible and maintainable for the future. This reverts commit 0f7b9777f8f39fbc230b3e1de2f844d9f839adea.
* tslog.4: Document what TSLOG excels atMateusz Piotrowski2022-07-011-2/+4
| | | | | | | | Based on an email mhorne@ sent to arch@. Reviewed by: debdrup, pauamma_gundo.com MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D34565
* boottrace.4: Document that boottrace is good at tracing one-shot eventsMateusz Piotrowski2022-07-011-2/+3
| | | | | | | Based on an email mhorne@ sent to arch@. Reviewed by: debdrup Differential Revision: https://reviews.freebsd.org/D34566
* ena: Remove TSO refs from the documentationMichal Krawczyk2022-06-301-5/+0
| | | | | | | | | | | The Hardware currently doesn't support TSO feature and it can be misleading to mention that in the docs. All references to the docs were removed from the man pages. Obtained from: Semihalf MFC after: 2 weeks Sponsored by: Amazon, Inc.
* Remove "All Rights Reserved" from Foundation copyrightsEd Maste2022-06-3012-12/+0
| | | | | | | on man pages. MFC after: 1 week Sponsored by: The FreeBSD Foundation
* ovpn: Introduce OpenVPN DCO supportKristof Provost2022-06-282-0/+55
| | | | | | | | | | | | | | OpenVPN Data Channel Offload (DCO) moves OpenVPN data plane processing (i.e. tunneling and cryptography) into the kernel, rather than using tap devices. This avoids significant copying and context switching overhead between kernel and user space and improves OpenVPN throughput. In my test setup throughput improved from around 660Mbit/s to around 2Gbit/s. Sponsored by: Rubicon Communications, LLC ("Netgate") Differential Revision: https://reviews.freebsd.org/D34340
* unix/dgram: smart socket buffers for one-to-many socketsGleb Smirnoff2022-06-241-2/+59
| | | | | | | | | | | | | | | | | | | A one-to-many unix/dgram socket is a socket that has been bound with bind(2) and can get multiple connections. A typical example is /var/run/log bound by syslogd(8) and receiving multiple connections from libc syslog(3) API. Until now all of these connections shared the same receive socket buffer of the bound socket. This made the socket vulnerable to overflow attack. See 240d5a9b1ce for a historical attempt to workaround the problem. This commit creates a per-connection socket buffer for every single connected socket and eliminates the problem. The new behavior will optimize seldom writers over frequent writers. See added test case scenarios and code comments for more detailed description of the new behavior. Reviewed by: markj Differential revision: https://reviews.freebsd.org/D35303
* Drop atheros dead link from uath manual pageSergio Carlavilla Delgado2022-06-241-3/+0
| | | | | PR: 264256 MFC after: 2 weeks
* Retire snd_sbc ISA sound card driverEd Maste2022-06-213-145/+0
| | | | | | | | | | | | | | | | | | | | | | | | Along with the snd_sb8 and snd_sb16 drivers. They supported ISA Creative Sound Blaster and compatible sound cards. Note that isa/sb.h is not removed, as it is still used by some PCI sound card drivers. ISA sound card drivers are deprecated as discussed on the current[1] and stable[2] mailing lists. Deprecation notices were added in e39ec8933be4 and MFCd to stable branches. Driver removals are being committed individually so that specific drivers can be restored if necessary (either in FreeBSD or by downstream projects). [1] https://lists.freebsd.org/archives/freebsd-current/2022-March/001680.html [2] https://lists.freebsd.org/archives/freebsd-stable/2022-March/000585.html Reviewed by: mav Relnotes: Yes Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D34671
* Retire snd_mss ISA sound card driverEd Maste2022-06-213-123/+0
| | | | | | | | | | | | | | | | | | | | The snd_mss driver supported Microsoft Sound System sound cards. ISA sound card drivers are deprecated as discussed on the current[1] and stable[2] mailing lists. Deprecation notices were added in e39ec8933be4 and MFCd to stable branches. Driver removals are being committed individually so that specific drivers can be restored if necessary (either in FreeBSD or by downstream projects). [1] https://lists.freebsd.org/archives/freebsd-current/2022-March/001680.html [2] https://lists.freebsd.org/archives/freebsd-stable/2022-March/000585.html Reviewed by: mav Relnotes: yes Sponsored by: The FreeBSD Foundation Differential Revision: Thttps://reviews.freebsd.org/D34671
* Retire snd_gusc ISA sound card driverEd Maste2022-06-213-104/+0
| | | | | | | | | | | | | | | | | | | | | snd_gusc supported the Gravis UltraSound MAX and UltraSound PnP sound cards. ISA sound card drivers are deprecated as discussed on the current[1] and stable[2] mailing lists. Deprecation notices were added in e39ec8933be4 and MFCd to stable branches. Driver removals are being committed individually so that specific drivers can be restored if necessary (either in FreeBSD or by downstream projects). [1] https://lists.freebsd.org/archives/freebsd-current/2022-March/001680.html [2] https://lists.freebsd.org/archives/freebsd-stable/2022-March/000585.html Reviewed by: mav Relnotes: Yes Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D34671
* Retire snd_ess ISA sound card driverEd Maste2022-06-213-79/+0
| | | | | | | | | | | | | | | | | | | | snd_ess supported sound cards using the ESS 18xx chipset. ISA sound card drivers are deprecated as discussed on the current[1] and stable[2] mailing lists. Deprecation notices were added in e39ec8933be4 and MFCd to stable branches. Driver removals are being committed individually so that specific drivers can be restored if necessary (either in FreeBSD or by downstream projects). [1] https://lists.freebsd.org/archives/freebsd-current/2022-March/001680.html [2] https://lists.freebsd.org/archives/freebsd-stable/2022-March/000585.html Reviewed by: mav Relnotes: Yes Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D34671
* Retire snd_ad1816 ISA sound card driverEd Maste2022-06-213-88/+0
| | | | | | | | | | | | | | | | | | | | | snd_ad1816 supported ISA sound cards based on the Analog Devices AD1816A "SoundPort® Controller". ISA sound card drivers are deprecated as discussed on the current[1] and stable[2] mailing lists. Deprecation notices were added in e39ec8933be4 and MFCd to stable branches. Driver removals are being committed individually so that specific drivers can be restored if necessary (either in FreeBSD or by downstream projects). [1] https://lists.freebsd.org/archives/freebsd-current/2022-March/001680.html [2] https://lists.freebsd.org/archives/freebsd-stable/2022-March/000585.html Reviewed by: mav Relnotes: Yes Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D34671
* mixer: remove volume backwards compat, add % interpretationKyle Evans2022-06-181-1/+1
| | | | | | | | | | | | | | | | The current situation is fairly confusing, where an integer is interpreted as a percent until you slap a decimal on it and magically it becomes an absolute value. Let's have a flag day in 14.0 and remove this shim entirely. Setting with percent can still be useful, so allow a trailing '%' to indicate as such. As a side effect, we tighten down the format allowed in the volume a little bit by ensuring there's no trailing garbage after the value once it's separated into left and right components. Reviewed by: christos, hselasky, pauamma_gundo.com (manpages) Relnotes: yes Differential Revision: https://reviews.freebsd.org/D35101
* rtw88: split driver up into a core and pci partBjoern A. Zeeb2022-06-121-2/+2
| | | | | | | | | | | | | | Split the driver up into two modules (if_rtw88_pci.ko and rtw88_core.ko). This is in preparation for the hopefully eventually upcoming USB support using the same driver core. Note: this changes the module name to load to if_rtw88_pci.ko instead of if_rtw88.ko. If using devmatch(8) everything should stay the same as the driver name (used for net.wlan.devices) stays rtw88. If using kld_list in rc.conf or loader.conf you will need to adjust the name. Update man page for this. MFC after: 3 days