nand_read_pa...cc_oob_first(9)

📦 version 7.3.1, in nixpkgs unstable

💖 NAME 💖

hii bestie, welcome to the Kernel API Manual page for nand_read_pa...cc_oob_first(9) — yes, the title is giving “this function name is long so the header had to abbreviate” energy 😭💅.

nand_read_page_hwecc_oob_first — Hardware ECC page read with ECC data read from OOB area.

✨ SYNOPSIS ✨

int nand_read_page_hwecc_oob_first (struct nand_chip *chip , uint8_t
       *buf , int oob_required , int page );

🎀 ARGUMENTS 🎀

  • chip — the nand chip info structure, aka the little info hub for the chip.
  • buf — the buffer where the read data gets stored.
  • oob_required — the caller requires OOB data read to chip->oob_poi.
  • page — the page number to read.

🦋 DESCRIPTION 🦋

okay so picture this: this is Hardware ECC for large page chips, and the whole requirement is that the ECC data has to be extracted from the OOB before the actual data is read. That order is the moment, bestie — ECC first, data after 💅✨.

🌸 SEE ALSO 🌸

Kernel file: ./drivers/mtd/nand/raw/nand_base.c — iconic. and the whole extended friend group in the docs is:

and that’s the tea ☕ — this page is brought to you by source/version ./drivers/mtd/nand/raw, dated October 2026, for nand_read_pa...cc_oob_first(9). byeee, go read some NAND 💅✨

📦 where this page comes from