Lines Matching refs:can_frame

268     struct can_frame {
278   struct can_frame to the user space.
321   of reading a struct can_frame:
323     struct can_frame frame;
325     nbytes = read(s, &frame, sizeof(struct can_frame));
333     if (nbytes < sizeof(struct can_frame)) {
342     nbytes = write(s, &frame, sizeof(struct can_frame));
351     struct can_frame frame;
353     nbytes = recvfrom(s, &frame, sizeof(struct can_frame),
369     nbytes = sendto(s, &frame, sizeof(struct can_frame),
379   bytes of payload (struct can_frame) like the CAN_RAW socket. Therefore e.g.
395   The struct canfd_frame and the existing struct can_frame have the can_id,
398   When the content of a struct can_frame is copied into a struct canfd_frame
402   code (DLC) of the struct can_frame was used as a length information as the
406   can_frame.can_dlc are equal and contain a length information and no DLC.
414   #define CAN_MTU   (sizeof(struct can_frame))   == 16  => 'legacy' CAN frame
590   not specified in the struct can_frame and therefore it is only valid in
645   struct can_frame as known from the CAN_RAW socket. Instead a special BCM
659             struct can_frame frames[0];
752       can_id(s) stored for transmission in the subsequent struct can_frame(s).
786             struct can_frame frame[4];
828             struct can_frame frame[5];
932     dev->mtu = CAN_MTU; /* sizeof(struct can_frame) -> legacy CAN interface */
937   The struct can_frame or struct canfd_frame is the payload of each socket
1161   payload. The representation of this length in can_frame.can_dlc and
1172   MTU = 16 (CAN_MTU)   => sizeof(struct can_frame)   => 'legacy' CAN device