libie_fwlog_set_supported(9)

💅 libie_fwlog_set_supported — the "does FW even do logging" check

okay so this is a page from the Kernel API Manual, section 9, bestie. buckle up 🎀

---

✨ NAME ✨

libie_fwlog_set_supported — sets the flag for whether FW logging is supported by FW. literally that's the whole job 💖

---

🌸 SYNOPSIS 🌸

void libie_fwlog_set_supported (struct libie_fwlog *fwlog );

---

🦋 ARGUMENTS 🦋

• fwlog — pointer to the fwlog structure 🫶 that's it, that's the whole input

---

💫 DESCRIPTION 💫

so here's the tea ☕ if FW returns success to the libie_aq_fwlog_get call, then it supports FW logging. if it doesn't? then it doesn't. no cap. set the fwlog_supported flag accordingly, periodt. ✨

heads up bestie 💀 this function is only meant to be called during driver init — like, its whole purpose in life is to figure out if the FW support FW logging. don't be calling it at random times, iykyk 🙈

---

🔥 SEE ALSO 🔥

the kernel file that lives at ./drivers/net/ethernet/intel/libie/fwlog.c — go read it, it's iconic 👑

and all of these besties, in order:

• libie_fwlog_realloc_rings(9)
• libie_fwlog_supported(9)
• libie_aq_fwlog_set(9)
• libie_fwlog_set(9)
• libie_aq_fwlog_register(9)
• libie_fwlog_register(9)
• libie_fwlog_unregister(9)
• libie_fwlog_print_module_cfg(9)
• libie_debugfs_module_show(9)
• libie_debugfs_module_write(9)
• libie_debugfs_nr_messages_read(9)
• libie_debugfs_nr_messages_write(9)
• libie_debugfs_enable_read(9)
• libie_debugfs_enable_write(9)
• libie_debugfs_log_size_read(9)
• libie_debugfs_log_size_write(9)
• libie_debugfs_data_read(9)
• libie_debugfs_data_write(9)
• libie_debugfs_fwlog_init(9)
• libie_aq_fwlog_get(9)
• libie_fwlog_init(9)
• libie_fwlog_deinit(9)
• libie_get_fwlog_data(9)

---

and that's the whole page, babe 🧚💜 source/version is ./drivers/net/ethernet/intel/l... and it's dated October 2026, footer still says libie_fwlog_set_supported(9) because of course it does. mwah, slay, go read the other pages now 🎀🌸