moonlight-qt: fix/enable drm
This is an attempt to enable drm support in moonlight-qt and unbreak a
non-reproducible run-time error. The ioctl isn't implemented on OpenBSD.
Perhaps it won't work; only users can find that out. Since it has currently
been reported as run-time broken, let's give it a try.
Update to 2025cgtz from https://github.com/JodaOrg/global-tz
o Baja California agreed with California’s DST rules in 1953 and in
1961 through 1975, instead of observing standard time all year.
o The leapseconds file contains commentary about the IERS and NIST
last-modified and expiration timestamps for leap second data.
o Commentary now also uses UTGF-8 characters. This also affects
data in iso3166.tab and zone1970.tab.
when using install-info on compressed info files, uncompress from stdin
rather than passing "< filename" to the shell. from espie, ok tb.
leaks, but so does the surrounding code.
Protect the array that keeps track of which MMU contexts are in use with
a mutex. Also disable the context stealing code. It isn't mpsafe and we
should have more than enough MMU contexts to never need to steal one with
the current (hard) limites on the number of processes.
This enables some code that checks that a context that is being freed no
longer has live entries in the TSB. This code is somewhat expensive so
we may want to disable it again in the not too distant future.
ok deraadt@
The sun4v_send_ipi() function completely blocks interrupts. This may
result in failures if there is lots of IPI traffic between CPUs as
CPUs that are busy sending an IPI won't be able to process incoming IPIs.
Instead of blocking interrupts, use splhigh() to protect the per-CPU state
involved in sending IPIs.
The sun4v_broadcast_ipi() function did not block interrupts and therefore
lacked protection of the per-CPU state. This means an IPI sent from an
interrupt handler could overwrite the state, resulting in TLB flushes being
sent to the wrong CPUs or with the wrong parameters. Use splhigh() here
as well. This seems to fix (some) of the recent instability seen on
sparc64 after changes to how we tear down exiting processes.
ok deraadt@
enable ld.bfd(1) on amd64, provide patch and comment for arm64
Upcoming net/ipxe requires a recent GNU linker, old 2.17 in base crashes.
This builds on amd64, arm64, armv7, i386, octeon, riscv64 and sparc64,
but as our iPXE currently builds only on amd64 and arm64 and ld.bfd does
not build reliably on the latter, start with LD_ARCHS=amd64 only.
Feedback OK jca fcambus
Switch the llvm dependency back from 21 to 19
In the Qt6.10 update, I updated qttools from llvm19 to llvm21. Since qttools
always selected the highest version when it was installed. Since pyside
requires qttools, I have also set shiboken to 21.
With this patch we can revert it and switch back to 19.
Feedback from sthen@ and kirill@, thanks
