summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
29 hoursImport latest mtree from NetBSDstable/15Jose Luis Duran
Merge commit '7e59b238fcf32f3d365e78ddc702ca494e1ff68d' This commit partially reverts the previous vendor import, given that the "type" keyword has been historically mandatory and should not be removed by "-R all". This was clarified in the man page. Reported by: glebius PR: 219467 MFC after: 1 week (cherry picked from commit 4250d2ad991b7bb9915e4c6b6d93b17369747ff0)
31 hoursGCE: ARM64 Support: Add hw.pci.honor_msi_blacklist=0.William Carrel
This is required for MSI support on GCE ARM64 instances which is prerequisite to gve(4) not panicking at boot, and nvme(4) also has a real sad time without interrupts. Tested on a variety of c4a VMs. This is meant to be a temporary hack; long term fix would be to check for the hypervisor and quirk gve(4) device with PCI_QUIRK_ENABLE_MSI_VM. PR: kern/292081 MFC after: 1 week (cherry picked from commit 9ae43352c89c776c8171f5881a984bc39acf5d6a)
2 daysnet80211: fix arguments to IEEE80211_NOTE in ieee80211_fix_rateYichen Chai
Fix the arguments to the debug statement. (slightly adjusted from the original submission by bz) PR: 286448 (cherry picked from commit 75556c7e999e9095ce71558ae61f49c1ba61a192)
2 daysLinuxKPI: pci: fix pcie_get_speed_cap()Bjoern A. Zeeb
pcie_get_speed_cap() has a hard coded skip of 3 devices at the beginning. It is either called on a pdev or on a result from pci_upstream_bridge(). In the latter case skipping another three devices might get us to acpi0 or nexus, neither of which is a PCI device still and pci_get_vendor() will panic() on that. Sponsored by: The FreeBSD Foundation (commit) GHI: https://github.com/freebsd/drm-kmod/issues/393 Differential Revision: https://reviews.freebsd.org/D53862 (cherry picked from commit fa24602ca6282d71c26079136a74b85824c0e63b)
2 daysiwlwifi/rtw89: improve module Makefile dependency on ACPIBjoern A. Zeeb
In order to compile iwlwifi(4) and rtw89(4) on RISC-V [1] make the currently manually tracked ACPI support option automatic based on DEV_ACPI. rtw89(4) is missing proper CONFIG_ACPI checks in the driver (or the mandatory dependency on ACPI) even upstream it seems. We just added that check to the modules/Makefile until this is fixed. [1] https://mail-archive.freebsd.org/cgi/getmsg.cgi?fetch=5947+0+archive/2026/freebsd-wireless/20260112.freebsd-wireless Sponosred by: The FreeBSD Foundation Reviewed by: emaste Differential Revision: https://reviews.freebsd.org/D54694 (cherry picked from commit f5a77dc8f8df09a907c2a2bdf86802513b1ebb15)
2 daysmodules: factor out LinuxKPI based wireless drivers and add RISC-VBjoern A. Zeeb
The LinuxKPI based wireless drivers are currently limited to amd64 and arm64 (and until cleaned up i386). Adding RISC-V now as we have a report that iwlwifi(4) works on RISC-V [1]. Factor the LinuxKPI based wireless drivers out into their own block. Given RISC-V has no ACPI support yet (though we fixed #includes in order to keep compiling the drivers without further modifications where possible) we need to take care of rtw89 which fails to compile without ACPI enabled. A quick check at the Linux build files indicates that the depenency is not correctly recorded there either. Disable compiling rtw89 without ACPI (on RISC-V) for the moment until this is fixed. [1] https://mail-archive.freebsd.org/cgi/getmsg.cgi?fetch=5947+0+archive/2026/freebsd-wireless/20260112.freebsd-wireless Sponsored by: The FreeBSD Foundation Reviewed by: emaste Differential Revision: https://reviews.freebsd.org/D54693 (cherry picked from commit 4162a419a475089c8a3d2350de40c58b023e9288)
2 daysLinuxKPI: include acpi headers for RISC-VBjoern A. Zeeb
In order to compile iwlwifi(4), which is reported to work on RISC-V, include the ACPI headers to avoid adding further FreeBSD-specific #ifdefs to the driver. With this iwlwifi(4) just compiles on RISC-V (at least if ACPI support is turned off in the module Makefile). Sponsored by: The FreeBSD Foundation Reviewed by: emaste Differential Revision: https://reviews.freebsd.org/D54692 (cherry picked from commit c71f18998e0b107845f2b627861225bf6156cda6)
2 daysriscv: add (a dummy) acpica_machdep.hBjoern A. Zeeb
We have reports that iwlwifi(4) works on RISC-V. While we can turn off full ACPI-specific files easily, intermittent code still relies on the header files to be present. In order to not need to completely #ifdef everything out we want to include acpi.h from LinuxKPI and as a result need this file. With this the iwlwifi(4) code compiles just fine and will do the right thing (given the functional ACPI parts are disabled/ unavailable). Sponsored by: The FreeBSD Foundation Reviewed by: mhorne, emaste Differential Revision: https://reviews.freebsd.org/D54691 (cherry picked from commit 0fa7b3bee72e7cfedabe371c7082fbf44508ec05)
3 daysdevice_delete_child should be destroying the child, not the devAZero13
MFC After: 1 week Reviewed by: imp, kib Pull Request: https://github.com/freebsd/freebsd-src/pull/1934 (cherry picked from commit 930a1341d62ccc4be969c2261e3abaf0c0573a9f)
3 daysiflib: remove convoluted custom zeroing codeBrooks Davis
Replace a collection of aliasing violations and ifdefs with memset (which now expands to __builtin_memset and should be quite reliably inlined.) The old code is hard to maintain as evidenced by the most recent change to if_pkt_info_t updating the defines, but not the zeroing code. Reviewed by: gallatin, erj Effort: CHERI upstreaming Sponsored by: Innovate UK Fixes: 43d7ee540efe ("iflib: support for transmit side nic KTLS offload") Differential Revision: https://reviews.freebsd.org/D54605 (cherry picked from commit 31e7dc6b9a000b02353bfc41cbd897533287cda2)
3 daysLinuxKPI: 802.11: fix rx_nss with VHTBjoern A. Zeeb
When fixing single-stream chipsets, like iwlwifi(4) AX101, we started masking the announced with the hardware supported values. This would probably limit, e.g., rx_nss. During these works we fixed a loop checking from the highest nss=7 to lowest nss=0 (8..1) and would set rx_nss if the stream was supported. This left us with always setting rx_nss on nss=0 to nss + 1 = 1. Instead only update once when we hit the first supported MCS value (highest number of supported streams). Looking at the diff of the mentioned commit hash which gets fixed it looks like even the old code was not correct either. This only fixes the logic to calculate rx_nss. This does not yet help with modern drivers to actually update the value. Code for this will come in a later commit. Sponsored by: The FreeBSD Foundation Fixes: adb4901ac9ae (cherry picked from commit 8494be1b5af7fe4f765532f802ac0a145e061d73)
3 daysLinuxKPI: 802.11: reset hdr after crypto in lkpi_80211_txq_tx_one()Bjoern A. Zeeb
When lkpi_80211_txq_tx_one() calls into the crypto offloading parts to possibly make space in the headroom, the beginning of our frame moves. We have to reset hdr after that call as otherwise later classifications based on the hdr->frame_control will fail or cause wrong classificaiton of packets. This makes sure frames will either be directly sent using (*mo_tx)() or use the correct tid for the correct queue. This helps to get rtwx8 packets flowing after BA was negotiated. Sponsored by: The FreeBSD Foundation Fixes: 11db70b6057e4 (cherry picked from commit f0395993e1ea83705e0da6623843e7d5d03f7269)
3 daysLinuxKPI: 802.11: assign sequence numbers to framesBjoern A. Zeeb
While all native drivers were converted to call ieee80211_output_seqno_assign() after changes to net80211 if needed, LinuxKPI 802.11 was not fixed. Add the missing call. Given we are currently only supporting STA mode, we can provide sequence numbers for all frames (mgmt/beacon would be a problem in AP mode). This greatly helps LinuxKPI based drivers other than iwlwifi(4). If drivers do their own sequence numbers, they will overwrite what we pre-set unless we would pass a txflag not to do so (beware the consequences). Sponsored by: The FreeBSD Foundation Fixes: eabcd1773fa3, 785edcc2af5a (cherry picked from commit 9cf85457b13bc7aa125388d63c82acf2b21e9e9e)
3 daysLinuxKPI: 802.11: add compat.linuxkpi.80211.IF.dump_stas_queuesBjoern A. Zeeb
Extend the normal compat.linuxkpi.80211.IF.dump_stas sysctl by queue information. This was helpful for debugging various issues, like selecting the outbound queue, stopping queues for BAR and helped finding multiple bugs. Sponsored by: The FreeBSD Foundation (cherry picked from commit 32ea8209825af594cbfa1fc654d45eb9a6aab528)
3 daysLinuxKPI: bitcount fix builds with gcc and older llvmBjoern A. Zeeb
LLVM before 19 and gcc before 14 do not support __builtin_popcountg(). Use __const_bitcount<n> from sys/bitcount.h as a replacement in these cases. This should still allow drm-kmod to build where the size needs to be known at compile-time. Remove the conditional for gcc around the iwlwifi modules build, which was collateral damage in all this. Sponsored by: The FreeBSD Foundation Fixes: 7cbc4d875971, 5e0a4859f28a Reviewed by: brooks, emaste (without the sys/modules/Makefile change) Differential Revision: https://reviews.freebsd.org/D54297 (cherry picked from commit 34892a8e30055000352d9612ad985be550c82bea)
3 dayssys/bitcount.h: add __const_bitcount<n>Bjoern A. Zeeb
Add a version of __const_bitcount<n> which can be used to get the numbers at compile-time when __builtin_popcountg() is not available (see sys/compat/linuxkpi/common/include/linux/bitops.h for LLVM before 19 and gcc before 14). Obtained from: https://reviews.freebsd.org/D50995#1174884 by obiwac Sponsored by: The FreeBSD Foundation Reviewed by: brooks, emaste Differential Revision: https://reviews.freebsd.org/D54301 (cherry picked from commit 27aa23cee81088b0ffa974eec9f03c654c36438e)
3 dayspowerpc: fix release image building for Apple partitionsAdrian Chadd
awk changed somewhere between 14 and 15 and it stopped accepting a hexadecimal number as its input - it will always return 0. This results in a very badly written apple boot block. So just remove it; do the math in shell. PR: kern/292341 Differential Revision: https://reviews.freebsd.org/D54639 Reviewed by: imp MFC after: 1 week (cherry picked from commit 7afa03963c448a14b1735a10eaf84941b0b74862)
4 dayslibarchive: merge from vendor branchMartin Matuska
libarchive 3.8.5 Important bugfixes: #2809 bsdtar: fix regression from 3.8.4 zero-length pattern issue bugfix Obtained from: libarchive Vendor commit: dd897a78c662a2c7a003e7ec158cea7909557bee MFC after: 1 week (cherry picked from commit 4b047c3af3fec1607ba1cfe04e1d442a17fc1cf6)
4 dayslibarchive: merge from vendor branchMartin Matuska
libarchive 3.8.4 Important bugfixes: #2787 bsdtar: Fix zero-length pattern issue #2797 lib: Fix regression introduced in libarchive 3.8.2 when walking enterable but unreadable directories Obtained from: libarchive Vendor commit: d114ceee6de08a7a60ff1209492ba38bf9436f79 MFC after: 1 week (cherry picked from commit c1e033c33e8b290cd40f4069249c879efcbae6a6)
4 dayslibarchive: merge from vendor branchMartin Matuska
libarchive 3.8.3 Important bugfixes: #2753 lib: Create temporary files in the target directory #2768 lha: Fix for an out-of-bounds buffer overrun when using p[H_LEVEL_OFFSET] #2769 7-zip: Fix a buffer overrun when reading truncated 7zip headers #2771 lz4 and zstd: Support both lz4 and zstd data with leading skippable frames Obtained from: libarchive Vendor commit: 1368b08875351df8aa268237b882c8f4ceb0882d MFC after: 1 week (cherry picked from commit 007679a138089676aadc9a712277f4004403b905)
4 daysmakefs.8: Cleanup man pageJose Luis Duran
Reviewed by: ziaee MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D54538 (cherry picked from commit 12c51484188f88bcabc5b38ca8523fcde76830a6)
4 daysmakefs: Fix typo 's/mirrorring/mirroring/'Jose Luis Duran
MFC after: 1 week (cherry picked from commit 73af599fb7be6806b553ac6f470d76711b74286c)
4 daysmakefs: tests: Fix timestamp-related testsJose Luis Duran
Use a variable for mtree that includes the DEFAULT_MTREE_KEYWORDS, in order to avoid missing the important "time" keyword or passing an unimplemented "nlink" keyword. Unskip the "failing" tests, and comment out the specific failing checks, these will be addressed (or at least discussed) in a different revision. For MS-DOS tests, use an even value timestamp, as precision is 2s. For ZFS tests, use import_image instead of mount_image consistently. Reviewed by: bnovkov, markj MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D54429 (cherry picked from commit 93b15dbc1fbc3c33c9bd53091b28c3b629d0abe1)
4 daysmakefs: tests: Fix -D flag testJose Luis Duran
As stated in the manual page: -F is almost certainly not the option you are looking for. To create an image from a list of files in an mtree format manifest, specify it as the last argument on the command line, not as the argument to -F. This change does exactly that. Also bug #192839 has already been fixed. Reviewed by: ngie MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D54428 (cherry picked from commit 96efda9cd55689ef3fa067281d8b0a42a7122536)
4 daysmakefs: tests: Cleanup and remove default flagsJose Luis Duran
Cleanup and remove default atf_check flags for clarity. The following two lines are equivalent: atf_check $cmd atf_check -s exit:0 -e empty -o empty $cmd Update the links to the reference documents. Remove the D_flag_cleanup function, as common_cleanup() for these particular set of tests does two things: 1. Unmount the md(4) device. 2. Destroy the md(4) device. Essentially, one should only call common_cleanup() if the test body invokes mount_image(). This is not the case for D_flag_body(). No functional changes intended. Reviewed by: ngie MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D54427 (cherry picked from commit 0a6deb87c2802a47709c58d09b5f9122ed40c157)
4 daysmakefs: tests: Double the timeout of ZFS file_extend testJose Luis Duran
The test makefs_zfs_tests:file_extend is timing out on ci.freebsd.org. Double the default timeout to allow it to finish. Reported by: Jenkins Reviewed by: asomers MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D54425 (cherry picked from commit 065f02174f76a49fbf537ee51ed8068d3d398b08)
4 daysmakefs: tests: Double the timeout of ZFS compression testJose Luis Duran
The test makefs_zfs_tests:compression is timing out on ci.freebsd.org. Double the default timeout to allow it to finish. While here, check if the file exists before cleaning up, otherwise, cat may fail. Reported by: Jenkins Reviewed by: asomers MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D54424 (cherry picked from commit 9f28e92637e9a29124f407b74d7665a921865a53)
4 daysmakefs/tests: Use require.kmods property instead of ad-hoc checksSiva Mahadevan
Signed-off-by: Siva Mahadevan <me@svmhdvn.name> MFC after: 3 days Sponsored by: The FreeBSD Foundation Pull Request: https://github.com/freebsd/freebsd-src/pull/1870 (cherry picked from commit 2cd31bd8fa687922d2a571ae53456ecd2e9ba095)
4 daysbsd.man.mk fix and simplify stagingSimon J. Gerraty
The STAGE_SETS need to match STAGE_DIR. For each STAGE_SET we have STAGE_DIR.${STAGE_SET} and create a target stage_files.${STAGE_SET}, the settings all need to be self consistent to work. We actually only need the high level targets stage_files and stage_links meta.stage.mk will take care of the details. (cherry picked from commit 9cd89fc5aa3c0e76375732788fe9d4282d65224f) (cherry picked from commit 9fed072b44223f061a0dbf604741091b3bc09aee)
4 daysEC2: Add extra SSM Parameter names for releasesColin Percival
Record releases in the SSM Parameter Store not just as e.g. /aws/service/freebsd/arm64/small/ufs/15.0/RELEASE but also as .../RELEASE/latest, e.g. /aws/service/freebsd/arm64/small/ufs/15.0/RELEASE/latest The latter parameters will be updated when new AMIs are built with security and errata updates appplied, and have been backfilled for 15.0. MFC after: 3 days MFC to: stable/15 (14.x will not get security-update AMIs) Sponsored by: Amazon (cherry picked from commit b558c92fd0005d311edbcd02953c17d4a34fb909)
5 dayspci_vendors: update to version 2025-12-12Baptiste Daroussin
(cherry picked from commit 3b8e13c4696e9b3dab284842902b9f7b18073c8d)
5 dayspci_vendors: update to 2025-10-18Baptiste Daroussin
(cherry picked from commit e5f545e0d872fbfdb6c3c94ca81e7f3bce9d094a)
5 daysusb_vendors: update to 2025-09-15Baptiste Daroussin
(cherry picked from commit 90cd623611b22e2e484b800743845b38d9c20250)
5 daysrelease: make sh the default shellBaptiste Daroussin
The default shell for root has been changed to sh(1) followup changing in release images sh(1) the shell for the "freebsd" user. MFC After: 1 week Reviewed by: manu, emaste (re) Approved by: manu, emaste (re) Differential Revision: https://reviews.freebsd.org/D54602 (cherry picked from commit d64db8892f8519f108d838f8d7e1d3b675ed37cd)
5 daysnuageinit: set the hostname when user-data is missingGonéri Le Bouder
This address the situation reported here https://github.com/freebsd/freebsd-src/pull/1952#issuecomment-3720210259 The user-data file was missing and the `sethostname` function is never called. This commit adjusts slightly the logic to avoid the `exit()` call when the `user-data` file is missing. MFC After: 1 week Signed-off-by: Gonéri Le Bouder <goneri@lebouder.net> Differential Revision: https://github.com/freebsd/freebsd-src/pull/1953 (cherry picked from commit cae280931c9e1f072d8bf300c377ae120300b898)
5 daysnuageinit: fix test after recent behaviour changeBaptiste Daroussin
with recent change nuageinit always create a "freebsd" user, if no users are specified, which means we do need to get the rootdir in the testsuite containing a group file otherwise pw complains and the tests fails. (cherry picked from commit 65e77d34fdff9065616cfaedef3ef53329cdad26)
5 daysrelease: stop disabling sendmailBaptiste Daroussin
sendmail is already disabled by default everywhere since 14.0 MFC After: 1 week Approved by: emaste (re) Reviewed by: emaste (re) Differential Revision: https://reviews.freebsd.org/D54575 (cherry picked from commit d07198ff72aeddc5a884cfb81b22c22f2abf88f6)
5 daysnuageinit: only create the default user when neededGonéri Le Bouder
The "default" user should only be created when: - the `users` key is missing - or the `default` string is present in the `users` list Since the `public_keys` is extracted from the meta-data, this patch has to slightly adjust the way they are loaded. The change simplify the logic around the default user SSH key injection. Both `ssh_authorized_keys` and `public_keys` are handled at the same time. MFC After: 1 week Signed-off-by: Gonéri Le Bouder <goneri@lebouder.net> Pull Request: https://github.com/freebsd/freebsd-src/pull/1952 (cherry picked from commit cbc00fcc2b92e6e38b0a180261547b1a22b461bd)
5 daysnuageinit(7): pert mandoc linterBaptiste Daroussin
MFC After: 1 week (cherry picked from commit 9ea30bbb0e3c34b3ea369e217d930e2165610c0c)
5 daysnuageinit: config2_network support dns service cfgGonéri Le Bouder
This change enhances `config2_network()` to honor the DNS configuration, when it's defined through the `services` section. The `network_data.json` file can hold DNS configuration at two different places: - within a network configuration entry - or `dns` entry in the `services` section, in this case the configuration is global. An example of such configuration: {"links": [{"id": "interface0", "type": "phy", "ethernet_mac_address": "52:54:00:01:59:03"}], "networks": [{"id": "private-ipv4-0", "type": "ipv4", "link": "interface0", "ip_address": "192.168.123.5", "netmask": "255.255.255.0", "routes": [{"network": "0.0.0.0", "netmask": "0.0.0.0", "gateway": "192.168.123.1"}], "network_id": "9e5b1ed9-f5e6-4941-a90f-2e06bab858de", "dns_nameservers": ["192.168.123.1"], "services": [{"type": "dns", "address": "192.168.123.1"}]}], "services": [{"type": "dns", "address": "192.168.123.1"}]} See: https://docs.openstack.org/nova/latest/user/metadata.html MFC After: 1 week Signed-off-by: Gonéri Le Bouder <goneri@lebouder.net> Pull Request: https://github.com/freebsd/freebsd-src/pull/1941 (cherry picked from commit 7af8b75201b7af353fa74c8feb937b52f5ccf9bb)
5 daysnuageinit/man: clarify how to enable sudo and doasGonéri Le Bouder
Clarify that both `sudo` and `doas` are not part of the base system and they need to be listed in the `packages` section if the user wants to enable them. MFC After: 1 week Signed-off-by: Gonéri Le Bouder <goneri@lebouder.net> Pull Request: https://github.com/freebsd/freebsd-src/pull/1944 (cherry picked from commit 402f1353707783e2adc8d0bff01faf557820f6f5)
5 daysncurses: readd "bsdpads"Baptiste Daroussin
During the import of ncurses 6.5 some bsd specifics configuration where lost and reintroduce quickly after the import, unfortunatly there was a typo in this fix which caused the "bsdpads" to not be enabled in ncurses. Fortunatly only very old programs may be affected by this change, unfortunatly Nethack (in the ports tree is one of them.) PR: 287358 MFC After: 3 days (cherry picked from commit 836a0d46320c18d83029bf138b630b6ce5ebe6ae)
6 daysloader.efi: Only use SPCR if enabled.Jarmo Jaakkola
SerialPort in the SPCR is zeroed when serial redirection is disabled, rather than the SPCR being omitted from the ACPI tables ony many systems. Check to see that SerialPort.Address is non-zero before using. FreeBSD would fail to boot on systems that could have a serial port redireciton, but don't have it enabled because the loader would create a bogus hw.uart.console. While one could unset this value to boot, you couldn't do that automatically very easily. Instead, don't even look at the SPCR table if the SerialPort is zero'd. PR: 292206 MFC After: 3 days Sponsored by: Netflix Co-authored-by: Warner Losh <imp@FreeBSD.org> Closes: https://github.com/freebsd/freebsd-src/pull/1948 (cherry picked from commit d82698ac68c23d856716dc9f6524b9ef363d7eba)
6 daysstand: Try to parse vdisk correctlyWarner Losh
PR: 289306 Sponsored by: Netflix Reviewed by: dab MFC After: 5 days Differential Revision: https://reviews.freebsd.org/D52500 (cherry picked from commit d18ed8e19c3cb264340987bdc191615108d8413a)
6 daysarm64: Correctly align the SVE signal contextAndrew Turner
The SVE signal context needs to be correctly aligned. Fix this by creating a new macro to calculate the needed size to provide this alignment, and use it when setting and checking the saved SVE signal context. Reported by: cperciva Reviewed by: cperciva, markj Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D54396 (cherry picked from commit a9e77eb7016df70723c208fc09fbd01ec23a732d)
6 daysarm64: Switch to gic_get_support_lpis in gicv3_itsAndrew Turner
The old gicv3_get_support_lpis will be removed. Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D53664 (cherry picked from commit 3ef673e98af669b5cf4e496bb2a1aab9020c480d)
6 daysarm/gic: Make GICV3_IVAR_SUPPORT_LPIS genericAndrew Turner
GICv5 will need this too, so move to the GIC_IVAR namespace. Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D53663 (cherry picked from commit 8178a4e3c13241804bb9625b2ef4c1b3fea3c7d9)
6 daysarm: Handle GIC_IVAR_VGIC in the gic driverAndrew Turner
We don't have a GICv2 vgic so can just return 0. Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D53662 (cherry picked from commit 262fadda370001eed2fd1a72592d79dbd533c650)
6 daysarm64: Add non-PCI MSI supportAndrew Turner
Add the arm64 parts to support for non-PCI MSI and MSI-X interrupts. Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D53331 (cherry picked from commit 4713f54013176fc73ada29cf094016fd3b328c80)
6 daysdev/fdt: Add support for non-PCI MSI interruptsAndrew Turner
Some non-PCI devices can send interrupts, e.g. the Arm SMMU or GICv5 Interrupt Wire Bridge. Add support for these by implementing pci_get_id and pci_alloc_msi and the MSI/MSI-X parts of the PCIB interface. Only the MSI parts of the PCI interface are added as that is all I am able to test. Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D53330 (cherry picked from commit 68e6422c6c91170a615e77028683a157e8e39d05)
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-19 09:26:09 +0000