dmi_first_match(9)

✨ dmi_first_match 💅

okay so this is a page from the Kernel API Manual (section 9, kernel-level stuff, iykyk) and it's about a little function that goes digging through DMI data to find a match. it's giving "find your person in a crowd" energy 🫶

---

🎀 NAME 🎀

dmi_first_match — literally finds the dmi_system_id structure that matches your system's DMI data. that's the whole vibe. no cap.

---

🌸 SYNOPSIS 🌸

const struct dmi_system_id * dmi_first_match (const struct dmi_system_id
*list );

---

🦋 ARGUMENTS 🦋

• list — the array of dmi_system_id structures you're matching against. and bestie, listen: all non-null elements of the list have to match their slot's (field index's) data for it to count as a successful match. so like, each list string must be a substring of the specified DMI slot's string data. every single one. no skipping. periodt 💅

---

💖 DESCRIPTION 💖

so what it does: it walks the blacklist table until it hits the first match. iconic behaviour honestly. then it returns the pointer to that matching entry — or NULL if there's no match at all 😭 (rip, not every search slays).

⭐ heads up bestie: dmi_setup must be called before this function is called. like, don't skip that step, fr fr. not optional. 🌈

---

👑 SEE ALSO 👑

kernel file ./drivers/firmware/dmi_scan.c 📁 and its whole friend group:

• dmi_setup(9)
• dmi_matches(9)
• dmi_is_end_of_table(9)
• dmi_check_system(9)
• dmi_get_system_info(9)
• dmi_name_in_serial(9)
• dmi_name_in_vendors(9)
• dmi_find_device(9)
• dmi_get_date(9)
• dmi_get_bios_year(9)
• dmi_walk(9)
• dmi_match(9)
• dmi_memdev_type(9)
• dmi_memdev_handle(9)

---

and that's the whole page bestie, you ate that reading 💖 this one's from ./drivers/firmware and the version stamp says October 2026 — written down in the books, timestamped, sealed with a 🎀. go forth and match some DMI data, main character 🧚💜