cec_msg_destination(9)
πΈ NAME πΈ
okay so bestie, meet cec_msg_destination from the Kernel API Manual β yes, thatβs cec_msg_destination(9) if weβre being all official about it. Her whole thing is: return the destination's logical address. Thatβs it, thatβs the vibe. π
β¨ SYNOPSIS β¨
__u8 cec_msg_destination (const struct cec_msg *msg );
Like, the signature is right there and she is not complicated: it takes a const struct cec_msg *msg and gives you back a __u8. Slay. β¨
π ARGUMENTS π
msgβ the message structure. Thatβs the whole argument, bestie. No secret extra params, no plot twist. π«Ά
π SEE ALSO π
If youβre going down the CEC rabbit hole (iykyk), these are the friends to check out too. First up, the kernel file ./include/uapi/linux/cec.h and struct cec_msg(9). Then the whole little group chat:
cec_msg_initiator(9)cec_msg_opcode(9)cec_msg_is_broadcast(9)cec_msg_init(9)cec_msg_set_reply_to(9)cec_msg_recv_is_tx_result(9)cec_msg_recv_is_rx_result(9)struct cec_caps(9)struct cec_log_addrs(9)struct cec_drm_connector_info(9)struct cec_connector_info(9)struct cec_event_state_change(9)struct cec_event_lost_msgs(9)struct cec_event(9)
thatβs the whole page, bestie π signed off from ./include/uapi/linux, dated October 2026, and filed under cec_msg_destination(9) in the Kernel API Manual β mwah ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms