nand_match_ecc_req(9)

📦 version 7.3.1, in nixpkgs unstable

💅 nand_match_ecc_req(9) — Kernel API Manual, but make it make sense

okay so bestie, welcome to the nand_match_ecc_req(9) page ✨ this lives in the Kernel API Manual and it's all about giving your NAND chip exactly the ECC it asked for — no more, no less. Let's get into it 🎀

🌸 NAME 🌸

nand_match_ecc_req — meet the chip's requirement with least ECC bytes 💖

✨ SYNOPSIS ✨

int nand_match_ecc_req (struct nand_chip *chip , const struct
       nand_ecc_caps *caps , int oobavail );

🦋 ARGUMENTS 🦋

  • chip — the nand chip info structure, aka the whole personality profile of your chip 👑
  • caps — the ECC engine caps info structure, i.e. what your ECC engine is actually capable of, its little resume of skills fr fr
  • oobavail — the OOB size that the ECC engine can use, the budget you're working with 💸

💜 DESCRIPTION 💜

so here's the vibe: if a chip's ECC requirement is provided, this function tries to meet it using the least number of ECC bytes — which is the same thing as saying it wants the largest number of OOB-free bytes. the way it's optimizing both ends at once, iconic 🧚

and when it succeeds? the chosen ECC settings get set. periodt. 💅

🫶 SEE ALSO 🫶

Kernel file ./drivers/mtd/nand/raw/nand_base.c — and like, so many friends, no cap:

bestie that list is long — but every single one of them is a real one, go read 'em 😭🫶

🌈 okay that's the whole page!! source path is ./drivers/mtd/nand/raw and it's dated October 2026, so like, from the future bestie 💀💖 go forth and match those ECC requirements, you absolute main character 👑✨

📦 where this page comes from