es58x_rx_can_msg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ es58x_rx_can_msg(9) πŸ¦‹

okay so bestie, this is the es58x_rx_can_msg(9) page from the Kernel API Manual, and it is literally about handling a received a CAN message. yes, β€œa received a” is staying, we respect the lore πŸ’…βœ¨

✨ NAME ✨

es58x_rx_can_msg β€” Handle a received a CAN message. πŸŽ€

🌸 SYNOPSIS 🌸

int es58x_rx_can_msg (struct net_device *netdev , u64 timestamp , const
       u8 *data , canid_t can_id , enum es58x_flag es58x_flags , u8 dlc );

🫢 ARGUMENTS 🫢

  • netdev β€” CAN network device. πŸ’–
  • timestamp β€” Hardware time stamp (only relevant in rx branches). ⏰
  • data β€” CAN payload. 🧚
  • can_id β€” CAN ID. πŸͺͺ
  • es58x_flags β€” Please refer to enum es58x_flag. 🌈
  • dlc β€” Data Length Code (raw value). πŸ”’

πŸ’œ DESCRIPTION πŸ’œ

Fill up a CAN skb and post it. πŸ’Œ

This function handles the case where the DLC of a classical CAN frame is greater than CAN_MAX_DLEN (c.f. the len8_dlc field of struct can_frame). no cap, that is the whole vibe check πŸ¦‹

⭐ RETURN ⭐

It returns zero on success. periodt. ✨

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file: ./drivers/net/can/usb/etas_es58x/es58x_core.c πŸ“


made with πŸ’– from the Kernel API Manual source/version line: source path ./drivers/net/can/usb/etas_es58x and date October 2026. byeee bestie, go handle those CAN messages 🫢✨

πŸ“¦ where this page comes from