Lines Matching full:can

3 # Controller Area Network (CAN) network layer core configuration
6 menuconfig CAN  config
7 	tristate "CAN bus subsystem support"
9 	  Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial
10 	  communications protocol. Development of the CAN bus started in
12 	  released in 1986. The CAN bus was originally mainly for automotive,
14 	  applications. More information on the CAN network protocol family
15 	  PF_CAN is contained in <Documentation/networking/can.rst>.
17 	  If you want CAN support you should say Y here and also to the
21 if CAN
24 	tristate "Raw CAN Protocol (raw access with CAN-ID filtering)"
27 	  The raw CAN protocol option offers access to the CAN bus via
31 	  To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW.
34 	tristate "Broadcast Manager CAN Protocol (with content filtering)"
38 	  sending of RTR frames, and cyclic CAN messages without permanent user
39 	  interaction. The BCM can be 'programmed' via the BSD socket API and
42 	  CAN messages are used on the bus (e.g. in automotive environments).
46 	tristate "CAN Gateway/Router (with netlink configuration)"
49 	  The CAN Gateway/Router is used to route (and modify) CAN frames.
51 	  msg sending and can optionally modify routed CAN frames on the fly.
52 	  CAN frames can be routed between CAN network interfaces (one hop).
53 	  They can be modified with AND/OR/XOR/SET operations as configured
56 source "net/can/j1939/Kconfig"
59 	tristate "ISO 15765-2:2016 CAN transport protocol"
61 	  CAN Transport Protocols offer support for segmented Point-to-Point
62 	  communication between CAN nodes via two defined CAN Identifiers.
63 	  As CAN frames can only transport a small amount of data bytes
64 	  (max. 8 bytes for 'classic' CAN and max. 64 bytes for CAN FD) this
66 	  as needed e.g. for vehicle diagnosis (UDS, ISO 14229) or IP-over-CAN
69 	  ISO 15765-2:2016 for 'classic' CAN and CAN FD frame types.