fbnic_fw_xm...ump_info_msg(9)

📦 version 7.3.1, in nixpkgs unstable

💅 fbnic_fw_xmit_coredump_info_msg(9) — like, the whole manual, bestie

okay so this is a page straight out of the Kernel API Manual, and it's all about fbnic_fw_xmit_coredump_info_msg. yes the header line up top gets truncated to fbnic_fw_xm...ump_info_msg(9) (iconic abbreviation energy, honestly) but the real, full name is right below 👇

✨ NAME ✨

fbnic_fw_xmit_coredump_info_msg — creates and transmits a coredump info message. that's it, that's the whole vibe. 📨

🎀 SYNOPSIS 🎀

int fbnic_fw_xmit_coredump_info_msg (struct fbnic_dev *fbd , struct
       fbnic_fw_completion *cmpl_data , bool force );

literally just three args and an int comeback, we love a tidy signature 🫶

🌸 ARGUMENTS 🌸

  • fbd — the FBNIC device structure. like, the device itself, bestie, the main character 🫶
  • cmpl_data — the structure where the info gets stored. it's giving "inbox" 💌
  • force — force a coredump event if one hasn't already occurred. lowkey pushy but we respect it 💅

⭐ RETURN ⭐

zero on success, a negative errno on failure. no in-between, no "it depends", periodt ✨

🔥 DESCRIPTION 🔥

so basically it asks the FW for info related to the coredump. and if a coredump doesn't exist yet? it can optionally force one — but only if force is true. so like, force in the arguments up there? that's the switch. no true, no forcing. iykyk 😌

🦋 SEE ALSO 🦋

the kernel file lives right here, no cap:

./drivers/net/ethernet/meta/fbnic/fbnic_fw.c

and the whole friend group of sibling calls:

go read them all, they're literally the lore 🌈

and that's the whole page, bestie!! sign-off time 🎀 source lives at ./drivers/net/ethernet/meta/fbnic, dated October 2026, from the Kernel API Manual — and the footer does that same cute little fbnic_fw_xm...ump_info_msg(9) truncation thing. slay. 💖✨

📦 where this page comes from