#
13d00a43 |
| 20-Jun-2024 |
Emmanuel Vadot <manu@FreeBSD.org> |
conf: Add usbhid and hidbus to GENERIC* kernel configs
Include the new unified HID stack by default in generic. This will allow us to migrate to the multi-stack hkbd and hms instead of relying on th
conf: Add usbhid and hidbus to GENERIC* kernel configs
Include the new unified HID stack by default in generic. This will allow us to migrate to the multi-stack hkbd and hms instead of relying on the older ukbd and ums which only work with USB. To test those drivers just add hw.usb.usbhid.enable=1 in loader.conf
Differential Revision: https://reviews.freebsd.org/D45658 Reviewed by: emaste, imp, wulf (all older version) Sponsored by: Beckhoff Automation GmbH & Co. KG
show more ...
|
Revision tags: release/14.1.0 |
|
#
8a8daeaf |
| 23-Apr-2024 |
Lexi Winter <lexi@le-Fay.ORG> |
sys/*/conf: do not use "../../conf/" when including std.*
Since config(8) searches sys/conf by default, there's no need to specify the full relative path here; replace it by the filename alone.
Rev
sys/*/conf: do not use "../../conf/" when including std.*
Since config(8) searches sys/conf by default, there's no need to specify the full relative path here; replace it by the filename alone.
Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/1124
show more ...
|
#
4f8f9d70 |
| 23-Apr-2024 |
Lexi Winter <lexi@le-Fay.ORG> |
sys: add conf/std.debug, generic debugging options
The new sys/conf/std.debug contains the list of debugging options enabled by default in -CURRENT, so they don't need to be listed individually in e
sys: add conf/std.debug, generic debugging options
The new sys/conf/std.debug contains the list of debugging options enabled by default in -CURRENT, so they don't need to be listed individually in every kernel config.
The enabled options are the set of all debug options which were enabled for the GENERIC kernel on any platform. This means some architectures now have debugging options enabled in GENERIC which weren't previously enabled:
- amd64: [1] - arm64: [2] - arm: [2]. [3] - i386: [1], [2] - powerpc: [1], [2], [3] - riscv: [2]
[1] ALT_BREAK_TO_DEBUGGER is now enabled. [2] BUF_TRACKING, FULL_BUF_TRACKING, and QUEUE_MACRO_DEBUG_TRASH are now enabled. [3] DEADLKRES is now enabled.
While here, move the documentation for the (commented out) K*SAN options for amd64 from GENERIC to NOTES.
Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/1124
show more ...
|
#
e045163c |
| 14-Apr-2024 |
John Baldwin <jhb@FreeBSD.org> |
i386: Use DEV_HYPERV to enable HyperV APIC vector
This avoids requiring both 'device hyperv' and 'options HYPERV' for kernel configs. Instead, just 'device hyperv' can now be used matching the kern
i386: Use DEV_HYPERV to enable HyperV APIC vector
This avoids requiring both 'device hyperv' and 'options HYPERV' for kernel configs. Instead, just 'device hyperv' can now be used matching the kernel configuration used for amd64.
Reviewed by: imp Differential Revision: https://reviews.freebsd.org/D44783
show more ...
|
Revision tags: release/13.3.0 |
|
#
89c1e54a |
| 18-Feb-2024 |
Bjoern A. Zeeb <bz@FreeBSD.org> |
ath(4): always enable 11n
Enabling 11n for ath(4) so far was handled by a kernel option, which was only enabled for certain kernel configurations. In order to allow loading ath(4) as a module with 1
ath(4): always enable 11n
Enabling 11n for ath(4) so far was handled by a kernel option, which was only enabled for certain kernel configurations. In order to allow loading ath(4) as a module with 11n support on all platforms, remove the kernel option and unconditionally enable 11n in ath(4).
Reported by: pkubaj Discussed with: adrian in D43549. Reviewed by: adrian, imp Differential Revision: https://reviews.freebsd.org/D43964
show more ...
|
Revision tags: release/14.0.0 |
|
#
84d12f88 |
| 06-Oct-2023 |
Kristof Provost <kp@FreeBSD.org> |
Add a COMPAT_FREEBSD14 kernel option
Use it wherever COMPAT_FREEBSD13 is currently specified.
Reviewed by: brooks, zlei Sponsored by: Rubicon Communications, LLC ("Netgate") Differential Revision:
Add a COMPAT_FREEBSD14 kernel option
Use it wherever COMPAT_FREEBSD13 is currently specified.
Reviewed by: brooks, zlei Sponsored by: Rubicon Communications, LLC ("Netgate") Differential Revision: https://reviews.freebsd.org/D42100
show more ...
|
#
031beb4e |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
sys: Remove $FreeBSD$: one-line sh pattern
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
|
#
a51f81c2 |
| 07-Aug-2023 |
Ed Maste <emaste@FreeBSD.org> |
x86: move EARLY_AP_STARTUP into DEFAULTS
EARLY_AP_STARTUP was introduced in 2016 (commit fdce57a04219) with note:
As a transition aid, the new behavior is moved under a new kernel option (E
x86: move EARLY_AP_STARTUP into DEFAULTS
EARLY_AP_STARTUP was introduced in 2016 (commit fdce57a04219) with note:
As a transition aid, the new behavior is moved under a new kernel option (EARLY_AP_STARTUP). This will allow the option to be turned off if need be during initial testing. I hope to enable this on x86 by default in a followup commit ...
It was enabled by default, but became effectively mandatory (on x86) some time later. Move it to DEFAULTS to avoid an unbootable system if the option is left out of a custom kernel configuration file.
Reported by: wollman Reviewed by: jhb Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D41352
show more ...
|
#
37c8ee88 |
| 07-Aug-2023 |
Marius Strobl <marius@FreeBSD.org> |
ath(4): Remove MIPS AHB frontend and join PCI one w/ main support again
Following the removal of general MIPS support, there's no longer a need to have the AHB bus-frontend in place, which according
ath(4): Remove MIPS AHB frontend and join PCI one w/ main support again
Following the removal of general MIPS support, there's no longer a need to have the AHB bus-frontend in place, which according to Linux sources also isn't used with any non-MIPS SoCs. For simplicity, PCI bus support is only made conditional on the main one again, i. e. device ath_pci is removed, and built into the main module, i. e. if_ath_pci.ko obsoleted, respectively. Effectively, this reverts the following commits and associated changes: dba9c8597747c6c9bf3d2ec68f7eb90552878dc7 e849bb3ecbb1963344a22ae77fc96f89fbebf40c
Approved by: adrian Relnotes: yes Differential Revision: https://reviews.freebsd.org/D41354
show more ...
|
#
fec74220 |
| 11-May-2023 |
Li-Wen Hsu <lwhsu@FreeBSD.org> |
Complete removing twe(4)
Fixes: 062a7b918fac twe: Remove driver
|
#
95e4f5ef |
| 25-Apr-2023 |
Mateusz Guzik <mjg@FreeBSD.org> |
x86: whack pmspcv from GENERIC
The driver is enormous and rarely used.
text data bss dec hex filename 23076646 1870505 4415872 29363023 0x1c00b4f kerne
x86: whack pmspcv from GENERIC
The driver is enormous and rarely used.
text data bss dec hex filename 23076646 1870505 4415872 29363023 0x1c00b4f kernel.before 20017433 1870305 4416000 26303738 0x1915cfa kernel.after
People using the driver will need to add pmspcv_load="YES" to their loader.conf.
Reviewed by: jhb Relnotes: yes Sponsored by: Rubicon Communications, LLC ("Netgate") Differential Revision: https://reviews.freebsd.org/D39816
show more ...
|
#
71883128 |
| 13-Apr-2023 |
Henri Hennebert <hlh@restart.be> |
rtsx: Add plug-and-play info
Add MODULE_PNP_INFO() to the driver to make it autoload if not linked statically into the kernel. Remove the device from amd64/i386 GENERIC.
Reviewed by: imp Differenti
rtsx: Add plug-and-play info
Add MODULE_PNP_INFO() to the driver to make it autoload if not linked statically into the kernel. Remove the device from amd64/i386 GENERIC.
Reviewed by: imp Differential Revision: https://reviews.freebsd.org/D35074
show more ...
|
Revision tags: release/13.2.0 |
|
#
3091d980 |
| 02-Apr-2023 |
Alexander V. Chernikov <melifaro@FreeBSD.org> |
netlink: add NETLINK to the DEFAULTS for each architecture
NETLINK is going to replace rtsock and a number of other ioctl/sysctl interfaces. In-base utilies such as route(8), netstat(8) and soon ifc
netlink: add NETLINK to the DEFAULTS for each architecture
NETLINK is going to replace rtsock and a number of other ioctl/sysctl interfaces. In-base utilies such as route(8), netstat(8) and soon ifconfig(8) are being converted to use netlink sockets as a transport between kernel and userland. In the current configuration, it still possible have the kernel without NETLINK (`nooptions NETLINK`) and use the aforementioned utilies by buidling the world with `WITHOUT_NETLINK` src.conf knob. However, this approach does not cover the cases when person unintentionally builds a custom kernel without netlink and tries to use the standard userland.
This change adds `option NETLINK` to the default options for each architecture, fixing the custom kernel issue. For arm, this change uses `std.armv6` and `std.armv7` (netlink already in) instead of DEFAULTS.
Reviewed By: imp Differential Revision: https://reviews.freebsd.org/D39339
show more ...
|
#
d44acf5d |
| 23-Feb-2023 |
Mike Karels <karels@FreeBSD.org> |
i386 kernel config: clean up whitespace
Most options in kernel config files use "options<space><tab>OPTION". This allows the option to be commented out without shifting columns. A few options had tw
i386 kernel config: clean up whitespace
Most options in kernel config files use "options<space><tab>OPTION". This allows the option to be commented out without shifting columns. A few options had two tabs, and some had spaces. Make them consistent.
show more ...
|
#
e80699a8 |
| 31-Jan-2023 |
Alexander V. Chernikov <melifaro@FreeBSD.org> |
netlink: add NETLINK to GENERIC.
This is a followup of 692e19cf5195 (add netlink to GENERIC@amd64).
Netlink is a communication protocol defined in RFC 3549. It is async, TLV-based protocol, providi
netlink: add NETLINK to GENERIC.
This is a followup of 692e19cf5195 (add netlink to GENERIC@amd64).
Netlink is a communication protocol defined in RFC 3549. It is async, TLV-based protocol, providing 1-1 and 1-many communications between kernel and userland. Netlink is currently used in Linux kernel to modify, read and subscribe for nearly all networking states. Interface state, addresses, routes, firewall, rules, fibs, etc, are controlled via Netlink.
Netlink support was added in D36002. It has got a number of improvements and first customers since then: * net/bird2 got netlink support, enabling route multipath in FreeBSD * netlink-based devd notifications are being worked on ( D37574 ). * linux(4) fully supports and depends on Netlink
Enabling Netlink in GENERIC targets two goals. The first one is to provide stability for the third-party userland applications, so they can rely on the fact that netlink always exists since 14.0 and potentially 13.2. Loadable module makes life of the app delepers harder. For example, `net/bird2` can be either build with netlink or rtsock support, but not both.
The second goal is to enable gradual conversion of the base userland tools to use netlink(4) interfaces. Converting tools like netstat (D36529), route, ifconfig one-by-one simplifies testing and addressing the feedback. Othewise, switching all base to use netlink at once may be too big of a leap.
MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D37783
show more ...
|
Revision tags: release/12.4.0, release/13.1.0 |
|
#
b4fba31b |
| 14-Dec-2021 |
Warner Losh <imp@FreeBSD.org> |
Remove references to PCMCIA
Remove more references to PCMCIA in kernel config files. We no longer support PC Card devices.
Sponsored by: Netflix
|
Revision tags: release/12.3.0 |
|
#
28dcccc1 |
| 28-Nov-2021 |
Ed Maste <emaste@FreeBSD.org> |
x86 GENERIC/MINIMAL: group sc(4) devices together
The vga and splash devices are part of the sc(4) system console. vt(4) uses the vt_vga driver instead, and has some limited splash support directly
x86 GENERIC/MINIMAL: group sc(4) devices together
The vga and splash devices are part of the sc(4) system console. vt(4) uses the vt_vga driver instead, and has some limited splash support directly in vt_core.c. Leave the sc(4) options in GENERIC/MINIMAL (for now) but group them together under an sc(4) comment.
Sponsored by: The FreeBSD Foundation
show more ...
|
#
b8cf1c5c |
| 27-Nov-2021 |
Ed Maste <emaste@FreeBSD.org> |
Remove options VESA from x86 GENERIC
options VESA / vesa.ko provides VESA Bios Extensions (VBE) support for the legacy sc(4) console. It is not used by the default console, vt(4).
There is a repor
Remove options VESA from x86 GENERIC
options VESA / vesa.ko provides VESA Bios Extensions (VBE) support for the legacy sc(4) console. It is not used by the default console, vt(4).
There is a report[1] of an incompatibility between VESA and the Nvidia driver breaking suspend/resume. Since VESA is not used by the default configuration anyway, just remove options VESA from GENERIC. The kernel module is still available and may be loaded by sc(4) users who want to select a VBE mode.
(Note that vt(4) does not support selecting a VBE mode. The loader can set a VBE mode and vt(4) will use it via the vt_vbefb driver.)
[1] https://lists.freebsd.org/archives/freebsd-hackers/2021-November/000469.html
PR: 253733 Reported by: Stefan Blachmann [1] Reviewed by: imp, manu, tsoome Relnotes: Yes Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D33141
show more ...
|
#
228e020a |
| 27-Nov-2021 |
Ed Maste <emaste@FreeBSD.org> |
Correct syscons description in i386 and amd64 configs
Commit 2d6f6d63733d switched to vt(4) as the default console.
Sponsored by: The FreeBSD Foundation
|
#
8722e05a |
| 25-Nov-2021 |
Warner Losh <imp@FreeBSD.org> |
twa: Remove
Belatedly remove twa(4). It was supposed to go before 13.0, but was overlooked.
Sponsored by: Netflix Relnotes: yes Reviewed by: scottl Differential Revision: https://reviews.freebsd
twa: Remove
Belatedly remove twa(4). It was supposed to go before 13.0, but was overlooked.
Sponsored by: Netflix Relnotes: yes Reviewed by: scottl Differential Revision: https://reviews.freebsd.org/D33114
show more ...
|
#
0d5935af |
| 25-Nov-2021 |
Warner Losh <imp@FreeBSD.org> |
esp: Remove
Belatedly remove esp(4). It was tagged as gone in 13, but was overlooked until now.
Sponsored by: Netflix Reviewed by: scottl Differential Revision: https://reviews.freebsd.org/D33115
|
#
60de2867 |
| 25-Nov-2021 |
Warner Losh <imp@FreeBSD.org> |
amr: remove
Belatedly remove amr(4). It was slated to depart before 13.0 but was overlooked until now.
Sponsored by: Netflix Relnotes: yes Reviewed by: scottl Differential Revision: https://revi
amr: remove
Belatedly remove amr(4). It was slated to depart before 13.0 but was overlooked until now.
Sponsored by: Netflix Relnotes: yes Reviewed by: scottl Differential Revision: https://reviews.freebsd.org/D33113
show more ...
|
#
399188a2 |
| 25-Nov-2021 |
Warner Losh <imp@FreeBSD.org> |
iir: Remove
Belatedly remove iir(4). It was slated to go before 13, but was overlooked.
Sponsored by: Netflix Relnotes: yes Reviewed by: scottl Differential Revision: https://reviews.freebsd.org
iir: Remove
Belatedly remove iir(4). It was slated to go before 13, but was overlooked.
Sponsored by: Netflix Relnotes: yes Reviewed by: scottl Differential Revision: https://reviews.freebsd.org/D33112
show more ...
|
#
a9620045 |
| 25-Nov-2021 |
Warner Losh <imp@FreeBSD.org> |
mly: Remove.
We'd said this was going away in 13, but was overlooked. Belatedly remove.
Sponsored by: Netflix Relnotes: yes Reviewed by: scottl Differential Revision: https://reviews.freebsd.org
mly: Remove.
We'd said this was going away in 13, but was overlooked. Belatedly remove.
Sponsored by: Netflix Relnotes: yes Reviewed by: scottl Differential Revision: https://reviews.freebsd.org/D33111
show more ...
|
#
4e85b648 |
| 15-Nov-2021 |
Kristof Provost <kp@FreeBSD.org> |
Add a COMPAT_FREEBSD13 kernel option
Use it wherever COMPAT_FREEBSD11 is currently specified.
Reviewed by: jhb (previous version) Sponsored by: Rubicon Communications, LLC ("Netgate") Differential
Add a COMPAT_FREEBSD13 kernel option
Use it wherever COMPAT_FREEBSD11 is currently specified.
Reviewed by: jhb (previous version) Sponsored by: Rubicon Communications, LLC ("Netgate") Differential Revision: https://reviews.freebsd.org/D33005
show more ...
|