buffer_icap...onfiguration(9)
okay bestie, welcome to the buffer_icap...onfiguration(9) page from the Kernel API Manual β it's giving very specific kernel energy and we're obsessed. π
β¨
πΈ NAME πΈ
buffer_icap_get_configuration β read configuration data from the device. that's the whole assignment, no cap. π«Ά
π¦ SYNOPSIS π¦
int buffer_icap_get_configuration (struct hwicap_drvdata *drvdata , u32
*data , u32 size );
π ARGUMENTS π
drvdataβ a pointer to thedrvdata. yes bestie, that is literally the description πdataβ Address of the data representing the partial bitstream. π¦sizeβ the size of the partial bitstream in 32 bit words. π’
π SEE ALSO π
the whole squad, in order, because we do not skip references around here π
- Kernel file
./drivers/char/xilinx_hwicap/buffer_icap.cπ buffer_icap_get_status(9)buffer_icap_get_bram(9)buffer_icap_busy(9)buffer_icap_set_size(9)buffer_icap_set_offset(9)buffer_icap_set_rnc(9)buffer_icap_set_bram(9)buffer_icap_device_read(9)buffer_icap_device_write(9)buffer_icap_reset(9)buffer_icap_set_configuration(9)
mwah π this cutie came from ./drivers/char/xilinx_hwicap, dated October 2026, and the page is buffer_icap...onfiguration(9). slay. π
π¦ 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