2 # CAN device configuration
7 tristate "CAN bus subsystem support"
9 Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial
10 communications protocol was developed by Bosch at 1991 mainly for
11 automotive, but now widely used in marine (NMEA2000), industrial and
13 More information is contained in the directory <file:Documentation/can/>.
15 If you want CAN support, you should say Y here and also to the
16 specific driver for your controller(s) below.
18 This CAN support can also be built as a module. If so, the module
19 will be called can.ko.
22 tristate "Raw CAN Protocol"
26 The Raw CAN protocol option offers access to the CAN bus via
27 the BSD socket API. You probably want to use the raw socket in
28 most cases where no higher level protocol is being used. The raw
29 socket has several filter options e.g. ID-Masking / Errorframes.
30 To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW.
33 tristate "Broadcast Manager (BCM)"
37 The Broadcast Manager offers content filtering, timeout monitoring,
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
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.
46 bool "CAN Core debugging messages"
49 Say Y here if you want the CAN core to produce a bunch of debug
50 messages to the system log. Select this if you are having a
51 problem with CAN support and want to see more of what is going on.
54 source "drivers/net/can/Kconfig"