onenand_write_oob(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

onenand_write_oob(9) πŸ¦‹

okay so bestie, gather round: this is the Kernel API Manual page for onenand_write_oob(9), and it is giving [MTD Interface] NAND write data and/or out-of-band. no cap, that’s the whole brief. πŸ’…βœ¨

✨ NAME ✨

onenand_write_oob β€” [MTD Interface] NAND write data and/or out-of-band. periodt. πŸŽ€

🌸 SYNOPSIS 🌸

int onenand_write_oob (struct mtd_info *mtd , loff_t to , struct
       mtd_oob_ops *ops );

πŸŽ€ ARGUMENTS πŸŽ€

  • mtd β€” MTD device structure. that’s the device structure you’re working through, bestie. πŸ’–
  • to β€” offset to write. literally the offset where the write goes. ✨
  • ops β€” oob operation description structure. the descriptor for the out-of-band operation. πŸ¦‹

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file: ./drivers/mtd/nand/onenand/onenand_base.c β€” go read it, iykyk. πŸ’…

the whole onenand friend group pulled up, and yes, every single one is invited:

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_fill_auto_oob(9), onenand_write_ops_nolock(9),
onenand_write_oob_nolock(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)

that’s the whole page, bestie β€” signed off from ./drivers/mtd/nand/onenand for the source/version, dated October 2026, with the title onenand_write_oob(9). mwah πŸ’‹πŸ«Ά periodt.

πŸ“¦ where this page comes from