Page MenuHomeFreeBSD

linuxkpi: Define `PCI_POSSIBLE_ERROR()` macro
ClosedPublic

Authored by dumbbell on Jan 4 2026, 10:17 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Feb 23, 6:08 AM
Unknown Object (File)
Jan 31 2026, 7:50 AM
Unknown Object (File)
Jan 22 2026, 5:41 PM
Unknown Object (File)
Jan 20 2026, 3:00 PM
Unknown Object (File)
Jan 19 2026, 10:29 PM
Unknown Object (File)
Jan 18 2026, 7:03 AM
Unknown Object (File)
Jan 11 2026, 9:52 PM
Unknown Object (File)
Jan 10 2026, 8:45 AM
Subscribers

Details

Summary

It comes with PCI_ERROR_RESPONSE and PCI_SET_ERROR_RESPONSE() but we don't use them so far. Therefore PCI_POSSIBLE_ERROR() will always reture false.

As written in the comment, this macro is a bit weird given the Linux `pci_read_*() functions can return an error code separately from the read value.

The PCI_POSSIBLE_ERROR() macro started to be used by the amdgpu DRM driver in Linux 6.10.

This is part of the update of DRM drivers to Linux 6.10.

Sponsored by: The FreeBSD Foundation

Diff Detail

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