Lines Matching refs:CAN_RAW

216     s = socket(PF_CAN, SOCK_RAW, CAN_RAW);
225 - see :ref:`socketcan-concept`). After binding (CAN_RAW) or connecting (CAN_BCM)
248 default. A read(2) system call on a CAN_RAW socket transfers a
268 be used (example for CAN_RAW sockets without error checking):
276     s = socket(PF_CAN, SOCK_RAW, CAN_RAW);
295 Reading CAN frames from a bound CAN_RAW socket (see above) consists
371 bytes of payload (struct can_frame) like the CAN_RAW socket. Therefore e.g.
372 the CAN_RAW socket supports a new socket option CAN_RAW_FD_FRAMES that
419 Using CAN_RAW sockets is extensively comparable to the commonly
430 To use the referenced definitions of the socket options for CAN_RAW
439 The reception of CAN frames using CAN_RAW sockets can be controlled
474 To disable the reception of CAN frames on the selected CAN_RAW socket:
584 CAN FD support in CAN_RAW sockets can be enabled with a new socket option
586 not supported by the CAN_RAW socket (e.g. on older kernels), switching the
634 data structure for CAN_RAW based applications. When the application is
647 The CAN_RAW socket can set multiple CAN identifier specific filters that
692 struct can_frame as known from the CAN_RAW socket. Instead a special BCM