STRUCT NAND_ECC_SW_HAMMING_CONF(9)
β¨ NAME β¨
bestie, this is struct nand_ecc_sw_hamming_conf β the private software Hamming ECC engine structure. yes it's a whole mouthful, no I will not be shortening it π
(and real quick β this page lives in the Kernel API Manual, iykyk π«Ά)
πΈ SYNOPSIS πΈ
okay so here's the actual shape of it, character for character, do not come for me:
struct nand_ecc_sw_hamming_conf {
struct nand_ecc_req_tweak_ctx req_ctx;
unsigned int code_size;
u8 *calc_buf;
u8 *code_buf;
unsigned int sm_order;
};
π¦ MEMBERS π¦
every single field, slayed and explained π
req_ctxβ saves the request context and tweaks the original request so it fits what the engine actually needs. like it's out here doing the adaptation work for you, main character energy fr π₯code_sizeβ the number of bytes needed to store a code, and it's one code per step. yes. per step. lowkey important πcalc_bufβ the buffer you use when calculating ECC bytes β¨code_bufβ the buffer you use when reading the (raw) ECC bytes from the chip π (raw in the original, keeping it raw, periodt)sm_orderβ Smart Media special ordering π that's genuinely all it says, that's the whole vibe check
π SEE ALSO π
- the kernel file
./include/linux/mtd/nand-ecc-sw-hamming.hβ go read it, it's giving source of truth π¦
ngl bestie, all five members gotta be exactly as specified β no renaming, no merging, no "fixing" the ones that look boring. they're load-bearing π
and that's a wrap, gorgeous πΈ this one came out of ./include/linux/mtd back in October 2026 β mwah, thanks for reading, ily, bye ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms