Changes in files

551b7c5e12bfea623a47edf97ad5689732a1233f - rtwn: add support for the RTL8723BU

Tue, 01 Sep 2026 23:07:59 +0200

rtwn: add support for the RTL8723BUPushed using the RTL8723BU.Reviewed by: ziaee, avos, adrianRelnotes: yesDifferential Revision: https://reviews.freebsd.org/D59205 List of files: /freebsd/sys/conf/files

9c9428825f4c55e3cb37412c661bb9d385db4c68 - video: add generic video(4) capture framework

Sun, 09 Aug 2026 18:48:13 +0200

video: add generic video(4) capture frameworkAdd a new video(4) framework that provides /dev/videoN, buffermanagement, mmap lifetime, and V4L2 ioctl dispatch for video capturedrivers. Hardware drivers implement struct video_hw_ops callbacksand use video_buf_acquire/write/done to deliver frames.Reviewed by: adrianDifferential Revision: https://reviews.freebsd.org/D58367 List of files: /freebsd/sys/conf/files

295f10230903d54c700518467c4ea4492f5c4faa - exterror(9): dynamic kernel categories

Mon, 03 Aug 2026 18:50:01 +0200

exterror(9): dynamic kernel categoriesMake it possible to define categories without compiling theirpaths into libc (important for third-party modules). TheEXTERR_CATEGORY_DYNAMIC macro can be defined to a string describing thecompilation unit (generally the path relative to src/sys) which takesthe place of EXTERR_CATEGORY.These strings are assembled in linker sets with category numbersassigned at system startup or module load time. The strings can beretrieved from the kern.exterr.categories. sysctl.Reviewed by: kibSponsored by: Innovate UKDifferential Revision: https://reviews.freebsd.org/D58237 List of files: /freebsd/sys/conf/files

316f6f2f7fa613d13316ea966a34ee5285b987ec - igbv: Isolate VF policy and validate its registers

Thu, 30 Jul 2026 06:05:47 +0200

igbv: Isolate VF policy and validate its registersGive igb virtual functions a separate ifdi method table and moveVF-specific attach, reset, queue, interrupt, and diagnostic policy toif_igbv.c. Keep shared descriptor-ring mechanisms in if_em.c.Derive VF identity from IFLIB_IS_VF and assert that hardwareidentification agrees. Under INVARIANTS, validate normal VF CSRaccesses against the sparse 82576 and I350 VF register maps.Stop shared setup from accessing PF-only controls. Require MSI-X anddefer VF sysctls until attach succeeds so failed attachment cannotleave handlers pointing at freed driver state.Advertise only VF capabilities, run adaptive moderation without thePF receive-buffer guard, enable SRRCTL.DROP_EN, and provide a VF-safediagnostic register view.The moved implementation is the existing FreeBSD code. Register modelwas cross-checked against the Intel datasheets and other Intel drivers.Sponsored by: BBOX.io List of files: /freebsd/sys/conf/files

a2ed165f0049595f2e52ec545095240e362f27c7 - igb: Add SR-IOV PF support for 82576 and I350

Tue, 28 Jul 2026 23:56:33 +0200

igb: Add SR-IOV PF support for 82576 and I350Add the PCI IOV schema and PF control plane for up to seven VFs withone hardware queue per pool. Implement VF mailbox handling, MAC andVLAN assignment, multicast filtering, promiscuity policy,anti-spoofing, malicious-driver recovery, reset replay, and queuelifecycle management.The basic SR-IOV and VMDq PF implementation follows DPDK Intel e1000code, including PF pool selection, one queue per pool, mailboxdispatch, and VF enablement. Intel FreeBSD igb-2.5.31 supplies theolder driver baseline. Linux igb and the Intel SDMs clear up lifecycle,isolation, reset, and family-specific details absent from DPDK.Enabling IOV requires the PF to attach with one TX and RX queue.Systems whose defaults select RSS queues must set the documented iflibqueue override tunables before attach.Only 82576 and I350 support SR-IOV in silicon. The series has beenextensively tested on I350, including thowing boundaries at the PCI BARthat shipping drivers will never. Still, think carefully beforereaching for this in critical environments.Relnotes: yesSponsored by: BBOX.io List of files: /freebsd/sys/conf/files

5f74217c05a99f38a31a6e4950220964595d4ac8 - coreboot: Add coreboot firmware table driver

Wed, 29 Jul 2026 21:11:55 +0200

coreboot: Add coreboot firmware table driverNexus-attached driver that discovers and parses coreboot's LBIO tablesfrom physical memory. Exposes firmware metadata (version, build info,mainboard, serial config, TSC frequency, CBMEM entries) via sysctlhw.coreboot.*, the firmware console ring buffer via /dev/coreboot_console,and structured CBMEM entry access via /dev/cbmem ioctl interface.Tested on:- Qotom Q535G6 (Kabylake)- Intel NUC D54250WYK (Haswell)- Intel NUC D33217GKE (Ivy Bridge)- Dell 3100 2-in-1 (Gabbiter)- Dell 3100 (Fleex)- Lenovo IdeaPad 320s- Lenovo ThinkPad T480- HP Chromebook 11 G4- HP Chromebook 11 G5- HP Chromebook 11 G6 EE- HP Chromebook 14 G4- HP Chromebook 14 G5- HP Chromebook x360 11 G1 EE- HP Chromebook x360 11 G2 EE- HP Chromebook x360 14 G1- Acer C720- Acer Chromebook 11- Lenovo N22Reviewed by: ngie, kib, adrianDifferential Revision: https://reviews.freebsd.org/D55649 List of files: /freebsd/sys/conf/files

e591a76621430d6d29f2580e2dec8991e450ed5e - LinuxKPI: page pool updates and add to the build

Sat, 18 Jul 2026 13:54:42 +0200

LinuxKPI: page pool updates and add to the buildSplit implementation out from the header files.This "page pool" is the very minimalistic version we need in order tosupport packets on mt76.We allocate the page pool in order to have the meta data available ofwhich we only make limited use.This implementation does no pooling, it does no page fragments for now,it always hands out a full page and frees it upon return.It is written in a way that it can be in the tree before the 'struct page'work it depends on has landed in order to reduce friction for people whowant to try mt7921 (or others later) upfront. We use the same #ifdefas in the struct page work for that reason so one knob will turn everythingon or off.Once the struct page work has landed and settled we can start filling thiswith more complexity.In the unlikely event that in the mean time any other consumer would startshowing up they will have to be aware that the current code as-isessentially is a NOP without the 'struct page' work. A WARN_ONCE() willnotify them.Sponsored by: The FreeBSD FoundationMFC after: 3 days List of files: /freebsd/sys/conf/files

dc5c0fc51cf47d6dfc737343e06805db294258e9 - aq(4): add Atlantic 2 (AQC113) device support

Sun, 19 Jul 2026 18:48:05 +0200

