spu2_fmd_ctrl2_write(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– spu2_fmd_ctrl2_write(9) πŸ’–

okay bestie, welcome to the Kernel API Manual page for spu2_fmd_ctrl2_write(9) β€” we're setting the ctrl2 field inside the fixed metadata field of the SPU2 header, and it's giving ✨kernel crypto✨. πŸ¦‹

✨ NAME ✨

spu2_fmd_ctrl2_write β€” sets the ctrl2 field in the fixed metadata field of the SPU2 header. Literally that's the job, no cap. πŸ’…

🌸 SYNOPSIS 🌸

void spu2_fmd_ctrl2_write (struct SPU2_FMD *fmd , u64 cipher_offset ,
u64 auth_key_len , u64 auth_iv_len , u64 cipher_key_len , u64
cipher_iv_len );

πŸŽ€ ARGUMENTS πŸŽ€

  • fmd β€” start of the FMD field to be written. This is the spot you're writing into. 🫢
  • cipher_offset β€” number of bytes from Start of Packet (end of FD field) where data to be encrypted or decrypted begins. That's the starting line for the cipher data. πŸ”₯
  • auth_key_len β€” length of authentication key, in bytes.
  • auth_iv_len β€” length of authentication initialization vector, in bytes.
  • cipher_key_len β€” length of cipher key, in bytes.
  • cipher_iv_len β€” length of cipher IV, in bytes.

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file: ./drivers/crypto/bcm/spu2.c β€” and here's the whole function friend group, all invited to the group chat: πŸ’¬

🫢 that's the whole page, bestie β€” source/version: ./drivers/crypto/bcm; date: October 2026; and yes, we're still in spu2_fmd_ctrl2_write(9) land. πŸ’–

πŸ“¦ where this page comes from