aperture_re...ting_devices(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ aperture_re...ting_devices(9) β€” the Kernel API Manual moment ✨

okay bestie so this is a page straight out of the Kernel API Manual, and it's about aperture_remove_conflicting_devices β€” yes the name is long, yes it's iconic, we move πŸ’…


🌸 NAME 🌸

aperture_remove_conflicting_devices β€” remove devices in the given range

πŸ¦‹ SYNOPSIS πŸ¦‹

int aperture_remove_conflicting_devices (resource_size_t base ,
resource_size_t size , const char *name );

πŸŽ€ ARGUMENTS πŸŽ€

  • base β€” the aperture's base address in physical memory. like, where it starts, fr fr.
  • size β€” aperture size in bytes. the actual bigness of it πŸ’–
  • name β€” a descriptive name of the requesting driver. so everyone knows who's asking, iykyk.

⭐ DESCRIPTION ⭐

okay so literally what this does: it removes devices that own apertures within base and size. that's the whole vibe check β€” anything holding an aperture inside that range gets evicted. no cap. πŸ”₯

🌈 RETURN 🌈

0 on success, or a negative errno code otherwise. zero is the slay outcome, negative is the "not me 😭" outcome.

πŸ‘‘ SEE ALSO πŸ‘‘

go read those too, bestie, it's giving required reading 🫢


ngl this page lives in ./drivers/video and it's stamped October 2026 β€” so that's the source, the version, and the date all in one cute little sign-off πŸ’– periodt.
πŸ“¦ where this page comes from