aboutsummaryrefslogtreecommitdiff
path: root/sys/contrib
Commit message (Collapse)AuthorAgeFilesLines
* Merge commit bfb276e55c76 from upstream OpenZFS (by Jessica Clarke)Jessica Clarke5 days1-1/+1
| | | | | | | | | | | | | | | | | | | | | Once upon a time, 32-bit PowerPC did indeed have a 32-bit time_t, but FreeBSD 12.0 switched to a 64-bit time_t for PowerPC as an ABI break, which predates the addition of FreeBSD support to OpenZFS. Moreover, 64-bit PowerPC has existed since FreeBSD 9.0, where __powerpc__ is also defined (alongside __powerpc64__ to disambiguate), which has always had a 64-bit time_t. This code has therefore always been wrong for all PowerPC variants. Fix this by limiting the 32-bit case to just i386, which is the only architecture in FreeBSD to have a 32-bit time_t and not have broken ABI, due to its special legacy compatibility status. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Alexander Motin <alexander.motin@TrueNAS.com> Signed-off-by: Jessica Clarke <jrtc27@jrtc27.com> Closes #18217 Closes #18218 Reported by: fuz MFC after: 1 day
* vchiq: Fix return type of vchiq_copy_from_userJohn Baldwin6 days1-2/+2
| | | | | | | | | | | | | | | | Change the function definition to map the declaration and consistently return an enum value. This fixes the following error reported by GCC: sys/contrib/vchiq/interface/vchiq_arm/vchiq_2835_arm.c:322:1: error: conflicting types for 'vchiq_copy_from_user' due to enum/integer mismatch; have 'int(void *, const void *, int)' [-Werror=enum-int-mismatch] 322 | vchiq_copy_from_user(void *dst, const void *src, int size) | ^~~~~~~~~~~~~~~~~~~~ In file included from sys/contrib/vchiq/interface/vchiq_arm/vchiq_arm.h:38, from sys/contrib/vchiq/interface/vchiq_arm/vchiq_2835_arm.c:61: sys/contrib/vchiq/interface/vchiq_arm/vchiq_core.h:647:1: note: previous declaration of 'vchiq_copy_from_user' with type 'VCHIQ_STATUS_T(void *, const void *, int)' 647 | vchiq_copy_from_user(void *dst, const void *src, int size); | ^~~~~~~~~~~~~~~~~~~~ Differential Revision: https://reviews.freebsd.org/D55163
* brcm80211: update Broadcom wireless brcmsmac and brcmfmac driversBjoern A. Zeeb13 days9-35/+65
| | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 24d479d26b25bce5faea3ddd9fa8f3a6c3129ea7 ( tag: v6.19-rc6 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* brcmfmac: make USB parts compile (and not panic right away)Bjoern A. Zeeb13 days2-0/+58
| | | | | | | | | | | | | | | | | Fix casts and consts and add one extra error check for a NULL pointer. This will require [a future] linuxkpi_usb. There are very few dongles I know off: - the original Raspberry PI USB dongle [1] - Cisco Linksys AE1200 The reason for making USB compile despite the limited 11n 150/300 Mbit/s adapters is that it is the simplest way to work on cfg80211 while on the road, not requiring a full PCIe slot or another SoC for SDIO. Sponsored by: The FreeBSD Foundation Hardware donated by: Martin Husemann (martin NetBSD.org) [1] MFC after: 3 days
* brcm80211: add LinuxKPI files and module MakefilesBjoern A. Zeeb13 days20-0/+609
| | | | | | | | | | | | | | sys/compat/linuxkpi/common/include/linux/platform_data/brcmfmac.h is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git e5f0a698b34ed76002dc5cff3804a61c80233a7a ( tag: v6.17 ). Currently only PCIe is made to compile. It does load firmware (if needed, e.g., on arm64 with an alignment issue fixed), and starts to come up. To make it work there is a cfg80211 layer and netdevice integration to do, so do not hold your breath just yet.
* brcm80211: import Broadcom wireless brcmsmac and brcmfmac driversBjoern A. Zeeb13 days133-0/+116023
| | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git e5f0a698b34ed76002dc5cff3804a61c80233a7a ( tag: v6.17 ). We are likely only going to use the brcmfmac driver but given they come nicely packaged in a directory structure and bwn(9) still uses GPL-only phy files we could use some of the information from brcmsmac and fix that (should it ever still be relevant). git-subtree-dir: sys/contrib/dev/broadcom/brcm80211 git-subtree-mainline: 69c64e3fb575e0db0e2f0c1fc56f466624940ded git-subtree-split: 1eabd3ed89eb4bb5c69e90eeaeda1a6dd31e8bab
* ath10k: update Atheros/QCA's ath10k driverBjoern A. Zeeb13 days1-8/+8
| | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 05f7e89ab9731565d8a62e3b5d1ec206485eeb0b ( tag: v6.19 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days
* rtw89: harmonize all MODULE_DEPEND to rtw89Bjoern A. Zeeb14 days4-8/+13
| | | | | | | | rtw89 came like rtw88 was done. Given rtw88 once was split up rtw89 got modelled the same way. Clean this up too. Sponsored by: The FreeBSD Foundation MFC after: 3 days
* rtw89: cleanup static_assert() callsBjoern A. Zeeb14 days9-58/+0
| | | | | | | | | These days we can use static_assert() without trouble so remove the FreeBSD-specific rtw89_static_assert implementation. This reduces the diff to upstream and will ease future driver updates. Sponsored by: The FreeBSD Foundation MFC after: 3 days
* rtw88: harmonize all MODULE_DEPEND to rtw88Bjoern A. Zeeb14 days4-12/+10
| | | | | | | | | | | | | | | | From the time I used to split up the driver into a core part and bus attachment sub-drivers the various bus attachments had their own module name but all is "rtw88" now. Core functionality depends on linuxkpi, linuxkpi_wlan, and for debug.c lindebugfs. Each bus attachment then depends on its own parent layer if needed: PCI gets pull in through linuxkpi, USB: depends on [the future] linuxkpi_usb, and SDIO: depends on [the future] linuxkpi_sdio. Sponsored by: The FreeBSD Foundation MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D55021
* rtw89: update Realtek's rtw89 driverBjoern A. Zeeb14 days57-1098/+4647
| | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 24d479d26b25bce5faea3ddd9fa8f3a6c3129ea7 ( tag: v6.19-rc6 ). Sponsored by: The FreeBSD Foundation MFC after: 3 days PR: 285228
* ath10k: usb: make compile using [a future] linuxkpi_usbBjoern A. Zeeb2026-02-091-0/+22
| | | | | | | | | | | | | | | | | | | | | | | Make ath10k usb code compile just to gather more USB bits. Currently (and likely forever) it is useless as the ath10k USB implementation never got finished. At the moment it lacks an entry for the USB bus attachment in core.c ath10k_hw_params_list[]. ath10k_usb0 on uhub1 ath10k_usb0: <Qualcomm Atheros USBWLAN, rev 2.01/92.10, addr 6> on usbus0 ath10k_usb0: Warning: ath10k USB support is incomplete, don't expect anything to work! ath10k_usb0: Unsupported hardware version: 0x5020001 ath10k_usb0: could not get hw params (-22) ath10k_usb0: could not probe fw (-22) There is another possible hardware [1] which was also never merged upstream. [1] https://lists.infradead.org/pipermail/ath10k/2024-August/016037.html "[PATCH] wifi: ath10k: add USB device ID for Atheros QCA9377-7" MFC after: 3 days
* ath10k: harmonize all MODULE_DEPEND to ath10kBjoern A. Zeeb2026-02-094-9/+15
| | | | | | | | | With theoretically multiple bus attachements (unclear if we will ever support anything but PCI) rename the module name to "ath10k" and use it consistently. Move the common depends to core.c and lindebugfs and usb to their respective files. MFC after: 3 days
* ath10k: cleanup some bits no longer FreeBSD-specificBjoern A. Zeeb2026-02-093-41/+4
| | | | | | | | We have since I did this port in 2023 added ACPI support to LinuxKPI, so we can use it. Also there is a linux/of.h header so we no longer need to guard the #include. MFC after: 3 days
* ath10k: add sysctl to turn on/off fwlogBjoern A. Zeeb2026-02-091-0/+17
| | | | | | | | FWLOG, if compiled in, was on by default without a way to stop it from printing everything to the console. Add a modparam to enable it with it being disabled by default if available. MFC after: 3 days
* ath10k: fix a schedule() callBjoern A. Zeeb2026-02-092-2/+10
| | | | | | | | | | | Using kern_yield does not seem ideal either for polling here; use a schedule_timeout() call from LinuxKPI instead and use about 100 iterations per second. Improve an error message to include the error code so we have a better idea of what happens. MFC after: 3 days
* rtw88: set .bsddriver.name for USB chipsetsBjoern A. Zeeb2026-02-097-4/+13
| | | | | | | | | We use the FreeBSD-specifc bsddriver.name to get the device name; set it everywere consistently. Sponsored by: The FreeBSD Foundation MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D55020
* openzfs sys/types32.h: use abi_compat.h for time32_tKonstantin Belousov2026-02-092-1/+7
| | | | | | | | | | | | | | | | The time32_t typedef leaks into openzfs compilation environment through sys/event.h. Simultaneously, openzfs provides its own definition that is only correct for amd64 on FreeBSD. Try to fix it by using sys/abi_compat.h directly. Since toolchain build from the make buildworld uses host abi_compat.h, add a preprocessor symbol __HAVE_TIME32_T to signal consumers that time32_t is typedef'ed. If not defined, fall back to old and wrong time32_t, which is enough for bootstraping toolchain. Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D55135
* mt76: fix a check wrongly giving us random ether addresses all the timeBjoern A. Zeeb2026-02-071-3/+6
| | | | | | | | | | | | | | | | | | Do not cover the is_valid_ether_addr() check under CONFIG_OF. Unclear if this is an initial porting or a merging error before the driver hit the FreeBSD src tree. The end result was that we always got a random link-layer address, while the individual drivers may have setup phy->macaddr and this function would only overwride if given in device tree. Only if both, driver and and the OF backup, fail then go and use the random link-layer address. While here adjust printing the random link-layer address using a FreeBSD format specifier and not the unsupported Linux one. Fixes: 6c92544d7c97 Sponsored by: The FreeBSD Foundation MFC after: 3 days
* mt76: mt7925: add missing LINUXKPI_PARAM_PREFIXBjoern A. Zeeb2026-02-071-0/+4
| | | | | | | | | | | There is a module_param_named() in the file so we need to set LINUXKPI_PARAM_PREFIX to get it a uniq sysctl name. mt7921 has the exact same option. Without their individual prefixes the names would clash on systems with both chipsets and not work for both. Sponsored by: The FreeBSD Foundation MFC after: 3 days
* mt76: make USB compileBjoern A. Zeeb2026-02-072-0/+13
| | | | | | | | This is the mt76-specific changes to make the USB driver targets for 7921 and 7925 compile. Sponsored by: The FreeBSD Foundation MFC after: 3 days
* mt76: sort out MODULE_DEPEND for PCI and USBBjoern A. Zeeb2026-02-078-5/+22
| | | | | | | | | | | | | | It is not enough to depend on mt76_core which then depends on linuxkpi and linuxkpi_wlan. Given each mt76 driver is its own module, each also needs to depend on these linuxkpi modules. In addition the core module usb part also has to depend on linuxkpi_usb. This in addition to the previously sorted PCI drivers, allows (or will allow) the individual chipsets (drivers) to load on systems with USB, if compiled in, as well. Sponsored by: The FreeBSD Foundation MFC after: 3 days
* mt76: update Mediatek's mt76 driverBjoern A. Zeeb2026-01-23213-1620/+4128
| | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 24d479d26b25bce5faea3ddd9fa8f3a6c3129ea7 ( tag: v6.19-rc6 ). Notable change: license got switched from ISC to BSD-3-Clause-Clear. util.h is now imported from upstream given it is no longer GPL-only. See the upstream repository 909675fd4344f73aad5f75f123bd271ada2ab9fb and a96fed2825d8dfb068bf640419c619b5f2df4218. For us the new version should also help with page pools and DMA32. Sponsored by: The FreeBSD Foundation
* rpc/xdr.h: make xdrproc_t always take two argumentsBrooks Davis2026-01-231-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The type of xdrproc_t is clearly defined in the comments as a function with two arguments, an XDR * and a void * (sometimes spelled caddr_t). It was initialy defined as: typedef bool_t (*xdrproc_t)(); At some point people started giving it a non-empty argument list. Unfortunatly, there has been widespread disagreement about how arguments are passed. There seems to have been a widespread view that it should be allowed to pass three argument function pointer to xdrproc_t. Most notable is xdr_string which takes a maximum length parameter. This lead to all sorts of prototypes (all of which have been present in the FreeBSD source tree): FreeBSD userspace (nominally from tirpc, but seemingly local): typedef bool_t (*xdrproc_t)(XDR *, ...); FreeBSD kernel, glibc: typedef bool_t (*xdrproc_t)(XDR *, void *, ...); rcp/xdr.h with _KERNEL defined (not used?): typedef bool_t (*xdrproc_t)(XDR *, void *, u_int); gssrpc (in krb5) and Linux kernel: typedef bool_t (*xdrproc_t)(XDR *, void *); For two argument functions on current ABIs, these all equivalent as these arguments are passed in registers regardless of decleration and definition, but we end up with two problems: - xdr_free((xdrproc_t)xdr_string, ...) calls xdr_string with no third argument and (at least on FreeBSD) may fail to free memory if the string is shorter than the value lying around in the third argument register. There are no instance of this in tree, but I found some with Debian code search, in particular in OpenAFS. - Under CheriABI, variadic arguments are passed in a separate, bounded array so theses prototypes aren't equilvalent to the non-variadic calling convention of the functions. The reality is that that xdr_string should not be cast to xdrproc_t and xdr_wrapstring should be used instead so we do not need to support this case. Instances of the former behavior are now extremely rare. With this change we bring FreeBSD in line with gssrpc and the Linux Kernel. Warnings about casts should now be correct and should be fixed. Bump __FreeBSD_version as some software required adaptation if it is declaring functions to cast to xdrproc_t. Update OpenZFS's workaround of this historic mess accordingly. Effort: CHERI upstreaming Sponsored by: Innovate UK Reviewed by: kib Differential Revision: https://reviews.freebsd.org/D54824
* ath10k: update Atheros/QCA's ath10k driverBjoern A. Zeeb2026-01-217-51/+274
| | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 24d479d26b25bce5faea3ddd9fa8f3a6c3129ea7 ( tag: v6.19-rc6 ). Sponsored by: The FreeBSD Foundation
* rtw88: update Realtek's rtw88 driverBjoern A. Zeeb2026-01-215-2/+21
| | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 24d479d26b25bce5faea3ddd9fa8f3a6c3129ea7 ( tag: v6.19-rc6 ). Sponsored by: The FreeBSD Foundation
* Revert "ophgo: import new .dts"Warner Losh2026-01-1019-2703/+0
| | | | | | | | | | | | | | | | | | | This reverts commit b55d106df9785d141f9e3e1c916e921df9d877ac. Per request of original author, manu, and mmel, revert this change. While this is a genuinely cool device, there's some issues that need to be sorted out before moving forward: o Imported dt-bindings that weren't used and could interfere in the future. o no platform code for sophgo, though it likely needs it o Potential interference from the dts/dtsi files imported for future linux device-tree imports. These are the dts files from the vendor sdk, and history has down often upstream introduces enough change that keeping them here in the mean time lays the groundwork for merge conflicts in the future. That makes this import premature. Revert until it's more mature.
* ophgo: import new .dtsMartin Filla2026-01-1019-0/+2703
| | | | | | Signed-off-by: Martin Filla <freebsd@sysctl.cz> Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/1844
* zfs: emit .note.GNU-stack section for all ELF targetsDimitry Andric2026-01-083-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | On FreeBSD, linking the zfs kernel module with binutils ld 2.44 shows the following warning: ld: warning: aesni-gcm-avx2-vaes.o: missing .note.GNU-stack section implies executable stack ld: NOTE: This behaviour is deprecated and will be removed in a future version of the linker Some of the `.S` files under `module/icp/asm-x86_64/modes` check whether to emit the `.note.GNU-stack` section using: #if defined(__linux__) && defined(__ELF__) We could add `&& defined(__FreeBSD__)` to the test, but since all other `.S` files in the OpenZFS tree use: #ifdef __ELF__ it would seem more logical to use that instead. Any recent ELF platform should support these note sections by now. Reviewed by: emaste, kib, imp MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D54578
* zfs: rename several printf attribute declarations to __printf__Dimitry Andric2025-12-305-14/+14
| | | | | | | | | | | | | | | | | | | | | | | | For kernel builds, we redefine `__printf__` to `__freebsd_kprintf__`, to support FreeBSD kernel printf(9) extensions with clang. In OpenZFS various printf related functions are declared with __attribute__((format(printf, X, Y))), so these won't work with the above redefinition. With clang 21 and higher, this leads to errors similar to: sys/contrib/openzfs/module/zfs/spa_misc.c:414:38: error: passing 'printf' format string where 'freebsd_kprintf' format string is expected [-Werror,-Wformat] 414 | (void) vsnprintf(buf, sizeof (buf), fmt, adx); | ^ Since attribute names can always be spelled with leading and trailing double underscores, rename these instances. Note that in FreeBSD proper we usually use `__printflike` from <sys/cdefs.h>, but that does not apply to OpenZFS. Reviewed by: emaste MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D54388
* zfs: merge openzfs/zfs@962e68865Martin Matuska2025-12-1959-713/+1318
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Notable upstream pull request merges: #16307 1d43387dd zdb: Add -O option for -r to specify object-id #17965 a62c62120 ARC: Pre-convert zfs_arc_min_prefetch_ms #17970 d393166c5 ARC: Increase parallel eviction batching #17981 20f09eae4 ZIO: ZIO_STAGE_DDT_WRITE is a blocking stage #17983 ff47dd35e Fix ddtprune causing space leak #18015 86b064469 FreeBSD: Fix a potential null dereference in zfs_freebsd_fsync() (already merged) #18020 ff47dd35e Ensure 64-bit `off_t` is used in user space instead of `loff_t` #18028 09492e0f2 Reduce dataset buffers re-dirtying #18033 f72fd378c Defer async destroys on pool import #18043 3d76ba273 Improve async destroy processing timing #18044 46d6f1fe5 DDT: Move logs searches out of the lock #18047 ff5414406 DDT: Switch to using ZAP _by_dnode() interfaces #18048 3b1ff816b DDT: Add/use zap_lookup_length_uint64_by_dnode() #18055 22e89aca8 DDT: Fix compressed entry buffer size #18059 0550abd4b RAIDZ: Remove some excessive logging #18060 a83bb15fc Reduce minimal scrub/resilver times #18061 962e68865 Use reduced precision for scan times #18063 051a8c749 Bypass snprintf() in quota checks if no quotas set #18064 7ff329ac2 Fix rangelock test for growing block size Obtained from: OpenZFS OpenZFS commit: 962e68865e4a569a8a51a07a45dcae7c33cdca78
* acpica: Merge ACPICA 20251212Jung-uk Kim2025-12-1932-156/+1106
|\ | | | | | | Merge commit '5cab380e2a2644aaa920b93f1580a1cfc803a8de'
* | zfs: Merge commit 86b064469dc9c2 from OpenZFSMark Johnston2025-12-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | FreeBSD: Fix a potential null dereference in zfs_freebsd_fsync() In general it's possible for a vnode to not have an associated VM object. This happens in particular with named pipes, which have some distinct VOPs, defined in zfs_fifoops. Thus, this chunk of zfs_freebsd_fsync() needs to check for the FIFO case, like other vm_object_mightbedirty() callers do. (Note that vn_flush_cached_data() calls are predicated on zn_has_cached_data() returning true, and it checks for a NULL v_object pointer already.) Fixes: ef4058fcdc01838117dd93a654228bac7487a37c Reported-by: Collin Funk <collin.funk1@gmail.com> Reviewed-by: Sean Eric Fagan <sef@FreeBSD.org> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Alexander Motin <alexander.motin@TrueNAS.com> Signed-off-by: Mark Johnston <markj@FreeBSD.org> Closes #18015 MFC after: 3 days
* | zfs: merge openzfs/zfs@89f729dccMartin Matuska2025-12-0778-8271/+1224
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Notable upstream pull request merges: #17932 1f3444f2b zpool: fix special vdev -v -o conflict #17934 -multiple Remove libuutil #17941 88d012a1d Fix snapshot automount expiry cancellation deadlock #17942 36e4f1888 Fix taskq NULL pointer dereference on timer race #17946 39303feba chksum: run 256K benchmark on demand, preserve chksum_stat_data #17948 -multiple Remove libtpool #17957 e37937f42 ztest: fix broken random call #17960 928eccc5b DDT: Reduce global DDT lock scope during writes #17961 48f33c1ef DDT: Make children writes inherit allocator #17975 7f7d4934c FreeBSD: Fix uninitialized variable error #17980 a5b665df3 DDT: Switch to using wmsums for lookup stats #18004 ffaea0831 FreeBSD: Remove HAVE_INLINE_FLSL use Obtained from: OpenZFS OpenZFS commit: 89f729dcca87425aadfa03d1764e96f285eb658d
* | ath11k: start making compile some moreBjoern A. Zeeb2025-12-062-0/+6
| | | | | | | | | | There is more work to do to make this compile again but we will do that when we get to the driver. For now just take the most noise out of it.
* | ath11k: update Atheros/QCA's ath11k driverBjoern A. Zeeb2025-12-0667-2069/+4853
| | | | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 7d0a66e4bb9081d75c82ec4957c50034cb0ea449 ( tag: v6.18 ). Merge commit '989a88787ef2c1a73f44b82031a6f4f4470e2676' Sponsored by: The FreeBSD Foundation
* | ath10k: update Atheros/QCA's ath10k driverBjoern A. Zeeb2025-12-0647-574/+1009
| | | | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 7d0a66e4bb9081d75c82ec4957c50034cb0ea449 ( tag: v6.18 ). Merge commit 'f4669ef6cf7860919442e67106e83f616ed36f51'. Sponsored by: The FreeBSD Foundation
* | ath-common: update common Atheros/QCA codeBjoern A. Zeeb2025-12-069-20/+177
| | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git e5f0a698b34ed76002dc5cff3804a61c80233a7a ( tag: v6.17 ). Merge commit '99ad6f4f54c86845d6e3f03541913c07fcdeef59'
* | rtw88: update Realtek's rtw88 driverBjoern A. Zeeb2025-12-062-6/+11
| | | | | | | | | | | | | | | | | | | | This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 7d0a66e4bb9081d75c82ec4957c50034cb0ea449 ( tag: v6.18 ). Merge commit 'e543442afe3ad5b27616575be2d2402b988656eb' into rtw88 Sponsored by: The FreeBSD Foundation
* | mt76: add LINUXKPI_PARAM_PREFIX for module_param*Bjoern A. Zeeb2025-12-0311-0/+44
| | | | | | | | | | | | | | | | | | | | In order to not overwrite sysctl/tunables under compat.linuxkpi we need to prefix the module_param* names with a per-driver/file designator to make them (more) uniq. Add the FreeBSD specific LINUXKPI_PARAM_PREFIX defines for that where missing in mt76. Sponsored by: The FreeBSD Foundation MFC after: 3 days
* | mt76: util.h: extend worker nameBjoern A. Zeeb2025-12-031-31/+8
| | | | | | | | | | | | | | | | | | | | In mt76_worker_setup() add the "name" argument to the description for the worker thread. That way we have a chance to keep them apart. While here, rename a variable and shorten the the (c)/SPDX section according to new style. MFC after: 3 days
* | mt76: ieee80211_is_first_frag() operates on the seq_ctrl field not on fc.Bjoern A. Zeeb2025-12-031-1/+1
| | | | | | | | | | | | | | | | | | Pass the correct field to ieee80211_is_first_frag(); otherwise the results may vary. Sponsored by: The FreeBSD Foundation MFC after: 3 days X-To-Upstream: yes
* | libuvmem: usermode port of vmem(9)Konstantin Belousov2025-12-021-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | The quantum cache is disabled, there is no uma. Intent is to use this for resource allocation in bhyve(8), for start. Addition of -luvmem to bhyve linking was done to test changes to share/mk. Reviewed by: bnovkov, markj Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D27220
* | openzfs: We are FreeBSD, not posix.Warner Losh2025-11-261-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Partially revert: https://github.com/openzfs/zfs/commit/99d7453b43dc0ef04a35e461ef14db72e1326c7c which introduced this file upstream. This causes this definition to be preferred for all builds. Make the smallest change possible to this file to change the default to FreeBSD. We're talking to the upstraem folks about the right fix. Feel free to revert this in the future, so long as `bectl activate -t` still works properly afterwards. Sponsored by: Netflix
* | dts: Revert its addition for rk356xEmmanuel Vadot2025-11-222-17/+5
| | | | | | | | | | | | | | Rockchip have two erratas (#3568001 and #3568002) for the GIC on RK356x. Until we have a way to handle them revert the changes that uses ITS instead of GIC for PCIe.
* | Import device-tree files from Linux 6.17Emmanuel Vadot2025-11-221212-8020/+67414
| |
* | Import device-tree files from Linux 6.16Emmanuel Vadot2025-11-221360-10122/+96802
| |
* | Import device-tree files from Linux 6.15Emmanuel Vadot2025-11-221067-3979/+51463
| |
* | Import device-tree files from Linux 6.14Emmanuel Vadot2025-11-22817-5159/+71981
| |
* | Import device-tree files from Linux 6.13Emmanuel Vadot2025-11-221454-20182/+83923
| |
generated by cgit v1.2.3 (git 2.25.1) at 2026-02-24 01:07:32 +0000