nfp_cpp_write(9)

📦 version 7.3.1, in nixpkgs unstable

💖 nfp_cpp_write(9) 💖

okay so this is the <rainbow>nfp_cpp_write</rainbow> page from the Kernel API Manual — yes it's a section 9 one, we're in kernel-land bestie, put your seatbelt on 🎀

✨ NAME ✨

nfp_cpp_write — write to CPP target 🖊️✨

🌸 SYNOPSIS 🌸

int nfp_cpp_write (struct nfp_cpp *cpp , u32 destination , unsigned long
long address , const void *kernel_vaddr , size_t length );

yeah the line wrap is doing its own thing, she's just built like that, copy her exactly as she is 💅

🦋 ARGUMENTS 🦋

  • cpp — the CPP handle, your little main-character passport for this whole operation 🫶
  • destination — the CPP id, like the address label on the envelope fr fr
  • address — offset into the CPP target, i.e. where inside the destination we're poking 💫
  • kernel_vaddr — kernel buffer to read from, this is the stuff getting written out 👑
  • length — number of bytes to write, count them, don't skip, no cap 🔥

⭐ RETURN ⭐

length of io, or -ERRNO 😭 — so if you get a negative number back, that's not a vibe, that's an error code, go read it.

💜 SEE ALSO 💜

first up, the source of truth, the kernel file itself:

Kernel file ./drivers/net/ethernet/netronome/nfp/nfpcore/nfp_cppcore.c

and then the whole girlies, the full friend group, in order, every single one, no gatekeeping 🙈:

like… she has a LOT of friends, and honestly? obsessed. iykyk 💅✨

mwah, that's the page 🎀 this one came from ./drivers/net/ethernet/netrono... and she's dated October 2026, signed off as nfp_cpp_write(9) — go write some bytes bestie, slay 💜🦋

📦 where this page comes from