Lines Matching refs:frames
15 3.2 local loopback of sent frames
44 6.2 local loopback of sent frames
83 receive raw CAN frames, directly to/from the controller hardware.
84 Queueing of frames and higher-level transport protocols like ISO-TP
97 network layer as a network device, so that CAN frames from the
106 frames on different or the same CAN IDs. Several sockets listening on
107 the same interface for frames with the same CAN ID are all passed the
108 same received matching CAN frames. An application wishing to
112 CAN-IDs, frames, etc.
145 CAN frames between them, (sophisticated) queueing of CAN frames, and
184 3.2 local loopback of sent frames
199 some kind of local loopback of the sent CAN frames on the appropriate
203 transmission and reception of media dependent frames. Due to the
226 arbitration problems and error frames caused by the different
231 same way as other CAN frames. Whenever an error on the physical layer
233 creates an appropriate error message frame. Error messages frames can
317 be 0 (zero). In this case the socket receives CAN frames from every
323 Reading CAN frames from a bound CAN_RAW socket (see above) consists
343 Writing CAN frames can be done similarly, with the write(2) system call:
364 To write CAN frames on sockets bound to 'any' CAN interface the
384 switches the socket into a mode that allows the handling of CAN FD frames
385 and (legacy) CAN frames simultaneously (see section 4.1.5).
428 - The socket only receives valid data frames (=> no error message frames)
429 - The loopback of sent CAN frames is enabled (see chapter 3.2)
430 - The socket does not receive its own sent frames (in loopback mode)
438 The reception of CAN frames using CAN_RAW sockets can be controlled
467 To disable the reception of CAN frames on the selected CAN_RAW socket:
472 data causes the raw socket to discard the received CAN frames. But
497 both SFF frames with CAN ID 0x123 and EFF frames with 0xXXXXX123 can pass.
515 application in the same way as other CAN frames. The possible
539 When the local loopback is enabled, all the sent CAN frames are
541 frames' CAN-ID on this given interface to meet the multi user
542 needs. The reception of the CAN frames on the same socket that was
559 Once CAN_RAW_FD_FRAMES is enabled the application can send both CAN frames
560 and CAN FD frames. OTOH the application has to handle CAN and CAN FD frames
594 CANFD_MTU sized CAN FD frames.
601 socket option returns an error: No problem. You'll get legacy CAN frames
602 or CAN FD frames and can process them the same way.
605 CAN FD frames by checking if the device maximum transfer unit is CANFD_MTU.
616 frames are passed to user space that matched *all* given CAN filters. The
631 CAN driver supports the echo of frames on driver level, see 3.2 and 6.2.
643 Periodic transmission tasks of CAN frames or a sequence of CAN frames can be
647 A BCM socket is not intended for sending individual CAN frames using the
652 message header with a command ('opcode') followed by zero or more CAN frames.
662 struct can_frame frames[0];
665 The aligned payload 'frames' uses the same basic CAN frame structure defined
753 subsequent frame in frames. This is intended as usage simplification. For
757 RX_FILTER_ID: Filter by can_id alone, no frames required (nframes=0).
768 RX_RTR_FRAME: Send reply for RTR-request (placed in op->frames[0]).
781 Up to 256 CAN frames can be transmitted in a sequence in the case of a cyclic
782 TX task configuration. The number of CAN frames is provided in the 'nframes'
783 element of the BCM message head. The defined number of CAN frames are added
786 /* create a struct to set up a sequence of four CAN frames */
798 With every transmission the index in the array of CAN frames is increased
818 than one CAN frames can be passed in a RX_SETUP configuration message. The
820 have to match in the subsequent CAN frames with the received CAN frame.
821 If one of the subsequent CAN frames is matching the bits in that frame data
823 Up to 257 CAN frames (multiplex filter bit mask CAN frame plus 256 CAN
861 (e.g. current/maximum frames per second) this 1 second timer is
870 lists to deliver received CAN frames to CAN protocol modules. These
889 rcvlist_err - list for error message frames masks
896 stats - SocketCAN core statistics (rx/tx frames, match ratios, ...)
908 frames received by CAN interfaces and to send CAN frames:
910 can_rx_register - subscribe CAN frames from a specific interface
911 can_rx_unregister - unsubscribe CAN frames from a specific interface
943 6.2 local loopback of sent frames
948 set to prevent the PF_CAN core from locally echoing sent frames
980 frames without real CAN controller hardware. Virtual CAN network
1158 by monitoring CAN error message frames and do a restart when
1177 CAN frames anyway. The payload length to the bus-relevant DLC mapping is
1188 N.B. CAN FD capable devices can also handle and send legacy CAN frames.