PVR_HAS_ENHANCEMENT(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ‘‘ PVR_HAS_ENHANCEMENT(9) β€” Kernel API Manual πŸ‘‘

okay so bestie, welcome to the PVR_HAS_ENHANCEMENT(9) page from the Kernel API Manual β€” it's literally the vibe check for hardware enhancements, and we're gonna read it together πŸ’…βœ¨

✨ NAME ✨

PVR_HAS_ENHANCEMENT β€” Tests whether a physical device has a given enhancement πŸŽ€

🌸 SYNOPSIS 🌸

PVR_HAS_ENHANCEMENT (pvr_dev , enhancement );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • pvr_dev β€” [IN] Target PowerVR device. 🫢
  • enhancement β€” [IN] Hardware enhancement name. ✨

πŸ’– DESCRIPTION πŸ’–

okay so here's the lore: enhancement numbers are derived from those found in #pvr_device_enhancements by dropping the 'has_ern' prefix, which is applied by this macro. That prefix situation is handled for you, bestie β€” iconic behavior, honestly πŸ’…

🌈 Returns 🌈

  • true if the enhancement is present in the hardware, or
  • false if the enhancement is not present in the hardware. 😭

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/gpu/drm/imagination/pvr_device.h β€” and then the whole squad: struct pvr_gpu_id(9), struct pvr_fw_version(9), struct pvr_device_data(9), struct pvr_device(9), struct pvr_file(9), PVR_HAS_FEATURE(9), PVR_FEATURE_VALUE(9), PVR_HAS_QUIRK(9), PVR_PACKED_BVNC(9), pvr_gpu_id_to_packed_bvnc(9), PVR_CR_FIELD_GET(9), pvr_cr_read32(9), pvr_cr_read64(9), pvr_cr_write32(9), pvr_cr_write64(9), pvr_cr_poll_reg32(9), pvr_cr_poll_reg64(9), pvr_round_up_to_cacheline_size(9), IOCTL validation helpers(9), pvr_ioctl_union_padding_check(9), PVR_STATIC_ASSERT_64BIT_ALIGNED(9), PVR_IOCTL_UNION_PADDING_CHECK(9). 🫢✨


πŸ’Œ source/version: ./drivers/gpu/drm/imagination Β· date: October 2026 Β· this page: PVR_HAS_ENHANCEMENT(9) β€” byeee bestie, ily! πŸ«ΆπŸ’–

πŸ“¦ where this page comes from