read_bbt(9)

📦 version 7.3.1, in nixpkgs unstable

💅 read_bbt — yes bestie, it's a whole kernel function

So this is a page from the Kernel API Manual, and the function we're simping over today is read_bbt. Strap in, it's giving "low-level NAND vibes" and honestly? We're obsessed. 🌸

✨ NAME ✨

read_bbt — [GENERIC] read the bad block table, starting from a page. That's it, that's the whole gig. 💖

🎀 SYNOPSIS 🎀

int read_bbt (struct nand_chip *this , uint8_t *buf , int page , int num
, struct nand_bbt_descr *td , int offs );

Like, look at that signature. Six whole arguments. Main character energy fr fr. ✨

🦋 ARGUMENTS 🦋

  • this — the NAND chip object. Yeah, it's literally called this. Iconic naming choice, no notes. 👑
  • buf — a temporary buffer. It's just passing through, doing its little job. 🫶
  • page — the starting page. Where the reading begins, bestie. 📖
  • num — how many bbt descriptors to read. Count carefully, ngl. 🔢
  • td — the bbt describtion table. (Yes we're spelling it like that, it's canon.) 🎀
  • offs — block number offset in the table. Offset queen. 💅

💜 DESCRIPTION 💜

Read the bad block table starting from page. 🌈

That's genuinely the whole description. Short king of a description. It ate and left no crumbs, but also left no extra details, so don't go looking for lore that isn't there. 😭

Lowkey important: this reads the bad block table starting from page — that's the starting point, not some random spot. No cap. 🔥

🌟 SEE ALSO 🌟

Everything here lives in the kernel file ./drivers/mtd/nand/raw/nand_bbt.c — and the friend group is huge. Miss nothing: 💀

Twenty-two entries. Twenty-two!! The way this function has more connections than a group chat on a Friday night. 🧚

Byeee bestie — this one's filed under ./drivers/mtd/nand/raw, dated October 2026, page read_bbt(9). Go read a bad block table for me, mwah 💋

📦 where this page comes from