Documentation/networking/can.rst

47 protocol family module and also vice-versa.  Also, the protocol family
48 module provides an API for transport protocol modules to register, so
50 dynamically.  In fact, the can core module alone does not provide any
52 protocol module.  Multiple sockets can be opened at the same time,
53 on different or the same protocol module and they can listen/send
127 module - which implements the protocol family CAN - provides several
129 application opens a CAN RAW socket, the raw protocol module itself
134 CAN protocol modules by the SocketCAN core (see :ref:`socketcan-core-module`).
368     /* get interface name of the received CAN frame */
671 socket option returns an error: No problem. You'll get Classical CAN frames
878 	Send reply for RTR-request (placed in op->frames[0]).
934 	CAN frame is stateless as state changes within the ival2 period may get
1010 .. _socketcan-core-module:
1015 The SocketCAN core module implements the protocol family
1016 PF_CAN. CAN protocol modules are loaded by the core module at
1017 runtime. The core module provides an interface for CAN protocol
1027   invoked at can.ko module start time by default. This timer can be
1028   disabled by using stattimer=0 on the module commandline.
1041 device and a protocol module identifier::
1198 When compiled as a module the virtual CAN driver module is called vcan.ko
1225 understand how to use them. The name of the module is can-dev.ko.
1228 Netlink interface to set/get devices properties
1472 Please check the "Kconfig" file in "drivers/net/can" to get an actual