drm_edid_ove...ector_update(9)

📦 version 7.3.1, in nixpkgs unstable

💖 drm_edid_override_connector_update — the Kernel API Manual page, but make it make sense 💖

okay bestie so this is a page from the Kernel API Manual (yes, that manual) and the star of the show is drm_edid_override_connector_update. The header up top gets truncated to drm_edid_ove...ector_update(9) because apparently even manpage headers have a character limit and honestly? relatable. 💅

✨ NAME ✨

drm_edid_override_connector_update — literally just adds modes from the override/firmware EDID 🎀

🌸 SYNOPSIS 🌸

int drm_edid_override_connector_update (struct drm_connector *connector);

🦋 ARGUMENTS 🦋

  • connector — the connector we're probing, aka the main character of this whole function 🫶

💜 DESCRIPTION 💜

so what it does is: it adds modes from the override/firmware EDID, if available. that's it, that's the vibe. ✨

but here's the important part, bestie, do not skip this: it's only to be used from drm_helper_probe_single_connector_modes as a fallback for when the DDC probe failed during drm_get_edid and caused the override/firmware EDID to get skipped. like, it's the backup dancer, not the lead. it swoops in when DDC probe fumbled the bag. 😭

⭐ RETURN ⭐

The number of modes added — or 0 if we couldn't find any. that's it. zero means the search came up empty, no cap. 💀

ngl if you get a 0 back, that's your sign the override/firmware EDID wasn't there to save you. 🙈

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/drm_edid.c — and then a whole friend group of related functions, all of them (9), all of them iconic in their own way 👑

that's the whole page, bestie, you ate that 🍓

coming at you from the source tree at ./drivers/gpu/drm, dated October 2026 — go forth and probe those connectors, ily 💖✨

📦 where this page comes from