STRUCT RPMSG_ENDPOINT_INFO(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ struct rpmsg_endpoint_info(9) ✨

okay so bestie, welcome to the Kernel API Manual entry for struct rpmsg_endpoint_info β€” it's literally the glow-up little struct that holds your endpoint info, and honestly? iconic. πŸ’…


πŸŽ€ NAME πŸŽ€

struct rpmsg_endpoint_info β€” it's giving endpoint info representation, no cap. That's the whole vibe check: this struct is a representation of endpoint info. periodt. ✨


🌸 SYNOPSIS 🌸

struct rpmsg_endpoint_info {
    char name[32];
    __u32 src;
    __u32 dst;
 };

like… three fields. that's it. small but mighty, she's got main character energy fr fr. πŸ¦‹


πŸ’– Members πŸ’–

  • name β€” the name of service. that's it, that's the field. 32 whole chars of char to work with, so pick something cute but not too cute. πŸŽ€
  • src β€” your local address. and listen: if you're not even using it, you set it to RPMSG_ADDR_ANY. don't leave it doing nothing, okay? πŸ™ˆ
  • dst β€” the destination address. same energy here: if it's not used, set it to RPMSG_ADDR_ANY. them's the rules, bestie. 😭
lowkey important: both src and dst get RPMSG_ADDR_ANY when they're not in use β€” that's literally the documented move, don't come up with your own thing. 🫢

πŸ‘‘ SEE ALSO πŸ‘‘

  • Kernel file ./include/uapi/linux/rpmsg.h β€” go read the source, iykyk. πŸ”₯

and that's the whole page, bestie!! 🌈 this lil beauty lives in ./include/uapi/linux, it's dated October 2026, and it's filed under struct rpmsg_endpoint_info(9) β€” so next time someone asks, you already know. slay, ate, no crumbs. πŸ’œβ­πŸ“

πŸ“¦ where this page comes from