Page MenuHomeFreeBSD

arm: Set NEW_PCIB in DEFAULTS rather than a subset of kernel configs
ClosedPublic

Authored by jrtc27 on Feb 9 2024, 7:31 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Apr 27, 8:06 AM
Unknown Object (File)
Sat, Apr 27, 8:02 AM
Unknown Object (File)
Sat, Apr 27, 7:59 AM
Unknown Object (File)
Sat, Apr 27, 6:19 AM
Unknown Object (File)
Fri, Apr 26, 12:52 PM
Unknown Object (File)
Fri, Apr 26, 3:20 AM
Unknown Object (File)
Tue, Apr 23, 3:16 AM
Unknown Object (File)
Feb 23 2024, 1:19 AM
Subscribers
None

Details

Summary

All other architectures set NEW_PCIB in DEFAULTS, with arm being the one
remaining straggler that only sets it for GENERIC and TEGRA124.
ARMADA38X and ARMADAXP contain device pci but don't set NEW_PCIB,
however GENERIC claims to support them and as part of that NEW_PCIB
support was added to mv_pci, so these configs are most likely just
stale. Other than NOTES that just leaves ALPINE as the one kernel with
PCI support not covered by GENERIC, but al_pci is supported by arm64
which enables NEW_PCIB, and it's just a generic_pcie_fdt_driver with
some fixup code to deal with quirks so should support PCI_RES_BUS just
fine. Therefore it is believed that all in-tree kernel configs support
NEW_PCIB in reality, and so let's take a step towards removing all the
non-NEW_PCIB code by having it always-on everywhere.

MFC after: 1 month


Split out from D32954 to isolate the part with a slight risk of regression as
discussed on IRC.

Test Plan

Passed tinderbox -DWITHOUT_WORLDS -DMAKE_ALL_KERNELS

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

jrtc27 requested review of this revision.Feb 9 2024, 7:31 PM

s/SYS_RES_BUS/PCI_RES_BUS/ in commit log

This revision is now accepted and ready to land.Feb 10 2024, 7:07 PM
In D43806#999575, @jhb wrote:

s/SYS_RES_BUS/PCI_RES_BUS/ in commit log

Oops; that's not the first time I've made that mistake, and most likely won't be the last...