fman_get_bmi_max_fifo_size(9)

📦 version 7.3.1, in nixpkgs unstable

✨ fman_get_bmi_max_fifo_size(9) ✨

okay so real talk, this page comes to you from the Kernel API Manual (section 9, the "we talk to the kernel directly" section, iykyk) and it's genuinely such a tiny little icon. one function, one job. let's get into it 💅

🌸 NAME 🌸

fman_get_bmi_max_fifo_size — and bestie, the original page literally gives you no description here, it's just vibes and a blank space. so the name is the whole personality. (we're getting to what it does, don't worry 🫶)

🎀 SYNOPSIS 🎀

u32 fman_get_bmi_max_fifo_size (struct fman *fman );

that's it, that's the whole call. returns a u32, takes one pointer. short and slay.

🦋 ARGUMENTS 🦋

  • fman — a pointer to the FMan device. that's the whole spec, bestie. just hand it your FMan device pointer and let it cook 🔥

👑 DESCRIPTION 👑

get the FMan maximum FIFO size. periodt. that's literally the entire description and honestly? respect for the lack of yapping 🧚

⭐ RETURN ⭐

it returns the FMan Maximum FIFO size — as a u32, per the synopsis. that's the whole return story, no plot twists, no error paths, nothing hidden. ate and left no crumbs 🌈

💖 SEE ALSO 💖

if you're going down this rabbit hole (and you are), the source lives in the kernel file ./drivers/net/ethernet/freescale/fman/fman.c — go read it, main character energy fr fr 📖

and here's the whole friend group, all section 9, no cap:

ngl this is a very short manpage and that's okay — not every function needs a whole saga. some of them just get a number and go home 😭

okay that's the page!! this one shipped out in October 2026 from the source path ./drivers/net/ethernet/freesca... (yes, truncated exactly like that, blame the footer not me 🙈). stay hydrated, read your manpages, and remember: u32 is a lifestyle 💜🌸

📦 where this page comes from