misc/kimi-code: Update to 2.6.3
Stops duplicated output and a stuck spinner for foreground shell
commands, runs the external stop hook again after every reply and
keeps background notifications from starting replies of their own
when a session is resumed.
Changes:
https://github.com/MoonshotAI/kimi-code/releases
Sponsored by: Netzkommune GmbH
pam_xdg.8: Mechanical polish
+ convert license to SPDX only
+ belatedly bump date for last content change
+ rewrite in semantic line breaks to fix one sentence per line
Reviewed by: manu
Fixes: ecd6631b19d9 ("pam_xdg: Add linger option")
Differential Revision: https://reviews.freebsd.org/D61703
www/immichframe: Update to 1.0.40.0
Switch to .NET 10 and build with the runtime identifier of the host
major version, which is the only one the SDK ships packs for.
Changelog: https://github.com/immichFrame/ImmichFrame/releases/tag/v1.0.40.0
Sponsored by: Netzkommune GmbH
linuxkpi: Release the "from" device in pci_get_class() and pci_get_base_class()
On Linux the pci_get_*() iterators drop the reference of the device passed
as "from" once the next one has been looked up, so a loop like
while ((pch = pci_get_class(class, pch)))
does not leak anything. LinuxKPI allocates a new pci_dev for every device
it returns but never released "from", so each device but the last one was
leaked together with its kobject, its name and its path name. i915 does
exactly this in intel_detect_pch() and leaked a device at every load.
Drop the reference, but only for the devices created by lkpinew_pci_dev();
the pci_dev of a device attached to a driver belongs to the bus.
Differential Revision: https://reviews.freebsd.org/D61222
lindebugfs: Free the kcov symlink when the module is unloaded
lindebugfs_init() creates the "kcov" symlink with debugfs_create_symlink(),
which allocates a node and a copy of the destination, but passed no destroy
callback to pfs_create_link(). pseudofs therefore never released them and
the "debugfsint" malloc type was reported as leaking memory each time the
module was unloaded.
Use debugfs_destroy(), as done for the other nodes.
Differential Revision: https://reviews.freebsd.org/D61221
linuxkpi: Release devres when the probe of a PCI driver fails
When the probe method of a driver fails, linux_pci_attach_device() only
dropped its reference on the device. Like on detach (see the previous
change), the devres actions are then not run if one of them holds a
reference on the device, which is what devm_drm_dev_alloc() does through the
drm_device. The device is never released, the drm_device is leaked with its
minor, its managed memory and its debugfs entries: unloading the driver
after a failed load (e.g. a missing firmware) printed
"WARNING !xa_empty(&drm_minors_xa)" and leaked memory.
Linux releases the devres resources of a device whose probe failed, so do the
same.
Differential Reivision: https://reviews.freebsd.org/D61223
pam_xdg: Add linger option
The pam_xdg module deletes a user's XDG_RUNTIME_DIR when the last
interactive session logs out. If the user leaves background processes
running on the system, like a terminal multiplexer, that puts state or
domain sockets in XDG_RUNTIME_DIR, then that state gets destroyed and
the processes become effectively orphaned.
On Linux, systemd-logind not only unlinks XDG_RUNTIME_DIR but also kills
all user processes on logout. To allow long-lived background processes,
it implements a per-user "linger" mode to disable the unlink and kill.
Because FreeBSD's pam_xdg does not implement process killing, this
"linger" option implementation skips only XDG_RUNTIME_DIR unlinking
when the user still has running processes after the last session logs
out.
Differential Revision: https://reviews.freebsd.org/D61332
sysutils/rpi-firmware: Use firmware DTB placement on Raspberry Pi 5
Set device_tree_address to an empty value for Pi 5, overriding the
inherited 0x4000 address and allowing firmware to place the DTB.
Keep DTB selection automatic for the D0 overlay. Preserve other models'
settings and bump PORTREVISION.
Companion src driver and release changes are required for Pi 5 support.
aw_thermal: Add support for the H6
Add the thermal sensor controller of the H6, which has two sensors, for
the CPU and the GPU.
The controller has other registers than the one of the supported SoCs.
The efuse has the temperature of the factory test and the value of each
sensor at this temperature, from which the calibration value of each
sensor is computed and written to the controller.
The alarm and shutdown thresholds and the interrupts are not supported
yet.
Tested on: Pine H64 (CPU and GPU temperatures, idle and under load)
aw_thermal: Make the data register and the alarm support per SoC
The controller of the H6 has its data registers at another offset and
other alarm, shutdown and interrupt registers.
Add the offset of the first data register to the SoC configuration,
and a flag for the alarm handling (interrupt, alarm and shutdown
thresholds and the cpufreq throttling), set for all the SoCs
currently supported.
No functional change intended.
aw_thermal: Add an init function to the SoC configuration
Move the initialisation of the controller to a function of the SoC
configuration, as the controller of the H6 is different from the one
of the other supported SoCs.
No functional change intended.
aw_sid: Add the thermal sensor calibration fuse of the H6
The thermal sensor controller of the H6 gets its calibration data from
the 8 bytes of the efuse at offset 0x14, referenced by the
ths_calibration nvmem cell. Add it so the thermal driver can read it.
Tested on: Pine H64 (thermal sensor calibration)