Change Details

With LinuxKPI returning DEFAULT we are having a hard time to make a native driver like iwm(4) preferable for the time being with the currently defined BUS_PROBE_* values. Downgrading the priority of LinuxKPI would affect all LinuxKPI based drivers rather than just the specific overlapping one(s). Introduce BUS_PROBE_HIGH_PRIORITY for the native driver to overcome this (working like LOW_PRIORITY just in the other direction and be careful in the man page to point out that LOW_PRIORITY is likely the better solution in most other cases). Sponsored by: The FreeBSD Foundation MFC after: 3 days

Add a boolean and an int a driver can set in their 'struct pci_driver' definiotion to raise or lower the default LinuxKPI pci return value. This is helpful in case of multiple drivers with overlapping IDs, such as iwlwifi(4) and iwm(4). The reason for the bool and the int is that 0 (BUS_PROBE_SPECIFIC) is a valid return but would also be the unintialised (bss) value. Having the bool allows us to check if we should apply the specific return value or stay with the default. Given 'struct pci_driver' is usually statically initialised we cannot set an easy global default to always use. Suggested by: jhb Sponsored by: The FreeBSD Foundation MFC after: 3 days X-MFC: struct members need to go to the end for stable/13 Differential Revision: https://reviews.freebsd.org/D33915

With LinuxKPI returning DEFAULT we are having a hard time to make a Add a boolean and an int a driver can set in their 'struct pci_driver' native driver like iwm(4) preferable for the time being with the definiotion to raise or lower the default LinuxKPI pci return value. currently defined BUS_PROBE_* values. This is helpful in case of multiple drivers with overlapping IDs, Downgrading the priority of LinuxKPI would affect all LinuxKPI based such as iwlwifi(4) and iwm(4). drivers rather than just The reason for the bool and the specific overlapping one(s).int is that 0 (BUS_PROBE_SPECIFIC) Introduce BUS_PROBE_HIGH_PRIORITY for is a valid return but would also be the native driver to overcome thisunintialised (bss) value. (work Having like LOW_PRIORITY just in the other direction and be carefulthe bool allows us to check if we should apply the specific in the man page to point out that LOW_PRIORITY is likely the better return value or stay with the default. Given 'struct pci_driver' solution in most other cases). Sponsored by: The FreeBSD Foundation is usually statically initialised we cannot set an easy global default MFC after: 3 days to always use. Suggested by: jhb Sponsored by: The FreeBSD Foundation MFC after: 3 days X-MFC: struct members need to go to the end for stable/13 Differential Revision: https://reviews.freebsd.org/D33915