onenand_fill_auto_oob(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to onenand_fill_auto_oob(9) from the Kernel API Manual πŸ’– this one is giving internal-helper energy, and we're gonna keep every single detail, no cap.

🌸 NAME 🌸

onenand_fill_auto_oob β€” [INTERN] oob auto-placement transfer. that's the whole name vibe, and yes, it's tagged internal πŸ™ˆ

✨ SYNOPSIS ✨

the signature is literally this, bestie:

int onenand_fill_auto_oob (struct mtd_info *mtd , u_char *oob_buf ,
       const u_char *buf , int column , int thislen );

πŸŽ€ ARGUMENTS πŸŽ€

  • mtd β€” the MTD device structure, aka the main character of this function's story ✨
  • oob_buf β€” the oob buffer; this is where the oob bytes are buffered, periodt
  • buf β€” source address, so this is where the bytes come from 🫢
  • column β€” oob offset to write to, aka the exact spot in oob you're writing at
  • thislen β€” oob length to write, aka how much oob is getting written πŸ’…

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/mtd/nand/onenand/onenand_base.c is the home base for this one. and the whole SEE ALSO squad is right here, all names exactly as given:

onenand_readw(9), onenand_writew(9), onenand_block_address(9), onenand_bufferram_address(9), onenand_page_address(9), onenand_buffer_address(9), flexonenand_block(9), flexonenand_addr(9), onenand_get_density(9), flexonenand_region(9), onenand_command(9), onenand_read_ecc(9), onenand_wait(9), onenand_bufferram_offset(9), onenand_read_bufferram(9), onenand_sync_read_bufferram(9), onenand_write_bufferram(9), onenand_get_2x_blockpage(9), onenand_check_bufferram(9), onenand_update_bufferram(9), onenand_invalidate_bufferram(9), onenand_get_device(9), onenand_release_device(9), onenand_transfer_auto_oob(9), onenand_recover_lsb(9), onenand_mlc_read_ops_nolock(9), onenand_read_ops_nolock(9), onenand_read_oob_nolock(9), onenand_read_oob(9), onenand_bbt_wait(9), onenand_bbt_read_oob(9), onenand_verify_oob(9), onenand_verify(9), onenand_panic_write(9), onenand_write_ops_nolock(9), onenand_write_oob_nolock(9), onenand_write_oob(9), onenand_block_isbad_nolock(9), onenand_multiblock_erase(9), onenand_block_by_block_erase(9), onenand_erase(9), onenand_sync(9), onenand_block_isbad(9), onenand_default_block_markbad(9), onenand_block_markbad(9), onenand_do_lock_cmd(9), onenand_lock(9), onenand_unlock(9), onenand_check_lock_status(9), onenand_unlock_all(9), onenand_otp_command(9), onenand_otp_write_oob_nolock(9), do_otp_read(9), do_otp_write(9), do_otp_lock(9), onenand_otp_walk(9), onenand_get_fact_prot_info(9), onenand_read_fact_prot_reg(9), onenand_get_user_prot_info(9), onenand_read_user_prot_reg(9), onenand_write_user_prot_reg(9), onenand_lock_user_prot_reg(9), onenand_check_features(9), onenand_print_device_info(9), onenand_check_maf(9), flexonenand_get_boundary(9), flexonenand_get_size(9), flexonenand_check_blocks_erased(9), onenand_chip_probe(9), onenand_probe(9), onenand_suspend(9), onenand_resume(9), onenand_scan(9), onenand_release(9).


cute sign-off bestie: source/version is ./drivers/mtd/nand/onenand, date is October 2026, and the manual name is onenand_fill_auto_oob(9) β€” slay πŸ’…πŸŽ€

πŸ“¦ where this page comes from