radeon_acpi_vfct_match(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… radeon_acpi_vfct_match(9) β€” Kernel API Manual

okay so bestie, welcome to the Kernel API Manual entry for radeon_acpi_vfct_match(9) β€” the little matchmaker that checks if a VFCT entry matches the device. no cap, she’s here to do one job and do it cute. πŸŽ€


πŸ‘‘ NAME πŸ‘‘

radeon_acpi_vfct_match β€” Check if a VFCT entry matches the device.


✨ SYNOPSIS ✨

int radeon_acpi_vfct_match (struct radeon_device *rdev ,
       VFCT_IMAGE_HEADER *vhdr );

πŸŽ€ ARGUMENTS πŸŽ€

  • rdev β€” Radeon device. the main character device energy.
  • vhdr β€” VFCT image header to check. the header getting the vibe check, periodt.

🌸 DESCRIPTION 🌸

Okay so here’s the tea: VFCT entries contain the PCI bus number as recorded during BIOS POST. On systems where the kernel renumbers PCI buses (e.g. pci=realloc or resource conflicts), the runtime bus number may differ from the POST value. So this function matches by device identity (vendor + device + function) and uses the bus number as a preference: exact bus match is preferred, but when the bus numbers disagree we accept the entry if the device identity matches. it’s giving flexible but picky in the right way. πŸ’…


πŸ’– RETURN πŸ’–

  • 0 on match β€” slay, it matched. ✨
  • -ENODEV on no match β€” not it, no match. πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹

iykyk 🫢


mwah πŸ’‹ β€” this cutie lives under source/version ./drivers/gpu/drm/radeon and is dated October 2026. πŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from