asd_write_ocm_seg(9)
π asd_write_ocm_seg(9) β Kernel API Manual, bestie edition β¨
okay so this is a page from the Kernel API Manual and it's about asd_write_ocm_seg, which literally writes a segment into on chip memory (OCM) π that's the whole vibe, no cap.
πΈ NAME πΈ
asd_write_ocm_seg β write an on chip memory (OCM) segment βοΈβ¨
π¦ SYNOPSIS π¦
void asd_write_ocm_seg (struct asd_ha_struct *asd_ha , void *buffer ,
u32 offs , int size );
she's a void function, she takes four things, and honestly she's iconic for it π
π ARGUMENTS π
asd_haβ pointer to the host adapter structure π«Ά like, this is the adapter we're talking to, bestiebufferβ where to read the write data π this is your source, the data comes from hereoffsβ offset into OCM to write to π exactly where in that on chip memory we're dropping the goodssizeβ how many bytes to write π’ yes, actual byte count, keep track of her
π DESCRIPTION π
so here's the thing, and this part is a lil plot twist π β this function returns the number of bytes not written. yep. the leftovers. the ones that didn't make it.
and it returns 0 on success π so a zero is genuinely the slay outcome here, don't panic when you see it.
fr fr, 0 = success. anything else = the count of bytes that got left on read π
π SEE ALSO π
Kernel file ./drivers/scsi/aic94xx/aic94xx_sds.c ποΈ and the rest of the friend group:
asd_read_ocm_seg(9)asd_read_ocm(9)asd_find_flash_dir(9)asd_find_ll_by_id(9)asd_ms_get_phy_params(9)asd_process_ms(9)asd_process_ctrl_a_user(9)asd_read_flash(9)asd_verify_flash_seg(9)asd_write_flash_seg(9)asd_erase_nv_sector(9)
β¨ that's the whole page, mwah π big sign-off energy: this one lives in ./drivers/scsi/aic94xx and it's dated October 2026 β go off, asd_write_ocm_seg(9) ππ
π¦ 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