intel_device...e_init_early(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– intel_device...e_init_early(9) πŸ’–

okay so bestie, welcome to the Kernel API Manual πŸŽ€ β€” yes that manual, the one for people who live in drivers/gpu/drm/i915 for fun. This page is about intel_device_info_runtime_init_early, and the header is literally truncated to intel_device...e_init_early(9) because apparently even manpage titles have a character limit and honestly? relatable 😭. Anyway. Sit down, hydrate, let's go 🧚


✨ NAME ✨

intel_device_info_runtime_init_early β€” initialize early runtime info 🫢

🌸 SYNOPSIS 🌸

void intel_device_info_runtime_init_early (struct drm_i915_private *i915 );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • i915 β€” the i915 device. that's it, that's the whole arg. your whole device, handed over, main character energy πŸ‘‘

πŸ’… DESCRIPTION πŸ’…

so the vibe here is: this function figures out the early intel_device_info fields at runtime ✨. like, it goes and determines them when the code actually runs, not at some other time. very "we'll find out when we get there" of it.

but here's the part where you must listen to me, no cap πŸ”₯: this function needs to be called before the MMIO has been setup. before. MMIO. is. set. up. that's a hard requirement, not a suggestion, not a soft launch β€” it's a whole ordering constraint, so respect it fr fr πŸ™ˆ

⚠️ seriously bestie: call it before MMIO setup. the manpage says "needs to be called before the MMIO has been setup" and we do not argue with the manpage πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

  • Kernel file ./drivers/gpu/drm/i915/intel_device_info.c β€” go read the source, it's giving lore πŸ“–
  • intel_device_info_runtime_init(9) β€” the sibling, the sequel, the other runtime init 🌈

and that's the page!! πŸ’œ tiny page, big responsibility. this little cutie lives in ./drivers/gpu/drm/i915, it's dated October 2026, and its footer goes by intel_device...e_init_early(9) β€” same truncated icon as the header, consistency queen ⭐ slay, bye bestie πŸ“πŸ’–

πŸ“¦ where this page comes from