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)
Fri, Oct 2, 2:25 PM
Unknown Object (File)
Mon, Sep 28, 1:09 PM
Unknown Object (File)
Mon, Sep 21, 3:13 PM
Unknown Object (File)
Sun, Sep 20, 9:14 AM
Unknown Object (File)
Fri, Sep 18, 8:25 PM
Unknown Object (File)
Fri, Sep 18, 8:14 PM
Unknown Object (File)
Fri, Sep 18, 6:13 PM
Unknown Object (File)
Sep 4 2026, 10:22 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