Home
last modified time | relevance | path

Searched refs:CAN_RAW (Results 1 – 7 of 7) sorted by relevance

/linux/include/uapi/linux/can/
H A Draw.h51 #define SOL_CAN_RAW (SOL_CAN_BASE + CAN_RAW)
/linux/net/can/
H A DKconfig24 config CAN_RAW config
32 To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW.
H A Draw.c1093 .name = "CAN_RAW",
1101 .protocol = CAN_RAW,
/linux/include/uapi/linux/
H A Dcan.h230 #define CAN_RAW 1 /* RAW sockets */ macro
/linux/Documentation/networking/
H A Dcan.rst216 s = socket(PF_CAN, SOCK_RAW, CAN_RAW);
225 - see :ref:`socketcan-concept`). After binding (CAN_RAW) or connecting (CAN_BCM)
264 default. A read(2) system call on a CAN_RAW socket transfers a
301 be used (example for CAN_RAW sockets without error checking):
309 s = socket(PF_CAN, SOCK_RAW, CAN_RAW);
328 Reading CAN frames from a bound CAN_RAW socket (see above) consists
404 bytes of payload (struct can_frame) like the CAN_RAW socket. Therefore e.g.
405 the CAN_RAW socket supports a new socket option CAN_RAW_FD_FRAMES that
470 Using CAN_RAW sockets is extensively comparable to the commonly
481 To use the referenced definitions of the socket options for CAN_RAW
[all …]
H A Diso15765-2.rst98 Unlike the CAN_RAW socket API, only the ISO-TP data field (the actual payload)
/linux/tools/testing/selftests/net/can/
H A Dtest_raw_filter.c69 s = socket(PF_CAN, SOCK_RAW, CAN_RAW); in FIXTURE_SETUP()