sw842_decompress(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– sw842_decompress(9) β€” Kernel API Manual πŸ’–

Welcome to the Kernel API Manual page for sw842_decompress(9), bestie. Buckle up, we're decompressing ✨


✨ NAME ✨

sw842_decompress β€” the description slot is literally blank in the source, so that's the whole name entry, periodt πŸ™ˆ


🌸 SYNOPSIS 🌸

int sw842_decompress (const u8 *in , unsigned int ilen , u8 *out ,
       unsigned int *olen );

πŸŽ€ ARGUMENTS πŸŽ€

Okay so the manpage did not describe these at all. Every single one is officially listed as -- undescribed --, and I am not gonna invent lore. Respect the source, bestie πŸ’…

  • in β€” -- undescribed -- 😭
  • ilen β€” -- undescribed -- 😭
  • out β€” -- undescribed -- 😭
  • olen β€” -- undescribed -- 😭

πŸ’… DESCRIPTION πŸ’…

Okay so here's the actual vibe: decompress the 842-compressed buffer of length ilen at in to the output buffer out, using no more than olen bytes. That's the assignment, and it ate πŸ”₯

The compressed buffer must be only a single 842-compressed buffer, with the standard format described in the comments in 842.h. Not a little buffer pile, not a buffer stack β€” one single 842-compressed buffer. Slay πŸ’–

Processing will stop when the 842 "END" template is detected, not the end of the buffer. That distinction is giving main character energy, so don't miss it πŸ‘‘

Heads up: detection is about the 842 "END" template, not wherever the buffer happens to end. ikyk 🫢

πŸ”₯ RETURN πŸ”₯

  • 0 on success πŸŽ‰
  • error on failure πŸ’€

The olen parameter will contain the number of output bytes written on success, or 0 on error. So olen is literally carrying the receipts either way 🧾✨


πŸ¦‹ SEE ALSO πŸ¦‹

  • Kernel file ./lib/842/842_decompress.c β€” go read it, bestie, it's right there πŸ“–πŸ¦‹

source/version: ./lib/842 β€’ dated October 2026 β€” mwah πŸ’‹ this has been your Kernel API Manual moment for sw842_decompress(9), and honestly? iconic πŸŽ€βœ¨

πŸ“¦ where this page comes from