aq(4): add Atlantic 2 (AQC113) device supportAdd support for the Marvell Atlantic 2 (AQC113/114/115/116) controllers,a new chip generation that is not register-compatible with the Atlantic 1parts aq(4) supports today. Adapted from the OpenBSD/NetBSD if_aq driver.Register and device definitions (aq2_hw.h): the firmware handshake(MIF_BOOT / MCP_HOST_REQ_INT / MIF_HOST_FINISHED), the 0x12000/0x13000firmware interface windows, and the action-resolver table (ART) thatreplaces Atlantic 1's discrete RX filters, plus the Atlantic 2 PCI deviceids and the aq_is_atlantic2() helper. Reserve a chip-feature bit(AQ_HW_CHIP_ATLANTIC2) and add the aq_hw fields the firmware fills at boot(ART base index, statistics interface version A0/B0). The per-VLAN-filterresolver-tag field comes from the Linux driver; the BSD sources neverwrite it.Firmware operations (aq_fwa2.c): Atlantic 2 talks to the management CPUthrough the 0x12000/0x13000 register windows plus the boot handshake,rather than Atlantic 1's mailbox in shared RAM. Implement that as a thirdaq_firmware_ops vtable (reset, set_mode, get_mode, get_mac_addr,get_stats); aq_fwa2_reboot() boots the firmware, selects the A2 ops, andreads the version and ART base index, failing fast on thecrash-init / boot-failed bits. fwa2_set_mode advertises full duplex only(the media model exposes no half-duplex types) and writes and acks thelink options before raising ACTIVE mode, so a forced media change does notbegin negotiation with a stale rate mask. enum aq_fw_link_speed gainsaq_fw_10M, which Atlantic 2 supports and Atlantic 1 does not.Probe and attach: list the device ids with their media types and linkspeeds (all copper; AQC113* up to 10G, AQC116C to 1G), populatehw->device_id, and tag the generation with AQ_HW_CHIP_ATLANTIC2 soIS_CHIP_FEATURE() recognises it uniformly. Branch firmware bring-up andreset on the generation: aq_hw_init_ucp() and aq_hw_reset() reboot the MCPinstead of the Atlantic 1 RBL/FLB reset -- without a real datapath resetevery stop/init cycle reprograms the rings on a live, desynced RX DMAengine and the receive path stays dead. aq_hw_init() programs theAtlantic 2 launch-time clock ratio in place of the Atlantic 1MRRS / TX-DMA request-limit clamp. Add an AQ_LINK_10M capability bit(Atlantic 2 links at 10M, Atlantic 1 cannot), offer 10baseT media, and mapIFM_10_T to aq_fw_10M.With every supported media type now present, replace the per-speed switchstatements in aq_media.c with a single {link bit, fw rate, IFM_* subtype,Mbit/s} table -- one source of truth for the supported link speeds.With this an Atlantic 2 card probes, brings up its firmware, reads itsMAC, and negotiates link; the RX action-resolver datapath comes next.Reviewed by: adrianDifferential Revision: https://reviews.freebsd.org/D58141 List of files: /freebsd/sys/conf/files

4085d1991e2a9e155e3d928955ce8ba53512b8da - hidwacom: Add Wacom ExpressKey Remote driver

Sun, 12 Jul 2026 19:11:07 +0200

hidwacom: Add Wacom ExpressKey Remote driverThe Wacom ExpressKey Remote (ACK-411050) is a wireless button padwith 18 programmable buttons and a touch ring, used as a companiondevice with Wacom tablets.It communicates via a USB wireless receiver (0x056a:0x0331) using avendor-specific HID report (ID 0x11).This driver exposes the device via evdev: - 18 buttons: BTN_0–BTN_Z, BTN_BASE, BTN_BASE2 - Touch ring position via ABS_WHEEL (0–71; reports 0 on release) - Pad activity marker via ABS_MISC (set to 15/PAD_DEVICE_ID when any input is active, 0 when idle that matches Linux wacom driver convention) - Remote serial number via MSC_SERIAL (for userland per-remote identification)Battery level, charging state, and touch ring mode (3 LEDs, values 0–2)are exposed as per-device sysctls (dev.hidwacom.0.battery, .charging,.ring_mode) rather than overloading evdev misc codes. The ring modesysctl is preserved across device idle periods.Protocol was decoded from USB traffic analysis and cross-referencedagainst the Linux wacom_remote_irq() implementation indrivers/hid/wacom_wac.c.Reviewed by: adrianDifferential Revision: https://reviews.freebsd.org/D56729Discussed with: ziaee List of files: /freebsd/sys/conf/files

23a6997e3071cea8d8fc5238792fdd0ad5b5dc9a - fwdv: add AV/C DV capture driver for FireWire camcorders

Sun, 12 Jul 2026 17:25:52 +0200

fwdv: add AV/C DV capture driver for FireWire camcordersAdd fwdv(4) driver for DV video capture from FireWire camcordersusing AV/C protocol and isochronous streaming.Supports AV/C tape transport commands (play, stop, ff, rewind, pause,record, eject) with NTSC/PAL auto-detection and read(2) interfacefor frame capture.Reviewed by: adrianDifferential Revision: https://reviews.freebsd.org/D58122 List of files: /freebsd/sys/conf/files

e2d56447b3a9d2ef9bd0b80c3aaa69e681f4be0f - hrfkill: Add driver to report RFKILL button press

Thu, 25 Jun 2026 04:03:36 +0200

hrfkill: Add driver to report RFKILL button pressThis driver only reports the RFKILL button presses.This is needed for the "airplane" key on some Framework laptops.Reviewed by: wulf, ziaeeEvent: Halifax Hackathon 202606Location: vishwin@'s carCo-authored-by: Daniel ShaeferSponsored by: Framework Computer IncSponsored by: The FreeBSD FoundationDifferential Revision: https://reviews.freebsd.org/D57838 List of files: /freebsd/sys/conf/files

cd7b65080f2f2e038ddba42048f24f8e98b011f2 - fwisound: add Apple FireWire audio driver

Thu, 09 Jul 2026 04:52:43 +0200

fwisound: add Apple FireWire audio driverExpose audio capture from Apple FireWire devices as a standardpcm(4)/dsp(4) device via the newpcm framework.(adrian: I've tested this on an isight camera and loopedit back to USB speakers via "sox -t oss /dev/dsp3 -t oss /dev/dsp4")Reviewed by: adrianDifferential Revision: https://reviews.freebsd.org/D58109 List of files: /freebsd/sys/conf/files

9313f6b01485ad9a0b7cc59b459f5714533587c3 - acpi: Add a pseudo-bus for APEI devices to manage resources

Tue, 07 Jul 2026 20:13:51 +0200

acpi: Add a pseudo-bus for APEI devices to manage resourcesDifferent APEI tables can reuse the same registers (and sometimesdifferent views of the same register, e.g. 32- vs 64-bit mappings ofthe same register). To enable this sharing, apei0 now acts as a busdevice managing a pool of allocated resources and handing out mappingsto child devices which handle individual tables.Most of the previous apei(4) driver has been moved into a newhest0 device that is a child of apei0.Reviewed by: gallatinSponsored by: NetflixDifferential Revision: https://reviews.freebsd.org/D58024 List of files: /freebsd/sys/conf/files

40e05479718460820cd24c22e59519a4f13eba3d - fwcam: add IIDC 1394 FireWire camera driver

Thu, 25 Jun 2026 04:14:22 +0200

fwcam: add IIDC 1394 FireWire camera driverAdd fwcam(4), a driver for IIDC v1.30 (TA Document 1999023) digitalcameras over IEEE 1394.Supports Format_0 (VGA) video modes with isochronous receive DMA,feature control (brightness, exposure, gain, shutter, white balance,focus, etc.), poll/kqueue, and hot-plug via bus reset handling.Reviewed by: adrianDifferential Revision: https://reviews.freebsd.org/D57685 List of files: /freebsd/sys/conf/files

b711ef9c75ba71d6258d028aaf7b119ccfffaa0a - uvideo: import uvideo(4) driver from OpenBSD

Tue, 05 May 2026 22:29:47 +0200

uvideo: import uvideo(4) driver from OpenBSDPort the uvideo(4) driver from OpenBSD. This providesnative USB Video Class (UVC) support for webcams and video capturedevices.The main changes are adaptation for:- USB transfer callback model- isoc data extraction via usbd_copy_out(),- V4L2 struct alignment for ABI compatibility with v4l_compat.Note that this implementation can coexist with webcamd.Reviewed by: manuDifferential Revision: https://reviews.freebsd.org/D56960 List of files: /freebsd/sys/conf/files

9931dc5bf3831146c08a381c42ecbfcedb8ac7f1 - if_bnxt: add few source files to version control

Mon, 15 Jun 2026 16:30:26 +0200

if_bnxt: add few source files to version controlCommits- f85e66e655c9 ("if_bnxt/bnxt_re: add support for driver snapdump")and 03839879a2dd ("if_bnxt: Add Firmware crashdump collection support")missed to add few files under version control, those files areadded now:sys/dev/bnxt/bnxt_en/bnxt_log.csys/dev/bnxt/bnxt_en/bnxt_log.hsys/dev/bnxt/bnxt_en/bnxt_log_data.csys/dev/bnxt/bnxt_en/bnxt_log_data.hsys/dev/bnxt/bnxt_en/bnxt_coredump.csys/dev/bnxt/bnxt_en/bnxt_coredump.hbnxt_coredump.c entry is added in sys/conf/files as well.Fixes: f85e66e655c9 ("if_bnxt/bnxt_re: add support for driver snapdump")Fixes: 03839879a2dd ("if_bnxt: Add Firmware crashdump collection support") List of files: /freebsd/sys/conf/files

03676cafa882c471a29436aae76c8751d451dd07 - if_bnxt: add bnxt logger module files to sys/conf/files for built-in kernel builds

Mon, 15 Jun 2026 14:22:25 +0200

if_bnxt: add bnxt logger module files to sys/conf/files for built-in kernel buildsThe bnxt snapdump and coredump support patches added bnxt_log/{_data}.c. and listed it insys/modules/bnxt/bnxt_en/Makefile, but missed to add these files in sys/conf/files.Fix up the issue by adding bnxt_log/{_data}.c in sys/conf/files.Fixes: f85e66e655c9 ("if_bnxt/bnxt_re: add support for driver snapdump") List of files: /freebsd/sys/conf/files

d9497217456002b0ddad3cd319570d0b098daa29 - zfs: merge openzfs/zfs@a170134fe

Sat, 06 Jun 2026 22:48:32 +0200

zfs: merge openzfs/zfs@a170134feNotable upstream pull request merges: #18372 eaaea55b6 Consistently encode DRR_BEGIN packed nvlist payloads with NV_ENCODE_XDR #18410 891e379d0 Fix failfast default and usage #18470 a2d053329 zdb: Add some more file layout output, triggered by -v #18472 d50f5b6d0 dsl_dir: avoid dd_lock during snapshots_changed updates #18493 d65015938 Vdev allocation bias/class change #18497 8fdc86675 zfs: annotate nested dd_lock in reservation sync accounting #18494 956deba27 zdb: detect BRT and DDT leaks during block traversal #18499 c7cfe0805 zarcstat: detect attached L2ARC device with no data #18503 439b802e7 sa: fix sa_add_projid lock ordering #18508 968f4db03 zpool-attach.8: add EXAMPLES section #18513 45dddc452 zfs.4: Fix documentation of zfs_arc_dnode_reduce_percent #18516 8ff64005a zap: split implementation out into more files #18520 181e1b522 Fix double free for blocks cloned after DDT prune #18535 -multiple zstream: fix crashes when refcount tracking enabled #18536 -multiple refcount tag fixups #18541 a65ed7afd zpool/zfs: accept --help and -? after a subcommand #18544 6fb72fda0 zio_ddt_write: compute have_dvas after taking dde_io_lock #18546 -multiple zap: internal locking uplift #18550 40a87651d zap_impl: use flex array field for mzap_phys_t.mz_chunks #18551 -multiple zap: make the _by_dnode() op variants be the primary implementation #18570 112b0131b zpl_xattr: stop heap-allocating prefixed xattr names #18578 4bc8c39b6 zed: Prefer dRAID distributed spares to regular ones #18596 e30ab5fa4 FreeBSD: Make it possible to build openzfs.ko with sanitizers #18597 472ddca11 zed: Prefer spares with matching rotational and size #18599 c90dc2808 enforce exact decompressed length for lz4, gzip, and zstd #18603 -multiple zap: add zap_cursor_init_by_dnode; cursor unit tests; mock dnode refcounts #18604 59dc88602 nvpair: Check for un-terminated strings in packed nvlist #18606 ef6f26145 When reading a vdev label skip libzfs_core_init() #18613 0aa4088dc sharenfs: Check for invalid characters #18615 80fb85b80 Fix the integer type in zfs_ioc_userspace_many() #18616 e199f6d98 Fix uninitialized variable warning in vdev_prop_get() #18617 7de42602c Extend dataset zfs_ioc_set_prop() secpolicy #18622 5fea0c838 Parallelize metaslab_sync_done() calls #18623 cab50d5ad Add additional verification of size fields and strings #18630 -multiple zap: misc function removal / uplift / tests #18633 a8ef128da Fix uninitialized variable warning in zil_parse()Obtained from: OpenZFSOpenZFS commit: a170134febea405c6b6f5ed51724cdcfb6d8e726 List of files: /freebsd/sys/conf/files

11d69a4558de2a5427d8191caed315c5f7e9a5d6 - LinuxKPI: 802.11: add support for suspend/resume

Wed, 09 Apr 2025 20:00:20 +0200

LinuxKPI: 802.11: add support for suspend/resumeAdd support for automatic suspend/resume as we know it for wireless.The problem is that the PCI driver which would normally gets the codeis the LinuxKPI PCI framework/Linux wireless driver, which we cannotammend or generally add extra suspend/resume code to.A further problem is that with growing support, the LinuxKPI 802.11(mac80211) layer also is involved in suspend/resume for WoWLAN (notyet supported) meaning that we need to hook the suspend/resumeframework into that as well. Unlike Linux we do not have a generalsuspend/resume "hook" we can hang into and we need to tie this oneto the hardware so cannot indepedently (after the driver one) run it.The solution for FreeBSD, in order to not mangle the Linux nativedrivers and get extra maintanace overhead, is to add a bus childwhich inherits the general framework and thus is 2 lines + #includesfor each driver extra to add to.The general suspend/resume framework lives in LinuxKPI (linuxkpi_80211_pm)and imitates the normal suspend/resume path overloading it (there isa slight code/logic duplication from the PCI code).Given we are passed the LinuxKPI p(ci)dev, we can go and peel out thenet80211 ic from the native bsddev and that way get access to thewireless stack. We then call into LinuxKPI 802.11 in order to dothe suspend/resume dance there, and, if needed also call theofficial suspend/resume routine from the device driver after(reverse for resume).If any in this fails, suspend will be blocked as we will return theerror (no different to any native driver could do).The LinuxKPI 802.11 suspend/resume code has the initial code fordoing a WoWLAN suspend (one could change the sysctl) but other bitslike access to ifnet flags etc. has to be sorted out before we cango and support that.The default code path calles into net80211 to clear everythinglike native wireless drivers do. The one thing we need to do inaddition is to remove the vif devices from the firmware and restorethem prior to net80211 resume.We also check for a possible HW SCAN to still be runinng on resumeand warn as that may cause problems though the scan should be stoppedbefore suspend (we may still get a callback). You can easily seethese problems if you suspend/resume without stopping the wlan.Enable the PM framework for iwlwifi in the module Makefile tobe able to use all this; others can follow as tested.In case anyone has problems with this, they can change the sysctlback to 0 until we can figure out any further problems.The linuxkpi_wlan.4 man page got adjusted to document this.Sponsored by: The FreeBSD FoundationTested on: Dell XPS 13 (AX200), Lenovo TP X270 (AX210)MFC after: 3 daysPR: 263632 List of files: /freebsd/sys/conf/files

cd3cc6e910c0f739925c57e42fae6781d693db02 - i2c/sensors: Add driver for W83793 hardware monitor

Wed, 20 May 2026 04:04:30 +0200

i2c/sensors: Add driver for W83793 hardware monitorThe Winbond/Nuvoton W83793G system monitor chip includes many featuresnot currently supported by this driver. The following are currentlysupported:* Up to 6 temperature sensors, 4 of which have 10-bit resolution (8.2),two with 8-bit resolution (no decimal component)* Up to 12 fans - Fans 0-4 (1-5 on the datasheet) are always enabled. The remaining 7 fans are individually enabled.* Multiple voltage sensors, reading up to 10 voltage sources. Sysctls are labeled to match the datasheet.* Chassis open detection.The W83793AG is a feature-reduced version, which lacks 3 thermal diodesand 2 voltage monitors. Since there is no way to tell the differencebetween the W83793AG and W83793G programmatically, sensors reported onthe W83793AG will report strange values.Temperature sensors and 7 of the fans can be individually enabled on thechip, but currently not configured by this driver. The driver onlyreports what was configured by the firmware. Additionally, this drivernumbers the sensors and fans according to the datasheet, so even if, forinstance, fan 8 is disabled, it would skip from fan 7 to fan 9, it doesnot renumber. This makes it easier to follow for hardware debuggingpurposes.Missing features:* Smart Fan support* Fan PWM control* ASF (Alert Standard Format)Only Bank 0 registers are used at this time.Reviewed by: adrianDifferential Revision: https://reviews.freebsd.org/D56776 List of files: /freebsd/sys/conf/files