doc_write_oob(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ doc_write_oob(9) ✨

okay so bestie, this is the Kernel API Manual page for doc_write_oob(9) β€” we're doing out of band flash writes and it's lowkey iconic πŸ’…


πŸŽ€ NAME πŸŽ€

doc_write_oob β€” write out of band bytes to flash πŸ¦‹

πŸ“œ SYNOPSIS πŸ“œ

int doc_write_oob (struct mtd_info *mtd , loff_t ofs , struct
       mtd_oob_ops *ops );

🌸 ARGUMENTS 🌸

  • mtd β€” the device πŸ“±
  • ofs β€” the offset from first block and first page, in bytes, aligned on page size πŸ“
  • ops β€” the mtd oob structure 🧺

πŸ’– DESCRIPTION πŸ’–

Okay so the vibe is: Either write OOB data into a temporary buffer, for the subsequent write page. The provided OOB should be 16 bytes long. If a data buffer is provided as well, issue the page write. Or provide data without OOB, and then a all zeroed OOB will be used (ECC will still be filled in if asked for). ✨

Returns 0 is successful, EINVAL if length is not 14 bytes. And yes, bestie, both 16 bytes and 14 bytes show up here β€” that's literally what the page says πŸ‘€πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/mtd/devices/docg3.c β€” and the whole squad:


mwah πŸ’‹ this page's source/version is ./drivers/mtd/devices, dated October 2026, and it's the doc_write_oob(9) manual page. slay, go write some OOB bytes responsibly 🫢

πŸ“¦ where this page comes from