Revision tags: release/13.1.0 |
|
#
c227269e |
| 07-Feb-2022 |
John Baldwin <jhb@FreeBSD.org> |
Stop adding -Wredundant-decls to CWARNFLAGS.
clang doesn't implement it, and Linux doesn't enforce it. As a result, new instances keep cropping up both in FreeBSD's code and in upstream sources fro
Stop adding -Wredundant-decls to CWARNFLAGS.
clang doesn't implement it, and Linux doesn't enforce it. As a result, new instances keep cropping up both in FreeBSD's code and in upstream sources from vendors.
Reviewed by: emaste Differential Revision: https://reviews.freebsd.org/D34144
show more ...
|
Revision tags: release/12.3.0 |
|
#
1961a14a |
| 04-Nov-2021 |
Emmanuel Vadot <manu@FreeBSD.org> |
linuxkpi: Add i2c support
Add i2c support to linuxkpi. This is needed by drm-kmod. For every i2c_adapter added by i2c_add_adapter we add a child to the device named "lkpi_iic". This child handle the
linuxkpi: Add i2c support
Add i2c support to linuxkpi. This is needed by drm-kmod. For every i2c_adapter added by i2c_add_adapter we add a child to the device named "lkpi_iic". This child handle the conversion between Linux i2c_msgs to FreeBSD iic_msgs. For every i2c_adapter added by i2c_bit_add_bus we add a child to the device named "lkpi_iicbb". This child handle the conversion between Linux i2c_msgs to FreeBSD iic_msgs. With the help of iic(4), this expose the i2c controller to userspace allowing a user to query DDC information from a monitor. e.g.: i2c -f /dev/iic0 -a 0x28 -c 128 -d r will query the standard EDID from the monitor if plugged.
The bitbang part (lkpi_iicbb) isn't tested at all for now as I don't have compatible hardware (all my hardware have native i2c controller).
Tested on: Intel (SandyBridge, Skylake, ApolloLake) Tested on: AMD (Picasso, Polaris (amd64 and arm64))
MFC after: 1 month Reviewed by: hselasky Sponsored by: Beckhoff Automation GmbH & Co. KG Differential Revision: https://reviews.freebsd.org/D33053
show more ...
|
#
2754373f |
| 11-Jan-2022 |
Andrew Turner <andrew@FreeBSD.org> |
Use ${MACHINE} for the kernel modeule ldscript
For consistancy with the kernel linker script also use ${MACHINE} for finding the kernel module linker script. As we currently only use this for amd64
Use ${MACHINE} for the kernel modeule ldscript
For consistancy with the kernel linker script also use ${MACHINE} for finding the kernel module linker script. As we currently only use this for amd64 and i386 this is a no-op, but I'm planning on using this with arm64 where ${MACHINE} != ${MACHINE_ARCH}.
Reviewed by: markj, kib, imp Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D33841
show more ...
|
#
c09981f1 |
| 31-Dec-2021 |
Warner Losh <imp@FreeBSD.org> |
mips: Remove sys/mips
Remove sys/mips as the next step of decomissioning mips from the tree. Remove mips special cases from the kernel make files. Remove the mips specific linker scripts.
Sponsored
mips: Remove sys/mips
Remove sys/mips as the next step of decomissioning mips from the tree. Remove mips special cases from the kernel make files. Remove the mips specific linker scripts.
Sponsored by: Netflix
show more ...
|
#
e8dca53a |
| 02-Jun-2021 |
Warner Losh <imp@FreeBSD.org> |
kmod.mk: Allow extra objects to be specified in modules
OBJS are automatically added to CLEANFILES. For pre-built objects, this is not desirable since it will delete the object from the source tree.
kmod.mk: Allow extra objects to be specified in modules
OBJS are automatically added to CLEANFILES. For pre-built objects, this is not desirable since it will delete the object from the source tree. Introduce EXTRA_OBJS which list these object files, but aren't added to clean files.
Sponsored by: Netflix Reviewed by: emaste@ Differential Revision: https://reviews.freebsd.org/D30615
show more ...
|
Revision tags: release/13.0.0 |
|
#
bcb7f57a |
| 27-Jan-2021 |
Mateusz Guzik <mjg@FreeBSD.org> |
conf/kern.mk: save some work by using realpath instead of cd ; pwd
I did not check if the entire ordeal can be avoided in the first place.
|
#
594389d1 |
| 12-Jan-2021 |
Andrew Turner <andrew@FreeBSD.org> |
Create a stack frame when needed in the arm64 kernel
When building the arm64 kernel for use with dtrace or hwpmc we need to include a stack frame so they can extract a stack trace.
As with amd64 al
Create a stack frame when needed in the arm64 kernel
When building the arm64 kernel for use with dtrace or hwpmc we need to include a stack frame so they can extract a stack trace.
As with amd64 also build a stack frame in modules.
Sponsored by: Innovate UK
show more ...
|
#
de27805f |
| 04-Jan-2021 |
Konstantin Belousov <kib@FreeBSD.org> |
linuxkpi: handle ARI
Stop trying to manually calculate RID, which cannot be done correctly by PCI_DEVFN(). Use PCI_GET_RID() method instead.
Do not use pci_find_dbsf() to go from the linux pci_dev
linuxkpi: handle ARI
Stop trying to manually calculate RID, which cannot be done correctly by PCI_DEVFN(). Use PCI_GET_RID() method instead.
Do not use pci_find_dbsf() to go from the linux pci_dev to freebsd device_t. First, device is readily available as dev.bsddev. Second, using pci_find_dbsf() fails for ARI-enabled functions with large function numbers, because PCI_SLOT()/PCI_FUNC() are for non-ARI.
Reviewed by: bz, hselasky, manu Tested by: manu (drm) Sponsored by: Mellanox Technologies/NVidia Networking MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D27960
show more ...
|
#
d021434a |
| 27-Dec-2020 |
Ryan Libby <rlibby@FreeBSD.org> |
openzfs: fix gcc kernel module builds
- Suppress -Wredundant-decls. Ultimately this warning is harmless in any case, and it does not look like there is a simple way to avoid redundant declar
openzfs: fix gcc kernel module builds
- Suppress -Wredundant-decls. Ultimately this warning is harmless in any case, and it does not look like there is a simple way to avoid redundant declarations in this case without a lot of header pollution (e.g. having openzfs's shim param.h pulling in sys/kernel.h for hz). - Suppress -Wnested-externs, which is useless anyway.
Unfortunately it was not sufficient just to modify OPENZFS_CFLAGS, because the warning suppressions need to appear on the command line after they are explicitly enabled by CWARNFLAGS from sys/conf/kern.mk, but OPENZFS_CFLAGS get added before due to use of -I for the shims.
Reviewed by: markj Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D27685
show more ...
|
#
a0953903 |
| 17-Dec-2020 |
John Baldwin <jhb@FreeBSD.org> |
Use a template assembly file for firmware object files.
Similar to r366897, this uses the .incbin directive to pull in a firmware file's contents into a .fwo file. The same scheme for computing sym
Use a template assembly file for firmware object files.
Similar to r366897, this uses the .incbin directive to pull in a firmware file's contents into a .fwo file. The same scheme for computing symbol names from the filename is used as before to maximize compatiblity and not require rebuilding existing .fwo files for NO_CLEAN builds. Using ld -o binary requires extra hacks in linkers to either specify ABI options (e.g. soft- vs hard-float) or to ignore ABI incompatiblities when linking certain objects (e.g. object files with only data). Using the compiler driver avoids the need for these hacks as the compiler driver is able to set all the appropriate ABI options.
Reviewed by: imp, markj Obtained from: CheriBSD Sponsored by: DARPA Differential Revision: https://reviews.freebsd.org/D27579
show more ...
|
Revision tags: release/12.2.0 |
|
#
40ec30d4 |
| 19-Oct-2020 |
Adrian Chadd <adrian@FreeBSD.org> |
[zfs] Remove a non-existent directory in the build infra
This directory doesn't exist and causes gcc-6.4 to complain about a non-existent include directory
Approved by: kevans, imp Differential Rev
[zfs] Remove a non-existent directory in the build infra
This directory doesn't exist and causes gcc-6.4 to complain about a non-existent include directory
Approved by: kevans, imp Differential Revision: https://reviews.freebsd.org/D26846
show more ...
|
#
2b68c973 |
| 02-Oct-2020 |
Emmanuel Vadot <manu@FreeBSD.org> |
linuxkpi: Add backlight support
Add backlight function to linuxkpi. Graphics drivers expose the backlight of the panel directly so allow them to use the backlight subsystem so user can use backlight
linuxkpi: Add backlight support
Add backlight function to linuxkpi. Graphics drivers expose the backlight of the panel directly so allow them to use the backlight subsystem so user can use backlight(8) to configure them.
Reviewed by: hselasky Relnotes: yes Differential Revision: The FreeBSD Foundation
show more ...
|
#
e2515283 |
| 27-Aug-2020 |
Glen Barber <gjb@FreeBSD.org> |
MFH
Sponsored by: Rubicon Communications, LLC (netgate.com)
|
#
9e5787d2 |
| 25-Aug-2020 |
Matt Macy <mmacy@FreeBSD.org> |
Merge OpenZFS support in to HEAD.
The primary benefit is maintaining a completely shared code base with the community allowing FreeBSD to receive new features sooner and with less effort.
I would a
Merge OpenZFS support in to HEAD.
The primary benefit is maintaining a completely shared code base with the community allowing FreeBSD to receive new features sooner and with less effort.
I would advise against doing 'zpool upgrade' or creating indispensable pools using new features until this change has had a month+ to soak.
Work on merging FreeBSD support in to what was at the time "ZFS on Linux" began in August 2018. I first publicly proposed transitioning FreeBSD to (new) OpenZFS on December 18th, 2018. FreeBSD support in OpenZFS was finally completed in December 2019. A CFT for downstreaming OpenZFS support in to FreeBSD was first issued on July 8th. All issues that were reported have been addressed or, for a couple of less critical matters there are pull requests in progress with OpenZFS. iXsystems has tested and dogfooded extensively internally. The TrueNAS 12 release is based on OpenZFS with some additional features that have not yet made it upstream.
Improvements include: project quotas, encrypted datasets, allocation classes, vectorized raidz, vectorized checksums, various command line improvements, zstd compression.
Thanks to those who have helped along the way: Ryan Moeller, Allan Jude, Zack Welch, and many others.
Sponsored by: iXsystems, Inc. Differential Revision: https://reviews.freebsd.org/D25872
show more ...
|
#
9b6edf36 |
| 23-Jun-2020 |
Conrad Meyer <cem@FreeBSD.org> |
kmod.mk: Don't split out debug symbols if requested
Ports bsd.kmod.mk explicitly sets MK_KERNEL_SYMBOLS=no to prevent auto- splitting of debuginfo from kernel modules. If that knob is set, don't sp
kmod.mk: Don't split out debug symbols if requested
Ports bsd.kmod.mk explicitly sets MK_KERNEL_SYMBOLS=no to prevent auto- splitting of debuginfo from kernel modules. If that knob is set, don't split out a .ko.debug and .ko from .ko.full; just generate a .ko with debuginfo and leave it be.
Otherwise, with DEBUG_FLAGS set and MK_KERNEL_SYMBOLS=no, we would helpfully strip out the debuginfo from the .ko.full and then not install it. That is not the desired result a WITH_DEBUG port kmod build.
Reviewed by: emaste, jhb Differential Revision: https://reviews.freebsd.org/D24835
show more ...
|
Revision tags: release/11.4.0 |
|
#
697b271d |
| 20-May-2020 |
Ed Maste <emaste@FreeBSD.org> |
pkgbase: use -dev,-dbg instead of -development,-debug
-development is long and awkward, and is also inconsistent with prior art from the Linux world, which uses -dev (Debian) or -devel (Red Hat). F
pkgbase: use -dev,-dbg instead of -development,-debug
-development is long and awkward, and is also inconsistent with prior art from the Linux world, which uses -dev (Debian) or -devel (Red Hat). Follow the Debian convention, and similarly for debug info packages.
Also remove redundant pkgbase development tag from includes. We already tag include files with package=runtime,dev; there is no need to separately tag them as dev.
Discussed with: bapt Reviewed by: manu Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D24139
show more ...
|
#
fac6dee9 |
| 12-May-2020 |
Eric van Gyzen <vangyzen@FreeBSD.org> |
Remove tests for obsolete compilers in the build system
Assume gcc is at least 6.4, the oldest xtoolchain in the ports tree. Assume clang is at least 6, which was in 11.2-RELEASE. Drop conditions f
Remove tests for obsolete compilers in the build system
Assume gcc is at least 6.4, the oldest xtoolchain in the ports tree. Assume clang is at least 6, which was in 11.2-RELEASE. Drop conditions for older compilers.
Reviewed by: imp (earlier version), emaste, jhb MFC after: 2 weeks Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D24802
show more ...
|
#
a8976aec |
| 18-Apr-2020 |
Alex Richardson <arichardson@FreeBSD.org> |
Allow kernel modules to build with a compiler that defaults to -fno-common
This uses the same approach as r359691.
Reviewed By: brooks Differential Revision: https://reviews.freebsd.org/D24405
|
#
8eb1a0ce |
| 07-Apr-2020 |
Kyle Evans <kevans@FreeBSD.org> |
Add -fno-common to all userland/kernel src builds
-fno-common will become the default in GCC10/LLVM11. Plenty of work has been put in to make sure our world builds are no -fno-common clean, so let's
Add -fno-common to all userland/kernel src builds
-fno-common will become the default in GCC10/LLVM11. Plenty of work has been put in to make sure our world builds are no -fno-common clean, so let's slap the build with this until it becomes the compiler default to ensure we don't regress.
At this time, we will not be enforcing -fno-common on ports builds. I suspect most ports will be or quickly become -fno-common clean as they're naturally built against compilers that default to it, so this will hopefully become a non-issue in due time. The exception to this, which is actually the status quo, is that kmods built from ports will continue to build with -fno-common.
As of the time of writing, I intend to also make stable/12 -fno-common clean. What's been done will be MFC'd to stable/11 if it's easily applicable and/or not much work to massage it into being functional, but I anticipate adding -fcommon to stable/11 builds to maintain its ability to be built with newer compilers for the rest of its lifetime instead of putting in a third branch's worth of effort.
show more ...
|
#
15fe2513 |
| 20-Mar-2020 |
Konstantin Belousov <kib@FreeBSD.org> |
Introduce LINUXKPI_GENSRCS.
Centralize the list of generated files required by linuxkpi consumers, into the common variable. This way, consumers that use the variable are insulated from possible ch
Introduce LINUXKPI_GENSRCS.
Centralize the list of generated files required by linuxkpi consumers, into the common variable. This way, consumers that use the variable are insulated from possible changes in the list.
Reviewed by: hselasky, imp Sponsored by: Mellanox Technologies MFC after: 1 week Differential revision: https://reviews.freebsd.org/D24137
show more ...
|
#
bb1d0df5 |
| 29-Jan-2020 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r357179 through r357269.
|
#
0c4c5948 |
| 29-Jan-2020 |
Kyle Evans <kevans@FreeBSD.org> |
kmod build: start generating opt_global.h, include it
For untied module builds, we'll generate opt_foo headers if they're included in SRCS. However, options that would normally be represented in opt
kmod build: start generating opt_global.h, include it
For untied module builds, we'll generate opt_foo headers if they're included in SRCS. However, options that would normally be represented in opt_global.h aren't properly represented.
Start generating opt_global.h with #define VIMAGE for !mips since it's almost universally a project default and right now kmods must hack it in themselves in order to be properly compiled for the default kernel. For example, ^/sys/modules/pf/Makefile
Reviewed by: imp Differential Revision: https://reviews.freebsd.org/D23345
show more ...
|
#
b1f8da38 |
| 27-Dec-2019 |
Brandon Bergren <bdragon@FreeBSD.org> |
[PowerPC] Switch to PIC kernel modules on powerpc*
To improve reliability of kernel modules after the clang switch, switch to -fPIC when building for now.
This bypasses some limitations to the way
[PowerPC] Switch to PIC kernel modules on powerpc*
To improve reliability of kernel modules after the clang switch, switch to -fPIC when building for now.
This bypasses some limitations to the way clang and LLD handle relocations, and is a more robustly tested compilation regime than the "static shared object" mode that we were previously attempting to convince the compiler stack to use.
The kernel linker was recently augmented to be able to handle this mode.
Reviewed by: jhibbits Differential Revision: https://reviews.freebsd.org/D22798
show more ...
|
#
9ab286b7 |
| 21-Nov-2019 |
John Baldwin <jhb@FreeBSD.org> |
Add a kmod.opts.mk.
This Makefile sets KERN_OPTS. This permits kernel module Makefiles to use KERN_OPTS to control the value of variables such as SRCS that are used by bsd.kmod.mk for KERN_OPTS val
Add a kmod.opts.mk.
This Makefile sets KERN_OPTS. This permits kernel module Makefiles to use KERN_OPTS to control the value of variables such as SRCS that are used by bsd.kmod.mk for KERN_OPTS values that honor WITH/WITHOUT options for standalone builds.
show more ...
|
#
3cc5d6a4 |
| 21-Nov-2019 |
Warner Losh <imp@FreeBSD.org> |
Introduce bsd.sysdir.mk to consolidate looking for the kernel.
Reviewed by: jhb Differential Revision: https://reviews.freebsd.org/D22144
|