Lines Matching refs:can_frame
236 struct can_frame {
265 struct can_frame to the user space.
329 of reading a struct can_frame:
333 struct can_frame frame;
335 nbytes = read(s, &frame, sizeof(struct can_frame));
343 if (nbytes < sizeof(struct can_frame)) {
352 nbytes = write(s, &frame, sizeof(struct can_frame));
363 struct can_frame frame;
365 nbytes = recvfrom(s, &frame, sizeof(struct can_frame),
383 nbytes = sendto(s, &frame, sizeof(struct can_frame),
404 bytes of payload (struct can_frame) like the CAN_RAW socket. Therefore e.g.
422 The struct canfd_frame and the existing struct can_frame have the can_id,
425 When the content of a struct can_frame is copied into a struct canfd_frame
429 code (DLC) of the struct can_frame was used as a length information as the
433 can_frame.len are equal and contain a length information and no DLC.
443 #define CAN_MTU (sizeof(struct can_frame)) == 16 => Classical CAN frame
663 not specified in the struct can_frame and therefore it is only valid in
727 struct can_frame as known from the CAN_RAW socket. Instead a special BCM
743 struct can_frame frames[0];
859 can_id(s) stored for transmission in the subsequent struct can_frame(s).
907 struct can_frame frame[4];
956 struct can_frame frame[5];
975 The programming API of the CAN_BCM depends on struct can_frame which is
1110 dev->mtu = CAN_MTU; /* sizeof(struct can_frame) -> Classical CAN interface */
1115 The struct can_frame or struct canfd_frame is the payload of each socket
1400 payload. The representation of this length in can_frame.len and
1411 MTU = 16 (CAN_MTU) => sizeof(struct can_frame) => Classical CAN device