2# Controller Area Network (CAN) network layer core configuration
   5menuconfig CAN
   6        depends on NET
   7        tristate "CAN bus subsystem support"
   8        ---help---
   9          Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial
  10          communications protocol which was developed by Bosch in
  11          1991, mainly for automotive, but now widely used in marine
  12          (NMEA2000), industrial, and medical applications.
  13          More information on the CAN network protocol family PF_CAN
  14          is contained in <Documentation/networking/can.txt>.
  16          If you want CAN support you should say Y here and also to the
  17          specific driver for your controller(s) below.
  19config CAN_RAW
  20        tristate "Raw CAN Protocol (raw access with CAN-ID filtering)"
  21        depends on CAN
  22        default N
  23        ---help---
  24          The raw CAN protocol option offers access to the CAN bus via
  25          the BSD socket API. You probably want to use the raw socket in
  26          most cases where no higher level protocol is being used. The raw
  27          socket has several filter options e.g. ID masking / error frames.
  28          To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW.
  30config CAN_BCM
  31        tristate "Broadcast Manager CAN Protocol (with content filtering)"
  32        depends on CAN
  33        default N
  34        ---help---
  35          The Broadcast Manager offers content filtering, timeout monitoring,
  36          sending of RTR frames, and cyclic CAN messages without permanent user
  37          interaction. The BCM can be 'programmed' via the BSD socket API and
  38          informs you on demand e.g. only on content updates / timeouts.
  39          You probably want to use the bcm socket in most cases where cyclic
  40          CAN messages are used on the bus (e.g. in automotive environments).
  41          To use the Broadcast Manager, use AF_CAN with protocol CAN_BCM.
  43config CAN_GW
  44        tristate "CAN Gateway/Router (with netlink configuration)"
  45        depends on CAN
  46        default N
  47        ---help---
  48          The CAN Gateway/Router is used to route (and modify) CAN frames.
  49          It is based on the PF_CAN core infrastructure for msg filtering and
  50          msg sending and can optionally modify routed CAN frames on the fly.
  51          CAN frames can be routed between CAN network interfaces (one hop).
  52          They can be modified with AND/OR/XOR/SET operations as configured
  53          by the netlink configuration interface known e.g. from iptables.
  55source "drivers/net/can/Kconfig"
  56 kindly hosted by Redpill Linpro AS, provider of Linux consulting and operations services since 1995.