pci_epc_bar...to_rebar_cap(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ pci_epc_bar_size_to_rebar_cap ✨

Okay so bestie, real talk: you're in the Kernel API Manual and the page you've got open is pci_epc_bar...to_rebar_cap(9) β€” a mouthful, I know, but stay with me, it's lowkey a one-job function and it does that job flawlessly. πŸ’…


🌸 NAME 🌸

pci_epc_bar_size_to_rebar_cap β€” convert a size to the representation used by the Resizable BAR Capability Register. That's it. That's the whole vibe. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

int pci_epc_bar_size_to_rebar_cap (size_t size , u32 *cap );

Like, look at her. Two params, one return, zero drama. πŸ‘‘


πŸ’– ARGUMENTS πŸ’–

  • size β€” the size you wanna convert, bestie. Hand it over.
  • cap β€” where the result gets stored. Give her a pointer to write into and she'll do the rest. 🫢

🌈 DESCRIPTION 🌈

So here's the tea: this function returns 0 on success and a negative error code in case of error. That's literally the whole description. No hidden twists, no plot, no cap. Not me being obsessed with a function that's this straightforward 😭 β€” she just converts and reports back. ⭐


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/pci/endpoint/pci-epc-core.c β€” that's where the magic lives, go read her siblings:

Yeah that's a long list, she has a big friend group, respect it. 🧚


Okay bestie that's the whole page β€” sourced from ./drivers/pci/endpoint, dated October 2026, and yeah the footer still says pci_epc_bar...to_rebar_cap(9) because we don't abbreviate legends in this house. Now go convert those sizes. Slay. πŸ’œ

πŸ“¦ where this page comes from