intel_fbc_re...run_dbg_info(9)
π NAME π
ok so this is the Kernel API Manual page for intel_fbc_read_underrun_dbg_info β and what it does is read and log FBC-related FIFO underrun debug info. that's the whole vibe, bestie π
β¨ SYNOPSIS β¨
void intel_fbc_read_underrun_dbg_info (struct intel_display *display ,
enum pipe pipe , bool log );
like, that's the signature fr fr β copy it exactly, don't come for me π«Ά
π¦ ARGUMENTS π¦
displayβ the display device instance. your main character, the whole screen situation πpipeβ the pipe that possibly contains the FBC. note the "possibly", she's not committing to anything πlogβ should we log the info? yes/no, that's it, that's the question β¨
πΈ DESCRIPTION πΈ
okay so picture this: if pipe does not contain an FBC instance, this function bails early. like, she checks the vibe, sees no FBC, and leaves. no cap, no drama, just gone π
otherwise (FBC is in there, we're doing this π), the FBC-related FIFO underrun gets read and cleared β both, in that order, the way that it just works π
and then β only if log is true β it gets printed with error level. so like, the logging is conditional, the reading-and-clearing is not, iykyk π₯
π SEE ALSO π
- Kernel file
./drivers/gpu/drm/i915/display/intel_fbc.cπ - Frame Buffer Compression (FBC)(9)
intel_fbc_disable(9)intel_fbc_handle_fifo_underrun_irq(9)intel_fbc_init(9)intel_fbc_sanitize(9)
the whole FBC friend group, honestly obsessed with them π
that's the page!! π this little icon lives over in ./drivers/gpu/drm/i915/display, dated October 2026, and the header she's filed under is intel_fbc_re...run_dbg_info(9) β slay, go read the source, ily, bye π§π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms