Lines Matching refs:can_frame

236     struct can_frame {
249 struct can_frame to the user space.
296 of reading a struct can_frame:
300     struct can_frame frame;
302     nbytes = read(s, &frame, sizeof(struct can_frame));
310     if (nbytes < sizeof(struct can_frame)) {
319     nbytes = write(s, &frame, sizeof(struct can_frame));
330     struct can_frame frame;
332     nbytes = recvfrom(s, &frame, sizeof(struct can_frame),
350     nbytes = sendto(s, &frame, sizeof(struct can_frame),
371 bytes of payload (struct can_frame) like the CAN_RAW socket. Therefore e.g.
389 The struct canfd_frame and the existing struct can_frame have the can_id,
392 When the content of a struct can_frame is copied into a struct canfd_frame
396 code (DLC) of the struct can_frame was used as a length information as the
400 can_frame.can_dlc are equal and contain a length information and no DLC.
410   #define CAN_MTU   (sizeof(struct can_frame))   == 16  => 'legacy' CAN frame
628 not specified in the struct can_frame and therefore it is only valid in
692 struct can_frame as known from the CAN_RAW socket. Instead a special BCM
708             struct can_frame frames[0];
824 	can_id(s) stored for transmission in the subsequent struct can_frame(s).
870             struct can_frame frame[4];
919             struct can_frame frame[5];
938 The programming API of the CAN_BCM depends on struct can_frame which is
1073     dev->mtu = CAN_MTU; /* sizeof(struct can_frame) -> legacy CAN interface */
1078 The struct can_frame or struct canfd_frame is the payload of each socket
1329 payload. The representation of this length in can_frame.can_dlc and
1340   MTU = 16 (CAN_MTU)   => sizeof(struct can_frame)   => 'legacy' CAN device