Lines Matching refs:frames
31 receive raw CAN frames, directly to/from the controller hardware.
32 Queueing of frames and higher-level transport protocols like ISO-TP
45 network layer as a network device, so that CAN frames from the
54 frames on different or the same CAN IDs. Several sockets listening on
55 the same interface for frames with the same CAN ID are all passed the
56 same received matching CAN frames. An application wishing to
60 CAN-IDs, frames, etc.
93 CAN frames between them, (sophisticated) queueing of CAN frames, and
160 some kind of local loopback of the sent CAN frames on the appropriate
164 transmission and reception of media dependent frames. Due to the
191 arbitration problems and error frames caused by the different
196 same way as other CAN frames. Whenever an error on the physical layer
198 creates an appropriate error message frame. Error messages frames can
322 be 0 (zero). In this case the socket receives CAN frames from every
328 Reading CAN frames from a bound CAN_RAW socket (see above) consists
350 Writing CAN frames can be done similarly, with the write(2) system call::
373 To write CAN frames on sockets bound to 'any' CAN interface the
406 switches the socket into a mode that allows the handling of CAN FD frames
407 and Classical CAN frames simultaneously (see :ref:`socketcan-rawfd`).
458 - The socket only receives valid data frames (=> no error message frames)
459 - The loopback of sent CAN frames is enabled (see :ref:`socketcan-local-loopback2`)
460 - The socket does not receive its own sent frames (in loopback mode)
472 The reception of CAN frames using CAN_RAW sockets can be controlled
507 To disable the reception of CAN frames on the selected CAN_RAW socket:
514 data causes the raw socket to discard the received CAN frames. But
542 both SFF frames with CAN ID 0x123 and EFF frames with 0xXXXXX123 can pass.
564 application in the same way as other CAN frames. The possible
596 When the local loopback is enabled, all the sent CAN frames are
598 frames' CAN-ID on this given interface to meet the multi user
599 needs. The reception of the CAN frames on the same socket that was
611 Note that reception of a socket's own CAN frames are subject to the same
612 filtering as other CAN frames (see :ref:`socketcan-rawfilter`).
624 Once CAN_RAW_FD_FRAMES is enabled the application can send both CAN frames
625 and CAN FD frames. OTOH the application has to handle CAN and CAN FD frames
664 CANFD_MTU sized CAN FD frames.
671 socket option returns an error: No problem. You'll get Classical CAN frames
672 or CAN FD frames and can process them the same way.
675 CAN FD frames by checking if the device maximum transfer unit is CANFD_MTU.
688 frames are passed to user space that matched *all* given CAN filters. The
707 CAN driver supports the echo of frames on driver level, see
722 Periodic transmission tasks of CAN frames or a sequence of CAN frames can be
726 A BCM socket is not intended for sending individual CAN frames using the
731 message header with a command ('opcode') followed by zero or more CAN frames.
743 struct can_frame frames[0];
746 The aligned payload 'frames' uses the same basic CAN frame structure defined
857 subsequent frame in frames. This is intended as usage simplification. For
862 Filter by can_id alone, no frames required (nframes=0).
878 Send reply for RTR-request (placed in op->frames[0]).
881 The CAN frames following the bcm_msg_head are struct canfd_frame's
897 Up to 256 CAN frames can be transmitted in a sequence in the case of a cyclic
898 TX task configuration. The number of CAN frames is provided in the 'nframes'
899 element of the BCM message head. The defined number of CAN frames are added
904 /* create a struct to set up a sequence of four CAN frames */
916 With every transmission the index in the array of CAN frames is increased
941 than one CAN frames can be passed in a RX_SETUP configuration message. The
943 have to match in the subsequent CAN frames with the received CAN frame.
944 If one of the subsequent CAN frames is matching the bits in that frame data
946 Up to 257 CAN frames (multiplex filter bit mask CAN frame plus 256 CAN
977 schema for the CAN FD frames a new flag 'CAN_FD_FRAME' in the bcm_msg_head
994 When using CAN FD frames for multiplex filtering the MUX mask is still
1026 (e.g. current/maximum frames per second) this 1 second timer is
1038 lists to deliver received CAN frames to CAN protocol modules. These
1057 rcvlist_err - list for error message frames masks
1064 stats - SocketCAN core statistics (rx/tx frames, match ratios, ...)
1078 frames received by CAN interfaces and to send CAN frames::
1080 can_rx_register - subscribe CAN frames from a specific interface
1081 can_rx_unregister - unsubscribe CAN frames from a specific interface
1127 set to prevent the PF_CAN core from locally echoing sent frames
1196 frames without real CAN controller hardware. Virtual CAN network
1381 by monitoring CAN error message frames and do a restart when
1404 CAN frames anyway. The payload length to the bus-relevant DLC mapping is
1415 N.B. CAN FD capable devices can also handle and send Classical CAN frames.