sysutils/cpu-microcode-intel: Update to 2026-08-11 release
This update includes security fixes for INTEL-SA-01379, INTEL-SA-01404,
INTEL-SA-01423, INTEL-SA-01428, INTEL-SA-01435, INTEL-SA-01441,
INTEL-SA-01442, and INTEL-SA-01443, affecting various Core, Core Ultra,
and Xeon processors, as well as functional updates and support for new
steppings.
Release notes: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260811
Sponsored by: The FreeBSD Foundation
Revert "sysutils/cpu-microcode-intel: Handle extended signature tables"
This reverts a change to the way Intel CPU microcode files were split.
In d4b93e8846, an explicitly named file was written for each
signature+platform combination in an image's extended signature table.
Writing these new files offered discoverability advantages, but it was
unnecessary since cpucontrol(8) already checks the embedded extended
signature table. Moreover, adding these extra files increased the size
of the split files by about 50% when the default SPLIT knob was enabled.
This reverts commit d4b93e88468975e64d6321cfc463f5fc19f46d35.
PR: 295351
Sponsored by: The FreeBSD Foundation
textproc/fcitx5: Update to 5.1.21
- Take maintainership
- Add build dependency on x11/plasma-wayland-protocols: since 5.1.20 the
Wayland module calls find_package(PlasmaWaylandProtocols 1.20 REQUIRED)
when USE_SYSTEM_PLASMA_WAYLAND_PROTOCOLS is on (the default). Bump the
wayland-protocols requirement to 1.46 to match CMakeLists.txt .
Approved by: khng at FreeBSD.org (maintainer)
ixgbe: Defer firmware recovery transitions to iflib
The firmware-mode callout invoked ixgbe_if_stop() directly. This
performed a full device reset without the iflib context lock or the
iflib queue lifecycle. It could also poll the E610 firmware command
interface from callout context while identification was active.
Request an iflib reset from the callout instead. Reject initialization
while firmware recovery remains active. This leaves the interface
stopped and lets iflib publish that state. Request initialization when
firmware exits recovery so an administratively-up interface can recover
without operator intervention.
MFC after: 2 weeks
ixgbe: Defer ECC recovery to iflib
The link interrupt filter performed a full hardware reset in interrupt
context. This bypassed iflib stop and initialization, including queue
quiescence and restoration of temporary LED state.
Record the ECC event in the administrative request mask and ask iflib
to perform the reset from its taskqueue. Keep the ECC cause masked
until reset so the intermediate admin pass cannot re-enable a sticky
condition. Handle ECC independently of Flow Director and in legacy
interrupt mode.
Remove the redundant EICR write; the filter has already cleared the
reported causes. Also remove the accompanying complement-mask update
of mac.flags. It set every flag except DOUBLE_RESET_REQUIRED and had
no place in ECC recovery.
MFC after: 2 weeks
ixl: Add led(4) identification support
Expose each physical port identification LED through /dev/led/ixl*.
Use the existing GPIO LED helpers for most devices and the PHY
provisioning interface for X710 10GBASE-T adapters.
Preserve and restore the original GPIO or PHY indication mode,
including before the interface is stopped.
MFC after: 2 weeks
ixgbe: Add led(4) identification support
Expose the physical port identification LED through /dev/led/ix*.
Save and restore the NVM-selected LEDCTL value around each request.
The X550 operations also clear their PHY manual override before the
register is restored.
Use the dedicated firmware port-identification command on E610. Its
interface selects between firmware blinking and the original mode
rather than directly controlling LEDCTL.
Restore the normal indication before a device stop or reset.
MFC after: 2 weeks
igc: Remove invalid debug ring pointer iteration
The debug routine reads queue registers by queue index. It also
advanced unused pointers to rings embedded in queue structures. Those
pointers had the wrong stride and could proceed beyond the ring object.
Remove the unused pointer arithmetic.
MFC after: 2 weeks
e1000: Fix the multiqueue debug register dump
The debug routine advanced ring pointers as if rings were contiguous.
They are embedded in queue structures, so rings beyond queue zero had
the wrong stride. The bogus queue index could cause an invalid MMIO
read and panic the machine.
Index the queue arrays first and then select the embedded ring.
MFC after: 2 weeks
e1000: Identify SerDes adapters with LED blink
The generic LED on and off operations do not handle internal SerDes
media, leaving the led(4) device ineffective on my I210 fiber port.
Use the hardware blink operation for the on phase on internal SerDes.
The off phase restores the saved OEM LED configuration as before.
MFC after: 2 weeks
igc: Add led(4) identification support
I225 and I226 expose three programmable LED outputs. Use LED1 for
adapter identification, following the convention in DPDK. Preserve the
OEM configuration across identification requests.
Restore the OEM configuration before a device reset so an active led(4)
pattern cannot leave the output overridden across stop or detach.
The LED mode values follow the Intel I225 Software User Manual.
MFC after: 2 weeks
igb(4): Document identification LED device nodes
The shared em(4) manual page lists only the em device-node name.
Document the /dev/led/igb* name as well.
MFC after: 2 weeks
