nfscl: Yet more fixes for the NFS over RDMA client glue
This should be it for a while, but there will be another cycle
of "glue" updates. I just found out that I'll need to create
an alternate code path that uses a contigmalloc() blob instead
of scatter/gather of pages, since some NICs cannot do the
scatter/gather of pages well.
This commit should not affect non-RDMA behaviour.
MFC after: 3 months
Fixes: 884ee8d6c9b4 ("nfscl: Add some glue for client side NFS over RDMA")
llama.cpp: update to 0.4.0.
llama.cpp 0.4.0 adds initial Qwen3.8-Flash-Next and Nemotron-3-Puzzle
support, on-demand tensor reading, per-slot server context limits,
video input options, and a ggml update to 0.23.0 with major sparse
flash attention and RDMA work.
NAS-143046 / 26.0.0-RC.1 / Exempt TNC_SUB from the product matrix completeness check (by sonicaj) (#19696)
This commit adds changes to keep the target vector completeness
assertion passing now that TNC_SUB exists in the LicenseFeature enum.
TNC_SUB reports a TrueNAS Connect account tier rather than a product
matrix row, so there is no HW/CE column that could grant or withhold it
and giving it a vector would add a row nothing ever consults.
Original PR: https://github.com/truenas/middleware/pull/19691
Co-authored-by: Waqar Ahmed <waqarahmedjoyia at live.com>
aq(4): arm PHY thermal shutdown from the admin poll
move thermal shutdown arming to the admin poll
this gives a more reasonable delay prior to the first attempt, and also
allows us to retry and make the option runtime-tuneable via a new
disable_thermal_arm sysctl
Approved by: adrian (mentor)
Reviewed by: adrian
Differential Revision: https://reviews.freebsd.org/D59593
Signed-off-by: Nick Price <nprice at FreeBSD.org>
fdescfs: descend through /dev/fd/N when mounted linrdlnk
Linux resolves a path below /proc/self/fd/N in the directory the
descriptor names, and linprocfs makes /proc/<pid>/fd a symlink to
/dev/fd. Under linrdlnk the fdescfs node carries only VV_READLINK,
which namei will not walk through, so such a path fails with ENOTDIR.
Return the underlying vnode from fdesc_lookup for a non-final component,
or a trailing slash, reusing the machinery the nodup option already
uses. The last component is untouched, so open("/dev/fd/N") keeps its
dup(2) semantic; a descriptor with no vnode behind it, such as a pipe,
yields ENOTDIR.
Add ATF coverage for traversal, descriptor reuse, and preservation of
last-component and mount-option semantics.
Approved by: adrian (mentor)
Reviewed by: kib, adrian
Differential Revision: https://reviews.freebsd.org/D59393
[2 lines not shown]
[SSAF][clang-reforge] Retrofit expressions after CppBoundedBuffers decl rewrites
PR #210457 introduces declaration rewriting. When CppBoundedBuffers
rewrites a declaration or return type to a bounded_ptr/bounded_array,
some of the existing uses of that entity needs retrofit.
This commit creates expression rewrites for the following patterns:
- Append '.data()' to call arguments when necessary parameter is not
transformed but argument is transformed.
- Append '.as_bounded<T>()' to call arguments when both parameter and
argument are transformed but element types are not identical.
- Rewrite '&e[i]' to '(e + i)' and '&*e'/'&(*e)' to 'e', if 'e' is
transformed.
- Rewrite '(T*)e', 'static_cast<T*>(e)', and 'reinterpret_cast<T*>(e)'
to 'e.as_bounded<T>()', if 'e' is transformed.
The 3rd step of
rdar://187125348
Update to 2026dgtz from https://github.com/JodaOrg/global-tz
o Canada’s Northwest Territories moved to permanent -06 on 2026-08-21.
o Obsolescent settings like TZ="EST5EDT" now conform better to POSIX.
o Colombia’s 1992-05-02 spring forward was at 00:00, not 24:00.
o Iran’s 1979-05-26 spring forward was at 00:00, not 24:00.
amd64, powerpc: Enable tpm(4) in supported kernels
tpm(4) was removed from amd64 GENERIC because it broke suspend and
resume. The preceding lifecycle, state-save, interrupt, locality, and
teardown fixes address those failures for both TPM 1.2 and TPM 2.0.
Restore the driver to amd64 GENERIC and MINIMAL, where TPM entropy
harvesting remained enabled. Enable the driver and entropy harvesting
in the MPC85XX and QORIQ64 configurations, which already provide FDT,
spibus, and the platform SPI controller required by FDT-attached TPMs.
Leave the generic AIM and POWER configurations unchanged because they
have no TPM attachment bus.
The TPM 1.2 path completed repeated S3 cycles and command tests on
ThinkPad T430 and T440p systems. The TPM 2.0 path completed repeated
device and full-system suspend/resume cycles on a ThinkPad P51. The
PowerPC configuration matrix was checked to retain tpm(4) only where its
FDT SPI attachment path is present.
[8 lines not shown]
puc: add the WCH CH382 2S dual serial card
Two 16850 UARTs in the first I/O BAR at offset 0xc0, 8 bytes apart.
Approved by: adrian (mentor)
Reviewed by: imp, adrian
Differential Revision: https://reviews.freebsd.org/D59512
Signed-off-by: Nick Price <nprice at FreeBSD.org>
gimp: update to 3.2.6.
Overview of Changes from GIMP 3.2.4 to GIMP 3.2.6
=================================================
Core:
- macOS: Macbook touchpad over-sensitivity now fixed.
- Destructive-only filter actions will be made insensitive on all
non-raster layers (unless rasterized).
- Windows: in release builds, we now attach our standard outputs to
the Windows console on certain scenarios only (when there is no
interface, or in verbose mode, or when --console-messages is set, or
finally when there are batch commands). By default, we are back to
how it was before GIMP 3.2.0, which is that GIMP doesn't output
anything on native shells it was called from.
- Fix expand from center which was failing in some cases.
- Layers to Image Size only works for raster (or rasterized) layers.
[247 lines not shown]
puc: be more careful about using MSI
puc has preferred MSI for every card since MSI support was added, with
only a global tunable to opt out. uart(4) makes the same decision for
the serial devices it attaches directly, and has since grown two
defences: it skips MSI unless the device advertises exactly one vector,
because attaching a single instance to a device offering many has caused
problems (PR 235016), and it lets individual devices be flagged when
they claim MSI support that does not work.
Adopt both.
Approved by: adrian (mentor)
Reviewed by: adrian
Differential Revision: https://reviews.freebsd.org/D59623
Signed-off-by: Nick Price <nprice at FreeBSD.org>
superio, ncthwm: add support for the Nuvoton NCT6798D
The ASUS PRIME X570-P carries a Nuvoton NCT6798D, Super I/O device ID 0xd42b. Add an exact-match entry to both. Exact rather than masked: the neighboring 0xd42a entries are deliberately exact with an extid because that ID is claimed by both NCT6796D-E and NCT5585D, and widening the family would make them collide.
The NCT6798D has seven tachometers, so raise NCTHWM_FAN_MAX to seven and describe the two extra ones; existing entries keep fan_count = 5 and are unaffected. Fan names follow the NCT6779 convention and do not map to any board's physical headers.
Tested on: ASUS PRIME X570-P, Ryzen 9 5950X, FreeBSD 16.0-CURRENT.
Approved by: adrian
Reviewed by: stephane.rochoy_stormshield.eu, adrian
Differential Revision: https://reviews.freebsd.org/D58291
Signed-off-by: Nick Price <nprice at FreeBSD.org>
gegl: update to 0.4.72.
GEGL-0.4.72 2026-09-07
----------------------
Build:
~~~~~~
- build with pure MSVC as well as wasm
- Improvements to defcheck,
- minimum meson version bumped to 0.60
- more CI integration, harmonized with gimp/babl
Core:
~~~~~
- use G_{BEGIN|END}_DECLS in all header declarations
- gegl_param_color_cmp, new function
- Avoid crashes in gegl_path
Buffer:
[30 lines not shown]
x11/nvidia-driver-devel, x11/nvidia-kmod-devel, x11/linux-nvidia-libs-devel, graphics/nvidia-drm*-kmod-devel: Update to 615.71.09
Update to latest New Feature Branch of drivers 615.71.09:
https://www.nvidia.com/en-us/drivers/details/278452/
Linux counterparts for x11/linux-nvidia-libs:
https://www.nvidia.com/en-us/drivers/details/278450/
Additional note:
Possibly vtys before invoking whichever of X11 or Wayland shifts
screen downward with about half character-based line, causing
command prompt at the bottom become hard to read.
Once X11 (tested only for xorg) or Wayland starts, it would be
fixed (on exitting X11 / Wayland or switching to vty from X11/
Wayland) until next restart of the computer.
This doesn't happen for everyone (among maintainance team of
NVIDIA GPU driver ports, only I myself am bitten).
[14 lines not shown]
[AMDGPU] Add getLDSAllocGranule to TargetParser
Expose the LDS allocation granule from GPUKind and subarch without an
MCSubtargetInfo. Use the dedicated granularity features and consolidate
backend users on the byte-valued query.
Change-Id: Ic0c9345e7657ec3c6978a646628598cb7608b390
[AMDGPU] Model LDS allocation granularity with subtarget features
Add numeric LDS allocation granularity features, expose them through the TargetParser feature bitset, and use them in the existing backend query.
Generic targets select the largest covered allocation granularity so their resource calculations remain conservative.
Change-Id: Icdd501d008c9d3cd566bdc8bde4a75d566ecb90a
[AMDGPU] Validate generic-target addressable local memory size
Apply the generic numeric at-most comparison to addressable LDS size. A
generic target must not advertise more local memory than any GPU it covers.
Keep the backend fallback of 32768 bytes and add integration tests using
the real LDS features for valid coverage, over-advertised capacity, and
conflicting feature values.
Change-Id: I9fffbe532b8b5bc8875f20f394f29e2e6899f52e
