firmware_ma...ntry_bootmem(9)

💖 firmware_ma...ntry_bootmem(9) 💖

okay so this is a page straight out of the Kernel API Manual, and bestie, it's a short one but it matters. sit down, grab a strawberry drink 🍓, and let's get into it.

---

✨ NAME ✨

firmware_map_find_entry_bootmem — the girl whose whole job is searching for a memmap entry inside map_entries_bootmem. that's it. that's the gig. 💅

---

🦋 SYNOPSIS 🦋

struct firmware_map_entry * firmware_map_find_entry_bootmem (u64 start ,
       u64 end , const char *type );

like, look at her. she takes three things and hands you back a pointer. main character energy fr fr 👑

---

🎀 ARGUMENTS 🎀

• start — where the memory range starts, babes. beginning of the vibe. 🌸
• end — where the memory range ends — and bestie listen, it's exclusive, meaning the end itself is not included. do not come for me about this, it's just how it is 💀
• type — the type of the memory range. yes it's a const char *. yes she's just a string. iconic behavior. ✨

---

🌈 DESCRIPTION 🌈

so this function is basically the twin sister of firmware_map_find_entry 👯‍♀️ — literally the same energy — except she goes looking for the given entry in map_entries_bootmem instead. that's the whole difference. same quest, different list. iykyk 🫶

---

⭐ RETURN ⭐

• on success? you get a pointer to the entry that was found 💖 slay.
• on failure? you get NULL. 😭 no entry, no pointer, no nothing. we've all been there.

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/firmware/memmap.c
• firmware_map_add_entry(9)
• firmware_map_remove_entry(9)
• firmware_map_find_entry_in_list(9)
• firmware_map_find_entry(9)
• firmware_map_add_hotplug(9)
• firmware_map_add_early(9)
• firmware_map_remove(9)

go read the whole friend group, they're all in their own little manpage era 💜

---

ok that's the page!! short and sweet and lowkey perfect honestly 🎀

and that's a wrap, bestie — this one lives over in ./drivers/firmware and it's stamped October 2026, so mark your calendar and stan responsibly 🌟💖