rmi_write_block(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… rmi_write_block(9) β€” from the Kernel API Manual, bestie ✨

okay so picture this: you're deep in the kernel, you've got a whole block of bytes and you need them to go somewhere. that's literally this function. it's in section 9 of the Kernel API Manual and it's lowkey iconic for how much it just… does its job 🫢


🌸 NAME 🌸

rmi_write_block β€” write a block of bytes πŸ’–


✨ SYNOPSIS ✨

int rmi_write_block (struct rmi_device *d , u16 addr , const void *buf ,
       size_t len );

like, that's the whole signature. four args. no cap. πŸ”₯


πŸŽ€ ARGUMENTS πŸŽ€

  • d β€” Pointer to an RMI device πŸ’« like, which device are we even talking to, bestie
  • addr β€” The start address to write to πŸ“ the spot where the writing begins
  • buf β€” The write buffer 🧺 your bytes live here, they're ready to travel
  • len β€” Length of the write buffer πŸ“ how many bytes we're sending out into the world

πŸ¦‹ DESCRIPTION πŸ¦‹

Writes a block of byte data from buf using the underlaying transport protocol ⭐ yeah, the underlaying one, spelling and all, that's how it's written and we respect it πŸ’œ

it returns the amount of bytes written or a negative error code 🌈 so like. check that return value, fr fr. positive-ish = good, negative = the vibe check failed 😭

ngl, if you're staring at a negative number wondering what went wrong, that's your error code talking. it's giving "read the return value" energy πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

like, go read the whole friend group, they all hang out together 🫢✨


and that's the page!! πŸ’… this little gem lives in ./drivers/input/rmi4, dated October 2026 β€” mwah, see you in the next manpage, bestie πŸ“πŸ§šπŸ’–

πŸ“¦ where this page comes from