Lines Matching +full:on +full:- +full:the +full:- +full:fly

1 # SPDX-License-Identifier: GPL-2.0-only
10 	  communications protocol. Development of the CAN bus started in
11 	  1983 at Robert Bosch GmbH, and the protocol was officially
12 	  released in 1986. The CAN bus was originally mainly for automotive,
14 	  applications. More information on the CAN network protocol family
17 	  If you want CAN support you should say Y here and also to the
18 	  specific driver for your controller(s) under the Network device
24 	tristate "Raw CAN Protocol (raw access with CAN-ID filtering)"
27 	  The raw CAN protocol option offers access to the CAN bus via
28 	  the BSD socket API. You probably want to use the raw socket in
29 	  most cases where no higher level protocol is being used. The raw
37 	  The Broadcast Manager offers content filtering, timeout monitoring,
39 	  interaction. The BCM can be 'programmed' via the BSD socket API and
40 	  informs you on demand e.g. only on content updates / timeouts.
41 	  You probably want to use the bcm socket in most cases where cyclic
42 	  CAN messages are used on the bus (e.g. in automotive environments).
43 	  To use the Broadcast Manager, use AF_CAN with protocol CAN_BCM.
49 	  The CAN Gateway/Router is used to route (and modify) CAN frames.
50 	  It is based on the PF_CAN core infrastructure for msg filtering and
51 	  msg sending and can optionally modify routed CAN frames on the fly.
54 	  by the netlink configuration interface known e.g. from iptables.
59 	tristate "ISO 15765-2 CAN transport protocol"
61 	  CAN Transport Protocols offer support for segmented Point-to-Point
65 	  introduced with ISO 15765-2:2016.
69 	  as needed e.g. for vehicle diagnosis (UDS, ISO 14229) or IP-over-CAN